It seems to be something within a script that is hanging, once I killed the cmd.exe process from my administrator login for that user, the desktop finally came up. Now to figure out what was hanging .... ugg!
Thanks! On Tue, Feb 15, 2011 at 10:08 AM, Ben Scott <[email protected]> wrote: > On Tue, Feb 15, 2011 at 9:36 AM, James Rankin <[email protected]> > wrote: > > Thinking about it, what is the cmd.exe process for? Is it some logon > script > > that is stalling? Have you got the "run logon scripts asynchronously" > policy > > enabled, and it is waiting for something? > > I think you mean synchronously. Synchronously means they run > serially, one at a time, and Windows waits for the last to finish > before the next is started. Asynchronously means Windows fires them > off and forgets about them. (Unless I have it backwards. But I never > make mistooks.) > > "Run scripts visible" can also help here. > > Good thought on CMD.EXE running a script that's hanging, that's a > clue I totally missed. > > -- Ben > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe ntsysadmin > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
