1

I am in the process of trying to automate our termination process. When a user is terminated by HR, we have to go into Director and manually log them out of their Citrix session. I was hoping to find a way to automate that by creating a PowerShell script to run in order to log a user out.

Does anyone know how I can make this happen?

3 Spice ups
2

Have a look here .

I suppose you need some stuff installed, either a snap-on or a module for the citric cmdlets.

1 Spice up
3

Powershell Is not solution for everything, whats the problem is doing it manually how many users are terminated in a day? how the server is supposed to know the user is terminated?

You can create Ctrix farm policy to logout disconnected / idle sessions or GPO to logout idle/disconnected sessions, and more importantly what have you tried yet can you post your script here, in code format </>

4

Hi, at the moment I do not have any code. I was hoping someone can direct me to a place that I can view examples to get an idea of what I need to do. Sometimes we get 10 terms in a day and I have to individually go to Director and select each user one by one to see if they are still in session or if I need to disconnect them. I am trying to find a way to automate that process and if Powershell can help me then all the better.

5

I am still looking for assistance with this. Can anyone help with this?

6

An example of how many terms, today we had over terminations and I had to go and manually check to make sure they are log out of Director. I was hoping to incorporate it with my termination script so that when HR fill out the Sharepoint termination form then it will trigger the script.

7

You would need the Xendesktop powersehll sdk / cmdlet installed on your machine. The script would look something like this

asnp Citrix*

$sessions = get-brokerdesktop * -MaxRecordCount 100000 -adminaddress <name of one of your DDC’s> |?{$_.SessionUserName -eq “Domain$USER”} | Stop-BrokerSession

For XenApp it would be different depending on what version you are using, 6.x or 7.x has different cmdlets that handle this