none
Windows 10 Feature Update 1903 disables Essentials Connector RRS feed

  • Question

  • I have begun testing the Windows 10, version 1903 Feature update.  In the three clients on which I installed the update, they were unable thereafter to connect to the Essentials Server.  The only way I was able to resolve the issue was to manually uninstall and reinstall the connector. 
    Friday, June 7, 2019 2:32 PM

All replies

  • Same issue on 3 clients (100%) so far
    Friday, June 7, 2019 5:13 PM
  • This began to be reported more than a month ago (https://social.technet.microsoft.com/Forums/windowsserver/en-US/044c29e5-7b0e-4241-803f-0cdcbe27db97/win-10-1903-clients-not-visible-in-ws2012r2-essentials?forum=winserveressentials) but follow up appears to die if the original poster does not pursue it.

    In my case, uninstalling and reinstalling the connector (Programs and Features, select, Uninstall) doesn't work, since immediately after entering login credentials into the connector during setup I get "The server is not available. Try connecting this computer again."

    BackupLaunchpad.log (affected):

    =====

    [16336] 190530.202751.5574: BackupLaunchpad: Program.Main(): BackupLaunchpad started
    [16336] 190530.202751.6194: General: Initializing...C:\Program Files\Windows Server\Bin\BackupLaunchpad.exe
    [16336] 190530.202751.6664: General: Color branding started
    [16336] 190530.202751.6664: General: Processing Microsoft default SKU branding colors XML
    [16336] 190530.202751.6784: General: Branding colors XML parsing started
    [16336] 190530.202751.6824: General: Branding colors XML parsing ended
    [16336] 190530.202751.6824: General: Looking for OEM branding colors XML
    [16336] 190530.202751.6824: General: No OEM informations available
    [16336] 190530.202751.6824: General: Color branding complete
    [16336] 190530.202751.7404: BackupLaunchpad: BackupLaunchpadControl constructed
    [16336] 190530.202751.7454: BackupLaunchpad: BackupDisconnectedControl constructed
    [16336] 190530.202751.7474: Backup: Trying to connect to provider Async.
    [16336] 190530.202751.7474: BackupLaunchpad: BackupLaunchpadProperties: constructed form
    [1676] 190530.202751.7524: Backup: Waiting for connection with the provider.
    [1676] 190530.202851.7548: Backup: Timeout waiting for connection : System.TimeoutException: Timeout occurred waiting for connection to complete.  Connection attempt is still in progress.
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.internal.ConnectorInternals.TimeoutWait`1.ThreadWaitHolder.WaitForTimeout(TimeSpan duration, ProviderConnector`1 providerConnector)
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.internal.ConnectorInternals.TimeoutWait`1.WaitForTimeout(TimeSpan duration, ProviderConnector`1 providerConnector)
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderConnector`1.WaitForConnection(TimeSpan duration)
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.ObjectModel.PCBackupClientManager.Connect()
    [16336] 190530.202917.6882: BackupLaunchpad: Program.Main(): BackupLaunchpad ending

    =====

    Launchpad.log (affected):

    =====

    [2364] 190530.205309.8116: ServerDiscoveryObjectModel:Backend: Connect: Calling Connector.Connect()
    [2364] 190530.205329.8124: ServerConnectivityStatus: Cannot connect to ServerPresenceProvider: System.TimeoutException: Timeout occurred waiting for connection to complete.  Connection attempt is still in progress.
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.internal.ConnectorInternals.TimeoutWait`1.ThreadWaitHolder.WaitForTimeout(TimeSpan duration, ProviderConnector`1 providerConnector)
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.internal.ConnectorInternals.TimeoutWait`1.WaitForTimeout(TimeSpan duration, ProviderConnector`1 providerConnector)
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderConnector`1.WaitForConnection(TimeSpan duration)
       at Microsoft.WindowsServerSolutions.Networking.ServerDiscovery.ProviderBackendBase`1.Connect(TimeSpan timeout)
       at Microsoft.WindowsServerSolutions.Networking.ServerDiscovery.ServerDiscoveryObjectModelBase`1.Connect(TimeSpan timeout)
       at Microsoft.WindowsServerSolutions.LaunchPad.ServerConnectivityStatus.connectWorker_DoWork(Object sender, DoWorkEventArgs e)
    [2364] 190530.205329.8124: General: _isNewState changed: False

    =====

    ClientDeploy.log (affected, same machine after in-place update to 1903, during reinstallation of client connector):

    =====

    [6932] 190601.112427.8757: ClientSetup: Cannot get configuration file with https, will try http...
    [6932] 190601.112427.8767: ClientSetup: Download file Setup.cab from server
    [6932] 190601.112427.8767: ClientSetup: Making web request: http://192.168.0.2//connect/default.aspx?Get=Setup.cab&LanguageId=1033&64bit=1
    [6932] 190601.112427.9938: ClientSetup: Downloaded file C:\WINDOWS\Temp\ClientDeploymentTempFiles\Setup.cab
    [6932] 190601.112427.9938: ClientSetup: The configuration cab is downloaded to C:\WINDOWS\Temp\ClientDeploymentTempFiles\Setup.cab
    [6932] 190601.112428.0688: ClientSetup: Adding Server Info data in the Product Registry
    [6932] 190601.112428.0921: DnsEnvironmentDetector: GetHostAddresses() returned 192.168.0.2, normal environment
    [6932] 190601.112428.0941: ClientSetup: Exiting PreConfigTask.Run()
    [6932] 190601.112428.0941: ClientSetup: Task with Id=ClientDeploy.PreConfiguration has TaskStatus=Success
    [6932] 190601.112428.0941: ClientSetup: Task with Id=ClientDeploy.PreConfiguration has RebootStatus=NoReboot
    [6932] 190601.112428.0941: ClientSetup: Exiting ConnectorWizardForm.RunTasks
    [6932] 190601.112434.3520: ClientSetup: Running InstallRootCert Task at WizardPage DomainUserCred
    [6932] 190601.112434.3520: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [6932] 190601.112434.3520: ClientSetup: Running Task with Id=ClientDeploy.InstallRootCertTask
    [6932] 190601.112434.3740: ClientSetup: Entering InstallRootCertTask.Run
    [6932] 190601.112434.3770: ClientSetup: Install root cert to local trusted store
    [6932] 190601.112434.3830: ClientSetup: Exiting InstallRootCertTask.Run
    [6932] 190601.112434.3830: ClientSetup: Task with Id=ClientDeploy.InstallRootCertTask has TaskStatus=Success
    [6932] 190601.112434.3830: ClientSetup: Task with Id=ClientDeploy.InstallRootCertTask has RebootStatus=NoReboot
    [6932] 190601.112434.3830: ClientSetup: Exiting ConnectorWizardForm.RunTasks
    [6932] 190601.112434.3830: ClientSetup: Running SetupVPNAndDA Task at WizardPage DomainUserCred
    [6932] 190601.112434.3830: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [6932] 190601.112434.3830: ClientSetup: Running Task with Id=ClientDeploy.SetupVpnAndDATask
    [6932] 190601.112434.4190: ClientSetup: Entering SetupVpnAndDATask.Run
    [6932] 190601.112434.4260: ClientSetup: Deploy VPN profile
    [6932] 190601.112434.4480: ClientSetup: Exting SetupVpnAndDATask.Run
    [6932] 190601.112434.4490: ClientSetup: Task with Id=ClientDeploy.SetupVpnAndDATask has TaskStatus=Success
    [6932] 190601.112434.4490: ClientSetup: Task with Id=ClientDeploy.SetupVpnAndDATask has RebootStatus=NoReboot
    [6932] 190601.112434.4490: ClientSetup: Exiting ConnectorWizardForm.RunTasks
    [6932] 190601.112434.4490: ClientSetup: Running ValidateUser Tasks at WizardPage DomainUserCred
    [6932] 190601.112434.4490: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [6932] 190601.112434.4490: ClientSetup: Running Task with Id=ClientDeploy.ValidateUser
    [6932] 190601.112434.4750: ClientSetup: Entering ValidateUserTask.Run
    [6932] 190601.112434.4750: ClientSetup: Validating User
    [6932] 190601.112434.4760: ClientSetup: Call MachineIdentityManager.GetMachineStatus
    [6932] 190601.112434.5060: General: Failed to open IDENTITY registry key.
    [6932] 190601.112434.5070: General: Failed to open IDENTITY registry key.
    [6932] 190601.112434.5070: General: Failed to open IDENTITY registry key.
    [6932] 190601.112434.5070: General: Failed to open IDENTITY registry key.
    [6932] 190601.112434.5070: General: Failed to open IDENTITY registry key.
    [6932] 190601.112434.5251: General: Failed to open IDENTITY registry key.
    [6932] 190601.112534.9557: 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)
    [6932] 190601.112534.9567: ClientSetup: ProcessHelper.StartProcessWithRedirectOutput() Executing "C:\WINDOWS\system32\ipconfig.exe"  /all
    [10068] 190601.112534.9847: ClientSetup: Standard Ouptput: 

    [redacted]

    =====

    BackupLaunchpad.log (same machine, Windows 10 1809 prior to in-place update to 1903):

    =====

    [2264] 190427.110129.7687: BackupLaunchpad: Program.Main(): BackupLaunchpad started
    [2264] 190427.110129.8357: General: Initializing...C:\Program Files\Windows Server\Bin\BackupLaunchpad.exe
    [2264] 190427.110129.9207: General: Color branding started
    [2264] 190427.110129.9207: General: Processing Microsoft default SKU branding colors XML
    [2264] 190427.110129.9317: General: Branding colors XML parsing started
    [2264] 190427.110129.9367: General: Branding colors XML parsing ended
    [2264] 190427.110129.9367: General: Looking for OEM branding colors XML
    [2264] 190427.110129.9367: General: No OEM informations available
    [2264] 190427.110129.9367: General: Color branding complete
    [2264] 190427.110130.1077: BackupLaunchpad: BackupLaunchpadControl constructed
    [2264] 190427.110130.1128: BackupLaunchpad: BackupDisconnectedControl constructed
    [2264] 190427.110130.1137: Backup: Trying to connect to provider Async.
    [2264] 190427.110130.1147: BackupLaunchpad: BackupLaunchpadProperties: constructed form
    [8] 190427.110130.1187: Backup: Waiting for connection with the provider.
    [1344] 190427.110135.2064: Backup: New connection detected. Try fetching all data
    [1344] 190427.110135.2304: Backup: Connected to provider Successfully
    [2264] 190427.110135.2304: BackupLaunchpad: Updated status to success
    [2264] 190427.110135.2314: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status Success and error None
    [2264] 190427.110135.2314: BackupLaunchpad: Updated status to success
    [2264] 190427.110135.2314: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status Success and error None
    [2264] 190427.110135.2314: BackupLaunchpad: Updated status to success
    [2264] 190427.110135.2324: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status Success and error None
    [2264] 190427.110135.2324: BackupLaunchpad: Synchronized state
    [2264] 190427.110135.2394: BackupLaunchpad: Updated status to success
    [2264] 190427.110135.2394: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status Success and error None
    [2264] 190427.110135.2394: BackupLaunchpad: Synchronized state
    [2264] 190427.110143.6196: BackupLaunchpad: Updated status to starting
    [2264] 190427.110143.8923: BackupLaunchpad: BackupLaunchpadControl.backupObjectModel_StartBackupAsyncCompletedEvent: StartBackupAsync ended
    [2264] 190427.110143.8933: BackupLaunchpad: Updated status to success
    [2264] 190427.110143.8933: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status Success and error None
    [2264] 190427.110143.9043: BackupLaunchpad: Updated status to progress 1

    ...

    =====



    Sunday, June 9, 2019 12:17 PM
  • Hi,

    In general, for system upgrade, it is recommended to un-install connector before upgrading and re-install connector to connect to WSE later.

    As you had mentioned that, system feature upgrade causing connection problem and re-install connector resolves the problem. If possible, please provide more detail information and I will test on my VM.
    1. Windows Server Essentials and client system before upgrade:
    Run “winver” on Windows Server Essentilas, provide me the detail OS version and build number.
    2. Detail error message or phenomenon about the failure connection from client to WSE.

    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, June 10, 2019 8:06 AM
    Moderator
  • Hi,

    How things are going there on this issue?

    Please let me know if you would like further assistance.

    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, June 12, 2019 2:30 AM
    Moderator
  • The issue is unchanged.  There are numerous posts on this site describing Windows 10 feature upgrades disabling the Essentials Connector.  Apparently, the connector will have to be uninstalled and reinstalled on each client.  Sad, but true...
    Wednesday, June 12, 2019 2:24 PM
  • Hi,

    Thank you for taking the time to share the details, I will try to reproduce it on my test environment.

    Also, as you mentioned that multi users and devices meet such problem, I will post such feedback to product team. Also, in general, as customer you can post such feedback via Windows Server General Feedback Forum:
    https://windowsserver.uservoice.com/forums/295047-general-feedback

    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, June 13, 2019 3:26 AM
    Moderator
  • I'm experiencing this issue with all my customers as well. The previous trick to flush DNS or restarting the PC a few times for connector to come alive again in the dashboard no longer works. As mentioned in this string, completely uninstalling the reinstalling the connector is the only solution at this time.

    Pete


    • Edited by pperry803 Saturday, June 15, 2019 8:20 PM
    Thursday, June 13, 2019 4:05 AM
  • Damn, I wish I had seen this BEFORE upgrading my clients to WIN10 v 1903.  I also installed KB4103712 to the server.  I am running WHS2011. Each major WIN10 client update has messed up the client connector.  This time, neither my server nor my clients can use the connector system to link--all report the others appear to be offline.
    Wednesday, June 19, 2019 12:31 PM
  • You have to go into the programs and features on each client/uninstall the connector and reinstall it.
    Thursday, June 20, 2019 3:49 PM
  • Eve,

    Come on now.  The Windows Server Essentials Connector for Windows Server 2012 R2 has been a problem for a long time and MSFT needs to upgrade the priority on an appropriate fix.  In my system I have one client on which I always have to re-install the connector using xxserver/Connect every time I install updates on the offending client.  After a major feature update ControlPanel/Programs and Features does not show Windows Essential installed, so I do it manually.  That has worked in the past, but with upgrade to Windows 10 1903 it does not work.  When executing Connect, all goes well until the end.  Then the program stops after the last step and I never get to Finish.  The Server has all of the current updates.

    On this offending client almost every update causes the Essentials application to be deleted.  Other clients do not have this problem.

    John

    Wednesday, July 10, 2019 9:22 PM
  • I'm having the same problem. WSE 2012 R2 on the server, Windows 10 build 1903 on three clients.

    But I can't even reinstall the Connector--when I get to the WSE Connector Configuration Wizard, it says "This server is not available. Try connecting this computer again."

    I've also tried downloading Connector from the Microsoft Download Center, but that install quits before it gets to the configuration wizard.

    I'm open to suggestions.

    Saturday, July 13, 2019 11:31 PM
  • Not sure your problem is the same as mine, but I have solved mine.  My solution was to uninstall the Connector first.  Earlier I had gone into Control Panel/Programs and Features and looked for something that began with Windows Server Essentials...  I knew it should be uninstalled first, but there was nothing there.  Then I found the name of the Connector application is “Client Connector for Windows Server Essentials”.  That seems a poor choice for the name.  Anyway I uninstalled that and then the new Connect feature worked.  It is very annoying that MSFT Windows 10 updates screws this up to begin with.  This ought to be a solvable problem and MSFT needs to fix it in the future.  It appears the Windows 10 people are not talking with the Server people.
    Saturday, July 13, 2019 11:58 PM
  • ****NEW SOLUTION****************

    Hi,

    I had the same problem on plain Essentials 2012.

    I followed all the advice like uninstalling the client, changing DNS, delete left other program data entries and task schedules, removing the computer from the server as already mentioned for other people.

    I was left with a situation where I was unable to reinstall the connector from the server.  It would find the server, but then abort with the generic problem with setup, please contact the network admin.

    The setup log would always show GetJoinedServerName: Failed to get the Server Name, under path: "SOFTWARE\Microsoft\Windows Server" with keyname: "ServerName". Err=2, even though previous steps in the log showed it getting the host name and downloading the setup.cab.

    I came across a blog that mentioned running a Powershell script to add multiple entries back to the registry, even though he is not sure it will work on plan Essentials 2012.  Please note the blog is in German, but can be easily translated in a popular search engines, but its quite self explanatory anyway.

    https://sbsland.me/2019/05/24/windows-10-update-1903-und-der-essentials-connector-fix/

    It is not my blog, but credit needs to be given to the author as he has fixed the issues, in fact many users mention that running the script does not need you to do any of the other actions like uninstall/reinstall connector first.

    I wish I had come across this before removing my client from the dashboard, as now I will need to do a full backup again which will take ages, but oh well at least my machine is up and running again.

    Hopefully this fixes the issues for you, and the message gets spread far and wide, as most threads seem to go round in circles with the same suggestions


    • Edited by Minimos Saturday, July 20, 2019 4:03 PM Bring attention to solution
    • Proposed as answer by Minimos Saturday, July 20, 2019 4:09 PM
    Saturday, July 20, 2019 4:03 PM
  • of my six systems all win10pro and server essen 2016, that fix did not work.
    Saturday, July 20, 2019 8:20 PM
  • Using Server Essentials 2016.  Was having this same issue on my Computer updated with 1903 a week ago.  Notice always offline and no backups since then.  

    I tried the usual Restart, Disable/Enable Ethernet, and nothing would get my computer to show back up as online.  

    So, I uninstalled the Essentials connector, signed out of my account.  Then logged into my local account (making sure I knew the password by updating it before signing out).  Installed the connector, which didn't go through all of it's normal sign out and resign-in processes.  It did the initial account sign in, and that was pretty much it.  It signed me out.  I signed in as normal after that, and now it's working.  

    My guess is that it's something with 1903, removing necessary established connections.  

    I've also had issues with recently updated computers not signing in at all after the 1903 install.  Restarting the server fixed this issue.  

    Wednesday, July 31, 2019 4:19 PM
  • I manage a small business running Essentials 2012 R2, I have 9 workstations running Win 10 Pro 1903.  I'm having problems with my client backups, but everything else seems to be ok.  When I check the services on the workstations none of them are missing the 5 that are mentioned in this thread, and the machines show up as "online" in the server dashboard.

    The problem I'm having is that the client backup service will frequently stop running on the server giving a critical error.  Checking event viewer I see Windows tries to restart the service a few times and then stops.  I can go back and restart it, but even when it's running about 25% of the backups fail with the status "unsuccessful", and inevitably the service will stop again anytime between an hour to a few days.  Is anyone else seeing behavior like this?

    • Proposed as answer by Peter400 Saturday, August 10, 2019 1:50 AM
    • Unproposed as answer by Peter400 Saturday, August 10, 2019 1:50 AM
    Wednesday, August 7, 2019 1:41 AM
  • I don't think this is due to 1903 update.  I've seen Client Backup failures like yours many times.  I'd say this problem warrants its own different thread.  Here is the solution, it has always worked for me over the years:

    I presume you have tried the built-in tool to Repair the database.


    I have found the scorched earth method always works, described below.

     

    How full is the backup drive?  Note that the drive you save Client Backups to needs to be much larger than you’d think, with lots of headroom.  And it has to be working properly (audit Events and use chkdsk).  I always use a separate internal drive just for the Client Backups.  A big one.  If you don’t have that, install a new large drive, then use the Dashboard built-in method to move the Client Backup folder to that new drive.

     

    Surefire fix, start from scratch:

     

    1.  Stop the Client Backup service: WseComputerBackupSvc

    2.  Delete Everything in the Client Backups folder (presumably nobody has put anything in there other than what the service puts there).

    3.  Restart the service.

    4.   In time, note in the Dashboard that Client Backup on all devices will show as not set up.

    5.   Re-setup the backup for a few devices.  Do a Manual backup for one of them, preferably that is not in much use and doesn’t have a large amount of data.  It should be successful and show some space being taken up (files generated) in the emptied backup folder.

    6.   Give it an overnight (presumably that is when the client backup is scheduled) and see how things worked.  Set up the rest of the devices.


     

     


    Peter

    Saturday, August 10, 2019 2:06 AM
  • this solution worked for me on all 4 computers I was having this same issue on.

    You will need to understand Powershell and know how to use it.

    Good Luck!

    Scott

    Friday, August 16, 2019 11:23 AM
  • I have tried all the suggested workarounds here with no luck. But I finally found a way: Join the computer manually to the domain (if it isn’already joined). Uninstall the client connector. Start command prompt as admin.Type «reg add "HKLM\SOFTWARE\Microsoft\Windows Server\ClientDeployment" /v SkipDomainJoin /t REG_DWORD /d 1» (without the exclamation marks «») and hit Enter. Restart computer. Install wse client connector. That sure was a tough one. Have spent countless hours trying to solve this :-).


    • Edited by Joen1 Tuesday, August 20, 2019 1:35 AM
    Tuesday, August 20, 2019 1:29 AM
  • This worked for me. Thanks for posting it. 

    However, I'm definitely going to look for an alternative backup solution. I have zero confidence in Microsoft's desire to support this product and, therefore, situations like this will continue to arise.

    Cheers 

    Lionel


     
    Tuesday, August 27, 2019 6:56 PM
  • This worked for me. Thanks for posting it. 

    However, I'm definitely going to look for an alternative backup solution. I have zero confidence in Microsoft's desire to support this product and, therefore, situations like this will continue to arise.

    Cheers 

    Lionel


     

    I believe this is response to my solution for Client Backup and not for the 1903 failure to connect problem.

    But your point may well apply to both:  Yes, I've seen no interest by Microsoft of correcting Client Backup's problems.

    And, I've seen these severe problems with the effect of client upgrades on Essentials networks and the ongoing problems with the connector.  Here to, the response of Microsoft seems disappointing and makes you wonder if they just don't much care about Essentials.


    Peter

    Wednesday, August 28, 2019 11:13 PM
  • I have tried all the suggested workarounds here with no luck. But I finally found a way: Join the computer manually to the domain (if it isn’already joined). Uninstall the client connector. Start command prompt as admin.Type «reg add "HKLM\SOFTWARE\Microsoft\Windows Server\ClientDeployment" /v SkipDomainJoin /t REG_DWORD /d 1» (without the exclamation marks «») and hit Enter. Restart computer. Install wse client connector. That sure was a tough one. Have spent countless hours trying to solve this :-).


    This could be the best solution.  Also, this could help to point out the root cause of the problem.

    First, for those worried about the registry change: This is the (safe) standard procedure provided by Microsoft for connecting to an Essentials server without having the Connector attempt to join the domain.

    https://docs.microsoft.com/en-us/windows-server-essentials/use/get-connected-in-windows-server-essentials#BKMK_10

    It is the given method to connect a "Home" version of Windows, or to connect a client that is already a member of a different domain.

    I think it should also be used to re-install the connector on a computer that is already (still) a member of the Essentials domain but just needs the connector installed.

    What I don't know is: Was the success for Joen1 the result of having the connector skip the domain join, or was it because the workstation had been removed from then manually reconnected to the domain (thus manually fixing some kind of corruption in the workstation's connection to the domain).

    Either way, I submit that the Connector software should be fixed to do the following:

    1.  Determine the state of the computer it is running on,  and make the registry change in situations where it is appropriate.

    2.  Be robust enough to detect whatever corruption exists in the computer's connection that is causing a problem, and either fixing it or else go through a procedure to remove and rejoin the domain, to fix the issue preventing Connector from properly completing.



    Peter

    Thursday, August 29, 2019 12:16 AM
  • The easy solution for this problem should already exist, given that a Feature update should be treated by Essentials as if it is a upgrade.

    Per Microsoft:

    "Important

    If you upgrade the operating system on a client computer, the Connector software is uninstalled automatically. You must reinstall the Connector software after the upgrade is complete. The preferred method is to uninstall the Connector software before you upgrade the operating system. Uninstalling the Connector software after the upgrade is complete is still acceptable; however, it might result in an inconsistent state for the client computer with the server until the Connector software is uninstalled and reinstalled."

    The problem is, this automatic uninstall of Connector has not actually ever worked right.

    That became most obvious back when people did the free upgrade from Windows 7 to Windows 10:  the Windows 7 connector continued to run (but completely fails to do what it is supposed to do) on the Windows 10.  And it was impossible without hacking to uninstall that Windows 7 connector once in Windows 10 since back then Connector was in Updates (which is wiped in the upgrade), not in Add and Remove Programs.

    Again, we see the solution for these problems that have existed all along would be for Microsoft to finally make Connector work they way it should.


    Peter


    • Edited by Peter400 Thursday, August 29, 2019 12:39 AM added quotation marks
    Thursday, August 29, 2019 12:37 AM
  • Per the other thread on this subject:

    "These instructions worked consistently for 12 client machines that were upgraded to the 1903 release. These are just nuances to the instructions above that may help you do this more easily.
    Uninstall Client Connector for Windows Server Essentials.
    Say yes to automatically closing  the system tray app.
    Open Task Scheduler.
    Inside the Task Scheduler Library, navigate to Microsoft > Windows > Windows Server Essentials  and delete every task in that folder. I deleted the folder too. Probably not necessary.
    Open a web browser and navigate to your server's Connect page: - you may need "https" depending on your local network setup. Examples:
    http://[ip address of server]/connect  OR
    http://[name of WSE Server]/connect
    Follow the instructions to connect the machine.
    I found that this worked without restarting any machines and that the Windows Server Essentials 2012R2 Dashboard app updated immediately without a refresh."

    This plus another reply where they found that the Connector software Uninstall removed the registry entry to skip domain join.  So you would have to redo that entry if needed to have the client connect to Essentials without attempting to join the domain.

    Two more things for Microsoft to fix in the Connector software Uninstall.


    Peter

    Thursday, August 29, 2019 9:07 PM
  • This procedure is not working for me.

    When this update first came out some months ago I had this issue and rolled all machines back.  This past week it resurfaced and insisted on installing so I thought that any issues would have been corrected by then.

    I now have 7 clients that are no longer connecting to the server.  This is invisible to the users, all functions are normal.  But I can no longer monitor health nor do my daily backups.  Somewhat risky as I have a two users that tend to nuke file systems from time to time with the familiar "I didn't do anything".

    I am testing the procedure on my laptop.  Which was formerly working just fine.  

    I uninstall, remove tasks, remove task folder, download the client connector from the server and install.  

    Results in no change at all.

    I am extremely reluctant to remove the machines from the domain and rejoin using the process in the windows 10 settings as this will result in having to create a new user domain profile, then copy across the profile, an other process fraught with potential problems.

    At this point, since tomorrow is the first day of September and updates should be released on Tuesday, I will wait to see if the next cycle improves the situation.

    If not I guess it is roll back time and block all further updates.

    Windows Server 2012R2 Japanese with English also installed.

    And all client machines running windows 10 pro.  Also native Japanese with 4 of them set for bilingual and 3 of them in Japanese only.

    It seems laughably absurd that this issue was not flagged before the update release and corrected.  Do the windows 10 people not talk to the windows server people at all?  Are they ring fenced from each other at MS?

    --------------------------------------------------------

    Dave (highly irritated, mostly at the waste of time).

    • Proposed as answer by vmandic Saturday, August 31, 2019 10:58 AM
    Saturday, August 31, 2019 8:08 AM
  • For anyone who still have issues with client connector this is the solution that worked for me.

    After upgrade to ver.1903 (about a week ago, since I had to wait update from Trend Micro for WFBS)  I immediately noticed that my client machine was marked offline on server console, so I did restart server, uninstall and reinstall connector, also in all desperation I deleted client machine from server and tried to add it again by reinstalling connector-nothing worked. So I decided to add it to the domain as usual, log in as local admin add it to the domain and everything goes smoothly as expected. Also just to let you know all shortcuts to shared folders were working after upgrade while I was trying to get connector to work and show my client as "online" again.

    My other client machines (win 8.1 and win 7) had no problem with all of this so it was annoying since I was unable to see my win 10 clients and follow their status and being unable to do scheduled backups.   

    To make it short this is what I did:

    - put the client win 10 manually on domain

    - started connector installation usual way through web browser with only difference that I didn't run the connector when prompted, instead I saved it in "downloads" folder on client machine

    - selected downloaded connector file, right clicked and select troubleshoot compatibility, choose win 8, and tested (it will fail, no worries just let it do this thing, (it's Microsoft after all) after that it asks me is it started correctly and I selected answer that it is successful  (although that was not true) 

    - after that I started connector installation again through web browser as usual and "boom" It goes smoothly as nothing happened before. Worked on all 3 win 10 upgraded machines.


    Saturday, August 31, 2019 11:26 AM
  • For anyone who still have issues with client connector this is the solution that worked for me.

    After upgrade to ver.1903 (about a week ago, since I had to wait update from Trend Micro for WFBS)  I immediately noticed that my client machine was marked offline on server console, so I did restart server, uninstall and reinstall connector, also in all desperation I deleted client machine from server and tried to add it again by reinstalling connector-nothing worked. So I decided to add it to the domain as usual, log in as local admin add it to the domain and everything goes smoothly as expected. Also just to let you know all shortcuts to shared folders were working after upgrade while I was trying to get connector to work and show my client as "online" again.

    My other client machines (win 8.1 and win 7) had no problem with all of this so it was annoying since I was unable to see my win 10 clients and follow their status and being unable to do scheduled backups.   

    To make it short this is what I did:

    - put the client win 10 manually on domain

    - started connector installation usual way through web browser with only difference that I didn't run the connector when prompted, instead I saved it in "downloads" folder on client machine

    - selected downloaded connector file, right clicked and select troubleshoot compatibility, choose win 8, and tested (it will fail, no worries just let it do this thing, (it's Microsoft after all) after that it asks me is it started correctly and I selected answer that it is successful  (although that was not true) 

    - after that I started connector installation again through web browser as usual and "boom" It goes smoothly as nothing happened before. Worked on all 3 win 10 upgraded machines.


    And did this result in new profiles on the client machines?
    Saturday, August 31, 2019 3:20 PM
  • Plain and simple, it didn't create new profiles, user accounts haven't changed since I didn't removed them, and soon as user logged in with their credentials everything is as it was before. 

    Saturday, August 31, 2019 10:14 PM
  • Well not working for me.

    I took the computer off the domain, logged in as a local user.  Downloaded the connector from the local server, there was and has never been an option to just run the connector, only a button dead centre on the monitor to download connector software.

    Stepped through the connector setup, faltered a few times on the domain name, could not locate it, finally found it.  Stepped through that process.  Joined domain.  New profile created.  Restart.

    And presto, no change.

    Laptop is still not showing as available on the device tab of dashboard.  All functions from the client to the server work, sales database is doing it's thing.  Full range of files and directories are available.

    However now my dashboard is showing about 12 alerts, two critical.  All probably not real.

    I tried doing a rollback on the laptop and that said I waited more than ten days, I count 4, so no longer possible.

    I did roll back one client machine and it is showing a critical error for services not running.  Checked the services listed and they are indeed running so not sure what the issue is there.

    I am extremely reluctant to mess with any of the other clients until I find a solution that works on my Laptop, reinstallation of the OS on my Laptop, though no fun, will not be the end of the planet.   Doing all my client computers will be an all day affair and fraught with issues.

    Will give it one more go, but at some point will have to throw in the towel.

    I bought a Windows server so that I did not have to mess about with this stuff.  Maybe it is time to load up some version of Linux on one of my old rack mounts and move on. 


    Tuesday, September 3, 2019 9:25 AM
  • FWIW, all the machines in my environment are running 1903 without issue with Windows Server 2016 Essentials. 

    Only some of my clients are domain-joined, but I always enable the SkipDomainJoin registry key on the client prior to installing the Connector regardless.  This keeps the Connector installation simple, and avoids user account and data migration on the client. (That is a complex step that could easily have dependencies on Windows 10 versions.)  Later, it's easy enough to add the machine to the domain as needed. 

    In case this helps.

    Edit: I missed that this discussion was specifically for 2012 Essentials, so maybe there is something different going on. Sorry for the confusion.


    • Edited by Gary Voth Tuesday, September 3, 2019 2:08 PM
    Tuesday, September 3, 2019 2:06 PM
  • Now this is getting strange.

    Today I removed the connector, ran a registry cleaner.  

    Tried running the connector software DL from MS.  Did not complete install.

    WSEClient-x64.msi

    Next step, browsed on to my server via Edge, because reasons.  I seldom use edge but someone said to try that.

    Downloaded the connector software from there again, a bit miffed that it says it is for Windows 7 SP1, Windows 8 and Windows 8.1 but no mention of Windows 10.

    Ran that again.

    Stepped through the details.

    Software says connector now installed.

    Computer still not showing up on the dashboard as active.  Can not do backups.  Now have 15 warnings for various things on the dashboard.  I am used to no warnings and everything green so this is highly irritating.

    But now I can run the dashboard from the client laptop.  Is this not strange?  On the dashboard open on the laptop it shows the laptop as not available.  But clearly it is available.

    I can open the launch pad, it has that little blinking flag showing the server offline, at the same time as the dashboard is open.

    I am also able to start a backup but it fails right away.

    Shared folders will open the shard folders in a windows explorer.

    One last point, my internet connection on the laptop shows me as connect to the domain, all the time, even when I remove the connector software, even when I previously pulled the machine off the domain and went to a local account.

    So, any new ideas?

    At some point I am going to have enough warnings on the dashboard that the information will be useless.

    I am already starting to get warnings about machines not having been backed up in a while. 

    Enough for tonight.  Tired.


    • Edited by pureheart999 Friday, September 6, 2019 10:25 AM word choice
    Wednesday, September 4, 2019 6:55 PM
  • WSE Reconnect – a slightly easier solution

    In one of our locations with 15 computers we decided to install the feature upgrade to Windows 10 Version 1903. Of all the computers there is a very stable and trouble-free Windows 7 Pro and another is a recently built computer with Win10 V1903. After the feature upgrades those were the only two computers still talking with the DC running Windows Server Essentials 2016.

    Comparing the working Win10 system with the others it appears that the feature upgrade simply wipes out the 5 Windows Essentials services from the client computers. Rather than go through deletion and a reinstall process, you can run a repair on the “Client Connector for Windows Server Essentials” in Program and Features. The executable needed for this was originally installed in “Windows\Temp\ClientDeploymentTempFiles"Win when the computer joined the domain. If the folder no longer exists you can retrieve it using the Connect software from the server.

    This can all be done remotely – your sneakers will thank you.

    To retrieve the folder do the following:

    1. Log on as the Domain Administrator
    2. Perform a partial Connect with the connector software "//Your_Server/Connect"
    3. At the Enter user name screen
    4. Go to the Windows Temp folder and take a copy of the folder "ClientDeploymentTempFiles"
    5. Close the Connect program

                This folder has the required “WSEClientx64.msi” (or x86) program in it. You will need to click through the "You don’t have permission to access this folder warning”.

    To reconnect Windows essentials to a client computer do the following:

    1. Log on to client computer as the Domain Administrator and paste the temp folder into C:\Windows\temp
    2. Go to Control panel - Programs and Features
    3. Select "Client Connector for Windows Server Essentials" and click on Repair - allow the process to finish

    Next Run Services.msc

    1. Set all the Windows Essentials services to manual (they will all be set as disabled)
    2. Start the second service "Windows Server Essentials Client Computer Monitoring Service"

    ... and Voila! - WSE is reconnected.

    Instead of hand cranking the services you can use the following lines in a CMD file and “Run as administrator” to configure the services and start WseClientMonitorSvc.

    @Echo off

    sc config WseClientMgmtSvc start= demand

    sc config WseClientMonitorSvc start= demand

    sc config WseHealthSvc start= demand

    sc config WseNtfSvc start= demand

    sc config ServiceProviderRegistry start= demand

    Echo.

    sc start WseClientMonitorSvc

    Echo.

    Pause

    When all that is done consider implementing the following Group Policy.

    Computer Configuration / Administrative Templates

    Windows Components/Windows Update/Defer Windows Updates

    Select when Feature Updates are received       Enabled          

    After a feature update is released, defer receiving it for this many days:         180

    That should provide a break of few months when you can actually do something other than deal with the latest MS update bug.

    Hopefully this will work for others. Now on to the other 36 computers left to do.

    Thursday, September 5, 2019 2:43 PM
  • FredDeTech thank you for the suggestion.  Worth a try.

    I have some items that are not quite the same as what you are showing.

    1 - I am using Win2012-R2 not the same server version you have.

    2 - The services to which you are referring are still shown as present and running, well most of them are running.  And I can start the ones not running.  This is on one of my clients which is not showing up on the dashboard as connected even when on and when actively using network features.  This machine was updated with the 1903 windows update at the end of August.  And from that point not diddled with, it is a production machine and since the needed domain functions were working I did not want to risk mucking it up.

    3 - on my laptop, which I am using as a test machine for attempts to reconnect, these services were present and not running.  Started them all.  The machine still shows as not connected.  I then did a repair from control panel on the connector.  I did not know that was an option as I was previously using the windows settings thing and it has a pruned set of abilities.  After the repair the services were still there and not started, started them all, no change.

    I have now removed the connector software via the control panel and presto these services have vanished.  Oddly the internet connection still shows this machine as on the domain.

    I will now try to install the connector software again and see if it works, I am of faint heart about the chances here.  I have poked and prodded this laptop so many times over the past week I fear it may suffer a psychic break with normalcy soon.

    Running the ComputerConnector(###.###.##.##).exe file now....

    Server found, rapidly this time

    Credentials input

    Selected "setup for myself"

    Entered computer description

    Selected backup only if on

    Software reports now connected to the server.

    Offers to allow me to open the dashboard (I took a quick peek at the dashboard on the server and client machine shows as offline)

    Press finish

    Enter credentials to open dashboard

    Close and reopen services, Windows Server Essentials various services now present and running

    Dashboard opens on client

    Dashboard shows same client as it is open on as not available

    Since I have essentially done everything now I am thinking of just doing a bare metal install of Windows 10 on my Laptop, remove the vestiges of that machine from the server and seeing if that allows it to reconnect.  But this is a fair bit of work to do when the issue seems to stunningly trivial.

    Open to ideas!  Would be very open to someone from MS popping up with an actual solution!


    • Edited by pureheart999 Friday, September 6, 2019 10:24 AM punctuation
    Friday, September 6, 2019 10:21 AM
  • Contacted MS support today.

    An absolute waste of time.  

    I would have been better off sticking my hand in a running food processor. 

    Tuesday, September 10, 2019 9:47 AM
  • This process worked for me and does not require any reboots.  You do need to go to each client though.  

    Download the WSEClient-x64.msi from https://www.microsoft.com/en-au/download/details.aspx?id=40285 It's Australia but it works.  Perhaps someone can provide the US link.

    Copy the msi file to the client machine at c:\windows\temp\ClientDeploymentTempFiles  you will be prompted to get access to this location

    From control panel, select the "Client Connector for Windows Server Essentials" and select repair

    The services are installed but are all dissabled.  

    Open each service and set startup type to manual.

    After setting them all to manual, Start the "Windows Server Essentials Client Computer Management Service"

    The computer will now show as online in the dashboard.


    Many Thanks, JP

    Thursday, September 12, 2019 1:59 PM
  • Next machine I went to do this on needed an additional step.  I re-ran the connector software.  I used the admin account as to not but the user for their password.  It installed quick and easy and did not give the warning that the computer is already on the domain.  I did not do the reg key addition to skip the domain join.  Once it finished, it said it was going to log off the user, but it did not, and the connector turned green and showed up as online on the dashboard.  

    I will post further issues as I go through the clients.


    Many Thanks, JP

    Thursday, September 12, 2019 3:28 PM
  • This process worked for me and does not require any reboots.  You do need to go to each client though.  

    Download the WSEClient-x64.msi from https://www.microsoft.com/en-au/download/details.aspx?id=40285 It's Australia but it works.  Perhaps someone can provide the US link.

    Copy the msi file to the client machine at c:\windows\temp\ClientDeploymentTempFiles  you will be prompted to get access to this location

    From control panel, select the "Client Connector for Windows Server Essentials" and select repair

    The services are installed but are all dissabled.  

    Open each service and set startup type to manual.

    After setting them all to manual, Start the "Windows Server Essentials Client Computer Management Service"

    The computer will now show as online in the dashboard.


    Many Thanks, JP

    This process is not working for me.

    I did install updates again early this week on all machines, including the domain controller.  But still not showing as connected on dashboard.

    Dashboard still opens on clients and all functions still work.  Just unable to do nightly backups on clients.

    Thursday, September 12, 2019 3:52 PM
  • I can confirm that the update breaks the connection on two levels. If you use the built in Windows Update, you will lose connection to the Windows Server. This includes file share folders and any apps your client uses from the server. If you use Windows Update Assistant you can still use the share folders and apps; the client does not know its not connected, but you will lose the connection to the server as far as the server is concerned. The dashboard will show any client updated with Windows Update Assistant as offline. Meaning, you will not be able to remote into the clients from the server and you won't be able to backup / restore client folders. You lose all monitoring benefits. 

    https://smulholland.me/blog/windows-update-1903-and-windows-server-connection-issues

    https://smulholland.me/blog/windows-update-1903-and-windows-server-connection-issues-part-2/

    Saturday, September 21, 2019 11:51 PM
  • Sorry it didn't do the trick for you.  Apparently this happened before and I found a different solution back then.  Wish I remembered that.  

    https://social.technet.microsoft.com/Forums/en-US/041fd2d3-a38c-46ce-bc26-4fc302a6e7a0/not-able-installreinstall-client-connector-on-windows-10-anniversary-update?forum=winserveressentials

    Below is the solution I proposed at that time.  Perhaps it will work for you.  The steps taken are on the client machine, not the server.  Be careful.

    Thank you for everyone who tried to help. I found solution for my problem. To make connector works on all my computers, I executed the following steps:

    1. Uninstall connector
    2. Delete folders under C:\ProgramData\Microsoft\Windows Server
    3. Start "task scheduler" and delete all tasks in folder Microsoft -> Windows -> Windows Server Essentials.  Delete "Windows Server Essentials" itself
    4. Reboot
    5. Execute registry change to SkipDomainJoin (required only if you don't want that computer will be part of your domain, otherwise you can skip this step):

    reg add "HKLM\SOFTWARE\Microsoft\Windows Server\ClientDeployment" /v SkipDomainJoin /t REG_DWORD /d 1

    6. Install connector from http://server/connect

    On all my computers I didn’t see any single warning/error about "task scheduler". All 4 computers had similar logs (which I posted above). What is strange, till I deleted folder "Windows Server Essentials" itself (not only tasks inside), connector installation was crashing.


    Many Thanks, JP

    Monday, September 30, 2019 2:19 PM
  • I am also experiencing this problem. 

    My client computers do not seem to have the windows server essentials uninstall programs but I still see the dashboard.  It shows the little alert flag in the bottom left corner of the window.  However, when I click the server dashboard and I log in, the dashboard displays from the server.

    I tried installing the client connector without being able to uninstall.  Very quickly after entering my domain credentials into the install wizard, the installation stopped and nothing was fixed.  

    My desktop systems haven't been backing up for about 1 month now.  I really hope this gets fixed soon.

    Thursday, October 3, 2019 3:31 AM
  • Did you use domain admin credentials in the wizard?  Also I would try downloading the file as opposed to just hitting run, and then right click the file and run as administrator.  I recall somewhere in an old post or maybe this one, there is a registry to skip domain join which may or may not help.   Sorry I can't be of more help.

    Many Thanks, JP

    • Proposed as answer by ldwhyte Friday, November 15, 2019 6:04 PM
    • Unproposed as answer by ldwhyte Friday, November 15, 2019 6:05 PM
    • Proposed as answer by ldwhyte Friday, November 15, 2019 6:05 PM
    • Unproposed as answer by ldwhyte Friday, November 15, 2019 6:18 PM
    Monday, October 7, 2019 7:25 PM
  • The only solution that worked for me (server ess 2016 using domain skip on all 6 computers) was to restore to a previous backup, remove the connector, run the 1903 update then reinstall the connector, also if anyone has been waiting for the 1909 don't, )if you have not installed the 1903 update the 1909 will break the connector aswell!  I left one laptop(all running Win10pro) with 1809 (not for sure but the latest before 1903)  same issue as the 1903 showing offline in the dashboard and loss of connection to the server.  so I'll do a image recovery from the server, remove the connector, complete all updates including the 1909 before reinstalling the connector again.  Hope this helps someone.
    • Edited by ldwhyte Friday, November 15, 2019 6:14 PM
    Friday, November 15, 2019 6:12 PM
  • Well three months now and nothing works.

    Can not resolve by removing and installing connector.  Have used all the various methods and "stand on one foot while typing password" type of ideas.

    All machines still able to access server.

    Dashboard not working on any of them.

    Backup not being done on any clients.

    What a mess.  What a waste of time.

    Do the people that make the updates for Windows 10 not tell the people that do the server stuff what they are doing?

    12 hours 9 minutes ago