Hi Shawn,

Don't realy have the ability to compare.
Here's an export of the Registry key you mentioned on the Citrix server:

[HKEY_CURRENT_USER\Software\KiXtart\TokenCache]
"S-1-5-21-921443515-557003545-1235820382-513"="MILO\\Domain Users;1060543"
"S-1-1-0"="Everyone;1066052"
"S-1-5-32-545"="MILO-CITRIX\\Users;1110073"
"S-1-5-32-544"="MILO-CITRIX\\Administrators;1065590"
"S-1-5-21-921443515-557003545-1235820382-512"="MILO\\Domain Admins;1060029"
"S-1-5-21-921443515-557003545-1235820382-1064"="MILO\\Internet Users;1105787"
"S-1-5-21-921443515-557003545-1235820382-1147"="MILO\\Belgofactors;1102429"
"S-1-2-0"="LOCAL;1063561"
"S-1-5-4"="INTERACTIVE;1068870"
"S-1-5-13"="TERMINAL SERVER USER;1085199"
"S-1-5-11"="Authenticated Users;1101471"
"CacheAge"=hex:10,6a,e4,f5,9b,0f,c2,01

Please note that the problem is at the Client side (Citrix/TS) and not at the PDC. The installation I did was an 'normal' W2K Server / Office 2000 Pro (following the Microsoft Faq on how to do this on a Terminal Server). Also note that I did a test and the problem is completely fixed by changing the loginscript. First scenario I used Kixtart, this produced the problem, second scenario was done by using NET USE... The test only mapped 1 network drive. Strange isn't is? Do you have the ability to check if Kixtart releases all Registry space when using it on a normal workstation? Probably the problem is magnified because the Citrix server is multi-user and logon/logoff is done at a frequent rate.

Any help is much appriciated.

Greetings,
Freddy Lauwers