SBS 2008 Migration to Windows 2012 Essentials

Hello,
I have a new VMware ESXi 5.5 host that I am creating a new Windows 2012 Essentials virtual server on.  I am migrating from a Windows SBS 2008 server to the new Windows 2012 Essentials server but I am running into a problem when entering the domain information on the destination server.  The error I get is "Your full domain name is not correct or reachable."  I am able to ping the IP and FQDN of the source server from the destination server and I am able to ping the destination server IP address from the source server.

Can someone help me?
blkfootAsked:
Who is Participating?
 
blkfootConnect With a Mentor Author Commented:
Thanks for the reply, Jeff.  Yes, I did follow all of the steps in that doc and no DHCP isn't running on the SBS 2008 server.  

The fix ended up being DNS on the source server.  After running DCDIAG and having it fail trying to resolve the GUID of the source server in the _msdcs folder I FINALLY found a comment that outlined the correct way to fix that problem.

Rename nelogon.dnb and netlogon.dns
net stop netlogon
ipconfig /flushdns
ipconfig /registerdns
net start netlogon
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Have you followed ALL of the steps outlined in the migration preparation documentation:
http://technet.microsoft.com/en-us/library/jj200165.aspx ??

Is DHCP running on your SBS 2008?

Jeff
0
 
blkfootAuthor Commented:
Found the resolution  FINALLY in a comment on a post.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Just curious -- the SBS BPA didn't pick up the DNS error on the source server?
0
 
blkfootAuthor Commented:
It did and when I followed the KB to resolve the DNS issue it had me remove the _msdcs folders which then created this issue when it came up that it couldn't find the GUID.  I basically chased the DNS tail for awhile with different KBs until I came across the correct way to recreate the _msdcs folders.  After I was able to enter the domain on the Essentials server it did also prompt me at that time that there was a DNS issue but since I'd been down that road already I bypassed and finished the migration.

I'm a little disappointed in Microsoft on this one.  I feel like they identified the DNS problem but then created a different problem by resolving the first problem.
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
It doesn't make sense that there would be instructions to REMOVE the _msdcs zone completely without putting it back.  Often, I've found that it is in the wrong location (nested inside the default domain's forward lookup zone rather than as a separate forward lookup zone -- this occurs when the domain has been upgraded from older systems).

Usually, the BPA leads you to this article:
http://technet.microsoft.com/en-us/library/ff807395(WS.10).aspx

Which describes how to recreate it.

Anyhow, glad you're moving forward.

Jeff
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.