Solved

Migrating from Server 2003 x32 to Server 2008 r2

Posted on 2010-09-15
12
214 Views
Last Modified: 2012-06-21
Looking for some confirmation in my upgrade plan.  I have a new server box on which I have installed Server 2008 r2.  The server that it will replace is a file/print server and is running server 2003.  I installed the new server with a temporary name into the domain.  I have restored the data files from my Backup Exec backups and I have recreated all the shares.  I used the print migration tool to migrate the printers from the old to the new.  

My plan is to shutdown the old server, log into the new server and change the name so that it becomes the name of the old server.  At this point I will restore the latest backups so that all the data will be current.

Will this process work?  This server also contains all the users redirected folders and profiles.  Am I missing some critical step?  Thanks in advance for your input.
0
Comment
Question by:tvenable
  • 6
  • 5
12 Comments
 
LVL 59

Accepted Solution

by:
Darius Ghassem earned 334 total points
ID: 33682427
Nope all seems good you just need to make sure that you change the IP address as well for the new server to the old server's

Run ipconfig /flushdns and ipconfig /registerdns after the change of workstation name and IP
0
 
LVL 6

Assisted Solution

by:mattconroy
mattconroy earned 166 total points
ID: 33682622
Also,

Run nbtstat -RR from the command prompt.

The -RR is undocumented but it will update the netbios information.
0
 

Author Comment

by:tvenable
ID: 33682953
I was planning on having a new ip address for the server. I am in the process of switching everything from a flat 192 network to a 172 vlan divided network. Should I wait and change the ip at a different time?
0
 
LVL 59

Expert Comment

by:Darius Ghassem
ID: 33683066
Know I would do it now then change it again later but if you are going to keep the same name I would advise to keep the same IP
0
 

Author Comment

by:tvenable
ID: 33685059
Thanks for the advice.  I plan to pull the trigger tomorrow night.  I will report back and let you know how things go.
0
 

Author Comment

by:tvenable
ID: 33720813
Well, unfortunately the server switch did not go as planned.  First off, I had issues with Backup Exec 12.5 restoring the data.  The restore jobs kept timing out so I had to break the job down into smaller chunks.  Once that was completed I was ready to do the switch.  Worked until 1am and everything seemed to be fine.  I could login and I was able to login from a couple of other workstations.  But when I arrived at work the next morning my phone was ringing off the hook.  Some could not login, others could not access their "My Documents" or email and no one could print.  I spent the bulk of the day trying to figure out what was going on.  I figured it had to do with file and or share permissions but everything looked fine.  So late in the day I switched back to the old server so at least the whole campus wasn't disrupted for an extended time.
I now have to figure out what went wrong.  Any ideas of what I need to check?
0
Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

 
LVL 59

Expert Comment

by:Darius Ghassem
ID: 33720841
Run dcdiag to check for errors. What do you mean switch back? What did you switch back? Did you keep the same name and IP address?
0
 

Author Comment

by:tvenable
ID: 33720881
When I did the original switchover I simply shutdown the old server and disconnected it from the network.  I then renamed the new server to the name of the old server.  I did use a new IP address for the new server.  Once I renamed the server I ran ipconfig /flushdns and then ipconfig /registerdns as well as nbtstat -RR.  So today when I switched back to the old server I renamed the new server, cleared the dns and then reconnected and booted the old server.  It came up normally and at that time the users could login and access their files once they rebooted.
0
 
LVL 59

Expert Comment

by:Darius Ghassem
ID: 33720895
I would use the old IP address.
0
 

Author Comment

by:tvenable
ID: 33720918
I will try that.  However I think it is a permissions problem.  I don't think the permissions where properly set when the files were restored from the backkup.  I say that because some users could see their files but could not open.  They would get an "Access Denied" message when they would try to open one of them.  I think I am going to try and do a restore of the permissions only and see what that does.
0
 
LVL 59

Assisted Solution

by:Darius Ghassem
Darius Ghassem earned 334 total points
ID: 33721000
yes that might be a good option.
0
 

Author Closing Comment

by:tvenable
ID: 33781494
After going through folder by folder I found that a lot of the file permissions were incorrect.  I think this may have been because of going from server 2003 to 2008 r2.  It seams the file permission are a little different in 2008.  I am guessing that the permissions may not have been completely right on the old box (this is a very old server and I think it was upgraded from 2000 a few years ago).  I have decided to do a slow migration instead of a replace.  All the advice that was given was good.  I am going to give each of you some of the points.
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

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

Suggested Solutions

Know what services you can and cannot, should and should not combine on your server.
The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
This tutorial will walk an individual through the steps necessary to configure their installation of BackupExec 2012 to use network shared disk space. Verify that the path to the shared storage is valid and that data can be written to that location:…
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…

861 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

Need Help in Real-Time?

Connect with top rated Experts

29 Experts available now in Live!

Get 1:1 Help Now