Posted on September 2nd, 2010
Sometimes the Delivery Services Console takes a long time to launch. This is due to a .NET delay in the authenticode signature component as described in Microsoft Article Q936707.
The following config file can be added to speed up the lauch of the Delivery Services Console.
Ensure the contents of the file contain the following:
<?xml version=”1.0″ encoding=”utf-8″?>
<generatePublisherEvidence enabled=”false” />
Copy this file to the following locations:
- 32-bit server – c:\windows\system32
- 64-bit server – c:\windows\sysWOW64
Posted on August 24th, 2010
During the initial instalation of XenDesktop, an Active Directory Controllers group is created and populated with the DDC servers in the farm. This group is named ‘controllers’.
For any subsequent installation of XenDesktop a new controllers group is added for each XenDesktop installation with a different name based on controllers – such as ‘ControlA0D3′
If there will be multiple XenDesktop instances in the same Active Directory it may be best to use a controllers group that reflects the business unit, project name or farm name to destinquish it from the others.
The process to do this is detailed in the following Citrix Article: CTX120451
However, the following points are worth noting when following this article.
- Create a new group in the same OU as the original ‘controllers’ group called: <farm_name>_Controllers
- Add the DDC controller objects to this group
- Enable advanced features in the ‘Active Directory Users and Computers’ tool (View | advanced features)
- Right click the new group | properties | Attribute Editor
- Locate the objectGUID entry
NOTE: you need the GUID as displayed here. If you open the entry by double clicking to copy/paste the value this mirrors some sections of the GUID as detailed in the Citrix article mentioned above.
- When entering the GUID into the registry key it needs to be in the format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
- Restart all DDC servers
- Run the AD Configuration wizard again from one DDC and it will now use the GUID entered in the regkey as the controllers group rather than the default. It appears to also update the SCP information with the details of the new group.
This registry key does not need to be applied to the virtual desktops as they get information about the controllers groups from the AD SCP configuration, which has just been updated from the AD config wizard.
Restarting the virtual desktops (VDA agents) now gives a sucessful registration with the farm.
Note: don’t forget to also update the settings for ‘Access this device over the network’ to include the new controllers group if this applies in your configuration.