13 Eylül 2011 Salı 20:16
I'm still trying to figure out migration of a SBS2003 network to SBS2011 Essentials.
This machine is running Win7, and was already connected to the old domain that was migrated.
I ran Connect, and after taking the user account name and password I get this screen:
I looked at the ClientDeploy log file, and the important lines look like:
 110913.145924.7363: ClientSetup: Entering JoinNetworkTask.Run  110913.145924.7363: ClientSetup: Network Join Client to Server: ClientComputerName=LABDELLD610-2 ServerName=ALPHA  110913.145924.7363: ClientSetup: Maximum amount of joined machines: 30  110913.145924.7363: ClientSetup: Current amount of joined machines: 4  110913.145924.7363: ClientSetup: Server already contains a computer joined with Client Machine Name  110913.145924.7363: ClientSetup: Network Join has been forced  110913.145924.7363: ClientSetup: Running Network Join  110913.145924.7363: ClientSetup: Call MachineIdentity.GetCert  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)  110913.145928.1318: ClientSetup: Exiting JoinNetworkTask.Run  110913.145928.1328: ClientSetup: Task with Id=ClientDeploy.JoinNetwork has TaskStatus=Failed  110913.145928.1328: ClientSetup: Task with Id=ClientDeploy.JoinNetwork has RebootStatus=NoReboot  110913.145928.1328: ClientSetup: Exting ConnectorWizardForm.RunTasks  110913.145928.1396: ClientSetup: JoinNetwork Tasks returned TaskStatus=Failed
I don't know what InvalidOwnerOfMachine might mean. I've looked at the active directory tree on my server, and this machine is in the same location as all of my other machines, and looking at the properties, it wasn't managed by anyone. Who would be declared the owner of the machine?
13 Eylül 2011 Salı 23:57
 110913.145924.7363: ClientSetup: Server already contains a computer joined with Client Machine Name
Hi: Is there any chance that the above might be the operative error?
- Düzenleyen Larry Struckmeyer [SBS-MVP]MVP 13 Eylül 2011 Salı 23:59
14 Eylül 2011 Çarşamba 00:43
It shouldn't be the operative error. This is a migration, so the machine that exists in the active directory tree is the exact same machine that I'm trying to get the connector software installed on.
The machine seems to be happy participating in the domain with the new domain controller, but I want to get the benefits of backup and dashboard control.
The account I'm trying to use to install the connector software is a member of the local machine administrators, named LAB. I'm wondering if this is all related to the fact that the active directory tree is named Dallas.RFSAW.com because of the migration instead of being a more simple domain something like RFSAW.local ?
20 Eylül 2011 Salı 12:36ModeratörWhat account are you using / credentials to install the connector?
Robert Pearman SBS MVP (2011) | www.titlerequired.com | www.itauthority.co.uk
22 Eylül 2011 Perşembe 01:44
Today I finally figured out a workaround that got this particular machine to install the connector software and be properly backed up. I'm still having problems with some of the other machines but here was my solution for this particular problem:
Create new LOCAL account on the machine that is a member of the local administrators group.
Log in with the LOCAL account and run the http://server/connect/ installation. Give it my NETWORK credentials when it asks. The installation completed successfully. I rebooted the machine and was able to log in with my standard NETWORK credentials, and the profile information appeared unchanged except for the installation of the new software, and the SBS control panel software that loaded automatically.
I plan to either disable or delete the LOCAL account on the machine again sometime soon for security, but at least this seems to have gotten this machine correctly configured to talk to the server.
- Yanıt Olarak İşaretleyen William C Bonner 22 Eylül 2011 Perşembe 01:45