Small Business Server 2003 to 2012 R2 Migration and Virtualized Domain Controller Questions
-
You will use robo copy more than one time. This can all be done at anytime:
- Turn up your new server
- Copy files with robocopy
- Go to Share management and add share permissions
- test shares
Now wait until maintenance window
- rerun robocopy to get changes
- change logon scripts
- disable sharing on old server
- force all workstations to reboot
Old server should still be online for YOU to get data from, but all users should now be on new file server.
-
Something I haven't seen mentioned here, When you join another DC to your SBS Domain, you have either 15 or 25 days (I just can't remember now) to turn off the old SBS server or it will start turning itself off - FYI.
-
@Dashrender said:
Something I haven't seen mentioned here, When you join another DC to your SBS Domain, you have either 15 or 25 days (I just can't remember now) to turn off the old SBS server or it will start turning itself off - FYI.
That timer only starts after you promote it. As a member DC it can be there indefinitely.
-
@scottalanmiller said:
@Dashrender said:
Something I haven't seen mentioned here, When you join another DC to your SBS Domain, you have either 15 or 25 days (I just can't remember now) to turn off the old SBS server or it will start turning itself off - FYI.
That timer only starts after you promote it. As a member DC it can be there indefinitely.
Good thing - I just added a new DC to a SBS 2003 domain this afternoon as a member DC and then saw this thread. I was starting to worry a little after that previous comment.
-
SBS has to be a forest root but can have as many members as you want.
-
@scottalanmiller said:
SBS has to be a forest root but can have as many members as you want.
Yes, it was even sold in a premium package that included a standard server license and a SQL license to install on an second box.
-
Good Morning Everyone. Reading the latest updates and slept some of the fear off.
Right now, I've created my two virtual machines and I am downloading updates to them.
VM1: Domain Controller. 2GB of RAM, 1 CPU
VM2: File Server (called services01): 4GB RAM, 2 CPU (this will also host the backup software and antivirus)When complete, I will let you know. The steps I mentioned several posts ago, I can actually complete up to the demotion and promotion part, correct? Even if the new server will contain the migrated domain name?
-
Correct you can do everything except the demote/promote parts. The new servers should be joined to the domain as member servers. There is no restriction on member servers.
-
Question about the virtual file server...it is set up and now I need it to see the D drive from the physical server so it will have its own D drive for the files.. So, when I eventually copy (RoboCopy) the files from the SBS 2003 server to the new file server...where will they be stored? In a VDISK that I attach to the VM or on the Hyper-V host physical drive? Again, sorry for a newbie question but feeling much more confident today.
-
A VHD sitting on your storage array. You should have only one place for putting VHDs in this setup.
-
OK, so for the file server VM, I am going to create a new VDISK (2 or 2.5 TB most likely) to attach to my file server for the files to copy to. Thanks...
I think it helps to take each thing step by step. I am still aiming for Friday night demotion/promotion.
-
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.
