Jump to content

Recommended Posts

Posted (edited)

Hi everyone,

 

Ok, so heres a quick summary of how our setup currently exists:

 

Two schools next to each other running their own networks with a physical server at each site. I can access both networks and they share the same internet connection. There are rules setup on the router to allow this. Each schools server has one VM running Sims.

 

 

Im going to be setting up our new domain server in the coming weeks which will replace both servers and make one main network accross the two schools.

 

My first step is to setup the server and I'l be running the domain controller as a VM in HyperV.

There will be two additional VM's on that server that will run Sims. Users will be able to pick which Sims (Infants or Juniors) to connect to when they open Sims.

 

The plan is to get the server setup and on a test network to test out logins, GPO's, etc.

 

 

I now need to do the network transition in stages. How does this sound?

 

1. Get our two Sims VM's transferred to the new server VM's.

2. Reset the network switches to default settings to set correct ip range / set ip's on printers, phones etc.

3. Disable the current Juniors domain controller and introduce the new server which will be located in the Junior school.

4. Get all computers in the Juniors connected to the new domain.

5. Disable the Infants domain controller.

7. Get all computers in the Infants connected to the new domain.

8. Test everything.

9. Book a holiday somewhere miles away from any I.T where there will be sunshine due to spending most of the summer in a server room.

 

 

 

Any pointers / things I've forgotten?

 

Many thanks for your help.

Edited by Sonic007
Posted

So you're merging two separate domains? E.g. school1.domain.com and school2.domain.com into school.domain.com?

 

Your probably going to want to look at using ADMT for the migrations for AD objects, servers, and computers with file permission conversions.

 

Ensure your SIMs servers have a local SA account before migrating so you don't lose access to either one after you change the domain.

 

How are you going to move the VMs? I've used Veeam with great success with Hyper-V rather than Microsofts transitions as you don't need any prerequisites really.

 

I wouldn't disable or destroy any old domain services until you get it all working correctly on the new domain. Just remove the trust first then see if anything breaks, then get rid after you know you've done it all.

  • Thanks 1
Posted
+1 for ADMT, when I set up a new domain (admittedly ages ago on a 2003/XP network) it made things so much easier for migrating the users and computers over. Pretty sure all I had to do was have the PCs turned on (and both old and new DCs running) and the tool handled the joining to the domain for me. I certainly don't remember having to visit every PC putting my password in or anything like that.
  • Thanks 1
Posted

Tones... Thanks for your message.

 

The networks so much of a mess that I won't be migrating any AD accounts, policies, etc. These will all be created from scratch on the new server.

 

I believe we do have SA accounts but will double check. Thankyou.

Luckily I've got our Sims Support people who are going to come in and transfer the Sims VM's and setup the multi Sims access.

Im going to be be busy enough so glad they are doing that.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...