Steve, I walked into an environment with an existing TS/Citrix farm on Win2k/SP3 and hyperthreading was enabled. I tracked the performance for about 45 days and although the affinity wasn't perfect, the overall stability and performance were good. Approaching a high-volume period, I didn't want to take any chances on stability and disabled hyperthreading. The last thing I needed was for a server to freeze if a "virtual" cpu got pegged. If I had it to do all over again, I'd have left the hyperthreading alone. I encountered heightened cpu contention afterwards. Stability can only be disproven, not proven, so I can't say if I dodged any bullets. I have enough servers that I could have absorbed a crash of a machine. In retrospect, I should have waited for a problem to appear before disabling hyperthreading. 2 cents, Bob ******************************************************** This Weeks Sponsor: ThinPrint, GmbH Now available: .print Remote Desktop Printing Engine for Microsoft Terminal Services http://www.thinprint.com/dotprint/index.php?s=682&lc=1 ********************************************************** Useful Thin Client Computing Links are available at: http://thin.net/links.cfm ThinWiki community - Excellent SBC Search Capabilities! http://www.thinwiki.com *********************************************************** For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link: http://thin.net/citrixlist.cfm