This is going to be a quick post to explain how you can extract all the AD groups that are currently being used for the various applications that you serve in XenApp/XenDesktop 7.x farms. This came very handy when I had a large number of applications that need to be migrated to a new XenApp 7.15 LTSR farm. This will also come very handy for documentation purposes.
First up, you will need to find the Delivery Group Name UUID that you need to extract the details from. If you have multiple delivery groups, you will need to find the UUIDs for all the Delivery groups.
To find the UUID, run the command below in a PowerShell window in admin mode
This returns the details of all the Delivery groups in the XenApp farm.
Take a note of the UUID value
Now run the below to show the application names and the assigned user AD groups
Get-BrokerApplication -AssociatedDesktopGroupUUID 918bd477-6848-4d27-b98d-28296e78d6a1 | select ApplicationName,AssociatedUserFullNames
You can get all sorts of results by changing the filters. To know the available filters, please refer here
Or simply run the below which shows the various filters that you can use for a given application
That’s it for now. I hope this helps someone with their PowerShell journey in Citrix
My colleague came across this error message while working with a customer where he had to prevent Citrix Desktops from being shown to users if they are in a particular AD group. He didn’t recall what he did wrong but he ended up with Desktops doubling up for a standard user who isn’t a member of exclusion group.
Inspecting the delivery group, he noticed Desktops per user settings under User Settings has a different value “Incompatible Settings on SDK”
Querying the Delivery group
Going through the results, there is an additional desktop without any filtering applied. The fix is to remove the additional desktop. In his case, it was named was “Desktop_2”
Remove-BrokerEntitlementPolicyRule -Name "Desktop_2"
Running the get command shows the below results.. the second desktop is gone!!!
Hopefully this helps someone.
As most of you are aware by now, Qfarm command doesn’t run anymore in XenApp 7.x as it is a part of old IMA architecture.
With FMA, there are several ways to check the Server load, the easiest being using Citrix Studio and checking Load Index.
However, there is another method to check the load from using a PowerShell window and it is as below.
Get-BrokerMachine –Filter ‘SessionSupport –eq “MultiSession”’ –Property @(‘DNSName’,’LoadIndex’)
if you need more details, you could add more parameters in your command line as below
Get-BrokerMachine –Filter ‘SessionSupport –eq “MultiSession”’ –Property @(‘DNSName’,'WindowsConnectionSetting','SessionCount',’LoadIndex’)
The result from running the above command is as follows
Hope it’s useful for someone out there!!!
There are many a times when you would want to prevent XenDesktop/XenApp 7.x power management from powering off virtual machines in the catalog. If you ever wondered how to do it, here are the steps
Open the PowerShell in administrative mode on the Controller server
Set-BrokerDesktopGroup "Delivery group Name" -AutomaticPowerOnForAssignedDuringPeak $True
if the above doesnt fix it, then run the below command as well which will ensure that all the VMs are ready for connections all the time
Set-BrokerDesktopGroup "<Delivery group Name>" -PeakBufferSizePercent 100 -OffPeakBufferSizePercent -100