Domain and netbios mismatch

Domain and netbios mismatch

SBS 2011 Essentials domain name and netbios name mismatch

When migrating from SBS 2003 to SBS 2011 essentials you may find that you hit an error where you cannot join the clients with the connect computer wizard.  If the netbios domain name is longer than 15 characters, the SBS 2003 will truncate the name and continue, the SBS 2011 essentials will have issues running the wizard.
In addition there can be times when the netbios and the domain name end up with different characters and thus the wizard will fail as well:

The domain name is dom-name.local and the netbios domain name is DOMNAME. Works fine in all regards except when trying to run the ComputerConnector.exe program to add the existing domain computers to the SBS 2011 Essentials dashboard. ComputerConnector.exe fails with an error saying “This computer is already connected to another Windows server.” Reviewing the CSetup.log file shows the following lines:


[02/10/2012 12:28:09 1ca4] NetJoinChecker::QueryNetJoinStatus - Compare domains xml: ServerDomain=dom-name ClientDomain=DOMNAME
[02/10/2012 12:28:09 1ca4] NetJoinChecker::QueryNetJoinStatus - Domain Joined, but to a different domain
[02/10/2012 12:28:09 1ca4] CSetup::RunTasks: Running Task: Id=-1 Description=Check Pending Reboot Index= 2
[02/10/2012 12:28:09 2594] CSetup::ReqsErrorDlgProc: IDD_PROPPAGE_REQS_ERROR Initialization
[02/10/2012 12:28:09 2594] NetJoin not valid, JoinStatus=4.
[02/10/2012 12:28:36 2594] wmain: End of CSetup: hr=0x80004005

In order to work around this issue, you can edit the ServerInfo.Xml file on the client machine and complete the wizard.

This solution (edit the xml file - see below) worked great, although timing was critical. You have to start the Connect Computer wizard, let it pause at the first screen, and then modify the xml file. After that, the wizard ran fine.

1. On the client machine, edit the *ServerInfo.Xml* file at the
following location:

*C:\Windows\Temp\Client Deployment Files\ServerInfo.Xml*

2. Find the following contents:

<DomainNetBiosName>*TEST*</DomainNetBiosName>

<DomainDnsName>*TestDomain.local*</DomainDnsName>

3. Manually change the *DomainNetBiosName *value per your network
settings.

After that, please running CSetup from the temp folder above.

At this time, the client should be able to run the connect computer wizard successfully.


Sort by: Published Date | Most Recent | Most Useful
Comments
  • I don't understand why, but my WHS2011 server now appears as "SERVER" instead of by its name, leading to lots of woe trying to establish the trust relationship, since the name didn't match what appeared in the certificate.  This trick worked, but I had to change the <ServerName> in addition to the <DomainNetBiosName> in the ServerInfo.Xml file to get the connector software to work.  Thank you so much!

Page 1 of 1 (1 items)