Small Business Susan

Rob hit another issue with his SBS 2011 Essentials migration from SBS 2003:  “I couldn’t connect this one workstation to the network; the ClientDeploy log showed the error as InvalidOwnerOfMachine.  The problem is fully described at http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver2011essentials/thread/d44b1dca-8327-4355-84c9-619f724e16cd . 

The log file showed the following:

[2108] 110913.145924.7363: ClientSetup: Entering JoinNetworkTask.Run
[2108] 110913.145924.7363: ClientSetup: Network Join Client to Server: ClientComputerName=LABDELLD610-2 ServerName=ALPHA
[2108] 110913.145924.7363: ClientSetup: Maximum amount of joined machines: 30
[2108] 110913.145924.7363: ClientSetup: Current amount of joined machines: 4
[2108] 110913.145924.7363: ClientSetup: Server already contains a computer joined with Client Machine Name
[2108] 110913.145924.7363: ClientSetup: Network Join has been forced
[2108] 110913.145924.7363: ClientSetup: Running Network Join
[2108] 110913.145924.7363: ClientSetup: Call MachineIdentity.GetCert
[2108] 110913.145928.1318: ClientSetup: JoinNetwork had errors: ErrorCatalog:InvalidOwnerOfMachine ErrorCode:-1
BaseException: Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityException: MachineIdentityManager.GetCert
at Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityManager.GetCert(String serverName, String userName, String password, Boolean bForce)
at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.JoinNetworkTask.Run(WizData data)
[2108] 110913.145928.1318: ClientSetup: Exiting JoinNetworkTask.Run
[2108] 110913.145928.1328: ClientSetup: Task with Id=ClientDeploy.JoinNetwork has TaskStatus=Failed
[2108] 110913.145928.1328: ClientSetup: Task with Id=ClientDeploy.JoinNetwork has RebootStatus=NoReboot
[2108] 110913.145928.1328: ClientSetup: Exting ConnectorWizardForm.RunTasks
[3560] 110913.145928.1396: ClientSetup: JoinNetwork Tasks returned TaskStatus=Failed

Their solution didn’t work for me, however.  The only way I could get the Connect Computer wizard to successfully run was to use the domain admin account when the wizard asked for network name and password.  After the wizard completed I restarted and logged in as the correct user, and all was well.