DPI Settings in an RDP/ICA Session on Windows Server 2008 R2 andWindows 7

In quite a few XenApp 6/6.5 Projects the Customer complained that the Users were not able to change the DPI Size when connected to a XenDesktop running Windows 7 or a XenApp Desktop hosted on Windows Server 2008 R2. This was due to a limitation in the Remote Desktop Services Stack from Microsoft.

There were some Workarounds with importing/injecting Values into the Registry for those Users to change the DPI Size but they were far from perfect.

Microsoft just recently released an Hotfix to enable the Adjustment of the DPI Size over Remote Desktop Protocol Sessions like RDP and ICA. You can find and download the Hotfix here:

http://support.microsoft.com/kb/2726399/en-us

And this is how the new DPI Menu looks (on a German Windows Server 2008 R2):

Why you shouldn't enable RDP via GPO on XenApp/RDS Hosts

I recently had to troubleshoot a Problem where the Customer told me that sometimes all the Sessions on a XenApp 6 Host got disconnected and the Users then had to reconnect to their XenApp Sessions to continue working.

After a little Research (more like googeling) I narrowed it down to the the Group Policy Refresh. Not always, but sometimes, when doing an "gpupdate /force" all User Sessions on the XenApp Host got disconnected. With this in mind I found the following Microsoft Knowledgebase Article: http://support.microsoft.com/kb/2083411

The customer in fact used the Group Policy Option "Allow users to connect remotely using Terminal Services" to enable Remote Desktop and force a specific Remote Desktop Security Setting on all of his XenApp Servers.

After setting the Registry Key "fDenyTSConnection" to 0 (as suggested in the Microsoft KB Article) the sudden disconnects were gone.

Problem solved! :)

Citrix XenApp 6/6.5 and the Error: Event 602, PrintService

I recently had a customer where on all XenApp 6 Workers an Error with the EventID 602 from the Source PrintService was logged in the EventViewer during the User Logon Process. This only seemed to happen when using Session-based Printers in the XenApp Session.

After a bit of Research I found a Microsoft KnowledgeBase Article with an Hotfix which fixed the Problem: http://support.microsoft.com/kb/2457866

Note: This Hotfix is NOT included in the Windows Server 2008 R2 Service Pack 1. I have only tested this on XenApp 6, but this should also apply to XenApp 6.5 Systems.