New to server builds. Making new DC on domain.
-
@g-i-jones said in New to server builds. Making new DC on domain.:
@tim_g Our old DC is corrupt, and it was a replication of an even older corrupt DC. We've opted to go with a new build entirely. I'm trying to figure out how to stand this new DC up, manually input the Users, Group Policy, all that, and transfer FSMO roles to it while simultaneously taking down the old DC.
Setup your DC, add the static IP of the server and prepare DNS on DHCP for all the computers and other devices, removed computers from the domain after backing up data and join them to the new domain.
-
@scottalanmiller roughtly 300 cpu's, 100 users.
If I made a new sub domain of say abc.alphabet.com and my current was abc.alphabet.net, but I NEEDED the .net could I set up the new DC on .com and then after unplugging the old DC from .net, then change the new DC to the .net? Or is that more of a pain than it's worth?
-
@g-i-jones said in New to server builds. Making new DC on domain.:
@scottalanmiller roughtly 300 cpu's, 100 users.
Computers are easy, users are the pain (as they have passwords.) But 100, not horrible.
-
@g-i-jones said in New to server builds. Making new DC on domain.:
If I made a new sub domain of say abc.alphabet.com and my current was abc.alphabet.net, but I NEEDED the .net could I set up the new DC on .com and then after unplugging the old DC from .net, then change the new DC to the .net? Or is that more of a pain than it's worth?
No, don't do renames. Nothing likes that.
Use ad.domain.com, don't use the .net from the beginning if you don't want to be on it.
No one should care what the domain is, it's not really something users interact with.
-
@scottalanmiller damn. Yea too many things already ride on our current domain, so we're trying to dodge a migration to a new domain if we can. Still thinking about our best course of action.
-
@g-i-jones said in New to server builds. Making new DC on domain.:
@scottalanmiller damn. Yea too many things already ride on our current domain, so we're trying to dodge a migration to a new domain if we can. Still thinking about our best course of action.
Like what?
-
@Dashrender roughly 100 cpu's, 10 servers, website, helpdesk, testing center, etc.
-
Sounds like fixing your corrupt Domain is your only fix then.
Sounds like it would likely be worth a $400 ticket to MS for support - and if they can't fix it, they will likely refund you.
-
Having done both, I would recommend building the new one. Yes it will be a pain to move things over, but you can do most of the server side work in isolation. You'll have a long weekend switching everyone over to the new domain, but it is doable in a fairly reasonable amount of time.
-
@kelly Thanks. Things are starting to pan out that way it seems.
-
One of the benefits of keeping the old domain alive is that you can move the end-users one at a time. Yeah you'll have to do all your member servers in one shot, but you can move your end users one at a time at your leisure.
-
@g-i-jones said in New to server builds. Making new DC on domain.:
@scottalanmiller damn. Yea too many things already ride on our current domain, so we're trying to dodge a migration to a new domain if we can. Still thinking about our best course of action.
What kind of things? Things should not be tied overly to a domain, too much to go wrong.
-
@g-i-jones said in New to server builds. Making new DC on domain.:
@Dashrender roughly 100 cpu's, 10 servers, website, helpdesk, testing center, etc.
That's all easy stuff, though. If the domain is corrupt, you are going to be moving. Best to make it all as simple and reliable as possible.
-
@g-i-jones said in New to server builds. Making new DC on domain.:
@kelly Thanks. Things are starting to pan out that way it seems.
Also, use this chance to consider if there are pieces that don't need to be on the domain. Might lessen the conversion process.
