Citrix XenApp and Terminal Server Tuning Tips Group Policy v1.0

Today, I finished up the testing phase of the new ADMX file for tuning of Citrix XenApp and Terminal Server.

In a recent project I am involved in with a big customer we needed to make a new set of GPOs for the Citrix XenApp 5.0 running on Windows Server 2008.
There is a lot of tuning in this GPO, I will update it when new tunings are found and post updates to the download section of ervik.as.

I've made the GPO in the new admx and adml format so that it can work 100% with Windows Server 2008. Also since the admx file format is in XML it's also quicker to load than regular adm files.

Citrix XenApp and Microsoft Terminal Server Tuning GPO. This GPO is in admx file format. Extract the zip file down to the c:\windows\PolicyDefinitions catalog

I also recommend that you install UPHClean if you are using Windows 2000 Server or Windows 2003 Server, to manage profiles at logoff and ensure no lock will remain leading to profile corruption and longer logoff times.

UPHClean is natively embedded into Windows Server 2008 (User Profile Service), so that is why you won't find it available for download anywhere.

Also, another Best Practice, I recommend that you Disable Data Execution Prevention on Windows 2003 Server and Windows Server 2008.

Here is how you can do that:

Warning! you have to modify the boot.ini file or use one of the following command line(s)

• For Windows 2003 : bootcfg.exe /raw /fastdetect /noexecute=AlwaysOff /ID 1

• For Windows 2008 : bcdedit.exe /set {current} nx AlwaysOff

Please note that this GPO is made for 32-bit systems. If you are planning on using this for a x64 bit OS, please adjust the GPO with WOW6432Node if hive is in HKLM\Software , when that is said, it works on x64 as well, but there are some Office 2007 tunings here which needs to be adjusted.

If you can't se the Download Image above click here to DOWNLOAD

If you got any good XenApp or Terminal Server tuning tips that you want to include in the GPO, please post them in the comments field below, thanks!

• < Prev
• Next >