none
Windows Server 2016 Essentials Client Connector stops working with Windows 10 1803

    Question

  • Just upgraded one machine to build 17115 of Windows 10 1803 (as it was looking 99% ready for release). After the upgrade, the Windows Server Essentials 2016 Client Connector shows now connection (was fine before - had just completed a backup).

    Tried running the setup to reconnect, but fails with the ever so useful "an unexpected error has occurred". Tried uninstalling and reinstalling, including clearing the relevant ProgramData folder registry entries and redownloading the installation from the server. All of them fail.

    ClientDeploy log files shows:

    ---------------------------------------------------------
    [25412] 180307.070117.9039: ClientSetup: Start of ClientDeploy
    [25412] 180307.070117.9820: General: Initializing...C:\Program Files\Windows Server\Bin\ClientDeploy.exe
    [25412] 180307.070117.9976: ClientSetup: Create client deployment registry subkey if necessary
    [25412] 180307.070117.9976: ClientSetup: The initial launching way: -LaunchedFrom:installer
    [25412] 180307.070117.9976: ClientSetup: The initial state is set
    [25412] 180307.070117.9976: ClientSetup: The initial serverName: [fe80::9c58:18b3:3d89:6cdf]
    [25412] 180307.070117.9976: ClientSetup: Loading Wizard Data
    [25412] 180307.070118.0133: ClientSetup: Saving Wizard Data
    [25412] 180307.070118.0133: ClientSetup: Current DeploymentStatus=Start
    [25412] 180307.070118.4195: ClientSetup: Showing the Client Deployment Wizard
    [25412] 180307.070118.7164: ClientSetup: The input server name is [fe80::9c58:18b3:3d89:6cdf]
    [7804] 180307.070118.7164: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [7804] 180307.070118.7164: ClientSetup: Running Task with Id=ClientDeploy.PreConfiguration
    [7804] 180307.070118.7320: ClientSetup: The configuration cab will be downloaded from [fe80::9c58:18b3:3d89:6cdf]
    [7804] 180307.070118.7320: ClientSetup: Download file Setup.cab from server
    [25412] 180307.070118.7320: ClientSetup: InitWizard, The currrent stage is ConnectingToServer
    [25412] 180307.070118.7320: ClientSetup: Set the Deployment Sync Event
    [7804] 180307.070118.7320: ClientSetup: Making web request: https://[fe80::9c58:18b3:3d89:6cdf]//connect/default.aspx?Get=Setup.cab&LanguageId=2057&64bit=1
    [7804] 180307.070118.7789: 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)
    [7804] 180307.070118.7789: ClientSetup: Cannot get configuration file with https, will try http...
    [7804] 180307.070118.7789: ClientSetup: Download file Setup.cab from server
    [7804] 180307.070118.7789: ClientSetup: Making web request: http://[fe80::9c58:18b3:3d89:6cdf]//connect/default.aspx?Get=Setup.cab&LanguageId=2057&64bit=1
    [7804] 180307.070119.3101: ClientSetup: Downloaded file C:\WINDOWS\Temp\ClientDeploymentTempFiles\Setup.cab
    [7804] 180307.070119.3101: ClientSetup: The configuration cab is downloaded to C:\WINDOWS\Temp\ClientDeploymentTempFiles\Setup.cab
    [7804] 180307.070119.4039: ClientSetup: Adding Server Info data in the Product Registry
    [7804] 180307.070119.4351: Networking:DnsEnvironmentDetector: Dns.GetHostAddresses threw exception: System.Net.Sockets.SocketException (0x80004005): No such host is known
       at System.Net.Dns.GetAddrInfo(String name)
       at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6)
       at System.Net.Dns.GetHostAddresses(String hostNameOrAddress)
       at Microsoft.WindowsServerSolutions.Networking.ServerDiscovery.DnsEnvironmentDetector.GetAddressesFromDns(String machine)
    [7804] 180307.070119.4351: ClientSetup: SkipDomainJoin hook is set, skip domain join
    [7804] 180307.070119.4351: ClientSetup: Exiting PreConfigTask.Run()
    [7804] 180307.070119.4351: ClientSetup: Task with Id=ClientDeploy.PreConfiguration has TaskStatus=Success
    [7804] 180307.070119.4351: ClientSetup: Task with Id=ClientDeploy.PreConfiguration has RebootStatus=NoReboot
    [7804] 180307.070119.4351: ClientSetup: Exiting ConnectorWizardForm.RunTasks
    [7804] 180307.070127.2007: ClientSetup: Running InstallRootCert Task at WizardPage DomainUserCred
    [7804] 180307.070127.2007: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [7804] 180307.070127.2007: ClientSetup: Running Task with Id=ClientDeploy.InstallRootCertTask
    [7804] 180307.070127.2007: ClientSetup: Entering InstallRootCertTask.Run
    [7804] 180307.070127.2163: ClientSetup: Install root cert to local trusted store
    [7804] 180307.070127.2163: ClientSetup: Exiting InstallRootCertTask.Run
    [7804] 180307.070127.2163: ClientSetup: Task with Id=ClientDeploy.InstallRootCertTask has TaskStatus=Success
    [7804] 180307.070127.2163: ClientSetup: Task with Id=ClientDeploy.InstallRootCertTask has RebootStatus=NoReboot
    [7804] 180307.070127.2163: ClientSetup: Exiting ConnectorWizardForm.RunTasks
    [7804] 180307.070127.2163: ClientSetup: Running SetupVPNAndDA Task at WizardPage DomainUserCred
    [7804] 180307.070127.2163: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [7804] 180307.070127.2163: ClientSetup: Running Task with Id=ClientDeploy.SetupVpnAndDATask
    [7804] 180307.070127.2163: ClientSetup: Entering SetupVpnAndDATask.Run
    [7804] 180307.070127.2319: ClientSetup: SkipDomainJoin hook is set, skip domain join
    [7804] 180307.070127.2319: ClientSetup: Deploy VPN profile
    [7804] 180307.070127.2319: VPN Client Utils: Error 632 returned from RasSetEntryProperties.
    [7804] 180307.070127.2476: ClientSetup: RAS exception: An incorrect structure size was detected.
    [7804] 180307.070127.2476: ClientSetup: Exting SetupVpnAndDATask.Run
    [7804] 180307.070127.2476: ClientSetup: Task with Id=ClientDeploy.SetupVpnAndDATask has TaskStatus=Failed
    [7804] 180307.070127.2476: ClientSetup: Task with Id=ClientDeploy.SetupVpnAndDATask has RebootStatus=NoReboot
    [7804] 180307.070127.2476: ClientSetup: Exiting ConnectorWizardForm.RunTasks
    [25412] 180307.070127.2476: ClientSetup: JoinNetwork Tasks returned TaskStatus=Failed
    [25412] 180307.070155.2862: ClientSetup: Back from the Client Deployment Wizard
    [25412] 180307.070155.2862: ClientSetup: Saving Wizard Data
    [25412] 180307.070155.2862: ClientSetup: End of ClientDeploy: ErrorCode=1603

    And when starting the ClientConnector (which has been installed through this process) shows

    [03/07/2018 07:01:03 3b08] --------------------------------------------------------------------------------------------------
    [03/07/2018 07:01:03 3b08] wmain: Start of Computerconnector
    [03/07/2018 07:01:03 3b08] GlobalData::Initialize ([fe80::9c58:18b3:3d89:6cdf], C:\Users\Andrew\Downloads\ComputerConnector(fe80__9c58_18b3_3d89_6cdf).exe)
    [03/07/2018 07:01:03 3b08] =================================
    [03/07/2018 07:01:03 3b08] Current Os information:
    [03/07/2018 07:01:03 3b08] Suite = [256]
    [03/07/2018 07:01:03 3b08] Type = [1]
    [03/07/2018 07:01:03 3b08] Architecture = [9]
    [03/07/2018 07:01:03 3b08] IsStarterEdition = [0]
    [03/07/2018 07:01:03 3b08] IsHomeSku = [0]
    [03/07/2018 07:01:03 3b08] Major = [10]
    [03/07/2018 07:01:03 3b08] Minor = [0]
    [03/07/2018 07:01:03 3b08] Build = [17115]
    [03/07/2018 07:01:03 3b08] SPMajor = [0]
    [03/07/2018 07:01:03 3b08] SPMinor = [0]
    [03/07/2018 07:01:03 3b08] =================================
    [03/07/2018 07:01:03 3b08] ExpandEnvironmentStrings return (C:\WINDOWS\Temp\ClientDeploymentTempFiles\)
    [03/07/2018 07:01:03 3b08] SetPackageDlcUrl: .NET url is set to http://go.microsoft.com/?linkid=9816306
    [03/07/2018 07:01:03 3b08] SetPackageDlcUrl: Connector url is set to http://go.microsoft.com/fwlink/?LinkId=789477
    [03/07/2018 07:01:03 3b08] wmain: Calling Computerconnector::ShowWizard()
    [03/07/2018 07:01:03 3b08] CComputerconnector::ShowWizard: Initializing common controls
    [03/07/2018 07:01:03 3b08] CComputerconnector::ShowWizard: Done initializing common controls
    [03/07/2018 07:01:03 3b08] Displaying the wizard
    [03/07/2018 07:01:03 3b08] CComputerconnector::WelcomeDlgProc: IDD_PROPPAGE_WELCOME Page Initialization
    [03/07/2018 07:01:03 3b08] Current user default UI lang setting is 2057
    [03/07/2018 07:01:03 45c0] CComputerconnector::Run: Installation is ready to run
    [03/07/2018 07:01:17 3b08] CComputerconnector::TaskDlgProc: IDD_PROPPAGE_TASKS Page Initialization
    [03/07/2018 07:01:17 2e6c] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Detecting the current system requirements... Index=  0
    [03/07/2018 07:01:17 2e6c] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {21E49794-7C13-4E84-8659-55BD378267D5} returned -1
    [03/07/2018 07:01:17 2e6c] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {46DCED50-3A1D-4EF4-94F0-45F2681E3D70} returned -1
    [03/07/2018 07:01:17 2e6c] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {C1E4D639-4A33-4314-809E-89BD0EF48522} returned -1
    [03/07/2018 07:01:17 2e6c] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {563CB0AF-E0B5-42B1-AB42-8E6964349900} returned 5
    [03/07/2018 07:01:17 2e6c] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Downloading .NET Framework 4.5... Index=  1
    [03/07/2018 07:01:17 2e6c] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Installing .NET Framework 4.5... Index=  2
    [03/07/2018 07:01:17 3b08] CComputerconnector::TaskDlgProc: DIALOG_UPDATE: Running
    [03/07/2018 07:01:17 2e6c] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Downloading the Connector... Index=  3
    [03/07/2018 07:01:17 2e6c] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Installing Windows Server Essentials Connector... Index=  4
    [03/07/2018 07:01:17 3b08] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Detecting the current system requirements...
    [03/07/2018 07:01:17 2e6c] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Starting the Windows Server Essentials Connector configuration... Index=  5
    [03/07/2018 07:01:17 2e6c] RunShellExecute: ShellExecute [C:\Program Files\Windows Server\Bin\ClientDeploy.exe] with parameters [ -Server:[fe80::9c58:18b3:3d89:6cdf] -LaunchedFrom:installer]
    [03/07/2018 07:01:17 3b08] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Downloading .NET Framework 4.5...
    [03/07/2018 07:01:17 3b08] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Installing .NET Framework 4.5...
    [03/07/2018 07:01:17 3b08] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Downloading the Connector...
    [03/07/2018 07:01:17 3b08] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Installing Windows Server Essentials Connector...
    [03/07/2018 07:01:17 3b08] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Starting the Windows Server Essentials Connector configuration...
    [03/07/2018 07:01:17 2e6c] CComputerconnector::Run: Waiting upto 60secs for Sync Event to be signaled
    [03/07/2018 07:01:18 2e6c] CComputerconnector::Run: WaitForSingleObject RetVal = 0
    [03/07/2018 07:01:18 3b08] CComputerconnector::TaskDlgProc: DIALOG_UPDATE: Success
    [03/07/2018 07:01:18 3b08] wmain: End of Computerconnector: hr=0x0

    Has anyone successfully managed to get the Essentials 2016 Client Connector working successfully on any recent builds of Windows 10 1803?

    I have reported this back via Feedback app on Windows 10 as well, as it does look like a regression issue with Windows 10, or some features in Windows 10 - but could be something that needs fixing from the WSE2016 side.

    Obviously this is a breaking issue for WSE2016 users wanting to upgrade to 1803 when it starts getting pushed out, and needs to be addressed as a matter of urgency.

    *** just checked install of the client connector on a fresh VM with build 17101 and exactly the same issue occurs ***
    Wednesday, March 7, 2018 7:06 AM

All replies

  • Hi,

    [7804] 180307.070127.2319: VPN Client Utils: Error 632 returned from RasSetEntryProperties.
    [7804] 180307.070127.2476: ClientSetup: RAS exception: An incorrect structure size was detected.
    [7804] 180307.070127.2476: ClientSetup: Exting SetupVpnAndDATask.Run
    [7804] 180307.070127.2476: ClientSetup: Task with Id=ClientDeploy.SetupVpnAndDATask has TaskStatus=Failed
    [25412] 180307.070155.2862: ClientSetup: End of ClientDeploy: ErrorCode=1603

    Based on the log file, it seems that problem happens during VPN configuration. So, I want to confirm with you:
    1. If you had manually added skipdomain registry on client to skip domain join.
    2. If VPN function has been enabled on WSE?

    If possible, please try to check/repair Anywhere Access and confirm that if there is any error/warning prompts:
    Dashboard - Settings - Anywhere Access - Repair

    >Has anyone successfully managed to get the Essentials 2016 Client Connector working successfully on any recent builds of Windows 10 1803?
    Please provide detail OS name and version of WSE 2016 and Problematic Windows 10:
    Run “msinfo32” check detail OS name, run “winver” check detail OS Build.

    And I will try to reproduce it on my test environment.

    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, March 8, 2018 3:56 AM
    Moderator
  • Thanks

    1. If you had manually added skipdomain registry on client to skip domain join - Yes I have

    2. If VPN function has been enabled on WSE? - Yes it is

    If possible, please try to check/repair Anywhere Access and confirm that if there is any error/warning prompts: Dashboard - Settings - Anywhere Access - Repair

    I will do this later and test again. I will also switch VPN Access off to see if the client then configures correctly. Will update this comment once done.

    Thursday, March 8, 2018 8:59 AM
  • Hi,

    Please feel free to let us know if there is any update.

    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, March 8, 2018 10:18 AM
    Moderator
  • Run check/repair Anywhere Access (which successfully ran) and still had the same issue.

    I then switched off the VPN option (needing a server reboot) and it has now connected fine and seems to be working fine! Will check that backup works ok later.

    As this change needed a reboot on the server, I can't switch VPN back on for now, but will doing so again tomorrow and see if that breaks the connector - and if switching off again allows connector to work ok.

    Will update you again once I've done that. And at least we might have a partial workaround for now :-)

    As for exact build/versions:

    Desktop:

    OS Name: Microsoft Windows 10 Pro
    Version: 10.0.17115 Build 17115
    System Type: x64-based PC

    Server:

    OS Name: Microsoft Windows Server 2016 Essentials
    Version: 10.0.14393 Build 14393
    System Type: x64-based PC

    Thursday, March 8, 2018 7:27 PM
  • Hi,

    Thank you for detail updating.

    I will also try to re-produce it on my test environment and 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.

    Friday, March 9, 2018 9:06 AM
    Moderator
  • Latest:

    Reinstalled the Anywhere Access VPN option, which did not need a reboot :-)

    Connector still appears to be working ok, but have not rebooted the PC where it might be ok, but might get disconnected during future updates/upgrades to Windows.

    However, the Connector Setup "C:\Program Files\Windows Server\Bin\ClientDeploy.exe" now fails with the same error as before.

    I suspect there are two problems identified:

    1. When upgrading/updating Windows, the Connector sometimes loses its connection to the server and needs to have ClientDeploy run to get it reconnected. This happened with the update to 17115.

    This is not a major issue, but is a significant frustration - it would better if it didn't lose connection to the server in these instances, but as a partial solution maybe the client should provide an option to "repair connection" (or a "troubleshoot problems" like the network) when it is showing in error, to give an easier way for less experienced users to be able to start the repair process. I will add this to UserVoice as a suggestion.

    2. ClientDeploy fails on Windows 10 1803 (certainly on the versions I've specifically tested) when Anywhere Access VPN connection is enabled. This is a more major issue, and a potential blocker for people who will want to upgrade to 1803.

    Overall, this all seems completely repeatable, so I am hoping it can be reproduced and fixed in the coming weeks.

    Friday, March 9, 2018 9:14 AM
  • Now just switched VPN off again - and ClientDeploy once again works fine. So it is clearly an incompatibility between ClientDeploy and Windows 10 1803 builds specifically related to the VPN configuration side of things. Maybe they way in which a new VPN connection is setup/configured programmatically in Windows 10 1803 has changed?
    Friday, March 9, 2018 2:22 PM
  • Hi,

    Sorry for my late reply (as I had took a week off), you had mentioned Windows 10 1803, this version has not been released until now. Also, Windows 10 Build 17115 is Insider Preview version, which is not an official released version.

    I am afraid that I am unable to reproduce it as we are unable to obtain an official version of Windows 10 1803 now.

    Thank you for your detail feedback, and I will post your feedback to product department.

    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.

    Tuesday, March 20, 2018 6:37 AM
    Moderator
  • If you could make sure the product department do look at this - surely one of the things we would expect Microsoft to do is to talk between departments to make sure that their server products are ready to work with the latest updates, including using pre-release versions of the operating systems to test for issues before new versions are released?
    Tuesday, March 20, 2018 8:29 AM
  • Hi,

    I had post this to product team.

    In general, there will be some issues for pre-release version, as it is a test version and it is helpful for collecting more information.

    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, March 21, 2018 10:09 AM
    Moderator
  • I've submitted a report about the RasSetEntryProperties error 632 in recent Insider builds through Feedback Hub and in reply to a similar problem at https://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_update-insiderplat_pc/ras-error-632-on-windows-insider-build-17083/aacf68b9-3171-4342-ab9e-cbd4e278d4a7.


    Graham

    Thursday, March 22, 2018 7:54 PM
  • Have  the same Situation win 10 1709  as Domain Client  works fine  and with the Insider Connector dont work 

    with the same  Error the Connector Software Install dont start from the Connector side. 

    Windows update and WSUS  = ( 0x8000fff)  remove WSUS reg Settings WU works fine 

     Windows update shows error  0x8000fff  after upgrade  ( same if i make clean install ) and join Client to Domain)  

    Saturday, March 31, 2018 7:57 AM
  • I am having the same issue with Server 2012 R2 Essentials and one PC which has just been updated to Win 10 1803 RC 17133.1. Three other PC's which did not loose the connector during update have been fine. 

    Disabled VPN on the server (which did not need a reboot) and then the connector installed fine. 

    Re-enabled VPN on the server successfully without a reboot, PC still connected OK. 

    Rebooted PC, Connector still OK. 

    This seems to be a problem with 1803 and the Connector (re)installation as indicated above but affects Server 2012 R2 Essentials as well as 2016 Essentials.



    • Edited by Dave Marchant Monday, April 9, 2018 2:46 PM inserted Win 10 version
    Monday, April 9, 2018 2:45 PM
  • The recommended version is currently 1709 16299.371 see Windows 10 release information. That version works just fine with any Windows Server Essentials version.

    Mariëtte Knap
    www.server-essentials.com | Linkedin | Migrations done the easy way

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.



    Thursday, April 12, 2018 5:45 AM
  • I have just upgraded one of my devices to 1803 using the now released 1803 and this issue still occurs. I dont use VPN. Time for Microsoft to have a proper look at this.

    I use SkipDomainJoin and I have re-installed the connector without success.


    Thanks, Tim

    Monday, April 30, 2018 10:26 PM
  • Just upgraded a second machine and have the same issue. No more upgrades for me until they fix this or I will end up with no ongoing backups.

    Thanks, Tim

    Tuesday, May 1, 2018 10:36 PM
  • Have a look here for the simple solution:

    https://social.technet.microsoft.com/Forums/en-US/b75d2462-0716-4af7-b763-605c02336412/windows-server-2016-essentials-connector-will-not-install-after-windows-10-1803-upgrade?forum=winservergen

    Worked for me.

    Wednesday, May 2, 2018 10:11 AM
  • I'll try the restart 3 times next time I do an update and it forces the connector off. In the meantime, the Essentials Connector installation REALLY NEEDS TO BE FIXED given that 1803 is now rolling out to everyone and is often a forced upgrade for some users.

    Saying they have to stay on an older version is really not acceptable, given that the advice from MS is to keep on the latest to ensure your the most protected from a security perspective. It is almost like it is a separate company using an excuse as to why they have not spent the effort to keep up to date with Windows released, now that we have Windows As A Service!

    For many people, not having the VPN setup in the server may be a reasonable work around, but for some this will be a deal-breaker, and will force them to choose between maintaining the highest level of security on their devices OR keeping their devices able to work correctly with Windows Server Essentials.

    As this is targeted at SMEs who have, in many cases, limited if any internal IT support, this really does send out a poor message.

    Wednesday, May 2, 2018 10:24 AM
  • I followed that link. Since you posted two others have posted it didnt work for them.  I can tell you it doesnt work for me either.

    Thanks, Tim

    Thursday, May 3, 2018 12:03 AM
  • I can tell you I dont use VPN and I have the issue. Maybe it is setup by default in Server 2016 Essentials? (Edit it is as part of Anywhere Access).

    I agree with your comments. Sometime in the next few weeks all of my devices will want to update and I would need to intervene to stop them.

    I am a home user and provide my own support and try to keep my devices up to date automatically.

    I do take the precaution of updating a spare computer early to make sure all is OK, especially with the poor track record around the Connector in 2012 R2 and 2016 with Windows 10.

    This problem was identified a few weeks ago and Microsoft have allowed 1803 to go out without addressing the problem. Noi doubt because we are a small user base in their eyes.


    Thanks, Tim


    • Edited by Oceang Thursday, May 3, 2018 11:25 AM
    Thursday, May 3, 2018 12:07 AM
  • I followed that link. Since you posted two others have posted it didnt work for them.  I can tell you it doesnt work for me either.

    Thanks, Tim

    It has worked for me on all client computers so far:

    I've updated 5 clients to Win 10 1803, all of them had a gray connector icon. All of them turned green after a client restart. I only had to restart once. It should be mentioned that I didn't do any registry changes prior to the client restarts.


    • Edited by jabb_03 Thursday, May 3, 2018 9:40 AM typo
    Thursday, May 3, 2018 9:30 AM
  • Hello,

    Would it be possible to export the registry location "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols" open the file in notepad and share the data from one of the affected windows 10-1803 machine please.

    Thursday, May 3, 2018 5:44 PM
  • If I can interject..

    Here is an export from a system that I am having trouble with.

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols]

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0]

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL 2.0\Client]
    "DisabledByDefault"=dword:00000001

    Thursday, May 3, 2018 8:48 PM
  • Hi,

    I had a test on my environment and all work without problem. Please check link below:
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/7923b8a8-ce95-4be0-930a-0fdf79ed28e7/server-2016-essentials-connector-broken-by-windows-10-1803-update?forum=winservergen

    On my working 1803 system, there is only default entry under:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\SSL

    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:13 AM
    Moderator
  • If you reboot at least three times after the upgrade the connector will light up again.  The key is to NOT uninstall or attempt to reinstall it.

    The first reboot after the 1803 upgrade the connector will act like it's broken.  Don't do anything at this point merely reboot the client workstation at least three times.

    We are tracking an issue with installing the connector on a fresh 1803 when VPN is set up on the server, but existing deployments should be okay.

    If you've already mucked with it, reinstall it from this location:  C:\Program Files\Windows Server\Bin\ClientDeploy.exe

    Sunday, May 6, 2018 3:56 AM
    Moderator
  • Hi Susan, I can confirm that you can re-install the connector if you temporarily turn VPN off on the server. Worked fine on one of my problem machines.

    Your suggestion for reinstalling from C:\Program Files\Windows Server\Bin\ClientDeploy.exe didnt work for me.


    Thanks, Tim

    Monday, May 7, 2018 12:36 AM
  • Addresses an issue that prevents certain VPN apps from working on builds of Windows 10, version 1803. These apps were developed using an SDK version that precedes Windows 10, version 1803, and use the public RasSetEntryProperties API.

    https://support.microsoft.com/en-us/help/4103721/windows-10-update-kb4103721

    Install that update on your 1803 workstations.

    Tuesday, May 8, 2018 6:08 PM
    Moderator
  • I'm a bit saddened by this admission, but rebooting WSE16 a couple of time, followed by the client computers a couple of times fixed this issue for me.  All connectors were grey, then suddenly sprung to life after the reboots.  No further action was taken on my part.  I prefer troubleshooting to arbitrary reboots here in 2018, but whatever, they are all fixed.  4/4 Win10 Pro 1803 to WSE16.
    Friday, May 11, 2018 12:58 AM
  • 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.

    Friday, May 11, 2018 1:38 AM
    Moderator
  • If you reboot at least three times after the upgrade the connector will light up again.  The key is to NOT uninstall or attempt to reinstall it.

    The first reboot after the 1803 upgrade the connector will act like it's broken.  Don't do anything at this point merely reboot the client workstation at least three times.

    We are tracking an issue with installing the connector on a fresh 1803 when VPN is set up on the server, but existing deployments should be okay.

    If you've already mucked with it, reinstall it from this location:  C:\Program Files\Windows Server\Bin\ClientDeploy.exe


    Susan Bradley is absolutely right. Reboot at least three times. It works, just see.
    Wednesday, May 16, 2018 5:09 PM