Usrlogon.cmd may stop running

  • Thread starter Thread starter Pierre
  • Start date Start date
P

Pierre

I've been updating some of my companies Windows 2000
terminal servers with service pack 4. Along with the
service pack I also ran all updates from windowsupdate.
Six of the server updates went well and solved many
problems but two of them stopped running usrlogon.cmd when
logging on to them so for the moment I don't have the
courage to update the rest of them. I've done some
research on the internet and it seems like I'm not the
only one with this issue. Is there a general fix, tweek,
anything I can do or do I have to reinstall the server
from scratch to solve this problem?

http://www.sbc-technet.com/modules.php?
name=News&new_topic=7

http://www.freelists.org/archives/thin/08-
2003/msg00302.html

http://www.saturnport.com/
 
That list is an "anecdotal" list of problems with SP4, most of
which have been fixed now. I've never heard anyone actually report
that UsrLogon.cmd didn't run, but this might be a part of a more
general logon issue.

Is UsrLogon.cmd never started at all, or does it hang and never
complete? Have you verified that the entry for UsrLogon.cmd is
still present in the registry at
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion
\Winlogon\Appsetup

I would download FileMon and RegMon from
http://www.sysinternals.com/. Run them as administrator and start
a TS session as a normal user.

FileMon and RegMon will show you all files and registry keys that
are accessed, including all "access denied" errors that occur.
This might give you a more precise idea of where the problem lies.
 
First of all, thanks for a fast answer.

I've read some about the registry key
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVer
sion\Winlogon\Appsetup and you're right about
usrlogon.cmd i missing. The strangest thing of all is
that the key is missing on the working servers also, but
the login script is running anyway. If I search the
registry for usrlogon.cmd on a working server I don't
find a single key and this makes me really confused.
There must something else triggering the login script but
I don't know what. Well I guess I have to explore this
further and I'll be happy for all tips and answers I can
get.

/Pierre
 
Back
Top