[THIN] Re: 2008 vs 2003 login times

  • From: "Anthony Green" <agreen@xxxxxxx>
  • To: <thin@xxxxxxxxxxxxx>
  • Date: Sun, 10 Jan 2010 22:51:17 -0000

Treated same as before, they get brand new 2008 TS profiles.  They are
roaming same as before.


Everything is virtualised on XenServer, are there any tweaks for 2008 on
XenServer?, we have the whole environment on XenServer (they use XenServer
for their 2003 environment as well).


Has anyone tested logon times between base 2k3 and base 2k8 in the same
environment?  It would be nice to know if there is noticeable difference or
if maybe we have introduced something that is making it that much slower.





PS           What should we class as "normal/good" logon times for 2k8?
(With standard setup ie normal roaming profiles, nothing clogging up the
startup, everything on same GB LAN etc...)


From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Triana, Eduardo
Sent: 09 January 2010 21:16
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: 2008 vs 2003 login times


What about the User Profiles? How did you treat them on Windows 2008, that
can be one of the reasons ..


From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Anthony Green
Sent: Thursday, January 07, 2010 9:25 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] 2008 vs 2003 login times


I've done a few upgrades recently moving people from 2003 to 2008 SP2 and
latest Xenapp.


Nearly every time the users have noticed a longer login time.


One company went from 7 secs to 14 secs (i know it's not a long login time
but it has doubled!).  We basically replicated their Windows 2003 setup
(xenapp\DCs\File\Print\SQL) but have everything on Windows 2008.


Most things work ok but the login times are killing me, I'm having to
explain why this is without really knowing why there is such a difference.
Anyone else notice this?  Any tips?





This communication and any files transmitted with it (the "Communication")
may contain privileged or other confidential information. This Communication
is intended solely for the individual(s) or entity (ies) to which it is
addressed and additionally should not be forwarded outside of MTM except in
the course of legitimate MTM company business. If you are not the intended
recipient, or believe that you have received this Communication in error,
please do not print, copy, retransmit, disseminate, or otherwise use this
Communication. Also, please indicate to the sender that you have received
this Communications in error, notify MTM Technologies, Inc. at HR@xxxxxxx
<mailto:HHRHR@xxxxxxx> or (203) 975-3700 that you have received this
Communication in error, and then delete this Communication and any copies
thereof. Thank you.

Other related posts: