Several services do not start when Windows Small Business Server 2003 restarts during a domain migration (839493)

SYMPTOMS

When Microsoft Windows Small Business Server 2003 restarts on a network that has an existing Small Business Server 4.5 domain or an existing Microsoft Windows NT Server 4.0 domain during a domain migration, the following symptoms may occur:

Between 30 and 40 instances of Wmiprvse.exe are running in Task Manager.
Task Manager shows the CPU usage as almost 100 percent.
Several services do not start in Windows Small Business Server 2003.
The following events are logged in the system log. Event ID: 7023
Source: Service Control Manager
Description: Could not start Service, not enough storage is available to complete this operation. Event ID: 3097
Source: Netlogon
Description: This computer is configured to be the primary domain controller of its domain. However, the computer <NT 4.0 server> is currently claiming to be the primary domain controller of the domain.

CAUSE

This behavior occurs if the Small Business Server 4.5 domain or the Windows NT Server 4.0 domain has the same NetBIOS domain name as the Windows Small Business Server 2003 domain.

RESOLUTION

To resolve this problem, make sure that Windows Small Business Server 2003 is on a different physical network than Small Business Server 4.5 and Windows NT Server 4.0 while Windows Small Business Server 2003 restarts. When all the services are restarted on Windows Small Business Server 2003, Small Business Server 4.5 or Windows NT Server 4.0 may reside on the same physical network as Windows Small Business Server 2003.

For more information about how to migrate from Small Business Server 4.5 or from Windows NT Server 4.0 to Windows Small Business Server 2003, visit the following Microsoft resource:

http://download.microsoft.com/download/6/f/a/6fa5ebc5-5a0f-4990-8833-ed24f4da4289/SBS_MigratingSBS45.doc

MORE INFORMATION

These symptoms may occur when you migrate from Small Business Server 2000 or from Windows 2000 Server to Windows Small Business Server 2003. For example, if you install Windows Small Business Server 2003 with the same NetBIOS domain name as Small Business Server 2000 or as Microsoft Windows 2000 Server and then you start the servers on the same physical network, the symptoms may occur.

For more information about how to migrate from Small Business Server 2000 or from Windows 2000 Server to Windows Small Business Server 2003, visit the following Microsoft resource:

http://download.microsoft.com/download/6/d/c/6dccf9b4-d915-4c95-b5af-100b89e02add/SBS_MigratingSBS2k.doc