[THIN] Re: Running Login Scripts...
- From: "Chris Grecsek" <cgrecsek@xxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Wed, 17 May 2006 16:23:07 -0700
Thanks for the feedback. We leave the CPU/Memory management "features"
turned off on all our servers as we've determined that they cause their own
issues! 051 addressed some other issues we were having and it seemed to be
OK in our testing. Guess we need to do better pre-rollout testing. We'll
definitely mandate a fresh reboot/restrict logins to any servers being
patched moving forward.
Our printers are autocreated during login (from either locally attached or
local network printers) and all users are forced to use the UPD (PS4). It's
pretty clean - at least we thought so!
Anyway - Thanks!
Chris
_____
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Joe Shonk
Sent: Wednesday, May 17, 2006 3:27 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Running Login Scripts...
Turn of CPU/Memory Management when installing the Rollup and Hotfixes..
Also a fresh reboott doesn't hurt... Rick Mack mentioned a few days ago
that Citrix's Cpatch process is a joke. If the file is busy, it doesn't get
updated.
Also Rick mentioned to stay away from hotfixes 036 and 051.
On a completely different path, are you client devices via the logon
script? If so, try setting the logon scripts to run synchronosly.
Joe
On 5/17/06, Chris Grecsek <cgrecsek@xxxxxxxxxxxxx > wrote:
We have been having an issue where one of our Citrix servers gets stuck at
"running login scripts". We've been working with Citrix, sending them dumps,
etc, etc and we haven't made much progress. The "fix" is to kill/restart the
cpsrv.exe and then users can login again. Users that were on the system have
their printing screwed up and have to reboot their local workstation to get
back to normal - but at least they aren't losing any work/getting booted
from their sessions.
The point of the post is that we've seen this on a few other servers and
when it's happened in the past we've just rebuilt the server as opposed to
trying to address it. Recently we decided that enough was enough and we'd
work with Citrix to help get it resolved and that was fine. Unfortunately
last evening we applied hotfixes 3009, 3047, 3051 to some servers and we now
have 5 servers experiencing the problem. Needless to say, we'll be removing
those hotfixes this evening but wanted to gives folks a head's up or see if
anyone else has been having this.
Cheers,
Chris
Other related posts:
