New Domain

[bladedanny]

Hi All,

 

I'm going to be setting up a brand new domain with a new server. My question is can I have a second domain controller on a second domain on the same lan? I'd obviously disable DHCP on the new server until needed.

 

Thanks,

[Seb1780]

Each Domain / DC would have to be on its own subnet with no overlap of IP Address ranges. You would have to create trust relationships between the domains to share data / access / etc.

 

It's not dis-similar to setting up multiple physical locations each with their own domain and sharing corporate resources; VLANs would help here.

[bladedanny]

I only want to connect it to the network whilst setting it up etc. When in production it will be the only domain/DC would this still apply?

 

Thanks,

[FN-GM]

Each Domain / DC would have to be on its own subnet with no overlap of IP Address ranges. You would have to create trust relationships between the domains to share data / access / etc.

 

It's not dis-similar to setting up multiple physical locations each with their own domain and sharing corporate resources; VLANs would help here.

 

That is incorrect. There is no reason why you can't have more than one domain on the same subnet. Just make sure you don't have 2 x DHCP servers as you will have issues. Vlans would be helpful must you don't have to have it like that.

[Seb1780]

That is incorrect. There is no reason why you can't have more than one domain on the same subnet. Just make sure you don't have 2 x DHCP servers as you will have issues. Vlans would be helpful must you don't have to have it like that.

 

I stand corrected

[PotNoodleTech]

Yes you can have more than one domain on the same IP range, only one domain would be able to run DHCP services though. I suggest you set the new domain controller on the new domain with DHCP disabled (but you can still set up your new scope etc if you want) and manually allocate static IP addresses with "new server" dns IP to any client PCs you wish use / join on the new domain.

 

In this way you can set up the new domain along side and get it exactly how you want it, transfer users and data over etc etc. Then when ready to do the full migration - just disable DHCP on the old domain, enable it on your new domain, and rebuild PCs as required.

 

Works a treat and gives you lots of testing time too for O/S and software deployment, GPOs etc.

Edited May 12, 2014 by PotNoodleTech

[bladedanny]

Cool, thanks all.

 

That's what I was hoping for.