mapped network drives ( logon.cmd ) fail...

[Cary Shultz]

Howdy! Howdy!

Basic question: logon script does not work sometimes in a
WIN2000 SBS Server/WIN2000 client environment. And
sometimes is the key word. Happens on two users with
regularity and on two others with irregularity. The other
seven people are fine. It is also something that started
about three weeks ago...no changes have been made ( well,
not to my knowledge ). Having said that, I will have to
say that it was formerly "logon.bat", problems started, I
suggested to boss that we change it to logon.cmd, he did,
problems still here.

It is a basic logon.cmd with five simple drive mappings.
The "logon.cmd" is in each user's profile - and is spelled
correctly! For the two users who experience this
regularly the do indeed have an IP Address from DHCP.
They can get to the Internet. Logon script simply does
not do it's thang!

I have not had a chance to really look at this - will on
Monday. They are going through an extremely busy time
right now and are glued to their computers.

For what should I be looking ( I need to cut to the chase
here as they are super busy and I can not be spending 15 -
20 minutes at their computer )?....

I am going to suggest to my boss that we drop the logon.cmd
( user's profile tab - logon script edit box ) and go with
a vbscript and make it part of "logon" ( user
configuration | Windows Settings | Scripts | Logon ).

However, I would like to know what is causing
this...Telling the users to simply log off and then back
on - or even worse, restart their computer - each time
this happens is getting old. That is a quick fix. We need
a solution.

I have never experienced this before. I guess that I have
been lucky - up til now!

Thanks all,

Cary

 

[Warren Williams [MSFT]]

Enable userenv logging and them search for the logon script name in the log.
If there is an error it will be logged there and a good chance it will point
you in the right direction.

221833 How to Enable User Environment Debug Logging in Retail Builds of
Windows
http://support.microsoft.com/?id=221833

You can also use .bat and .cmd files with GPO assigned logon scripts.

 

[Cary Shultz]

-----Original Message-----
Enable userenv logging and them search for the logon script name in the log.
If there is an error it will be logged there and a good chance it will point
you in the right direction.

221833 How to Enable User Environment Debug Logging in Retail Builds of
Windows
http://support.microsoft.com/?id=221833

You can also use .bat and .cmd files with GPO assigned logon scripts.

--
Warren

This posting is provided "AS IS" with no warranties, and confers no rights





.

Warren,

Thank you for you reply. Don't I feel stupid? I should
have known that...

We will probably continue with the .cmd logon script...I
just just try to get my boss to put it in the "other"
location ( the scripts | logon location ). He is not
familiar at all with .vbs - and I just started last week!