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
*C:\Windows\Temp\Client Deployment Files\ServerInfo.Xml*
2. Find the following contents:
3. Manually change the *DomainNetBiosName *value per your network
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.