none
Trouble with joining ANY computer using the connector software

    Question

  • Hi,  I'm running through the migration steps for an SBS2003 to SBS 2011 essentials migration.  I'm running into an issue joining any computer to the SBS using the connector software.  I get the same result, " an unknown error has occurred."  When I look this up, the web server advises me to make sure the WSS web server has been started, which it has.  My SBS Essentials server runs the Office 365 integration module provided by Rollup2, and the server is up to date.  Client computers that I have tried are: 1 domain joined Windows 7 32-bit, 1 non domain computer running Windows 7 32-bit, 1 non domain computer running Windows 7 x64, fresh Windows 7 install with no antivirus.  I've even changed the name of one of the computers to be "Win7" in case the hyphen in my computer names might be causing the issue.  From the log included below, it looks like it fails on getting the machine status, but I can't seem to make it work.  Also, is it possible to run the connector and not join a computer to the domain.  I basically want to install the connector for backup purposes only.

    [2116] 120228.143120.4628: ClientSetup: Start of ClientDeploy
    [2116] 120228.143121.1347: General: Initializing...C:\Windows\Temp\Client Deployment Files\ClientDeploy.exe
    [2116] 120228.143121.1503: ClientSetup: Loading Wizard Data
    [2116] 120228.143122.7128: ClientSetup: Current DeploymentStatus=Running
    [2116] 120228.143126.2910: ClientSetup: Showing the Client Deployment Wizard
    [2116] 120228.143127.1191: ClientSetup: Adding Server Info data in the Product Registry
    [2116] 120228.143127.3066: ClientSetup: Set the Deployment Sync Event
    [836] 120228.143149.2441: ClientSetup: Running ValidateUser Tasks at WizardPage DomainUserCred
    [836] 120228.143149.2597: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [836] 120228.143149.2597: ClientSetup: Running Task with Id=ClientDeploy.ValidateUser
    [836] 120228.143149.4160: ClientSetup: Entering ValidateUserTask.Run
    [836] 120228.143149.5253: ClientSetup: Install root cert to local trusted store
    [836] 120228.143149.6035: ClientSetup: Validating User
    [836] 120228.143149.6035: ClientSetup: Call MachineIdentityManager.GetMachineStatus
    [836] 120228.143205.4941: ClientSetup: MachineIdentityManager.GetMachineStatus had errors: ErrorCatalog:OtherError ErrorCode:-2146233087
    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)
    [836] 120228.143205.4941: ClientSetup: Exiting ValidateUserTask.Run
    [836] 120228.143205.4941: ClientSetup: Task with Id=ClientDeploy.ValidateUser has TaskStatus=Failed
    [836] 120228.143205.4941: ClientSetup: Task with Id=ClientDeploy.ValidateUser has RebootStatus=NoReboot
    [836] 120228.143205.4941: ClientSetup: Exting ConnectorWizardForm.RunTasks
    [2116] 120228.143205.5097: ClientSetup: JoinNetwork Tasks returned TaskStatus=Failed
    [2116] 120228.144315.8271: ClientSetup: Back from the Client Deployment Wizard
    [2116] 120228.144315.8427: ClientSetup: Saving Wizard Data
    [2116] 120228.144315.8427: ClientSetup: End of ClientDeploy: ErrorCode=1603

    Wednesday, February 29, 2012 4:27 AM

Answers

  • I ended up working with Microsoft on this.  They suspected that there was something wrong with the Certificate Authority and active directory replication between the old 2003 server and the new Essentials server.  They remove the CA, demoted the server, and had the 2003 server seize FSMO roles back from the old server. They then promoted it back to a DC, moved FSMO roles back in place, added CA, and restored the keys.  They had to fiddle around to get CA to install correctly, but once it did, it would finally connect server using the software.  Thanks everybody for your help.

    Tyler.

    • Marked as answer by TylerDo Tuesday, March 13, 2012 5:38 PM
    Tuesday, March 13, 2012 5:38 PM

All replies

  • Did you complete the certificate services part of the migration yet?

    Robert Pearman SBS MVP (2011) | www.titlerequired.com | www.itauthority.co.uk

    Wednesday, February 29, 2012 11:12 AM
    Moderator
  • Yup.  I've re-established the certificate authority per the migration steps.  I can even hit the server at https://servername:65515 and I don't have any certificate errors. 
    Wednesday, February 29, 2012 4:01 PM
  • What's the name of the user you are using to install this?
     
    Wednesday, February 29, 2012 6:11 PM
    Moderator
  • Do client and server side time, time zone and date match?
    Is the user joining local administrator on the computer?

    If so, is .NET Framework 4.0 installed and the Net.Tcp Port Sharing Service on the clients running (and configured to start under Local Service account)?

    Best greetings
    Olaf

    Wednesday, February 29, 2012 11:59 PM
  • Hi,

    I assumed that the migration from SBS 2003 to SBS 2011 Essentials is successful. Open the IE browser on the Windows 7 client, and then enter the URL: https://servername:65515/connect. If the connection between the server and client is fine you could receive the following page as followed:

     

    Then we need to click “Download Software for Windows”, the installation processing will start up. Note: We need to the administrator permission to download and install the software.

    During the installation processing, we will find some information included. Such as the .NET Framework 4.0 will be installed during the software installation.

    Then we need to enter the credentials to build up the trust relation session between the server and client. Note: You will get a Windows promotion about the account you enter, you could select Administrator or Standard account on your need.

    If the connection failed, it will display an error window. I believe the error message you have received will be a checkpoint.

    Please share the error message with us. At the same time, please look into the Event Viewer to verify whether there are some related errors or warnings included. It will give you some clues to narrow down the issue.

    As we know, the SBS 2011 Essentials are newly released. I hope you could pay attention to the Windows Small Business Server 2011 Essentials Blog.

    Regards,
    James


    James Xiong

    TechNet Community Support

    Thursday, March 01, 2012 5:13 AM
    Moderator
  • Hi Olaf,

    The client and server time match.  The user that I am joining is the local administrator on the system.  I've tried using both a normal domain user and the domain administrator's credentials.  I'll check on .net framework 4.0 and net.tcp port sharing service to see if it's running on the client.

    Thursday, March 01, 2012 1:58 PM
  • You might want to review this:

    http://social.technet.microsoft.com/wiki/contents/articles/3887.connectcomputer-troubleshooting.aspx

    And the posts linked at the bottom.


    Robert Pearman SBS MVP (2011) | www.titlerequired.com | www.itauthority.co.uk

    Thursday, March 01, 2012 8:53 PM
    Moderator
  • Also use the log collector tool and send the logs up online for us?

    Robert Pearman SBS MVP (2011) | www.titlerequired.com | www.itauthority.co.uk

    Thursday, March 01, 2012 9:07 PM
    Moderator
  • Did you enable the UPnP beacon on the Essentials Server yet?

    Robert Pearman SBS MVP (2011) | www.titlerequired.com | www.itauthority.co.uk

    Friday, March 02, 2012 10:44 AM
    Moderator
  • Hey guys,

    Sorry for the delay.  Been dealing with an SBS 2011 standard install issue for another client.  Back to this, though.  I've enabled the UPNP beacon on the server already.  I've also looked through the wiki and posts, and I don't see anything that pertains to the error messages that I get in the logs, (which I have attached to this post). I've followed this page for migration steps and have gone all the way up to joining computers to the network.

    http://onlinehelp.microsoft.com/en-us/sbs2011essentials/gg186110.aspx

    Tuesday, March 06, 2012 3:35 PM
  • Here's the logs.

    Logs

    Tuesday, March 06, 2012 3:39 PM
  • Looks like either a .net4 issue or an authentication issue.

    This might be useful.

    http://titlerequired.com/2011/08/30/joining-a-client-to-an-sbs-2011-essentials-network/


    Robert Pearman SBS MVP (2011) | www.titlerequired.com | www.itauthority.co.uk

    Tuesday, March 06, 2012 4:52 PM
    Moderator
  • Hi Robert,

    I checked out that article, and I didn't see anything that applies to my situation. 

    Thanks!

    Tyler

    Tuesday, March 06, 2012 8:30 PM
  • Ignore previous message

    Uninstall .net 4 and let the installer manually install it as part of the package.

    [03/06/2012 10:02:08  384] CoCreateInstance CLSID_DOMDocument60 succeeded.
    [03/06/2012 10:02:08  384] DotNet::QueryInstallState -  Unable to read install key [Install] from registry [SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full] error code 2
    [03/06/2012 10:02:08  384] CSetup::RunTasks: Running Task: Id=4 Description=Download Dot Net 4.0 Index=  1
    [03/06/2012 10:02:08  384] NetworkUtil::DownloadFile (HTTP://192.168.10.20:65510/Connect/default.aspx?Get=dot


    Tuesday, March 06, 2012 8:43 PM
    Moderator
  • I'm using the administrator account.  Netbios domain name of the server is agenesis (agenesis.com is the FQDN).
    Tuesday, March 06, 2012 8:45 PM
  • That error on machinekey might also be this:

    ============

     It appears that if the machine has been upgraded from Fat32 to NTFS, the rights on the Machine key folders are incorrectly set and needs Admin and System added with full rights, see http://support.microsoft.com/kb/278381   (source WHS 2011 forum )

    Tuesday, March 06, 2012 8:56 PM
    Moderator
  • I went into C:\ProgramData\Microsoft\Crypto\RSA and modified MachineKeys to allow administrators full control on the folder (from that article). I did this to both the server and the client just to be sure, and no change.
    Tuesday, March 06, 2012 9:09 PM
  • So you are a local admin on your pc.

    And the wizard fails, before if prompts you for your network credentials?

    I agree with Susan, remove .Net4 from the PC (should be 2 or 3 components)

    Also check for a c:\program files\Windws Server\ folder on the client, and remove it if it is there.


    Robert Pearman SBS MVP (2011) | www.titlerequired.com | www.itauthority.co.uk

    Tuesday, March 06, 2012 9:35 PM
    Moderator
  • It fails immediately after I put in my network credentials.
    Tuesday, March 06, 2012 9:37 PM
  • What exactly fails?
    Tuesday, March 06, 2012 9:40 PM
    Moderator
  • And immediately following this, I get the following error

    And according to the logs, it fails on a getMachineStatus command.

    Tuesday, March 06, 2012 9:46 PM
  • That should be asking for the user that will be on this workstation, not the network admin account.

    Tuesday, March 06, 2012 9:48 PM
    Moderator
  • Tried both.  Neither work.
    Tuesday, March 06, 2012 9:49 PM
  • Is the user on the box the same user that was domain joined to the SBS 2003?

    Also can you remove the .net 4 from that system if you have not done so already?

    Tuesday, March 06, 2012 9:51 PM
    Moderator
  • No, the user is different.  This is a fresh Windows 7 install with a user named "Setup."  It's the only user on the box.  .Net has been removed from the system.

    Tuesday, March 06, 2012 9:53 PM
  • You named the user setup?

    Can you try this with another name ... like Fred or something as if you are using setup that's probably a reserved name.

    Tuesday, March 06, 2012 9:56 PM
    Moderator
  • I created a user named Fred with a password of Fred.  Gave him local admin rights on the computer.  Had .Net 4 removed.  Ran the wizard and supplied network credentials of a user.  It still fails with the same issue.

    Tuesday, March 06, 2012 10:01 PM
  • Win7 clean install.  This is not making sense.  Is the user set up on the essentials already in the domain as a user?
    Tuesday, March 06, 2012 10:03 PM
    Moderator
  • Fred is not, but the user that I'm using for network credentials is.  It's not a wrong password, because if I type in an incorrect password or a user that doesn't exist in the system, I get a prompt that the username and password is incorrect.
    Tuesday, March 06, 2012 10:07 PM
  • Try this flow.  Set Fred up on the box as a user.  Then use Fred's credentials to run the wizard.

    Tuesday, March 06, 2012 10:08 PM
    Moderator
  • By box you mean on the server, right?

    Tuesday, March 06, 2012 10:09 PM
  • On the server, set up a user of Fred that will be a domain user.

    Go to the workstation and run the wizard.  I personally have found that in the first part of the wizard where it asks if you are setting this up on behalf of someone I do that, enter my domain network credentials, and then in the next section where it says "whom do you want to assign this to" I will then enter Fred who has been set up wtih credentials on the server.

    Run it like that, if it STILL barfs, post up the log files again.

    Tuesday, March 06, 2012 10:13 PM
    Moderator
  • Changed the password for Fred on the machine, since it didn't match the policy on the server.  Created a user named Fred with the same password on the server.  Logged off the machine as Fred and logged back in.  Ran the program and it still creates the same error message.

    Here's the log

    Tuesday, March 06, 2012 10:24 PM
  • MachineIdentityManager.GetMachineStatus

    What's the name of the local computer?

    What (if any) add ins do you have installed/

    Wednesday, March 07, 2012 12:37 AM
    Moderator
  • After removing .NET Framework 4, did you reinstall it (and all updates)?

    Best greetings from Germany
    Olaf


    Wednesday, March 07, 2012 9:06 AM
  • Just recapping again as this thread is huge.

    SBS 2003 Migration.

    Connetcor failing after network credentials supplied - any valid credentials.

    Essentials Server is showing in the Dashboard?

    You Added the User Groups for RA_XXX and modified the memberships?

    Did you import all of the Users into the Dashboard yet?

    Again sorry if you have answered these already, just easier to get a recap.


    Robert Pearman SBS MVP (2011) | www.titlerequired.com | www.itauthority.co.uk

    Wednesday, March 07, 2012 9:40 AM
    Moderator
  • What is the status of the service Net.Tcp Port Sharing Service on the client?

    Is it started and running under Local Service account?

    Best greetings from Germany
    Olaf

    Thursday, March 08, 2012 12:31 PM
  • The Local computer name is Windows7VM.  I have Office 365 integration module installed along with Rollup2.  Keep in mind this happens on ALL computers that I've attempted to install this software on.
    Friday, March 09, 2012 12:52 AM
  • Olaf, no, I didn't reinstall it.  I let the connector install it for me.
    Friday, March 09, 2012 12:52 AM
  • The essentials server is showing in the dashboard. 

    I've created the RA_XXX user groups.  The users whose credentials that I'm using are a part of the RA_XXX groups.

    All users are in the dashboard...I needed them to be for Office 365 integration.

    No problem.  Thanks for helping out.

    Friday, March 09, 2012 12:54 AM
  • You created the groups?  They should be just there.
    Friday, March 09, 2012 12:56 AM
    Moderator
  • *Sigh*

    Yes, I agree, the groups should just be in there, but since the migration process isn't as refined as that of an SBS 2011 Standard, we are forced to create the groups ourselves.

    See

    http://onlinehelp.microsoft.com/en-us/sbs2011essentials/gg186128.aspx

    Friday, March 09, 2012 1:00 AM
  • I apologize, I forgot you were migration.

    You have update rolluup 2 installed on this server?

    If so can you remove it please to test?

    Friday, March 09, 2012 1:11 AM
    Moderator
  • Interestingly enough, I can't create new users in the dashboard, either.  It keeps throwing an error when I try to submit the user.  Something about it failing and i have to open the wizard again.
    Friday, March 09, 2012 1:14 AM
  • Hi Olaf,

    The Net.Tcp service is currently set to automatic, but isn't started.  It's running under the local service account.  I've tried at one time start it and run through the wizard, but I still encounter the same issue.

    Friday, March 09, 2012 1:20 AM
  • Removed Rollup2, and I still have the same issues.
    Friday, March 09, 2012 1:26 AM
  • Can you send me the console log to susan-at-msmvps.com

    also make sure you have rebooted the server after the removal of ur2

    Friday, March 09, 2012 1:32 AM
    Moderator
  • I ended up working with Microsoft on this.  They suspected that there was something wrong with the Certificate Authority and active directory replication between the old 2003 server and the new Essentials server.  They remove the CA, demoted the server, and had the 2003 server seize FSMO roles back from the old server. They then promoted it back to a DC, moved FSMO roles back in place, added CA, and restored the keys.  They had to fiddle around to get CA to install correctly, but once it did, it would finally connect server using the software.  Thanks everybody for your help.

    Tyler.

    • Marked as answer by TylerDo Tuesday, March 13, 2012 5:38 PM
    Tuesday, March 13, 2012 5:38 PM
  • Hi. I am running into the same error. From the logs, I see:

    [4528] 120810.143336.9239: ClientSetup: Start of ClientDeploy
    [4528] 120810.143337.0957: General: Initializing...C:\WINDOWS\Temp\Client Deployment Files\ClientDeploy.exe
    [4528] 120810.143337.1270: ClientSetup: Loading Wizard Data
    [4528] 120810.143337.5176: ClientSetup: Current DeploymentStatus=Running
    [4528] 120810.143338.1739: ClientSetup: Showing the Client Deployment Wizard
    [4528] 120810.143338.3770: ClientSetup: Adding Server Info data in the Product Registry
    [4528] 120810.143338.4239: ClientSetup: Set the Deployment Sync Event
    [3816] 120810.143410.6901: ClientSetup: Running ValidateUser Tasks at WizardPage DomainUserCred
    [3816] 120810.143410.7058: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [3816] 120810.143410.7058: ClientSetup: Running Task with Id=ClientDeploy.ValidateUser
    [3816] 120810.143410.7526: ClientSetup: Entering ValidateUserTask.Run
    [3816] 120810.143410.7995: ClientSetup: Install root cert to local trusted store
    [3816] 120810.143410.9089: ClientSetup: Validating User
    [3816] 120810.143410.9089: ClientSetup: Call MachineIdentityManager.GetMachineStatus
    [3816] 120810.143414.6902: ClientSetup: MachineIdentityManager.GetMachineStatus had errors: ErrorCatalog:OtherError ErrorCode:-2146233087
    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)
    [3816] 120810.143414.6902: ClientSetup: Exiting ValidateUserTask.Run
    [3816] 120810.143414.6902: ClientSetup: Task with Id=ClientDeploy.ValidateUser has TaskStatus=Failed
    [3816] 120810.143414.6902: ClientSetup: Task with Id=ClientDeploy.ValidateUser has RebootStatus=NoReboot
    [3816] 120810.143414.6902: ClientSetup: Exting ConnectorWizardForm.RunTasks
    [4528] 120810.143414.6902: ClientSetup: JoinNetwork Tasks returned TaskStatus=Failed

    This is a Windows 2003 to SBS 2011 Essentials migration. I have been following the migration doc's, and verified I have done it step by step. I am wondering, should I move the FSMO roles back, unpromo, repromo, re-do the Certificate authority?

    I noticed on my install that it had not created the My Businnes OU or any sub OU's. I maunally created those.... any ideas?


    Lyle Epstein
    Kortek Solutions
    http://www.korteksolutions.com

    Friday, August 10, 2012 9:54 PM
  • ok, I think I got mine fixed.

    Here is what I did.

    Logged into the old 2003 server. I looked at the event log under file replication service. I noticed that NTFRS was failing. I did indeed run dcdiag, netdiag, etc. and everything was clean before migration. Anyways, I restarted the netlogon service.

    I checked DNS and saw there were entries to another server which did not exist under _msdcs. I went through all the sub folders in DNS and checked and cleaned them properly.

    I then restarted DNS. I then forced a replication using replmon from the 2003 support tools. Everything worked correctly. I then re-ran the Wizard.

    I entered in the domain user's credentials. Got an error about I was not a network admin. Oh well. So I used the Domain Admin account. It went through the wizard just fine now. I Then saw the computer appear on the dashboard. 

    Everything seems to be functioning correctly, and no more error.

    Here is the sucess log of clientDeploy if anyone is interested:

    [5384] 120810.152047.3269: ClientSetup: Start of ClientDeploy
    [5384] 120810.152047.4831: General: Initializing...C:\WINDOWS\Temp\Client Deployment Files\ClientDeploy.exe
    [5384] 120810.152047.4987: ClientSetup: Loading Wizard Data
    [5384] 120810.152047.8894: ClientSetup: Current DeploymentStatus=Running
    [5384] 120810.152048.4050: ClientSetup: Showing the Client Deployment Wizard
    [5384] 120810.152048.6081: ClientSetup: Adding Server Info data in the Product Registry
    [5384] 120810.152048.6863: ClientSetup: Set the Deployment Sync Event
    [6812] 120810.152059.3115: ClientSetup: Running ValidateUser Tasks at WizardPage DomainUserCred
    [6812] 120810.152059.3115: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [6812] 120810.152059.3271: ClientSetup: Running Task with Id=ClientDeploy.ValidateUser
    [6812] 120810.152059.3583: ClientSetup: Entering ValidateUserTask.Run
    [6812] 120810.152059.3583: ClientSetup: Install root cert to local trusted store
    [6812] 120810.152059.4365: ClientSetup: Validating User
    [6812] 120810.152059.4365: ClientSetup: Call MachineIdentityManager.GetMachineStatus
    [6812] 120810.152059.8427: ClientSetup: Current Machine Join Status: Active
    [6812] 120810.152059.8583: ClientSetup: Exiting ValidateUserTask.Run
    [6812] 120810.152059.8583: ClientSetup: Task with Id=ClientDeploy.ValidateUser has TaskStatus=Warning
    [6812] 120810.152059.8583: ClientSetup: Task with Id=ClientDeploy.ValidateUser has RebootStatus=NoReboot
    [6812] 120810.152059.8583: ClientSetup: Exting ConnectorWizardForm.RunTasks
    [6812] 120810.152101.7178: ClientSetup: User has chosen to continue using domain admin credentials
    [6812] 120810.152101.7178: ClientSetup: Running JoinNetwork Tasks at WizardPage DomainUserCred
    [6812] 120810.152101.7334: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [6812] 120810.152101.7334: ClientSetup: Running Task with Id=ClientDeploy.JoinDomain
    [6812] 120810.152101.7490: ClientSetup: Entering JoinDomainTask.Run
    [6812] 120810.152101.7490: ClientSetup: Domain Join Client to Server Domain: ClientComputerName=COMP-MCG21 ServerDomainNetBiosName=mcg
    [6812] 120810.152101.7490: ClientSetup: Trying to set Local Nic Dns address as the Server IP.
    [6812] 120810.152101.7490: ClientSetup: Configure DNS settings on local NIC
    [6812] 120810.152101.7490: ClientSetup: Got Server Ip=[10.1.1.3]
    [6812] 120810.152101.9678: ClientSetup: Exception in CheckNetworkAdapter: System.Management.ManagementException: Invalid query
       at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
       at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
       at System.Management.ManagementObjectCollection.get_Count()
       at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.JoinDomainTask.IsNicHardwareLoopback(String nicGuid)
    [6812] 120810.152101.9834: ClientSetup: NetGetJoinInformation (server = [], ...)
    [6812] 120810.152101.9990: ClientSetup: Client is already joined to a Domain: ClientDomainNetBiosName = DOMAIN

    [6812] 120810.152101.9990: ClientSetup: Client has been manually joined to the Server Domain...Moving to Next Task
    [6812] 120810.152101.9990: ClientSetup: Join Domain will not be Run
    [6812] 120810.152101.9990: ClientSetup: Exiting JoinDomainTask.Run
    [6812] 120810.152101.9990: ClientSetup: Task with Id=ClientDeploy.JoinDomain has TaskStatus=Success
    [6812] 120810.152101.9990: ClientSetup: Task with Id=ClientDeploy.JoinDomain has RebootStatus=NoReboot
    [6812] 120810.152101.9990: ClientSetup: Running Task with Id=ClientDeploy.JoinNetwork
    [6812] 120810.152101.9990: ClientSetup: Entering JoinNetworkTask.Run
    [6812] 120810.152101.9990: ClientSetup: Network Join Client to Server: ClientComputerName=COMP-MCG21 ServerName=SBS2011E

    [6812] 120810.152101.9990: ClientSetup: Maximum amount of joined machines: 30
    [6812] 120810.152101.9990: ClientSetup: Current amount of joined machines: 0
    [6812] 120810.152101.9990: ClientSetup: Server already contains a computer joined with Client Machine Name
    [6812] 120810.152101.9990: ClientSetup: Network Join has been forced
    [6812] 120810.152101.9990: ClientSetup: Running Network Join
    [6812] 120810.152101.9990: ClientSetup: Call MachineIdentity.GetCert
    [6812] 120810.152104.9678: ClientSetup: Exiting JoinNetworkTask.Run
    [6812] 120810.152104.9678: ClientSetup: Task with Id=ClientDeploy.JoinNetwork has TaskStatus=Success
    [6812] 120810.152104.9678: ClientSetup: Task with Id=ClientDeploy.JoinNetwork has RebootStatus=NoReboot
    [6812] 120810.152104.9678: ClientSetup: Running Task with Id=ClientDeploy.AllowProfileMigration
    [6812] 120810.152104.9834: ClientSetup: Entering AllowProfileMigrationTask.Run
    [6812] 120810.152104.9834: ClientSetup: NetQueryUsers (Server = [COMP-MCG21] )
    [6812] 120810.152111.9054: ClientSetup: Completed getting list of users
    [6812] 120810.152111.9054: ClientSetup: Logon User Details: COMP-MCG21\domain.user

    [6812] 120810.152111.9054: ClientSetup: Checking if UserProfile exist: UserSid=S-1-5-21-776561741-1482476501-1801674531-1008
    [6812] 120810.152111.9054: ClientSetup: ProfileMgmt on Windows XP
    [6812] 120810.152111.9054: ClientSetup: LogonUser has a local profile
    [6812] 120810.152112.2023: ClientSetup: Domain User Details: domain\ServerAdmin
    [6812] 120810.152112.2023: ClientSetup: Checking if UserProfile exist: UserSid=S-1-5-21-1399462067-113518370-3635262003-1152
    [6812] 120810.152112.2023: ClientSetup: Domain User has a local profile on the client machine
    [6812] 120810.152112.2023: ClientSetup: Logon User Profile Migration wil be Not Allowed
    [6812] 120810.152112.2023: ClientSetup: Exiting AllowProfileMigrationTask.Run
    [6812] 120810.152112.2023: ClientSetup: Task with Id=ClientDeploy.AllowProfileMigration has TaskStatus=Success
    [6812] 120810.152112.2023: ClientSetup: Task with Id=ClientDeploy.AllowProfileMigration has RebootStatus=NoReboot
    [6812] 120810.152112.2023: ClientSetup: Exting ConnectorWizardForm.RunTasks
    [5384] 120810.152112.2023: ClientSetup: JoinNetwork Tasks returned TaskStatus=Success
    [6812] 120810.152136.5153: ClientSetup: Running Tasks for Wizard Page ConfiguringComputer
    [6812] 120810.152136.5153: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [6812] 120810.152136.5153: ClientSetup: Running Task with Id=ClientDeploy.PrepareClient
    [6812] 120810.152136.5465: ClientSetup: Entering PrepareClientTask.Run
    [6812] 120810.152136.5465: ClientSetup: Ensuring that ServiceName=NetTcpPortSharing is Running
    [6812] 120810.152136.5778: ClientSetup: Ensuring that ServiceName=SSDPSRV is Running
    [6812] 120810.152136.5934: ClientSetup: NetGetJoinInformation (server = [], ...)
    [6812] 120810.152136.7184: ClientSetup: Adding domain user [serveradmin] to local Administrators group
    [6812] 120810.152136.7184: ClientSetup: LookupAccountSid (computerName = [], sid = [S-1-5-32-544])
    [6812] 120810.152136.7340: ClientSetup: NetLocalGroupAddMember (server = [], groupName = [Administrators], sidMember = [S-1-5-21-1399462067-113518370-3635262003-1152])
    [6812] 120810.152136.7340: ClientSetup: Enabling Compression on the Log Directory.
    [6812] 120810.152136.8122: ClientSetup: Exiting PrepareClientTask.Run
    [6812] 120810.152136.8122: ClientSetup: Task with Id=ClientDeploy.PrepareClient has TaskStatus=Success
    [6812] 120810.152136.8122: ClientSetup: Task with Id=ClientDeploy.PrepareClient has RebootStatus=NoReboot
    [6812] 120810.152136.8122: ClientSetup: Running Task with Id=ClientDeploy.DownloadSoftware
    [6812] 120810.152136.8591: ClientSetup: Entering DownloadSoftwareTask.Run
    [6812] 120810.152136.8591: ClientSetup: Download client package ClientCore.cab
    [6812] 120810.152136.8747: ClientSetup: Download file ClientCore.cab from server
    [6812] 120810.152136.8747: ClientSetup: Making web request: System.Net.HttpWebRequest
    [6812] 120810.152139.4529: ClientSetup: Downloaded file C:\WINDOWS\Temp\Client Deployment Files\ClientCore.cab
    [6812] 120810.152139.6716: ClientSetup: Found MSI file within cab: ClientCoreX86.msi
    [6812] 120810.152139.6716: ClientSetup: Exiting DownloadSoftwareTask.Run
    [6812] 120810.152139.6716: ClientSetup: Task with Id=ClientDeploy.DownloadSoftware has TaskStatus=Success
    [6812] 120810.152139.6716: ClientSetup: Task with Id=ClientDeploy.DownloadSoftware has RebootStatus=NoReboot
    [6812] 120810.152139.6716: ClientSetup: Running Task with Id=ClientDeploy.InstallSoftware
    [6812] 120810.152139.6716: ClientSetup: Entering InstallSoftwareTask.Run
    [6812] 120810.152139.6716: ClientSetup: Install package C:\WINDOWS\Temp\Client Deployment Files\ClientCoreX86.msi
    [6812] 120810.152139.8122: ClientSetup: Running MSI: C:\WINDOWS\Temp\Client Deployment Files\ClientCoreX86.msi  SOFTWARE_NAME="Windows Small Business Server 2011" REBOOT=ReallySuppress
    [6812] 120810.152319.4391: ClientSetup: Exting InstallSoftwareTask.Run
    [6812] 120810.152319.4391: ClientSetup: Task with Id=ClientDeploy.InstallSoftware has TaskStatus=Success
    [6812] 120810.152319.4391: ClientSetup: Task with Id=ClientDeploy.InstallSoftware has RebootStatus=NoReboot
    [6812] 120810.152319.4391: ClientSetup: Running Task with Id=ClientDeploy.EnableAndReportSqmData
    [6812] 120810.152319.4860: ClientSetup: Entering EnableAndReportSqmDataTask.Run
    [6812] 120810.152319.5954: ClientSetup: Trying to Start SqmProviderSvc
    [6812] 120810.152319.6110: SqmProvider: SqmProviderUtilities.TryStartSqmProviderService: Sqm service is set to AutoStart.
    [6812] 120810.152321.2048: SqmProvider: SqmProviderUtilities.TryStartSqmProviderService: Sqm service is started.
    [6812] 120810.152321.2048: ClientSetup: User selected not to opt-in for SQM
    [6812] 120810.152321.2048: ClientSetup: Exting EnableAndReportSqmDataTask.Run
    [6812] 120810.152321.2048: ClientSetup: Task with Id=ClientDeploy.EnableAndReportSqmData has TaskStatus=Success
    [6812] 120810.152321.2048: ClientSetup: Task with Id=ClientDeploy.EnableAndReportSqmData has RebootStatus=NoReboot
    [6812] 120810.152321.2048: ClientSetup: Exting ConnectorWizardForm.RunTasks
    [5384] 120810.152329.6425: ClientSetup: Back from the Client Deployment Wizard
    [5384] 120810.152329.6581: ClientSetup: Saving Wizard Data
    [5384] 120810.152329.6581: ClientSetup: Launching Dashboard
    [5384] 120810.152329.7050: ClientSetup: End of ClientDeploy: ErrorCode=0


    Lyle Epstein
    Kortek Solutions
    http://www.korteksolutions.com

    Friday, August 10, 2012 10:39 PM
  • I have the exact same Problem as described here:

    SBS 2003 to SBS 2011 Essentials Migration, completed all steps in the Migration guide, everything went smoothly until I tried to join the first Computer. Then "unexpected error", with Clientdeploy.log looking exactly as cited above.

    DNS on the source Server did not list the Destination Server as NS. This was fixed by triggering a replication through replmon, but joining the Client still failed with the same error. Apart from that, DNS Looks fine.

    DNS on the Destination Server had a forwarding entry to the source Server which is stupid as the DNS Service on the source Server has been stopped two Migration steps earlier. I removed that forwarding entry and DNS Resolution became a lot more responsive, but joining the Client still failed with the same error.

    Now I am at my wit's end.

    Any ideas?

    Thursday, August 15, 2013 8:45 AM
  • I also saw this same issue at another client. The solution in that case was that a bunch of the standard windows services were set to disabled. I had to change them back to defaults and start the correct services, and it then worked. I can't recall what services they were, but I ran into it on about 15 machines at this one client... who knows why the previous IT person disabled all of them. Check out your services on the workstation and confirm the default ones are running. If you don't know which ones are default just Google it.

    Hope that helps!


    Lyle Epstein
    Kortek Solutions
    http://www.korteksolutions.com

    Thursday, August 15, 2013 9:13 AM
  • If the suggestions don't work, you'll need to call Microsoft.  When it gets this messy, it's very difficult to debug in a forum.

    Don't Retire TechNet

    Thursday, August 15, 2013 1:42 PM
    Moderator
  • Alas, it's also very difficult to call Microsoft.

    The online form lets me enter three pages of information and then invariably displays: "System error, please try again later or call by phone".

    The phone hotline is not at all prepared for that sort of case and obviously doesn't even know what a migration is. (Asked me if I had changed anything!)

    She is also unwilling to treat this problem as mission critical because the users are still able to work normally. Asks me to wait a week for my credit card transaction to be verified. By then the 21 days will almost be over, so the case will become critical very very fast.

    So yes, of course, I am trying to get help from Microsoft, but I have little hope of getting a solution from them in time to avoid a production shutdown for my customer. Therefore I would still be glad for any hint how to solve this on my own.

    Alternatively, is there a way to extend the 21 days migration period, perhaps by reverting some or all the migration steps I already completed?

    Friday, August 16, 2013 8:50 AM
  • 1. use Chrome.  Go to http://support.microsoft.com and find the "get IT pro help"

    2. what area are you located in?  Try 1-800-microsoft

    The info above is unfortunately all I have... review the connector log files.  Reveiw the connector troubleshooting page.  

    http://social.technet.microsoft.com/wiki/contents/articles/14370.windows-2012-server-essentials-connectcomputer-troubleshooting.aspx

    For SBS 2003 google home server sbscore and you'll see ways to delay the 21 days. 


    Don't Retire TechNet

    Friday, August 16, 2013 2:03 PM
    Moderator
  • Sorry I haven't been clear. I do have a support case open with Microsoft. (Opened by phone, against the resistance of the phone agent, as the web form didn't work. Credit card verification didn't actually take a week, that's just what she had menaced me with.)

    It's just that I haven't received any actual help from MS support so far. After poking around on the involved machines for three hours, the support engineer insists on a "Scope Agreement" for the call that's narrowed to the point of uselessness. In fact, he went as far as suggesting I might be served better by trying to find a Microsoft Partner in my area to help me. :-(

    At least, thanks to your hint, I was able to defuse the 21 days timebomb.

    Thanks,

    Tilman

    Tuesday, August 20, 2013 11:29 AM
  • Update:

    After four online sessions with two different support engineers for a total of six hours, still no sign of progress towards a solution. Apparently the error message and log entries are as unhelpful to the experts as to me.

    Interestingly, support's strategy differs markedly from my own approach. I usually try to analyze what's going wrong, isolate the root cause, and then develop a fix. In contrast, Microsoft support tries (or asks me to try) a series of possible fixes, checking every time whether the problem is still present. Perhaps I should adapt my troubleshooting approach.


    Friday, August 23, 2013 5:32 PM
  • BTW, the second support engineer carped at my defusing the 21 day timebomb, repeating over and over: "We don't support that". He didn't however offer any alternative for avoiding production shutdown, claiming that wasn't part of my support call's "Scope Agreement".
    Saturday, August 24, 2013 4:39 PM
  • They don't support that and it's not part of their support.  It's a community hack and not anything that Microsoft recommends.  It is what it is.

    Don't Retire TechNet

    Saturday, August 24, 2013 5:20 PM
    Moderator
  • I didn't expect nor ask Microsoft to support that hack. I wouldn't even have mentioned it to the support engineer, but he asked me explicitly if I had reached the 21 day limit. I am just reporting his reaction here so that future support callers will know not to admit to using that hack even when asked.

    What I would have expected, when being told off like that, is some kind of alternative, a proposal of what I should have done instead. But that's crying over spilt milk, in a way.

    Saturday, August 24, 2013 7:51 PM