Small Business Server 2003 to 2012 R2 Migration and Virtualized Domain Controller Questions
-
I'm about to do the next step:
§ Prepare your Domain for your new Server 2012 R2 Domain Controllers □ Run adprep /forstprep from the 2012 DVD on the old server.Is it safe to run during business hours or should I wait?
-
I would generally wait until after hours but should be pretty safe in most environments. AD is rarely something that an SMB depends on minute to minute.
-
@scottalanmiller said:
I would generally wait until after hours but should be pretty safe in most environments. AD is rarely something that an SMB depends on minute to minute.
Tempting to do now...but I can VPN around 5:30 and run it too.
-
Yeah. If you can do that, it is a better way to go.
-
@scottalanmiller said:
Yeah. If you can do that, it is a better way to go.
OK, so Adprep tonight. Question when looking slightly ahead at my list past ADPREP. If I promote my new DC to a Domain Controller, when does it eventually inherit the name of the soon to be old domain controller? I don't see that option in my list and in this thread even, it is said it can remain the same domain name.
-
It doesn't. You don't name servers the same thing as old servers.
-
@scottalanmiller said:
It doesn't. You don't name servers the same thing as old servers.
I hope I didn't confuse everyone again. I understand server name is different but the domain name. I thought I read where it can remain the same
Earlier Question: "If I migrate, the domain remains the same, correct? Dashrender said Yes"
and if so, was wondering at what step does it take over the name of the current domain. Sorry for the confusion...
-
The domain name does remain the same. It's the name of the entire domain. There is no other name at any time.
Every machine in a domain whether a node, a DC member or the forest root all share the same name. So the "rename" happens the moment you join the new server to the domain.
And in DNS, the moment you make it a DC it will have an equal share in the DNS round robin name resolution of the domain.
-
@scottalanmiller said:
The domain name does remain the same. It's the name of the entire domain. There is no other name at any time.
Every machine in a domain whether a node, a DC member or the forest root all share the same name. So the "rename" happens the moment you join the new server to the domain.
And in DNS, the moment you make it a DC it will have an equal share in the DNS round robin name resolution of the domain.
That makes a little more sense...I think.
-
Another curve ball. New backup software wasn't in the budget and the only way our current suite (Backup Assist) backs up AD only if it runs on the Domain Controller. It can backup files remotely but can only backup AD on the AD machine. So, unless I can get another backup solution (doubtful), I'll have to run backups from the Domain Controller and thus, I may need to bump up the memory some.
-
There is some weird terminology there. What is "the AD machine" mean?
-
@scottalanmiller said:
There is some weird terminology there. What is "the AD machine" mean?
(Masking the real names with generic names)
Current Domain Controller
Name: servernamedc
Domain: domainname.localNew Domain Controller (Virtual)
Name: newserverI think what I am trying to explain and get an answer to...I want the domain domainname.local to remain the same when it migrates to the new domain controller. I do understand that it will be a new server name. Check. But I've been told in this threat and another one, that the domain name can and will remain the same post migration. If that is true so far, I'll follow up with secondary questions.
SO appreciate your patience.
-
The domain name will point to all DCs equally.
-
@scottalanmiller said:
The domain name will point to all DCs equally.
So at one point of this migration, both servers will be handing the domain, correct?
-
@garak0410 said:
@scottalanmiller said:
The domain name will point to all DCs equally.
So at one point of this migration, both servers will be handing the domain, correct?
Yes. Until you decommission the old one they will be an application cluster.
-
@scottalanmiller said:
@garak0410 said:
@scottalanmiller said:
The domain name will point to all DCs equally.
So at one point of this migration, both servers will be handing the domain, correct?
Yes. Until you decommission the old one they will be an application cluster.
Excellent...sorry, this would be easier if I could TALK rather than type.
My roadblock now is backups since our current solution wants to run on the domain controller to backup AD. I guess it can but I was really moving toward it being the domain controller and nothing else. Everything I look at a glace shows to be $1000 or more per license per server.
-
That's the issue. "the" domain controller is equally either box for a while. So you should be fine.
Now any software with that requirement needs to be eliminated ASAP. Backup should not run there.
-
How many VMs will you have when you are all done?
-
It is hard to imagine that you are not in the "free" backup envelope. How many VMs and how many physical hosts total will you have when the migration is all done?
-
@scottalanmiller said:
It is hard to imagine that you are not in the "free" backup envelope. How many VMs and how many physical hosts total will you have when the migration is all done?
It is Backup Assist. It is basically a glorified NT Backup. It has served us well.
Since I won't be repurposing the old server for a few weeks, once demoted, we will have the following:
New Server (Hypervisor)
VM1: Domain Controller
VM2: Services (File, Print, Web, Anti-Virus) (need file backup here)SQL Server (Physical) - We just backup SQL with Backup Assist.
Misc - Some of our shop machines have local SQL that we also backup with BackupAssist.
As mentioned, in order to backup AD, BackupAssist has to be ran from the Domain Controller where it also can backup remote files (including the files on VM2)
So, I am open to other free or low cost solutions where I can backup AD, SQL (with options for Transaction Logs), File Server and any other remote PC from a location other than the Domain Controller.
