Ever wondered how to list all the published applications on individual Citrix servers. Below is a script that queries all the applications and lists them according to the delivery group and Servers they are published on. Just copy the below code and save as a Powershell file. I ran the below script in a XenApp 7.16 farm and it worked like a charm. This would work on other XenApp/CVAD 7.x versions too.
The result will look like the following. The below is a sample of just a single application. The script lists all the applications published in the farm. So there you go!
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
asnp Citrix*
Get-BrokerDesktopGroup
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
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
Get-BrokerEntitlementPolicyRule
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”
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
asnp citrix*
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