[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 806
  • Last Modified:

Server 2003 R2 to Server 2008 (R2) migration/Fresh start

Hello, I am looking to move off the Server 2003 R2 platform onto 2008.

The old Active Directory is very basic, lots of things not working properly, currently only using one site whereas we have 3 branches and 1 HQ. We also have no OUs setup.

It seems it would be best to just build up AD on the server 2008 box that is new hardware side by side. I will probably be importing the users at least, the groups are messed up and we will be switching to a role based access setup in the near future.

What would be the best way to do this? Has anyone else done something similar? Some ideas tossed around were to join the 2008 server to the domain, replicate, then demote the 2003, but that gets all the old stuff, which I do not want, but would be easiest solution. Another solution I suppose is to create a different domain, setup trusts between new and old, then migrate. That also isn't the greatest, but I am not sure. We are a highly operational network and need the highest uptime possible.

I can swing having to disjoin computers from old domain and join them to new domain probably, provided that is really fast.

What is best practice? What is the best solution?

Thanks in advance
0
googol13
Asked:
googol13
2 Solutions
 
computerdoctorserviceCommented:
There is no easy way without joing the servers together and then replicating the AD.

I would say that if you can't do this, build the new server in a different network schema but same domain name, set everything up, create users and groups etc as you want them, add an additional IP address, then map across and replicate data lgging on with an admin logon on the old domain.

Then disjoin each workstation to a workgroup and rejoin every workstation using the new address schema.

Not really a low downtime option simply from the point of data transfer, unless your users use very discreet sets of data and you can transfer one user at a time.

0
 
googol13Author Commented:
I have been looking into ADMT provided by microsoft, seems like it will handle the disjoin and rejoin domains as part of the process using an agent.

Maybe I will just accept the mess they have right now, it probably wouldn't be too difficult to clean it up properly.  That way everyone including management is happy.

Definitely still interested in other ways than ADMT or just simply joining the domain then demoting the old server 2003 box.
0
 
Darius GhassemCommented:
0
 
obeniCommented:
Hello,
Two Options I can think of:
1- Upgrade your current schema and to w2k8 and join the new server to the exisitng domain and clean up all the domain. with this approach, there will be no downtime to the end user
2-redesign a new domain and create a trust between the old and new and migrate users and workstations using ADMT..Possible problem here is that, if you have applications that depended on the current domain, you will have to figure how to migrate those as well.etc
So suggest you do a clean up of your current domain, then upgrade to 2008
0

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now