none
Server 2016 essentials connector broken by windows 10 1803 update

    Question

  • I have recently updated our server with essentials 2016 on a trial. The latest Windows 10 update installed on a PC and it has deleted the server essentials connector. When I try to reinstall the connector it fails without even having the option to put a username in. 

    Are Ms aware of this and/or is there a fix as I'm rather disappointed that Microsoft would release this knowing it doesn't work. 

    <g class="gr_ gr_760 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar only-ins doubleReplace replaceWithoutSep" data-gr-id="760" id="760">Server</g> is version 1607 (14393.2214)

    Windows 10 user PC is version 1803.

    Tuesday, May 1, 2018 2:08 PM

All replies

  • https://social.technet.microsoft.com/Forums/windowsserver/en-US/72f391bb-2099-472d-b85c-e8ebd02ef6af/windows-server-esentials-broken-after-update-to-windows-10-1803-?forum=ws16essentials

    • OK it is a missing registry key

    dir "hklm:SOFTWARE\Microsoft\Windows Server\IDENTITY" dir : Cannot find path 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Server\IDENTITY' because it does not exist. At line:1 char:1 + dir "hklm:SOFTWARE\Microsoft\Windows Server\IDENTITY" + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + CategoryInfo          : ObjectNotFound: (HKEY_LOCAL_MACH...Server\IDENTITY:String) [Get-ChildItem], ItemNotFoundException     + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetChildItemCommand

    Exporting the registry key from a working machine and importing it seems to fix the problem

    One last note: The "LocalMachineCert" key under IDENTITY needs to be reset to match the machine it is being used on

    (look under manage computer certificates/personal/certificates for a cert with the same name as your machine and with a template of "Windows Server", pick the last one and use it's sha1 value in the registry key)

    I also cleared the backup registry key

    With this I now have a green tray icon

    Tuesday, May 1, 2018 8:37 PM
  • I'm experiencing this issue as well with ALL new and reinstalls of the connector with Windows 10 1803 for both WS2012 R2 Essentials and WS2016 Essentials connectos. I get the below error in the connector logs.


    [9988] 180501.123158.4162: ClientSetup: Deploy VPN profile

    [9988] 180501.123158.4162: VPN Client Utils: Error 632 returned from RasSetEntryProperties.

    [9988] 180501.123158.4162: ClientSetup: RAS exception: An incorrect structure size was detected.

    [9988] 180501.123158.4162: ClientSetup: Exting SetupVpnAndDATask.Run

    I tried adding the missing IDENTITY key using the method mentioned but I still get an error when I click next after entering credentials.

    Pete


    Wednesday, May 2, 2018 1:52 AM
  • Hi,

    Please provide below log files on Windows 10 - %ProgramData%\Microsoft\Windows Server\Logs:
    1. ClientDeploy.log
    2. Clientconnector.log

    If possible, please try to connect other OS version to WSE, confirm that if problem only happens on specific OS version. 

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, May 2, 2018 3:42 AM
    Moderator
  • Hands down this positively a build Windows 10 1803 issue. It happens on a clean installs of 1803 and existing where the client would need to be reinstalled. The connector works on all previous builds. Logs below...

    [11324] 180501.205341.0044: ClientSetup: Start of ClientDeploy
    [11324] 180501.205341.0826: General: Initializing...C:\Program Files\Windows Server\Bin\ClientDeploy.exe
    [11324] 180501.205341.0983: ClientSetup: Create client deployment registry subkey if necessary
    [11324] 180501.205341.0983: ClientSetup: The initial launching way: -LaunchedFrom:installer
    [11324] 180501.205341.0983: ClientSetup: The initial state is set
    [11324] 180501.205341.0983: ClientSetup: The initial serverName: 192.168.0.4
    [11324] 180501.205341.0983: ClientSetup: Loading Wizard Data
    [11324] 180501.205341.1139: ClientSetup: Saving Wizard Data
    [11324] 180501.205341.1139: ClientSetup: Current DeploymentStatus=Start
    [11324] 180501.205341.4891: ClientSetup: Showing the Client Deployment Wizard
    [11324] 180501.205341.6924: ClientSetup: The input server name is 192.168.0.4
    [10504] 180501.205341.7080: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [10504] 180501.205341.7080: ClientSetup: Running Task with Id=ClientDeploy.PreConfiguration
    [10504] 180501.205341.7080: ClientSetup: The configuration cab will be downloaded from 192.168.0.4
    [11324] 180501.205341.7237: ClientSetup: InitWizard, The currrent stage is ConnectingToServer
    [11324] 180501.205341.7237: ClientSetup: Set the Deployment Sync Event
    [10504] 180501.205341.7237: ClientSetup: Download file Setup.cab from server
    [10504] 180501.205341.7549: ClientSetup: Making web request: https://192.168.0.4//connect/default.aspx?Get=Setup.cab&LanguageId=1033&64bit=1
    [10504] 180501.205341.8018: ClientSetup: Failed to download Setup.cab from server: System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.
       at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
       at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
       at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
       at System.Net.ConnectStream.WriteHeaders(Boolean async)
       --- End of inner exception stack trace ---
       at System.Net.HttpWebRequest.GetResponse()
       at Microsoft.WindowsServerSolutions.ClientSetup.CSCommon.DownloadFileFromConnectSite(String outputDirectory, Uri serverUrl, String fileName, Int32 languageId, Boolean is64bit)
    [10504] 180501.205341.8018: ClientSetup: Cannot get configuration file with https, will try http...
    [10504] 180501.205341.8018: ClientSetup: Download file Setup.cab from server
    [10504] 180501.205341.8018: ClientSetup: Making web request: http://192.168.0.4//connect/default.aspx?Get=Setup.cab&LanguageId=1033&64bit=1
    [10504] 180501.205341.8488: ClientSetup: Downloaded file C:\WINDOWS\Temp\ClientDeploymentTempFiles\Setup.cab
    [10504] 180501.205341.8488: ClientSetup: The configuration cab is downloaded to C:\WINDOWS\Temp\ClientDeploymentTempFiles\Setup.cab
    [10504] 180501.205341.9269: ClientSetup: Adding Server Info data in the Product Registry
    [10504] 180501.205341.9425: DnsEnvironmentDetector: GetHostAddresses() returned 192.168.0.4, normal environment
    [10504] 180501.205341.9425: ClientSetup: Exiting PreConfigTask.Run()
    [10504] 180501.205341.9425: ClientSetup: Task with Id=ClientDeploy.PreConfiguration has TaskStatus=Success
    [10504] 180501.205341.9425: ClientSetup: Task with Id=ClientDeploy.PreConfiguration has RebootStatus=NoReboot
    [10504] 180501.205341.9425: ClientSetup: Exiting ConnectorWizardForm.RunTasks
    [10504] 180501.205350.7294: ClientSetup: Running InstallRootCert Task at WizardPage DomainUserCred
    [10504] 180501.205350.7294: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [10504] 180501.205350.7294: ClientSetup: Running Task with Id=ClientDeploy.InstallRootCertTask
    [10504] 180501.205350.7294: ClientSetup: Entering InstallRootCertTask.Run
    [10504] 180501.205350.7294: ClientSetup: Install root cert to local trusted store
    [10504] 180501.205350.7451: ClientSetup: Exiting InstallRootCertTask.Run
    [10504] 180501.205350.7451: ClientSetup: Task with Id=ClientDeploy.InstallRootCertTask has TaskStatus=Success
    [10504] 180501.205350.7451: ClientSetup: Task with Id=ClientDeploy.InstallRootCertTask has RebootStatus=NoReboot
    [10504] 180501.205350.7451: ClientSetup: Exiting ConnectorWizardForm.RunTasks
    [10504] 180501.205350.7451: ClientSetup: Running SetupVPNAndDA Task at WizardPage DomainUserCred
    [10504] 180501.205350.7451: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [10504] 180501.205350.7451: ClientSetup: Running Task with Id=ClientDeploy.SetupVpnAndDATask
    [10504] 180501.205350.7451: ClientSetup: Entering SetupVpnAndDATask.Run
    [10504] 180501.205350.7607: ClientSetup: Deploy VPN profile
    [10504] 180501.205350.7607: VPN Client Utils: Error 632 returned from RasSetEntryProperties.
    [10504] 180501.205350.7607: ClientSetup: RAS exception: An incorrect structure size was detected.
    [10504] 180501.205350.7607: ClientSetup: Exting SetupVpnAndDATask.Run
    [10504] 180501.205350.7607: ClientSetup: Task with Id=ClientDeploy.SetupVpnAndDATask has TaskStatus=Failed
    [10504] 180501.205350.7607: ClientSetup: Task with Id=ClientDeploy.SetupVpnAndDATask has RebootStatus=NoReboot
    [10504] 180501.205350.7607: ClientSetup: Exiting ConnectorWizardForm.RunTasks
    [11324] 180501.205350.7607: ClientSetup: JoinNetwork Tasks returned TaskStatus=Failed
    [11324] 180501.205351.8708: ClientSetup: Back from the Client Deployment Wizard
    [11324] 180501.205351.8708: ClientSetup: Saving Wizard Data
    [11324] 180501.205351.8708: ClientSetup: End of ClientDeploy: ErrorCode=1603

    [05/01/2018 20:53:38 3288] wmain: Start of Computerconnector
    [05/01/2018 20:53:38 3288] GlobalData::Initialize (192.168.0.4, \\STPSERVER\Folder Redirection\stpadmin\Desktop\ComputerConnector(192.168.0.4).exe)
    [05/01/2018 20:53:38 3288] =================================
    [05/01/2018 20:53:38 3288] Current Os information:
    [05/01/2018 20:53:38 3288] Suite = [256]
    [05/01/2018 20:53:38 3288] Type = [1]
    [05/01/2018 20:53:38 3288] Architecture = [9]
    [05/01/2018 20:53:38 3288] IsStarterEdition = [0]
    [05/01/2018 20:53:38 3288] IsHomeSku = [0]
    [05/01/2018 20:53:38 3288] Major = [10]
    [05/01/2018 20:53:38 3288] Minor = [0]
    [05/01/2018 20:53:38 3288] Build = [17134]
    [05/01/2018 20:53:38 3288] SPMajor = [0]
    [05/01/2018 20:53:38 3288] SPMinor = [0]
    [05/01/2018 20:53:38 3288] =================================
    [05/01/2018 20:53:38 3288] ExpandEnvironmentStrings return (C:\WINDOWS\Temp\ClientDeploymentTempFiles\)
    [05/01/2018 20:53:38 3288] SetPackageDlcUrl: .NET url is set to http://go.microsoft.com/?linkid=9816306
    [05/01/2018 20:53:38 3288] SetPackageDlcUrl: Connector url is set to http://go.microsoft.com/fwlink/p/?LinkId=799487
    [05/01/2018 20:53:38 3288] wmain: Calling Computerconnector::ShowWizard()
    [05/01/2018 20:53:38 3288] CComputerconnector::ShowWizard: Initializing common controls
    [05/01/2018 20:53:38 3288] CComputerconnector::ShowWizard: Done initializing common controls
    [05/01/2018 20:53:38 3288] Displaying the wizard
    [05/01/2018 20:53:38 3288] CComputerconnector::WelcomeDlgProc: IDD_PROPPAGE_WELCOME Page Initialization
    [05/01/2018 20:53:38 3288] Current user default UI lang setting is 1033
    [05/01/2018 20:53:38 27c4] CComputerconnector::Run: Installation is ready to run
    [05/01/2018 20:53:40 3288] CComputerconnector::TaskDlgProc: IDD_PROPPAGE_TASKS Page Initialization
    [05/01/2018 20:53:40 2a7c] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Detecting the current system requirements... Index=  0
    [05/01/2018 20:53:40 2a7c] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {21E49794-7C13-4E84-8659-55BD378267D5} returned -1
    [05/01/2018 20:53:40 2a7c] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {46DCED50-3A1D-4EF4-94F0-45F2681E3D70} returned -1
    [05/01/2018 20:53:40 2a7c] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {C1E4D639-4A33-4314-809E-89BD0EF48522} returned -1
    [05/01/2018 20:53:40 2a7c] Connector installation state is 1
    [05/01/2018 20:53:40 2a7c] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Downloading .NET Framework 4.5... Index=  1
    [05/01/2018 20:53:40 2a7c] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Installing .NET Framework 4.5... Index=  2
    [05/01/2018 20:53:40 2a7c] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Downloading the Connector... Index=  3
    [05/01/2018 20:53:40 2a7c] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Installing Windows Server Essentials Connector... Index=  4
    [05/01/2018 20:53:40 2a7c] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Starting the Windows Server Essentials Connector setup... Index=  5
    [05/01/2018 20:53:40 3288] CComputerconnector::TaskDlgProc: DIALOG_UPDATE: Running
    [05/01/2018 20:53:40 3288] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Detecting the current system requirements...
    [05/01/2018 20:53:40 2a7c] RunShellExecute: ShellExecute [C:\Program Files\Windows Server\Bin\ClientDeploy.exe] with parameters [ -Server:192.168.0.4 -LaunchedFrom:installer]
    [05/01/2018 20:53:40 3288] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Downloading .NET Framework 4.5...
    [05/01/2018 20:53:40 3288] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Installing .NET Framework 4.5...
    [05/01/2018 20:53:40 3288] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Downloading the Connector...
    [05/01/2018 20:53:40 3288] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Installing Windows Server Essentials Connector...
    [05/01/2018 20:53:40 3288] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Starting the Windows Server Essentials Connector setup...
    [05/01/2018 20:53:40 2a7c] CComputerconnector::Run: Waiting upto 60secs for Sync Event to be signaled
    [05/01/2018 20:53:41 2a7c] CComputerconnector::Run: WaitForSingleObject RetVal = 0
    [05/01/2018 20:53:41 3288] CComputerconnector::TaskDlgProc: DIALOG_UPDATE: Success
    [05/01/2018 20:53:41 3288] wmain: End of Computerconnector: hr=0x0

    Pete

    Wednesday, May 2, 2018 10:57 AM
  • I had a test on my virtual environment.

    Environment:
    1. New installed Windows Server 2016 Essentials, version as below:



    2. Newly upgraded Windows 10 version 1803, it is upgraded from 1709:



    Operation:
    Connect Windows 10 to WSE 2016 - on windows 10, open IE and access http://<WSE 2016 ip address>/connect to download Connector.exe. Then, follow the wizard to complete the configuration.

    Result:
    Windows 10 1803 successfully connected to WSE 2016.


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, May 4, 2018 6:01 AM
    Moderator
  • Hi,

    Please make sure that your WSE is fully patched with Windows Update/Hotfix.

    Then, re-start both server and client system in Clean Boot and try to connect again to check the result.

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, May 4, 2018 6:03 AM
    Moderator
  • Just went through this yesterday with all my machines updated to 1803 but only two needed to be reconnected back to the server via this procedure. Yet I haven't updated my server yet to 1803 since it hasn't come through my windows update on server yet...….. 
    Friday, May 4, 2018 1:41 PM
  • Tried this. Doesn't work. The connector still fails after entering credentials and clicking next.

    Pete

    Saturday, May 5, 2018 2:12 AM
  • Eve?  In your test did you have VPN enabled on the server?  That appears to be a trigger with the latest failures with 1803.
    Sunday, May 6, 2018 3:57 AM
  • Hi,

    It is a fresh installed WSE2016, neither VPN nor RWA is enabled.

    I had seen that one customer had posted that, disable VPN has resolved such problem

    I will try to enable and disable VPN on my WSE to check the details.

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, May 7, 2018 9:18 AM
    Moderator
  • I can't even get the Connector software to install now. Both server and client PC have all latest updates as advised by Eve and VPN isn't on (never even configured that on the server)

    Tail of the log file indicates that can't find the server for some reason...

    [05/07/2018 14:00:17 12dc] NetworkUtil::DownloadFromLocal(pData, WSEClient-x64.msi)
    [05/07/2018 14:00:17 12dc] NetworkUtil::DownloadFromLocal: the package could not be found in current program location
    [05/07/2018 14:00:17 12dc] NetworkUtil::DownloadFromServer(pData, Connect/default.aspx?Get=ClientCore.cab&amd64=1, ClientCore.cab)
    [05/07/2018 14:00:17 12dc] NetworkUtil::DownloadFile(pData, Connect/default.aspx?Get=ClientCore.cab&amd64=1, C:\Windows\Temp\ClientDeploymentTempFiles\ClientCore.cab, 443, HTTPS)
    [05/07/2018 14:00:17 12dc] NetworkUtil::DownloadFile (https://192.168.1.100:443/Connect/default.aspx?Get=ClientCore.cab&amd64=1, C:\Windows\Temp\ClientDeploymentTempFiles\ClientCore.cab)
    [05/07/2018 14:00:17 12dc] NetworkUtil::DownloadFile - Create directory [C:\Windows\Temp\ClientDeploymentTempFiles] if not exist.
    [05/07/2018 14:00:17 138c] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Downloading .NET Framework 4.5...
    [05/07/2018 14:00:17 138c] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Installing .NET Framework 4.5...
    [05/07/2018 14:00:17 138c] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Downloading the Connector...
    [05/07/2018 14:00:17 12dc] NetworkUtil::_WinInetDownloadFile (https://192.168.1.100:443/Connect/default.aspx?Get=ClientCore.cab&amd64=1, C:\Windows\Temp\ClientDeploymentTempFiles\ClientCore.cab)
    [05/07/2018 14:00:17 12dc] InternetOpenUrl (https://192.168.1.100:443/Connect/default.aspx?Get=ClientCore.cab&amd64=1) returns 12038
    [05/07/2018 14:00:17 12dc] _WinInetDownloadFile returns 0x80072f06.
    [05/07/2018 14:00:17 12dc] NetworkUtil::DownloadFromServer:DownloadFile(https://192.168.1.100:443, Connect/default.aspx?Get=ClientCore.cab&amd64=1, C:\Windows\Temp\ClientDeploymentTempFiles\ClientCore.cab) failed with hr = 0x80072f06. Try http.
    [05/07/2018 14:00:17 12dc] NetworkUtil::DownloadFile(pData, Connect/default.aspx?Get=ClientCore.cab&amd64=1, C:\Windows\Temp\ClientDeploymentTempFiles\ClientCore.cab, 80, HTTP)
    [05/07/2018 14:00:17 12dc] NetworkUtil::DownloadFile (http://192.168.1.100:80/Connect/default.aspx?Get=ClientCore.cab&amd64=1, C:\Windows\Temp\ClientDeploymentTempFiles\ClientCore.cab)
    [05/07/2018 14:00:17 12dc] NetworkUtil::DownloadFile - Create directory [C:\Windows\Temp\ClientDeploymentTempFiles] if not exist.
    [05/07/2018 14:00:17 12dc] NetworkUtil::_WinInetDownloadFile (http://192.168.1.100:80/Connect/default.aspx?Get=ClientCore.cab&amd64=1, C:\Windows\Temp\ClientDeploymentTempFiles\ClientCore.cab)
    [05/07/2018 14:00:17 12dc] Download from url: http://192.168.1.100:80/Connect/default.aspx?Get=ClientCore.cab&amd64=1 failed with HTTP error 404
    [05/07/2018 14:00:17 12dc] _WinInetDownloadFile returns 0x8000ffff.
    [05/07/2018 14:00:17 12dc] NetworkUtil::DownloadFromServer:DownloadFile(http://192.168.1.100:80, Connect/default.aspx?Get=ClientCore.cab&amd64=1, C:\Windows\Temp\ClientDeploymentTempFiles\ClientCore.cab) failed with hr = 0x8000ffff.
    [05/07/2018 14:00:17 12dc] NetworkUtil::DownloadFromDLC(pData, http://go.microsoft.com/fwlink/?LinkId=789477, WSEClient-x64.msi)
    [05/07/2018 14:00:17 12dc] NetworkUtil::DownloadFile (http://go.microsoft.com/fwlink/?LinkId=789477, C:\Windows\Temp\ClientDeploymentTempFiles\WSEClient-x64.msi)
    [05/07/2018 14:00:17 12dc] NetworkUtil::DownloadFile - Create directory [C:\Windows\Temp\ClientDeploymentTempFiles] if not exist.
    [05/07/2018 14:00:17 12dc] NetworkUtil::_WinInetDownloadFile (http://go.microsoft.com/fwlink/?LinkId=789477, C:\Windows\Temp\ClientDeploymentTempFiles\WSEClient-x64.msi)
    [05/07/2018 14:00:56 12dc] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Installing Windows Server Essentials Connector... Index=  4
    [05/07/2018 14:00:56 138c] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Installing Windows Server Essentials Connector...
    [05/07/2018 14:00:56 12dc] CMsi::CreateInstance ([C:\Windows\Temp\ClientDeploymentTempFiles\WSEClient-x64.msi])
    [05/07/2018 14:00:56 12dc] CMsi::ExecMsiCmd - Running [msiexec.exe /qn /i "C:\Windows\Temp\ClientDeploymentTempFiles\WSEClient-x64.msi" /norestart /l*v "C:\ProgramData\Microsoft\Windows Server\Logs\WSEClient-x64.msi-F9F2C454-AE2D-4BFB-584EC989D97B33B8.log"]
    [05/07/2018 14:01:04 12dc] CMsi::ExecMsiCmd - [msiexec.exe /qn /i "C:\Windows\Temp\ClientDeploymentTempFiles\WSEClient-x64.msi" /norestart /l*v "C:\ProgramData\Microsoft\Windows Server\Logs\WSEClient-x64.msi-F9F2C454-AE2D-4BFB-584EC989D97B33B8.log"] completed with exit code 1603
    [05/07/2018 14:01:04 12dc] Connector Install (C:\Windows\Temp\ClientDeploymentTempFiles\WSEClient-x64.msi) failed with status 5
    [05/07/2018 14:01:04 12dc] CComputerconnector::RunTasks: Task Id=-1 Description=Installing Windows Server Essentials Connector... Failed
    [05/07/2018 14:01:04 12dc] CComputerconnector::Run: RunTasks: 0x8000ffff
    [05/07/2018 14:01:04 138c] CComputerconnector::TaskDlgProc: DIALOG_UPDATE: FatalError
    [05/07/2018 14:01:04 138c] CComputerconnector::ErrorDlgProc: IDD_PROPPAGE_ERROR Initialization
    [05/07/2018 14:01:06 138c] wmain: End of Computerconnector: hr=0x80004005


    Monday, May 7, 2018 2:21 PM
  • Hi,

    Please reference below steps to manually clear stable files:
    1. Open Control Panel Programs and Features, If Client Connector for Windows Server Essentials exists, manually un-install it.
    2. Open %ProgramData%\Microsoft\, if Windows Server folder exists, manually delete it.
    3. Open Task Scheduler Task Scheduler LibraryMicrosoft Windows, if Windows Server Essentials folder exists, manually delete it. 
    4. Open System, if current system belongs to domain environment, please re-join it back to Workgroup.
    5. Open PowerShell and type “get-hotfix”, if KB4103721 has not been installed, please manually install it.

    Re-start client system, and try to connect again to check the result.

    Windows 10 version 1803 - KB4103721:
    https://www.catalog.update.microsoft.com/Search.aspx?q=KB4103721

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, May 10, 2018 2:58 AM
    Moderator
  • Hi Eve, 

    I've followed your latest instructions to the letter. and unfortunately, the same result. The client connector goes through the downloading phase and then fails almost immediately on installing. Here's the Computerconnector log:

    [05/10/2018 18:39:56 395c] --------------------------------------------------------------------------------------------------
    [05/10/2018 18:39:56 395c] wmain: Start of Computerconnector
    [05/10/2018 18:39:56 395c] GlobalData::Initialize (192.168.1.100, E:\Paul Bambury\Desktop\ComputerConnector(192.168.1.100).exe)
    [05/10/2018 18:39:56 395c] =================================
    [05/10/2018 18:39:56 395c] Current Os information:
    [05/10/2018 18:39:56 395c] Suite = [256]
    [05/10/2018 18:39:56 395c] Type = [1]
    [05/10/2018 18:39:56 395c] Architecture = [9]
    [05/10/2018 18:39:56 395c] IsStarterEdition = [0]
    [05/10/2018 18:39:56 395c] IsHomeSku = [0]
    [05/10/2018 18:39:56 395c] Major = [10]
    [05/10/2018 18:39:56 395c] Minor = [0]
    [05/10/2018 18:39:56 395c] Build = [17134]
    [05/10/2018 18:39:56 395c] SPMajor = [0]
    [05/10/2018 18:39:56 395c] SPMinor = [0]
    [05/10/2018 18:39:56 395c] =================================
    [05/10/2018 18:39:56 395c] ExpandEnvironmentStrings return (C:\Windows\Temp\ClientDeploymentTempFiles\)
    [05/10/2018 18:39:56 395c] SetPackageDlcUrl: .NET url is set to http://go.microsoft.com/?linkid=9816306
    [05/10/2018 18:39:56 395c] SetPackageDlcUrl: Connector url is set to http://go.microsoft.com/fwlink/?LinkId=789477
    [05/10/2018 18:39:56 395c] wmain: Calling Computerconnector::ShowWizard()
    [05/10/2018 18:39:56 395c] CComputerconnector::ShowWizard: Initializing common controls
    [05/10/2018 18:39:56 395c] CComputerconnector::ShowWizard: Done initializing common controls
    [05/10/2018 18:39:56 395c] Displaying the wizard
    [05/10/2018 18:39:56 395c] CComputerconnector::WelcomeDlgProc: IDD_PROPPAGE_WELCOME Page Initialization
    [05/10/2018 18:39:56 395c] Current user default UI lang setting is 2057
    [05/10/2018 18:39:56  ec0] CComputerconnector::Run: Installation is ready to run
    [05/10/2018 18:39:58 395c] CComputerconnector::TaskDlgProc: IDD_PROPPAGE_TASKS Page Initialization
    [05/10/2018 18:39:58 312c] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Detecting the current system requirements... Index=  0
    [05/10/2018 18:39:58 395c] CComputerconnector::TaskDlgProc: DIALOG_UPDATE: Running
    [05/10/2018 18:39:58 395c] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Detecting the current system requirements...
    [05/10/2018 18:39:58 312c] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {21E49794-7C13-4E84-8659-55BD378267D5} returned -1
    [05/10/2018 18:39:58 312c] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {46DCED50-3A1D-4EF4-94F0-45F2681E3D70} returned -1
    [05/10/2018 18:39:58 312c] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {C1E4D639-4A33-4314-809E-89BD0EF48522} returned -1
    [05/10/2018 18:39:58 312c] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {563CB0AF-E0B5-42B1-AB42-8E6964349900} returned -1
    [05/10/2018 18:39:58 312c] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Downloading .NET Framework 4.5... Index=  1
    [05/10/2018 18:39:58 395c] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Downloading .NET Framework 4.5...
    [05/10/2018 18:39:58 312c] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Installing .NET Framework 4.5... Index=  2
    [05/10/2018 18:39:58 312c] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Downloading the Connector... Index=  3
    [05/10/2018 18:39:58 312c] NetworkUtil::DownloadFromLocal(pData, WSEClient-x64.msi)
    [05/10/2018 18:39:58 312c] NetworkUtil::DownloadFromLocal: the package could not be found in current program location
    [05/10/2018 18:39:58 312c] NetworkUtil::DownloadFromServer(pData, Connect/default.aspx?Get=ClientCore.cab&amd64=1, ClientCore.cab)
    [05/10/2018 18:39:58 312c] NetworkUtil::DownloadFile(pData, Connect/default.aspx?Get=ClientCore.cab&amd64=1, C:\Windows\Temp\ClientDeploymentTempFiles\ClientCore.cab, 443, HTTPS)
    [05/10/2018 18:39:58 312c] NetworkUtil::DownloadFile (https://192.168.1.100:443/Connect/default.aspx?Get=ClientCore.cab&amd64=1, C:\Windows\Temp\ClientDeploymentTempFiles\ClientCore.cab)
    [05/10/2018 18:39:58 312c] NetworkUtil::DownloadFile - Create directory [C:\Windows\Temp\ClientDeploymentTempFiles] if not exist.
    [05/10/2018 18:39:58 395c] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Installing .NET Framework 4.5...
    [05/10/2018 18:39:58 395c] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Downloading the Connector...
    [05/10/2018 18:39:58 312c] NetworkUtil::_WinInetDownloadFile (https://192.168.1.100:443/Connect/default.aspx?Get=ClientCore.cab&amd64=1, C:\Windows\Temp\ClientDeploymentTempFiles\ClientCore.cab)
    [05/10/2018 18:39:58 312c] InternetOpenUrl (https://192.168.1.100:443/Connect/default.aspx?Get=ClientCore.cab&amd64=1) returns 12038
    [05/10/2018 18:39:58 312c] _WinInetDownloadFile returns 0x80072f06.
    [05/10/2018 18:39:58 312c] NetworkUtil::DownloadFromServer:DownloadFile(https://192.168.1.100:443, Connect/default.aspx?Get=ClientCore.cab&amd64=1, C:\Windows\Temp\ClientDeploymentTempFiles\ClientCore.cab) failed with hr = 0x80072f06. Try http.
    [05/10/2018 18:39:58 312c] NetworkUtil::DownloadFile(pData, Connect/default.aspx?Get=ClientCore.cab&amd64=1, C:\Windows\Temp\ClientDeploymentTempFiles\ClientCore.cab, 80, HTTP)
    [05/10/2018 18:39:58 312c] NetworkUtil::DownloadFile (http://192.168.1.100:80/Connect/default.aspx?Get=ClientCore.cab&amd64=1, C:\Windows\Temp\ClientDeploymentTempFiles\ClientCore.cab)
    [05/10/2018 18:39:58 312c] NetworkUtil::DownloadFile - Create directory [C:\Windows\Temp\ClientDeploymentTempFiles] if not exist.
    [05/10/2018 18:39:58 312c] NetworkUtil::_WinInetDownloadFile (http://192.168.1.100:80/Connect/default.aspx?Get=ClientCore.cab&amd64=1, C:\Windows\Temp\ClientDeploymentTempFiles\ClientCore.cab)
    [05/10/2018 18:39:58 312c] Download from url: http://192.168.1.100:80/Connect/default.aspx?Get=ClientCore.cab&amd64=1 failed with HTTP error 404
    [05/10/2018 18:39:58 312c] _WinInetDownloadFile returns 0x8000ffff.
    [05/10/2018 18:39:58 312c] NetworkUtil::DownloadFromServer:DownloadFile(http://192.168.1.100:80, Connect/default.aspx?Get=ClientCore.cab&amd64=1, C:\Windows\Temp\ClientDeploymentTempFiles\ClientCore.cab) failed with hr = 0x8000ffff.
    [05/10/2018 18:39:58 312c] NetworkUtil::DownloadFromDLC(pData, http://go.microsoft.com/fwlink/?LinkId=789477, WSEClient-x64.msi)
    [05/10/2018 18:39:58 312c] NetworkUtil::DownloadFile (http://go.microsoft.com/fwlink/?LinkId=789477, C:\Windows\Temp\ClientDeploymentTempFiles\WSEClient-x64.msi)
    [05/10/2018 18:39:58 312c] NetworkUtil::DownloadFile - Create directory [C:\Windows\Temp\ClientDeploymentTempFiles] if not exist.
    [05/10/2018 18:39:58 312c] NetworkUtil::_WinInetDownloadFile (http://go.microsoft.com/fwlink/?LinkId=789477, C:\Windows\Temp\ClientDeploymentTempFiles\WSEClient-x64.msi)
    [05/10/2018 18:41:24 312c] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Installing Windows Server Essentials Connector... Index=  4
    [05/10/2018 18:41:24 395c] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Installing Windows Server Essentials Connector...
    [05/10/2018 18:41:24 312c] CMsi::CreateInstance ([C:\Windows\Temp\ClientDeploymentTempFiles\WSEClient-x64.msi])
    [05/10/2018 18:41:24 312c] CMsi::ExecMsiCmd - Running [msiexec.exe /qn /i "C:\Windows\Temp\ClientDeploymentTempFiles\WSEClient-x64.msi" /norestart /l*v "C:\ProgramData\Microsoft\Windows Server\Logs\WSEClient-x64.msi-F59E0842-ED21-4E66-B8588D1029260F9E.log"]
    [05/10/2018 18:41:32 312c] CMsi::ExecMsiCmd - [msiexec.exe /qn /i "C:\Windows\Temp\ClientDeploymentTempFiles\WSEClient-x64.msi" /norestart /l*v "C:\ProgramData\Microsoft\Windows Server\Logs\WSEClient-x64.msi-F59E0842-ED21-4E66-B8588D1029260F9E.log"] completed with exit code 1603
    [05/10/2018 18:41:32 312c] Connector Install (C:\Windows\Temp\ClientDeploymentTempFiles\WSEClient-x64.msi) failed with status 5
    [05/10/2018 18:41:32 312c] CComputerconnector::RunTasks: Task Id=-1 Description=Installing Windows Server Essentials Connector... Failed
    [05/10/2018 18:41:32 312c] CComputerconnector::Run: RunTasks: 0x8000ffff
    [05/10/2018 18:41:32 395c] CComputerconnector::TaskDlgProc: DIALOG_UPDATE: FatalError
    [05/10/2018 18:41:32 395c] CComputerconnector::ErrorDlgProc: IDD_PROPPAGE_ERROR Initialization

    As you can see its the same 404 not found. If I try entering that url (http://192.168.1.100:80/Connect/default.aspx?Get=ClientCore.cab) in Chrome and i also get the 404, but if I remove the ?Get=ClientCore.cab then the default connector.apsx page loads, so I don't have a firewall or port issue

    Regards,

    Paul


    Thursday, May 10, 2018 5:49 PM
  • Hi Paul,

    I was getting this error trying to install the WS2016E connector on a Windows 10 machine (which had previously connected fine). When I checked in the C:\WINDOWS\Temp\ dir I saw that my Antivirus folder had a identical timestamp to the time stamp of the C:\WINDOWS\Temp\ClientDeploymentTempFiles\ dir. I disabled the active shields and it let me install the connector (finally).

    May not be the same for you but thought I'd mention in case.

    Regards

    Rod

    • Proposed as answer by adutchman Sunday, May 13, 2018 7:31 PM
    Sunday, May 13, 2018 4:00 PM
  • Hi Paul,

    I was getting this error trying to install the WS2016E connector on a Windows 10 machine (which had previously connected fine). When I checked in the C:\WINDOWS\Temp\ dir I saw that my Antivirus folder had a identical timestamp to the time stamp of the C:\WINDOWS\Temp\ClientDeploymentTempFiles\ dir. I disabled the active shields and it let me install the connector (finally).

    May not be the same for you but thought I'd mention in case.

    Regards

    Rod

    I've been pulling my hair out for days.  Backed up all data, wiped and reloaded Windows 10 Build 1803 from scratch.  I still could not get the Client Connector installed until I saw this post.  I disabled the active shields on my anti-virus software and sure enough, I was able to install the connector.  FINALLY!!!!

    This worked for me!!!  YMMV

    Sunday, May 13, 2018 7:31 PM
  • I have been having the same issue trying to connect Win10 1803 to a new Server 2016 install.  Neither Win10 machine will join via WSE Connector or the direct Join Domain via the Control panel.  KB4103721 Hotfix for x64 says not valid for this install.  Trying to do the Join Domain via the CP give a "Domain Controller could not be contacted.  NSlookup and DCDIAG say all is good with the DC.  ALL AV and Firewalls are OFF, and still have the issue.

    NetSetup log from the last attempt is below...  Anyone have any thoughts?  I have been searching for solutions, and am already 6 days into trying to figure this out....  Thanks!!!

    05/29/2018 19:47:51:845 NetpDoDomainJoin
    05/29/2018 19:47:51:845 NetpDoDomainJoin: using current computer names
    05/29/2018 19:47:51:845 NetpDoDomainJoin: NetpGetComputerNameEx(NetBios) returned 0x0
    05/29/2018 19:47:51:845 NetpDoDomainJoin: NetpGetComputerNameEx(DnsHostName) returned 0x0
    05/29/2018 19:47:51:845 NetpMachineValidToJoin: 'GC02'
    05/29/2018 19:47:51:846 NetpMachineValidToJoin: status: 0x0
    05/29/2018 19:47:51:846 NetpJoinDomain
    05/29/2018 19:47:51:846 HostName: GC02
    05/29/2018 19:47:51:846 NetbiosName: GC02
    05/29/2018 19:47:51:846 Domain: gooding.local
    05/29/2018 19:47:51:846 MachineAccountOU: (NULL)
    05/29/2018 19:47:51:846 Account: gooding.local\kg
    05/29/2018 19:47:51:846 Options: 0x10000027
    05/29/2018 19:47:51:848 NetpValidateName: checking to see if 'gooding.local' is valid as type 3 name
    05/29/2018 19:47:51:909 NetpCheckDomainNameIsValid [ Exists ] for 'gooding.local' returned 0x0
    05/29/2018 19:47:51:909 NetpValidateName: name 'gooding.local' is valid for type 3
    05/29/2018 19:47:51:909 NetpDsGetDcName: trying to find DC in domain 'gooding.local', flags: 0x1020
    05/29/2018 19:47:52:368 NetpDsGetDcName: failed to find a DC having account 'GC02$': 0x525, last error is 0x0
    05/29/2018 19:47:52:371 NetpDsGetDcName: found DC '\\GCSERVER.gooding.local' in the specified domain
    05/29/2018 19:47:52:371 NetpJoinDomainOnDs: NetpDsGetDcName returned: 0x0
    05/29/2018 19:47:52:371 NetpDisableIDNEncoding: using FQDN gooding.local from dcinfo
    05/29/2018 19:47:52:373 NetpDisableIDNEncoding: DnsDisableIdnEncoding(UNTILREBOOT) on 'gooding.local' succeeded
    05/29/2018 19:47:52:373 NetpJoinDomainOnDs: NetpDisableIDNEncoding returned: 0x0
    05/29/2018 19:47:55:400 NetUseAdd to \\GCSERVER.gooding.local\IPC$ returned 53
    05/29/2018 19:47:55:400 NetpJoinDomainOnDs: status of connecting to dc '\\GCSERVER.gooding.local': 0x35
    05/29/2018 19:47:55:400 NetpJoinDomainOnDs: Function exits with status of: 0x35
    05/29/2018 19:47:55:402 NetpResetIDNEncoding: DnsDisableIdnEncoding(RESETALL) on 'gooding.local' returned 0x0
    05/29/2018 19:47:55:402 NetpJoinDomainOnDs: NetpResetIDNEncoding on 'gooding.local': 0x0
    05/29/2018 19:47:55:402 NetpDoDomainJoin: status: 0x35
    05/29/2018 19:47:56:016 -----------------------------------------------------------------
    05/29/2018 19:47:56:016 NetpDoDomainJoin
    05/29/2018 19:47:56:016 NetpDoDomainJoin: using current computer names
    05/29/2018 19:47:56:016 NetpDoDomainJoin: NetpGetComputerNameEx(NetBios) returned 0x0
    05/29/2018 19:47:56:016 NetpDoDomainJoin: NetpGetComputerNameEx(DnsHostName) returned 0x0
    05/29/2018 19:47:56:016 NetpMachineValidToJoin: 'GC02'
    05/29/2018 19:47:56:016 NetpMachineValidToJoin: status: 0x0
    05/29/2018 19:47:56:016 NetpJoinDomain
    05/29/2018 19:47:56:016 HostName: GC02
    05/29/2018 19:47:56:016 NetbiosName: GC02
    05/29/2018 19:47:56:016 Domain: gooding.local
    05/29/2018 19:47:56:016 MachineAccountOU: (NULL)
    05/29/2018 19:47:56:016 Account: gooding.local\kg
    05/29/2018 19:47:56:016 Options: 0x10000027
    05/29/2018 19:47:56:018 NetpValidateName: checking to see if 'gooding.local' is valid as type 3 name
    05/29/2018 19:47:56:073 NetpCheckDomainNameIsValid [ Exists ] for 'gooding.local' returned 0x0
    05/29/2018 19:47:56:073 NetpValidateName: name 'gooding.local' is valid for type 3
    05/29/2018 19:47:56:073 NetpDsGetDcName: trying to find DC in domain 'gooding.local', flags: 0x1020
    05/29/2018 19:47:56:527 NetpDsGetDcName: failed to find a DC having account 'GC02$': 0x525, last error is 0x0
    05/29/2018 19:47:56:530 NetpDsGetDcName: found DC '\\GCSERVER.gooding.local' in the specified domain
    05/29/2018 19:47:56:530 NetpJoinDomainOnDs: NetpDsGetDcName returned: 0x0
    05/29/2018 19:47:56:530 NetpDisableIDNEncoding: using FQDN gooding.local from dcinfo
    05/29/2018 19:47:56:531 NetpDisableIDNEncoding: DnsDisableIdnEncoding(UNTILREBOOT) on 'gooding.local' succeeded
    05/29/2018 19:47:56:531 NetpJoinDomainOnDs: NetpDisableIDNEncoding returned: 0x0
    05/29/2018 19:47:57:545 NetUseAdd to \\GCSERVER.gooding.local\IPC$ returned 53
    05/29/2018 19:47:57:545 NetpJoinDomainOnDs: status of connecting to dc '\\GCSERVER.gooding.local': 0x35
    05/29/2018 19:47:57:545 NetpJoinDomainOnDs: Function exits with status of: 0x35
    05/29/2018 19:47:57:548 NetpResetIDNEncoding: DnsDisableIdnEncoding(RESETALL) on 'gooding.local' returned 0x0
    05/29/2018 19:47:57:548 NetpJoinDomainOnDs: NetpResetIDNEncoding on 'gooding.local': 0x0
    05/29/2018 19:47:57:548 NetpDoDomainJoin: status: 0x35
    05/29/2018 19:48:27:740 -----------------------------------------------------------------
    05/29/2018 19:48:27:740 NetpDoDomainJoin
    05/29/2018 19:48:27:740 NetpDoDomainJoin: using current computer names
    05/29/2018 19:48:27:740 NetpDoDomainJoin: NetpGetComputerNameEx(NetBios) returned 0x0
    05/29/2018 19:48:27:740 NetpDoDomainJoin: NetpGetComputerNameEx(DnsHostName) returned 0x0
    05/29/2018 19:48:27:740 NetpMachineValidToJoin: 'GC02'
    05/29/2018 19:48:27:740 NetpMachineValidToJoin: status: 0x0
    05/29/2018 19:48:27:740 NetpJoinDomain
    05/29/2018 19:48:27:740 HostName: GC02
    05/29/2018 19:48:27:740 NetbiosName: GC02
    05/29/2018 19:48:27:740 Domain: gooding.local
    05/29/2018 19:48:27:740 MachineAccountOU: (NULL)
    05/29/2018 19:48:27:740 Account: gooding.local\kg
    05/29/2018 19:48:27:740 Options: 0x10000027
    05/29/2018 19:48:27:742 NetpValidateName: checking to see if 'gooding.local' is valid as type 3 name
    05/29/2018 19:48:27:796 NetpCheckDomainNameIsValid [ Exists ] for 'gooding.local' returned 0x0
    05/29/2018 19:48:27:796 NetpValidateName: name 'gooding.local' is valid for type 3
    05/29/2018 19:48:27:796 NetpDsGetDcName: trying to find DC in domain 'gooding.local', flags: 0x1020
    05/29/2018 19:48:28:247 NetpDsGetDcName: failed to find a DC having account 'GC02$': 0x525, last error is 0x0
    05/29/2018 19:48:28:251 NetpDsGetDcName: found DC '\\GCSERVER.gooding.local' in the specified domain
    05/29/2018 19:48:28:251 NetpJoinDomainOnDs: NetpDsGetDcName returned: 0x0
    05/29/2018 19:48:28:251 NetpDisableIDNEncoding: using FQDN gooding.local from dcinfo
    05/29/2018 19:48:28:255 NetpDisableIDNEncoding: DnsDisableIdnEncoding(UNTILREBOOT) on 'gooding.local' succeeded
    05/29/2018 19:48:28:255 NetpJoinDomainOnDs: NetpDisableIDNEncoding returned: 0x0
    05/29/2018 19:48:31:278 NetUseAdd to \\GCSERVER.gooding.local\IPC$ returned 53
    05/29/2018 19:48:31:278 NetpJoinDomainOnDs: status of connecting to dc '\\GCSERVER.gooding.local': 0x35
    05/29/2018 19:48:31:278 NetpJoinDomainOnDs: Function exits with status of: 0x35
    05/29/2018 19:48:31:290 NetpResetIDNEncoding: DnsDisableIdnEncoding(RESETALL) on 'gooding.local' returned 0x0
    05/29/2018 19:48:31:290 NetpJoinDomainOnDs: NetpResetIDNEncoding on 'gooding.local': 0x0
    05/29/2018 19:48:31:290 NetpDoDomainJoin: status: 0x35
    05/29/2018 19:48:31:311 -----------------------------------------------------------------
    05/29/2018 19:48:31:311 NetpDoDomainJoin
    05/29/2018 19:48:31:311 NetpDoDomainJoin: using current computer names
    05/29/2018 19:48:31:311 NetpDoDomainJoin: NetpGetComputerNameEx(NetBios) returned 0x0
    05/29/2018 19:48:31:311 NetpDoDomainJoin: NetpGetComputerNameEx(DnsHostName) returned 0x0
    05/29/2018 19:48:31:311 NetpMachineValidToJoin: 'GC02'
    05/29/2018 19:48:31:312 NetpMachineValidToJoin: status: 0x0
    05/29/2018 19:48:31:312 NetpJoinDomain
    05/29/2018 19:48:31:312 HostName: GC02
    05/29/2018 19:48:31:312 NetbiosName: GC02
    05/29/2018 19:48:31:312 Domain: gooding.local
    05/29/2018 19:48:31:312 MachineAccountOU: (NULL)
    05/29/2018 19:48:31:312 Account: gooding.local\kg
    05/29/2018 19:48:31:312 Options: 0x10000027
    05/29/2018 19:48:31:315 NetpValidateName: checking to see if 'gooding.local' is valid as type 3 name
    05/29/2018 19:48:31:371 NetpCheckDomainNameIsValid [ Exists ] for 'gooding.local' returned 0x0
    05/29/2018 19:48:31:371 NetpValidateName: name 'gooding.local' is valid for type 3
    05/29/2018 19:48:31:371 NetpDsGetDcName: trying to find DC in domain 'gooding.local', flags: 0x1020
    05/29/2018 19:48:31:824 NetpDsGetDcName: failed to find a DC having account 'GC02$': 0x525, last error is 0x0
    05/29/2018 19:48:31:827 NetpDsGetDcName: found DC '\\GCSERVER.gooding.local' in the specified domain
    05/29/2018 19:48:31:827 NetpJoinDomainOnDs: NetpDsGetDcName returned: 0x0
    05/29/2018 19:48:31:827 NetpDisableIDNEncoding: using FQDN gooding.local from dcinfo
    05/29/2018 19:48:31:828 NetpDisableIDNEncoding: DnsDisableIdnEncoding(UNTILREBOOT) on 'gooding.local' succeeded
    05/29/2018 19:48:31:828 NetpJoinDomainOnDs: NetpDisableIDNEncoding returned: 0x0
    05/29/2018 19:48:32:839 NetUseAdd to \\GCSERVER.gooding.local\IPC$ returned 53
    05/29/2018 19:48:32:839 NetpJoinDomainOnDs: status of connecting to dc '\\GCSERVER.gooding.local': 0x35
    05/29/2018 19:48:32:839 NetpJoinDomainOnDs: Function exits with status of: 0x35
    05/29/2018 19:48:32:841 NetpResetIDNEncoding: DnsDisableIdnEncoding(RESETALL) on 'gooding.local' returned 0x0
    05/29/2018 19:48:32:841 NetpJoinDomainOnDs: NetpResetIDNEncoding on 'gooding.local': 0x0
    05/29/2018 19:48:32:841 NetpDoDomainJoin: status: 0x35

    Wednesday, May 30, 2018 2:54 AM
  • Think you might be looking at a different issue TJ. When I was encountering this issue I could join the PC to the domain in the control panel.

    Given you are seeing this error:

    NetpDsGetDcName: failed to find a DC having account 'GC02$': 0x525, last error is 0x0

    Might be worth looking at the solution in this thread:

    https://social.technet.microsoft.com/Forums/windows/en-US/ad533b07-b836-474a-8de1-73376d587750/unable-to-join-domain-failed-to-find-a-dc-having-account-computername-0x525-last-error-is?forum=w8itprogeneral

    Hope this helps

    Rod


    • Edited by subtlerod Monday, June 4, 2018 9:51 AM
    Monday, June 4, 2018 9:00 AM
  • Hi Paul,

    I was getting this error trying to install the WS2016E connector on a Windows 10 machine (which had previously connected fine). When I checked in the C:\WINDOWS\Temp\ dir I saw that my Antivirus folder had a identical timestamp to the time stamp of the C:\WINDOWS\Temp\ClientDeploymentTempFiles\ dir. I disabled the active shields and it let me install the connector (finally).

    May not be the same for you but thought I'd mention in case.

    Regards

    Rod

    Hi Rod,

    Finally got back to this after holidays, and as adutchman has found disabling avast shields allowed me to install the connector software. However, upon entering the user account details in the wizard I was getting a error "server is not available". Strange, because the wizard happily identified the server in the previous step...

    Anyway, after a bit more cursing and googling I finally stumbled onto a technet thread from six months ago in which Eve wrote this:

    "On the client, manually configure the Preference DNS server as Essential Server’s IP address:
    Network Adapter - Properties - TCP/IP Properties – Use the following DNS server address – Preferred DNS server"

    Setting the clients preferred DNS to the server IP and then running the Connector finally allowed the client to connect!

    Paul


    Saturday, June 9, 2018 10:31 AM