[Today's post comes to us courtesy of Roderick White, David Copeland and Damian Leibaschoff from Commercial Technical Support]
The Windows Small Business Server 2011 Standard Migration Preparation Tool is included in the Windows Small Business Server 2011 Standard installation media. This tool is run on the migration source server (for example, a computer that is running Windows Small Business Server 2003 or Windows Small Business Server 2008) to prepare the source server for migration . This tool performs the following tasks on the source server:
This update is a critical step in helping prevent known causes that can lead to a failure during the migration setup.
To get the latest set of rules, when you launch the tool, select the option to check for updates.
For details check the following article:
2578426: An update for the Windows Small Business Server 2011 Standard Migration Preparation To...
For the out of box existing rules check the following article:
2481235: List of rules for the Windows Small Business Server Migration Preparation Tool
You might hit Sub Rule 7 from the update (KB 2578426) unexpectedly.
Error is found in DNS Zone [DNS zone name]
Description: DNS zone [DNS zone name] does not exist. Migration will fail without fixing this issue. Go to http://support.microsoft.com/kb/2578426 for more details.
There are 2 causes that can lead to this unexpected error besides the issues discussed in the KB article.
if your _MSDCS zone is not a forward lookup zone delegated from your primary domain zone. you may see the error.
The check expects your _MSDCS zone to be delegated like this:
If your _MSDCS is a subdomain (see screenshot below), then the check will fail.
You will have to remove the _MSDCS subdomain, create a new AD integrated forward lookup zone for _MDCS.domain.local (replace domain.local with the name of your domain), and finally create a delegation for _MSDCS under your domain.local primary lookup zone pointing back to the name servers in your domain (your own server only in most SBS networks). Restart the netlogon service, confirm that the new _MSDCS zone gets populated.
This is a known issue and a long term resolution is being investigated.
If the microsoftDNS namespace is missing from the WMI repository this query will fail. To test this open a Powershell command prompt as an administrator and run the following command:
Get-wmiobject –namespace root\MicrosoftDNS –class “MicrosoftDNS_Zone”
If you have this issue you will get an Get-WmiObject : Invalid namespace error.
Use the following steps to resolve this issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.