Solved

scripts in server 2000 and 2003

Posted on 2008-11-02
11
230 Views
Last Modified: 2013-12-05
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
0
Comment
Question by:probiemcgee
[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
  • 5
  • 3
  • 3
11 Comments
 
LVL 14

Expert Comment

by:igor-1965
ID: 22862250
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
 

Author Comment

by:probiemcgee
ID: 22863418
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
 
LVL 14

Expert Comment

by:igor-1965
ID: 22863598
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
Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

 
LVL 23

Expert Comment

by:Malli Boppe
ID: 22864464
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
 

Author Comment

by:probiemcgee
ID: 22867934
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
 

Author Comment

by:probiemcgee
ID: 22867950
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
 
LVL 14

Expert Comment

by:igor-1965
ID: 22868828
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
 
LVL 23

Expert Comment

by:Malli Boppe
ID: 22872067
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
 

Author Comment

by:probiemcgee
ID: 22924942
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
 

Accepted Solution

by:
probiemcgee earned 0 total points
ID: 22985427
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
 
LVL 23

Expert Comment

by:Malli Boppe
ID: 22989726
I think you are using some third party tool to replicate the AD data.Uninstall that
 
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

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

Welcome to my series of short tips on migrations. Whilst based on Microsoft migrations the same principles can be applied to any type of migration. My first tip Migration Tip #1 – Source Server Health can be found listed in my profile here: http:…
This article provides a convenient collection of links to Microsoft provided Security Patches for operating systems that have reached their End of Life support cycle. Included operating systems covered by this article are Windows XP,  Windows Server…
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…
Suggested Courses

632 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