server 2003 change of platform / migration - how to?

Currently running Server 2003 DC with Terminal Services. This supports a multitude of applications and file serving.

We intend to change the hardware platform from IBM to HP. What is the easiest way to do this?

Can we just use NTbsckup with or without "System State" after loading the OS and appropriate drivers on the new server.

Would all permissions, policies and accounts be retained?

The thought of having to reinstall all applicatiionns and accounts etc. along with transfering data is quite intimidating. Any other solutions anybody would suggest?

TIA
LVL 1
localhost_offlineAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Kieran_BurnsConnect With a Mentor Commented:
Well..... no is the short answer. :)
I would try this:
1. Build the new DC and DCPROMO it into the domain. Move all the AD ROLES (FSMO and DNS DHCP et al) across to the new Server
2. Test that in place and ensure it is working
3. Build the 2nd Server with an absolute base image, then follow the instructions here: http://support.microsoft.com/kb/249694 to backup and restore from the OLD DC to the 2nd Server.
4. If this works you will still have the OLD Server to fall back on AND have a known working AD structure independent of any 'testing issues'
5. If you get the migration working on the 2nd Server you can then DCPROMO it as well (if that is what you intend to do)
 
0
 
Kieran_BurnsCommented:
The easiest way is to build the new DC while the old one is in place - you really should have two DCs anyway.
DCPROMO the new Server into the domain and all the accounts / AD settings will be copied over.
Add all the Services running on the OLD DC onto the NEW one (DNS, DHCP etc)
Then you can copy data over by sharename (presuming you have mapped to shares) onto the new Server which would leave the old data intact in case of failback.
Then once everything datawise is moved over and stable (and being backed up!) you can (if you choose) re-install the applications.
Personally I would be tempted to leave some things running on the old platform for fault tolerance...
0
 
snusgubbenConnect With a Mentor Commented:
First, when your changing your HW I would beg my boss for an additional server to split the TS from the DC!

If that is not an option, make the HP server a TS and add the it as an additional DC. Let the replication finish and move FSMO, DHCP, GC etc. to the HP box. Then demote the IBM (if needed).

If it also serve as a fileserver MS has a GUI based file migration tool. Free of charge.
0
 
localhost_offlineAuthor Commented:
Thanks for the replies.

Indeed the intention is to replace the single IBM server with 2 HP machines. I guess the concern I have is re-installing all the applications, folder redirects etc. I thought perhaps I could use NTbackup to build the first machine to an identical condition as the IBM server. Then introduce the second server.

Is there any wayy to easily migrate the applications/settings - as the customer does not have original media for some apps and it is not generally available.
0
 
localhost_offlineAuthor Commented:
Followed your ideas AND got a second server! Used XP Unlimited for the TS - great!
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.