My 2 Windows 7 Pro computers cannot complete connection to WHS 2011 ("WHS 2011 Connector has encountered an unexpected error) - run out of suggestions RRS feed

  • Question

  • I have thecommon problem of being unable to connect from 2 Windows 7 Pro 64-bit computers (Cannot connect this computer to the nmetwork, An unexpected error has occurred....). and have tried ALL the suggestions listed above. I have checked IIS settings on the server, My server is found, microsoft.net framework is installed, I enter correct password,  I can RDP, ping both name and IP address, have disabled IP6, tuned off firewall and microsoft security essentials, added hosts statement server, Windows Media Center services are set to ‘Manual', and uninstalled and reinstalled 

    My error message is as follows, on both machines:



    In c:\ProgramData\Microsoft\Windows Server\ClientDeploy.log


    [11060] 120202.200559.9344: ClientSetup: Start of ClientDeploy

    [11060] 120202.200600.0194: General: Initializing...C:\Windows\Temp\Client Deployment Files\ClientDeploy.exe

    [11060] 120202.200600.0314: ClientSetup: Loading Wizard Data

    [11060] 120202.200600.1924: ClientSetup: Current DeploymentStatus=Running

    [11060] 120202.200600.3924: ClientSetup: Showing the Client Deployment Wizard

    [11060] 120202.200600.4864: ClientSetup: Adding Server Info data in the Product Registry

    [11060] 120202.200600.5084: ClientSetup: Set the Deployment Sync Event

    [2732] 120202.200604.9277: ClientSetup: Running ValidateUser Tasks at WizardPage HomeServerCred

    [2732] 120202.200604.9427: ClientSetup: Entering ConnectorWizardForm.RunTasks

    [2732] 120202.200604.9427: ClientSetup: Running Task with Id=ClientDeploy.ValidateUser

    [2732] 120202.200604.9527: ClientSetup: Entering ValidateUserTask.Run

    [2732] 120202.200604.9537: ClientSetup: Install root cert to local trusted store

    [2732] 120202.200604.9607: ClientSetup: Validating User

    [2732] 120202.200604.9607: ClientSetup: Call MachineIdentityManager.GetMachineStatus

    [2732] 120202.200607.0158: ClientSetup: MachineIdentityManager.GetMachineStatus had errors: ErrorCatalog:ProviderNotAvailable ErrorCode:-1

    BaseException: Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityException: MachineIdentityManager.GetMachineStatus

       at Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityManager.GetMachineStatus(String serverName, String userName, String password, String machineName, Boolean& isAdmin)

       at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.ValidateUserTask.Run(WizData data)

    [2732] 120202.200607.0168: ClientSetup: Exiting ValidateUserTask.Run

    [2732] 120202.200607.0168: ClientSetup: Task with Id=ClientDeploy.ValidateUser has TaskStatus=Failed

    [2732] 120202.200607.0168: ClientSetup: Task with Id=ClientDeploy.ValidateUser has RebootStatus=NoReboot

    [2732] 120202.200607.0168: ClientSetup: Exting ConnectorWizardForm.RunTasks

    [11060] 120202.200607.0218: ClientSetup: JoinNetwork Tasks returned TaskStatus=Failed

    [11060] 120202.200610.2060: ClientSetup: Back from the Client Deployment Wizard

    [11060] 120202.200610.2110: ClientSetup: Saving Wizard Data

    [11060] 120202.200610.2170: ClientSetup: End of ClientDeploy: ErrorCode=1603



    Thursday, February 2, 2012 10:12 AM

All replies

  • I don't know if you have found an answer yet, but I found that not only had the media services be st in manual as soon as I started them I was able to complete the connector installation.  This Media Center services, both of them.  Hope this helps.
    Thursday, February 9, 2012 3:13 PM