Small Business Server 2003 to 2012 R2 Migration and Virtualized Domain Controller Questions
-
Why demote so soon? I would wait a bit longer than that.
-
You have at least 15 days if not longer before this server will start shutting down on it's own. Give yourself plenty of time to make sure all things work.
Did you setup DHCP for the client computers?
-
Definitely wait a little while. My rule of thumb is no less than a week, even in really small environments. Gives me enough time to verify that there are no replication issues going on.
Garak is giving me some 70-410 practice over on another forum
-
It's looking good y'all! I'm gonna buy everyone pizza or coffee when this is done!
The next step on my list is this:
•Transfer FSMO Roles to new Server 2012 R2 Domain Controller
Transfer all 5 or one at a time and start demoting your old Server 2003 DC's in the next step. But the key to remember is to NOT demote any of the current domain controllers that have any of your FSMO roles on them. Be sure to transfer them off first before proceeding to DC demotion.
http://blogs.technet.com/b/canitpro/archive/2013/05/27/step-by-step-active-directory-migration-from-windows-server-2003-to-windows-server-2012.aspxStick with this?
-
@Dashrender said:
You have at least 15 days if not longer before this server will start shutting down on it's own. Give yourself plenty of time to make sure all things work.
90 days I think. Need to look that up.
-
And the timer doesn't start when this one is added. It starts when the FSMO roles are moved.
-
OK, so what is really recommended next? Run off both DC's for a good while? Since my old DC was my file server as well, I am wanting to get that moved. So perhaps move on to that this Friday evening. That is where the DHCP may come into play. And changing some of our messy VBA apps code to point to new file server.
-
Most people have said just ROBOCOPY the files from the old file server (in this case, SBS 2003) to the new one (2012 R2 Virtual Machine) and it will keep the permissions intact and echo the different server name...correct?
-
@garak0410 said:
Most people have said just ROBOCOPY the files from the old file server (in this case, SBS 2003) to the new one (2012 R2 Virtual Machine) and it will keep the permissions intact and echo the different server name...correct?
Something like this should suffice: robocopy /mir /sec /secfix "source" "destination"
-
@garak0410 said:
Most people have said just ROBOCOPY the files from the old file server (in this case, SBS 2003) to the new one (2012 R2 Virtual Machine) and it will keep the permissions intact and echo the different server name...correct?
It will keep permissions.
What do you mean by echoing a server name?
-
@garak0410 said:
Most people have said just ROBOCOPY the files from the old file server (in this case, SBS 2003) to the new one (2012 R2 Virtual Machine) and it will keep the permissions intact and echo the different server name...correct?
I am running a robocopy from an old file server to a new one right now. I have been slowly robycopying everything over to the new server. Yes it will keep all the permissions.
-
@garak0410 said:
Most people have said just ROBOCOPY the files from the old file server (in this case, SBS 2003) to the new one (2012 R2 Virtual Machine) and it will keep the permissions intact and echo the different server name...correct?
After you decommission the old server, just create a DNS forwarder. That will forward all requests for the Old Server name to the New Server Name
-
@IRJ said:
@garak0410 said:
Most people have said just ROBOCOPY the files from the old file server (in this case, SBS 2003) to the new one (2012 R2 Virtual Machine) and it will keep the permissions intact and echo the different server name...correct?
After you decommission the old server, just create a DNS forwarder. That will forward all requests for the Old Server name to the New Server Name
CNAME (alias) he means.
-
@scottalanmiller said:
@IRJ said:
@garak0410 said:
Most people have said just ROBOCOPY the files from the old file server (in this case, SBS 2003) to the new one (2012 R2 Virtual Machine) and it will keep the permissions intact and echo the different server name...correct?
After you decommission the old server, just create a DNS forwarder. That will forward all requests for the Old Server name to the New Server Name
CNAME (alias) he means.
yeah exactly. Its been a long day
-
@IRJ said:
@scottalanmiller said:
@IRJ said:
@garak0410 said:
Most people have said just ROBOCOPY the files from the old file server (in this case, SBS 2003) to the new one (2012 R2 Virtual Machine) and it will keep the permissions intact and echo the different server name...correct?
After you decommission the old server, just create a DNS forwarder. That will forward all requests for the Old Server name to the New Server Name
CNAME (alias) he means.
yeah exactly. Its been a long day
Heck...that makes my life easier for now. I could even complete this tonight if I didn't have to play Soccer Dad.
-
I told you about using the CNAME process at the beginning of this process
-
My RoboCopy tests have proven to be good so far. I see the domain level permissions!
-
@scottalanmiller said:
I told you about using the CNAME process at the beginning of this process
My memory is fading when I spend 2 hours trying to explain to our office manager why scanning in a 500 page project in our copier make it run out of memory and I cannot change that fact...
-
You can only use the CNAME after you turn off the old server.
-
Don't forget, before you turn off the old server you should DCPromo it to remove it from the Active Directory. Then you can turn it off and delete the records from the DNS server.
