Small Business Server 2003 to 2012 R2 Migration and Virtualized Domain Controller Questions

DenisKelley

Wow. A ton of posts from beginning to end of this process. I almost feel like the community just helped deliver a baby.

Dashrender

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

scottalanmiller

@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

garak0410

As ignorant as my posts may have looked during this process...now that is complete, it makes so much more sense now...

scottalanmiller

Lots of little pieces in that puzzle

IRJ

@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.

garak0410

@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...

Dashrender

We all have to learn some how. And you did well looking for help from real people with experience.

scottalanmiller

This is definitely a great thread example. Hopefully some people share it on Twitter or Facebook

garak0410

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.aspx

And 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?

IRJ

@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.aspx
And 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.

IRJ

This post is deleted!

Dashrender

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.

garak0410

@Dashrender

Right, I do need to migrate DNS off the old server...VPN services are also still there...

scottalanmiller

DNS should be transparent. The two servers both run DNS. Then just make sure that everyone is pointing primarily to the new one or, to be extra sure, exclusively to the new one. Then just turn off the service on the old one. DNS is one of the easiest services to migrate.

scottalanmiller

I believe that this is our first thread to top 300 posts.

Nara

@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.

Mangolassies sounds nice. Are the guys Mangoladdies?

scottalanmiller

I think so.

Dashrender

As good a name as any

garak0410

@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.aspx
And 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?

I'm doing all remaining steps tonight...before I demote the old one, can it be tested by simply shutting down the old server before I demote, to make sure the new DC is handling it OK?