?
Solved

Windows Server 2003 - Login script - not updating network drive mapping after change

Posted on 2012-03-25
8
Medium Priority
?
761 Views
Last Modified: 2012-04-22
Hi,

In a windows server 2003 environment we needed to move a network drive to a new location. Therefore we transferred data to another location on the network and changed the login script so that the Drive letter T was mapped to a different location

e.g.
NET USE T: \\SERVER1\ShareLocation
Became:
NET USE T: \\SERVER2\ShartLocation

However all the uses on the network still retain the old location unless we manually go to their PC, disconnect the T drive network drive manually and then run the login scrip for the NETLOGON folder.

Why is it not updating automatically with the updated script. What more can I do to make it work for all users?
Thanks in advance
0
Comment
Question by:afflik1923
[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
  • 3
  • 2
  • 2
8 Comments
 
LVL 2

Expert Comment

by:tetran_au
ID: 37763732
It will maintain the last know drive mapping unless you delete.  Easiest way is to do the following

NET USE T: \\SERVER1\ShareLocation /delete
NET USE T: \\SERVER2\SharetLocation

Run this till you are sure that all the drives have been remapped and then remove the first line from your script
0
 

Author Comment

by:afflik1923
ID: 37763786
I assume if it encounters the delete command and there is nothing to delete this will not cause a problem (Maybe just issue an error message)?
0
 
LVL 2

Accepted Solution

by:
tetran_au earned 2000 total points
ID: 37763826
sorry my code above was wrong.

it is just
NET USE T: /delete

Thats what happens when you copy and paste.  And if the drive does not exist it will just throw up a error saying the network connection could not be found and continue on its merry way.
0
Fill in the form and get your FREE NFR key NOW!

Veeam® is happy to provide a FREE NFR server license to certified engineers, trainers, and bloggers.  It allows for the non‑production use of Veeam Agent for Microsoft Windows. This license is valid for five workstations and two servers.

 
LVL 9

Expert Comment

by:Timothy McCartney
ID: 37767465
I'll second tetran_au, our clients use a simple logon.bat file with the following command for each network drive

net use p: /delete
net use s: /delete
net use p: \\Server\%username%
net use s: \\Server\shared

This ensures that no conflicts occur when mapping their appropriate drives. The only errors I've seen are when it has issues locating the drive it is trying to map (due do various issues, network down, permissions issues, etc)
0
 
LVL 2

Expert Comment

by:tetran_au
ID: 37768487
Correct Tracerfett,  If you use the net use command to map a drive on logon and the drive exists but for some reason you do not have access to it I.E. no permissions then the device will look as though its hung.  You will be presented with a blank screen which looks like ur profile is hung and has not loaded properly.

To over come this hit ctrl - alt - esc and bring up task manager and run explorer.   If your desktop comes up correct then you know that there is definatly a issue with the drive mapping.  REM out all your drives and slowely add one back at the time. Eventually you will find the culprit and then  you can discover why it is not working.
0
 
LVL 9

Expert Comment

by:Timothy McCartney
ID: 37768498
+1 for tetran_au's previous comment.
0
 

Author Closing Comment

by:afflik1923
ID: 37879026
Great answer. Sorry for delay.
0

Featured Post

Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

Question has a verified solution.

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

Always backup Domain, SYSVOL etc.using processes according to Microsoft Best Practices. This is meant as a disaster recovery process for small environments that did not implement backup processes and did not run a secondary domain controller that ne…
A bad practice commonly found during an account life cycle is to set its password to an initial, insecure password. The Password Reset Tool was developed to make the password reset process easier and more secure.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…
Suggested Courses

650 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