I've been working on the same issue for 8mo now. I built a fresh XP farm on 2k and I applied the first fix (registry flush) which did nothing for me. I'm now at level 5 support ,whatever that is, at MS and they can't figure it out. They feels it's the print spooler causing the delays. But my CPU just spikes once in awhile. I also have the Local Time zone unchecked and I'm running FR2. No change. Users are still complaining of delays, even on the LAN. Did you spend time investigating printer auto-creation as the problem?? Daniel J. Samaan=20 Senior Network/Security Engineer - CCSE, CCA, CCNA, MCSE dsamaan@xxxxxxxxxxxxxxxx -----Original Message----- From: Jim Kenzig [mailto:jimkenz@xxxxxxxxxxxxxx]=20 Sent: Tuesday, September 10, 2002 1:58 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Re: MF-XP slowdown RESOLVED!!! This makes sense...if all of your clients are in the same time zone there is really no need for this box to be ticked the server time should be alright, though it is by default. Find the setting by right clicking on the farm name in the CMC choose properties from the popup and choose the Metaframe settings tab and uncheck the box that says use local time of ICA clients. Regards, Jim Kenzig http://thethin.net -----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On Behalf Of Erik Gerard Sent: Tuesday, September 10, 2002 2:05 PM To: thin@xxxxxxxxxxxxx Cc: <"Dan Samaan" Subject: [THIN] MF-XP slowdown RESOLVED!!! We have a farm w/ 75+ that we upgraded from Win4.0TSE/MF1.8 to Win2k/MF-XPe=3D , that was having a critical problem. Periodically, we would see the =3D processor fall to almost 0% utilization and the users would experience a =3D 5-30 second delay in keyboard response or pull-down/pop-up menus, although =3D screen refreshes were fine. It was severe enough that we had to roll =3D back.=3D20 We applied the following MS HotFixes: Q317357 & Q320261. The later =3D required modifying the Registry Flush rate from the default of 5 sec. to =3D 30 sec. While this reduced the problem from happening every 5-8 minutes to =3D once every 90 minutes, it did not eliminate it all together.=3D20 After much hassle attempting and finally getting a Live Remote Debug and =3D Kernel Memory Dump (can't have more than 2GB physical RAM and must only =3D have a single hard drive!), we found out that Citrix' TZHOOK.DLL was a = =3D part of the problem.=3D20 This DLL tracks the time zones for each user session and can be turned off =3D in the Farm Properties of the CMC. Once we did that, our processor =3D utilization nose dived from 80% to 25% for 90 users.=3D20 I hope some of you will find this helpful and won't have to go through the =3D long, painful process we did.=3D20 Erik ********************************************** This weeks sponsor 99Point9.com 99Point9 helps solve your unresolved technical server-based questions, issues and incidents. http://www.99point9.com *********************************************** For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link. http://thethin.net/citrixlist.cfm ********************************************** This weeks sponsor 99Point9.com 99Point9 helps solve your unresolved technical server-based questions, issues and incidents. http://www.99point9.com *********************************************** For Archives, to Unsubscribe, Subscribe or=20 set Digest or Vacation mode use the below link. http://thethin.net/citrixlist.cfm ********************************************** This weeks sponsor 99Point9.com 99Point9 helps solve your unresolved technical server-based questions, issues and incidents. http://www.99point9.com *********************************************** For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link. http://thethin.net/citrixlist.cfm