login script

[Guest]

I use a login script to log the network drives for my users. I put in a new
server and named it different from the old one. I updated the login script
to point to the new one. But when a user logs into a XP machine that was
present when the old server was their (last year) it runs the old script.
So I made a new script and named it different. Still same thing. The
network drives were not locally mapped.

If a new user logs in to a XP machine the correct script runs.

Please help ...

 

[Chad Mahoney]

I use a login script to log the network drives for my users. I put in a new
server and named it different from the old one. I updated the login script
to point to the new one. But when a user logs into a XP machine that was
present when the old server was their (last year) it runs the old script.
So I made a new script and named it different. Still same thing. The
network drives were not locally mapped.

If a new user logs in to a XP machine the correct script runs.

Please help ...

In active directory users and computers make sure the login script is
properly defined under the user properties. The login script should
reside on both servers if they are both still in the network.

 

[Lanwench [MVP - Exchange]]

In

I use a login script to log the network drives for my users. I put
in a new server and named it different from the old one. I updated
the login script to point to the new one. But when a user logs into
a XP machine that was present when the old server was their (last
year) it runs the old script. So I made a new script and named it
different. Still same thing. The network drives were not locally
mapped.

If a new user logs in to a XP machine the correct script runs.

Please help ...

In addition to the other reply -

I'm presuming you're using AD. If so, there are two places where login
scripts can be set.

One is in the user's ADUC properties - and all you do in there is put the
name of the file you want to run (.bat, .vbs, whatnot). That file has to be
in the \\server\netlogon share, and you don't specify a path to it, just the
file name.

The other is via group policy - this is in User Configuration\Windows
Settings\Scripts (Logon/Logoff).

This might help you narrow down where the login script is being applied.

In addition - if you're using a batch file with net use commands, I suggest

net use * /del

before mapping the drives - and use

net use x: \\server\share /persistent:no

when mapping them.

 

[Guest]

My current login script look like this:

net use g: \\severname\data
net use h: \\severname\programs

Do you suggest this:
net use * /del
net use g: \\severname\data
net use h: \\severname\programs

What does the /persistent:no do???

 

[Lanwench [MVP - Exchange]]

In

My current login script look like this:

net use g: \\severname\data
net use h: \\severname\programs

Do you suggest this:
net use * /del
Yes...

net use g: \\severname\data
net use h: \\severname\programs

What does the /persistent:no do???

Keeps the connection from being remembered between sessions.

 

[Ray]

That will break people accessing the network remotely from a non-Microsoft
VPN, since they normally cannot run login scripts. They won't have their
drive letter and will call the Help Desk.

I just have the delete command in mine and it works fine.

Ray

 

[Lanwench [MVP - Exchange]]

In

That will break people accessing the network remotely from a
non-Microsoft VPN, since they normally cannot run login scripts.

No, but you could put a batch file on their desktop, if you like. Or don't
have them use mapped drives. Up to you!