Slowness to Logon on citrix/terminal services environment

SYMPTOM
=======

On Windows Server 2003 the logon process is extremely slowness. The process to logon is around 15-20minutes.
After logging there isn't any issue with application or performance. Just during the process.

ENVIRONMENT
===========
Windows Server 2003 ENT SP2 (x64) – 16 GB RAM
Applications: Citrix Metaframe 4.5

SOLUTION
========

1. The First action to solve the issue is getting the "userenv.log". If it log "userenv.log" is not enabled please use the article http://support.microsoft.com/kb/221833 to do that. "How to enable user environment debug logging in retail builds of Windows"


2. For this case we could find some tips and information really important.
3. GPO starts at 13:00:04
4. And finished at 13:27:20 and then still loading others policies. If you enable Userenv logging on the problem server, it shows a delay related to Resultant Set of Policy (RSoP). Check the logs below:
------------------
USERENV(615c.4c80) 13:00:04:767 AllocAdmFileInfo: Adding File name <\\XYZ.domain.com\SysVol\XYZ.domain.com\Policies\{982E46A9-9CDE-45D9-B52B-E75BF7B682E8}\Adm\conf.adm> to the Adm list.
USERENV(615c.4c80) 13:00:04:767 AllocAdmFileInfo: Adding File name <\\XYZ.domain.com\SysVol\XYZ.domain.com\Policies\{982E46A9-9CDE-45D9-B52B-E75BF7B682E8}\Adm\inetres.adm> to the Adm list.
USERENV(615c.4c80) 13:00:04:767 AllocAdmFileInfo: Adding File name <\\XYZ.domain.com\SysVol\XYZ.domain.com\Policies\{982E46A9-9CDE-45D9-B52B-E75BF7B682E8}\Adm\system.adm> to the Adm list.
USERENV(615c.4c80) 13:00:04:767 AllocAdmFileInfo: Adding File name <\\XYZ.domain.com\SysVol\XYZ.domain.com\Policies\{982E46A9-9CDE-45D9-B52B-E75BF7B682E8}\Adm\wmplayer.adm> to the Adm list.
USERENV(615c.4c80) 13:00:04:767 AllocAdmFileInfo: Adding File name <\\XYZ.domain.com\SysVol\XYZ.domain.com\Policies\{982E46A9-9CDE-45D9-B52B-E75BF7B682E8}\Adm\wuau.adm> to the Adm list.
------------------

------------------
USERENV(615c.4c80) 13:27:20:218 LogRegistry RsopData: Successfully logged registry Rsop data
USERENV(615c.4c80) 13:27:37:312 CAdmFileLogger::Log: Logging \\XYZ.domain.com\SysVol\XYZ.domain.com\Policies\{982E46A9-9CDE-45D9-B52B-E75BF7B682E8}\Adm\wuau.adm
USERENV(615c.4c80) 13:27:38:124 CAdmFileLogger::Log: Logging \\XYZ.domain.com\SysVol\XYZ.domain.com\Policies\{982E46A9-9CDE-45D9-B52B-E75BF7B682E8}\Adm\wmplayer.adm
USERENV(615c.4c80) 13:27:38:187 CAdmFileLogger::Log: Logging \\XYZ.domain.com\SysVol\XYZ.domain.com\Policies\{982E46A9-9CDE-45D9-B52B-E75BF7B682E8}\Adm\system.adm
USERENV(615c.4c80) 13:27:38:265 CAdmFileLogger::Log: Logging \\XYZ.domain.com\SysVol\XYZ.domain.com\Policies\{982E46A9-9CDE-45D9-B52B-E75BF7B682E8}\Adm\inetres.adm
USERENV(615c.4c80) 13:27:40:671 CAdmFileLogger::Log: Logging \\XYZ.domain.com\SysVol\XYZ.domain.com\Policies\{982E46A9-9CDE-45D9-B52B-E75BF7B682E8}\Adm\conf.adm
USERENV(615c.4c80) 13:27:43:421 CAdmFileLogger::Log: Logging \\BRCAKP5500WAP\admin$\System32\GroupPolicy\Adm\wuau.adm
USERENV(615c.4c80) 13:27:43:577 CAdmFileLogger::Log: Logging \\BRCAKP5500WAP\admin$\System32\GroupPolicy\Adm\word11.adm
USERENV(615c.4c80) 13:27:45:421 CAdmFileLogger::Log: Logging \\BRCAKP5500WAP\admin$\System32\GroupPolicy\Adm\wmplayer.adm
USERENV(615c.4c80) 13:27:45:484 CAdmFileLogger::Log: Logging \\BRCAKP5500WAP\admin$\System32\GroupPolicy\Adm\system.adm
USERENV(615c.4c80) 13:27:45:609 CAdmFileLogger::Log: Logging \\BRCAKP5500WAP\admin$\System32\GroupPolicy\Adm\ppt11.adm
USERENV(615c.4c80) 13:27:47:359 CAdmFileLogger::Log: Logging \\BRCAKP5500WAP\admin$\System32\GroupPolicy\Adm\office11.adm
USERENV(615c.4c80) 13:27:47:453 CAdmFileLogger::Log: Logging \\BRCAKP5500WAP\admin$\System32\GroupPolicy\Adm\inetres.adm
USERENV(615c.4c80) 13:27:49:187 CAdmFileLogger::Log: Logging \\BRCAKP5500WAP\admin$\System32\GroupPolicy\Adm\excel11.adm
USERENV(615c.4c80) 13:27:49:343 CAdmFileLogger::Log: Logging \\BRCAKP5500WAP\admin$\System32\GroupPolicy\Adm\conf.adm
USERENV(615c.4c80) 13:27:51:343 LogAdmRsopData: Successfully logged Adm data
------------------

5. This issue may occur if RSoP logging is enabled and there is a large WMI repository on the problem server.
6. "The WMI repository is located at the following location: %windir%\System32\Wbem\Repository
RSoP uses the CIMOM database through WMI. When a computer logs on to a network, information such as the computer hardware, Group Policy Software Installation settings, Internet Explorer Maintenance settings, Scripts, Folder Redirection settings, and Security Settings, are written to the CIMOM database. When you start RSoP in logging mode, RSoP reports policy settings that have been applied using the information provided in the CIMOM database."
7. To fix create the Dword value following:
"HKLM\Software\Policies\Microsoft\Windows\System"
Create a new DOWRD "RSoPLogging = HEX 0"

Articles Used
=============
http://support.microsoft.com/kb/2020286
http://technet.microsoft.com/en-us/library/cc783154(WS.10).aspx