Solved

Login Scripts

Posted on 2004-10-06
4
203 Views
Last Modified: 2010-04-14
On my Windows 2000 server I am using the following called logon.bat

net use s: \\BigServer\Share

net use t: \\BigServer\DataFiles

net use u: \\BigServer\acct

I am changing servers, so the BigServer will no longer exist as so I re-did to login script as follows:

net use s: \\Myserver\Share

net use t: \\Myserver\DataFiles

net use u: \\Myserver\acct

But when a user logins they are not presented with the new logins scripts. I don't know why its holding on to the old. Is there a was besides going to everyone desktop and manually change it which I can't do? And help is appreciated. This is so simple and I can't figure it out. Uh I aslo check to see if the login script was in the correct location c:\WINNT\SYSVOL\sysvol\DomainName\scripts\map.bat
0
Comment
Question by:elegal
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
4 Comments
 

Author Comment

by:elegal
ID: 12244348
Sorry should read c:\WINNT\SYSVOL\sysvol\DomainName\scripts\logon.bat

 
0
 
LVL 15

Assisted Solution

by:adamdrayer
adamdrayer earned 25 total points
ID: 12244364
good login script practice for mapping drives is:

net use s: /d
net use s: \\Myserver\Share

net use t: /d
net use t: \\Myserver\DataFiles

net use u: /d
net use u: \\Myserver\acct

the "/d" command deletes the mapping.  This will ensure that the following net use command is not rejected because the drive is already mapped
0
 
LVL 96

Accepted Solution

by:
Lee W, MVP earned 25 total points
ID: 12244395
Try mapping the NETLOGON share to a drive letter on one of the clients.  Then execute the script manually.  You should be able to see things clearer as to what is happening.

My guess is that the drive letters are being remembered by the clients and now that you are changing them to a different drive letter, you have to first disconnect them.

You COULD try modifying the script like this:

net use s: /delete
net use t: /delete
net use u: /delete
net use s: \\Myserver\Share
net use t: \\Myserver\DataFiles
net use u: \\Myserver\acct

This way, the connections are first removed then reestablished to the correct server.
0
 

Author Comment

by:elegal
ID: 12244536
Thanks guys... That slipped my mind.
0

Featured Post

On Demand Webinar - Networking for the Cloud Era

This webinar discusses:
-Common barriers companies experience when moving to the cloud
-How SD-WAN changes the way we look at networks
-Best practices customers should employ moving forward with cloud migration
-What happens behind the scenes of SteelConnect’s one-click button

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

NTFS file system has been developed by Microsoft that is widely used by Windows NT operating system and its advanced versions. It is the mostly used over FAT file system as it provides superior features like reliability, security, storage, efficienc…
Let’s face it: one of the reasons your organization chose a SaaS solution (whether Microsoft Dynamics 365, Netsuite or SAP) is that it is subscription-based. The upkeep is done. Or so you think.
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…

729 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question