Mapped drives disappeared (login script)

[Guest kingsroad]

I have a strange problem about login script. I used to use the login script

to map several network drives for the users. But some users (no particular

users, just random) occassionaly lost their all mapped drives. They just

disappeared with no reason. Manually running the login script will show up

again.

 

I checked the event log on server and the client's machine and there aren't

any clues.

[Guest Pegasus \(MVP\)]

Re: Mapped drives disappeared (login script)

 

 

"kingsroad" <kingsroad@discussions.microsoft.com> wrote in message

news:51211A80-26B0-4D9F-805A-DC5D60627366@microsoft.com...

>I have a strange problem about login script. I used to use the login script

> to map several network drives for the users. But some users (no particular

> users, just random) occassionaly lost their all mapped drives. They just

> disappeared with no reason. Manually running the login script will show up

> again.

>

> I checked the event log on server and the client's machine and there

> aren't

> any clues.

 

Place a "pause" command at the end of the logon

script so that you can see what's going on.

[Guest kingsroad]

Re: Mapped drives disappeared (login script)

 

Maybe this is a good idea for the case. But in what situation the home folder

setting in "AD Users and Computers" snap-in will not work? Cause for those

users, their Home drive is missing too which is controlled in that snap-in.

 

"Pegasus (MVP)" wrote:

>

> "kingsroad" <kingsroad@discussions.microsoft.com> wrote in message

> news:51211A80-26B0-4D9F-805A-DC5D60627366@microsoft.com...

> >I have a strange problem about login script. I used to use the login script

> > to map several network drives for the users. But some users (no particular

> > users, just random) occassionaly lost their all mapped drives. They just

> > disappeared with no reason. Manually running the login script will show up

> > again.

> >

> > I checked the event log on server and the client's machine and there

> > aren't

> > any clues.

>

> Place a "pause" command at the end of the logon

> script so that you can see what's going on.

>

>

>