scripts in server 2000 and 2003

Hello all,
I am migrating data and exchange mailboxes to a new server running windows server 2003 from a box running 2000 , I have done all the domain prep and moved the mail boxes and all is good. My problem is that I am moving all the data to the new server from the old one and I have changed all of the scripts for drive mapping. When I changed the scripts on the old server and the other server that is in the domain (besides the new one) and finally went to the new server and changed its scripts to match then restarted all of the DC`s ;users are still being sent to the old drive paths. I double checked all of the script folders even searched for .bat files to make sure I was not missing something and they all point to the new server, I also restarted the servers again with no luck. Is there something I am missing ,can you help. By the way I am trying not to switch the server roles to the new server yet because I want to make sure everything is ok on the new server before I switch the roles. As I understand it as soon as I turn the schema master role over to the new 2003 server I have to pull the old 2000 server off of the domain. Thanks
probiemcgeeAsked:
Who is Participating?
 
probiemcgeeConnect With a Mentor Author Commented:
It was the server something about being the Schema master and they had sure sync with another server that would change the scripts. Thanks
0
 
igor-1965Commented:
Could you post your login script? Have you found the "root" script (the one that is the first one)? Its name is usually defined in AD / Profile tab, script itself located at the %LOGONSERVER%.

I personally think it is a good practice to remove all the drive mapping at the beginning of the script and then follow with the drive mapping. This way you can ensure every time you amend the script the drives are always mapped to new locations.
0
 
probiemcgeeAuthor Commented:
net use F: /delete
net use G: /delete
net use p: /delete
net use q: /delete
net use F: \\nola-server\E:\F drive
net use G: \\nola-server\E:\G drive
net use p: \\nola-server\E:\F drive
net use q: \\nola-server\E:\H drive
These are the scripts I am using and they are named login.bat and in the scripts folder. I will double check that the scripts are inserted in the root script. The 2000 box as of right now is the box running the show. I just want it to point to the 03 box , this is what i thought I accomplished here.
0
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

 
igor-1965Commented:
Strange share names but anyway...

net use * /delete
net use F: "\\nola-server\E:\F drive"
net use G: "\\nola-server\E:\G drive"
net use p: "\\nola-server\E:\F drive"
net use q: "\\nola-server\E:\H drive"


Is it correct that F: and P: are mapped to the same share?

0
 
Malli BoppeCommented:
can you check if the login script has been changed on new and old dc's.
Also trying mapping the drives manually from a workstation.
 
0
 
probiemcgeeAuthor Commented:
yes for some reason F and P are mapped to the same share. For some reason they want to keep it that way so everyone keeps using the drives they are used to. I have tried mapping it from a workstation and it does map. If I remove the login.bat from the users profile it works fine. But I want to get a permanent solution because they have another DC off site and until it can get replaced I dont want to have issues.
0
 
probiemcgeeAuthor Commented:
Every where I can find the script I have changed it ! It looks as if it has been changed but it must not be somewhere because it keeps the old drives on all the client machines for some reason.
0
 
igor-1965Commented:
When you said "If I remove the login.bat from the users profile it works fine" does it mean that you then able to manually map the shares or all the drives mapped automatically?

Normally, the login.bat should be located at %logonserver%\netlogon at the network.
0
 
Malli BoppeCommented:
I suggest to create a deuplicate login script and put a pause in the script and also turn on the echo.Set this script to a test user and when the user logs in you should see if the script ran successfully or not.
0
 
probiemcgeeAuthor Commented:
Thanks I still can not get it to work. I can manually map the shared drives and I then am having to remove the login scripts from the users profiles. I will try a new script when I remove the old server this week. If not for the time being I will leave the drives mapped manually and have them reconnect at logon. I will then write a new script and put it in the user files.
0
 
Malli BoppeCommented:
I think you are using some third party tool to replicate the AD data.Uninstall that
 
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.