Small Business Server 2003 to 2012 R2 Migration and Virtualized Domain Controller Questions
-
After first Robocopy completed, I rebooted my VM for my file server. Immediately, it is at 95% memory usage (7.5 GB out of 8GB). I turned it off, turned DYNAMIC memory OFF and bam...looks much better.
-
Awesome
-
Big round of applause for all of the tips I got here. It looks like my file server migration went quite well. A few minor things today:
As it would happen, we had a power surge and the battery backups for the old server (domain controller) both went nuts and turned the server off. I assume since the other roles haven't been officially moved to the new Domain Controller is why no one had any DNS services.
One of our VBA programs has messy, messy code and it's all over the place. Any job made prior to the file server would not open unless I restored sharing to the folder on the old server that contains the code for this project. So, the workaround works but adding this fix to my list.
Beyond some users needing to log out and in a few times to get their login scripts right and some typos I made in the script,, I couldn't be happier.
I guess I will be planning on the eventual demotion of the old DC...
-
Once you think you have everything moved off the old server, turn it off for a few days (before you move the FSMO roles) You don't need the server with the roles running all the time (OK maybe PDC emulator might be nice to keep live). If there are no complaints you know you are good to go moving the FSMO roles and turning the old server off.
-
DNS is not affected by roles. DNS is not tied to AD. Two separate services. Are you sure that people's desktop are pointing to the new machine for DNS? Use nslookup to test.
-
@scottalanmiller said:
DNS is not affected by roles. DNS is not tied to AD. Two separate services. Are you sure that people's desktop are pointing to the new machine for DNS? Use nslookup to test.
Agreed...now that I've had time to think, this may go back to my static assignments and not using DHCP...adding to list...
-
that would do it. -
Wow. A ton of posts from beginning to end of this process. I almost feel like the community just helped deliver a baby.
-
@DenisKelley said:
Wow. A ton of posts from beginning to end of this process. I almost feel like the community just helped deliver a baby.
And ever better - We didn't get mod'ed for going off topic
-
@Dashrender said:
@DenisKelley said:
Wow. A ton of posts from beginning to end of this process. I almost feel like the community just helped deliver a baby.
And ever better - We didn't get mod'ed for going off topic
FTW
-
As ignorant as my posts may have looked during this process...now that is complete, it makes so much more sense now...
-
Lots of little pieces in that puzzle
-
@garak0410 said:
As ignorant as my posts may have looked during this process...now that is complete, it makes so much more sense now...
You cant be that ignorant. You just did a major migration on your own. Sure alot of Mangolassies gave you info, but no one remoted in your server and did the work.
-
@IRJ said:
@garak0410 said:
As ignorant as my posts may have looked during this process...now that is complete, it makes so much more sense now...
You cant be that ignorant. You just did a major migration on your own. Sure alot of Mangolassies gave you info, but no one remoted in your server and did the work.
Just a little humility...
-
We all have to learn some how. And you did well looking for help from real people with experience.
-
This is definitely a great thread example. Hopefully some people share it on Twitter or Facebook
-
Well, I am in a position where I do need the CNAME of the old server in place so we can fix an in house software quirk.
Going back to my check list, this appears to be the next step:
§ 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.aspxAnd all of the suggestions lead to that I can do this during business hours....so, taking this step by step. OK to proceed as according to the link above?
-
@garak0410 said:
Well, I am in a position where I do need the CNAME of the old server in place so we can fix an in house software quirk.
Going back to my check list, this appears to be the next step:
§ 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.aspxAnd all of the suggestions lead to that I can do this during business hours....so, taking this step by step. OK to proceed as according to the link above?
You can do it during business hours, but I wouldn't.
-
This post is deleted! -
FSMO roles should be no problem transfering during the day, I've done it many times in the past, never had a problem.
Even demoting it shouldn't be an issue.
Where you can run into an issue is if DHCP and DNS are still active on the old server. And in reality, as long as it remains a domain member you could/should be OK with those - but you should migrate them off that box before you demote it to make the system more clean.
