none
Connector functionality broken with Redstone 4 (Windows 10 1803)

    Frage

  • So, this made me some headache:

    I had to add a client to my WSE2016. So I downloaded the connector software from the server (https://server/connect) and ran it. It got to the point after entering your Username and password and then failed with an "unexpected error". I noticed that it suddenly did on all my PCs. First I thought it to be a DNS problem (I got a new router and searched long for a DNS misconfiguration on either the router or the server, but that was not the case).

    Then I realized that similar issues had happened when people upgraded from Windows 8 to 8.1 some years ago when connecting to their Server 2012 versions some years ago (thanks, Google...). 'Cause what I did before was to install the Windows 10 Update known as "Redstone 4", Windows 10 Version 1803 (Build 17133.1); as this is not yet officially released, I was using the .cab-Data from the MS-Servers with the MediaCreationTool.exe and the /SelfHost option.

    After going back to a restore point from before the update, everything worked again as it should.

    While the update itself went flawlessly, it apparently broke the connector functionality (see logfile below). It may very well be that server versions will receive an update with the upcoming patchday before the official 1803 releae, but I just wanted to inform if anybody else runs into this issue.

    This is what happend in the Clientdeploy.log

    [8472] 180407.104042.5444: ClientSetup: Start of ClientDeploy
    [8472] 180407.104042.7319: General: Initializing...C:\Program Files\Windows Server\Bin\ClientDeploy.exe
    [8472] 180407.104042.7475: ClientSetup: Create client deployment registry subkey if necessary
    [8472] 180407.104042.7631: ClientSetup: The initial launching way: -LaunchedFrom:installer
    [8472] 180407.104042.7631: ClientSetup: The initial state is set
    [8472] 180407.104042.7631: ClientSetup: The initial serverName: 192.168.0.101
    [8472] 180407.104042.7631: ClientSetup: Loading Wizard Data
    [8472] 180407.104042.7788: ClientSetup: Saving Wizard Data
    [8472] 180407.104042.7944: ClientSetup: Current DeploymentStatus=Start
    [8472] 180407.104043.8882: ClientSetup: Showing the Client Deployment Wizard
    [8472] 180407.104044.4663: ClientSetup: The input server name is 192.168.0.101
    [4608] 180407.104044.4976: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [4608] 180407.104044.4976: ClientSetup: Running Task with Id=ClientDeploy.PreConfiguration
    [4608] 180407.104044.5288: ClientSetup: The configuration cab will be downloaded from 192.168.0.101
    [4608] 180407.104044.5444: ClientSetup: Download file Setup.cab from server
    [8472] 180407.104044.5444: ClientSetup: InitWizard, The currrent stage is ConnectingToServer
    [8472] 180407.104044.5444: ClientSetup: Set the Deployment Sync Event
    [4608] 180407.104044.7788: ClientSetup: Making web request: https://192.168.0.101//connect/default.aspx?Get=Setup.cab&LanguageId=1031&64bit=1
    [4608] 180407.104045.0132: ClientSetup: Failed to download Setup.cab from server: System.Net.WebException: Die zugrunde liegende Verbindung wurde geschlossen: Für den geschützten SSL/TLS-Kanal konnte keine Vertrauensstellung hergestellt werden.. ---> System.Security.Authentication.AuthenticationException: Das Remotezertifikat ist laut Validierungsverfahren ungültig.
       bei System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
       bei System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
       bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       bei System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
       bei System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
       bei System.Net.ConnectStream.WriteHeaders(Boolean async)
       --- Ende der internen Ausnahmestapelüberwachung ---
       bei System.Net.HttpWebRequest.GetResponse()
       bei Microsoft.WindowsServerSolutions.ClientSetup.CSCommon.DownloadFileFromConnectSite(String outputDirectory, Uri serverUrl, String fileName, Int32 languageId, Boolean is64bit)
    [4608] 180407.104045.0132: ClientSetup: Cannot get configuration file with https, will try http...
    [4608] 180407.104045.0132: ClientSetup: Download file Setup.cab from server
    [4608] 180407.104045.0132: ClientSetup: Making web request: http://192.168.0.101//connect/default.aspx?Get=Setup.cab&LanguageId=1031&64bit=1
    [4608] 180407.104045.0913: ClientSetup: Downloaded file C:\WINDOWS\Temp\ClientDeploymentTempFiles\Setup.cab
    [4608] 180407.104045.0913: ClientSetup: The configuration cab is downloaded to C:\WINDOWS\Temp\ClientDeploymentTempFiles\Setup.cab
    [4608] 180407.104045.2007: ClientSetup: Adding Server Info data in the Product Registry
    [4608] 180407.104045.2320: DnsEnvironmentDetector: GetHostAddresses() returned 192.168.0.101, normal environment
    [4608] 180407.104045.2320: ClientSetup: Exiting PreConfigTask.Run()
    [4608] 180407.104045.2320: ClientSetup: Task with Id=ClientDeploy.PreConfiguration has TaskStatus=Success
    [4608] 180407.104045.2320: ClientSetup: Task with Id=ClientDeploy.PreConfiguration has RebootStatus=NoReboot
    [4608] 180407.104045.2320: ClientSetup: Exiting ConnectorWizardForm.RunTasks
    [7592] 180407.104053.4510: ClientSetup: Running InstallRootCert Task at WizardPage DomainUserCred
    [7592] 180407.104053.4666: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [7592] 180407.104053.4666: ClientSetup: Running Task with Id=ClientDeploy.InstallRootCertTask
    [7592] 180407.104053.4666: ClientSetup: Entering InstallRootCertTask.Run
    [7592] 180407.104053.4666: ClientSetup: Install root cert to local trusted store
    [7592] 180407.104053.4822: ClientSetup: Exiting InstallRootCertTask.Run
    [7592] 180407.104053.4822: ClientSetup: Task with Id=ClientDeploy.InstallRootCertTask has TaskStatus=Success
    [7592] 180407.104053.4822: ClientSetup: Task with Id=ClientDeploy.InstallRootCertTask has RebootStatus=NoReboot
    [7592] 180407.104053.4822: ClientSetup: Exiting ConnectorWizardForm.RunTasks
    [7592] 180407.104053.4822: ClientSetup: Running SetupVPNAndDA Task at WizardPage DomainUserCred
    [7592] 180407.104053.4822: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [7592] 180407.104053.4822: ClientSetup: Running Task with Id=ClientDeploy.SetupVpnAndDATask
    [7592] 180407.104053.4822: ClientSetup: Entering SetupVpnAndDATask.Run
    [7592] 180407.104053.5135: ClientSetup: Deploy VPN profile
    [7592] 180407.104053.5291: VPN Client Utils: Error 632 returned from RasSetEntryProperties.
    [7592] 180407.104053.5291: ClientSetup: RAS exception: Eine ungültige Strukturgröße wurde entdeckt.
    [7592] 180407.104053.5291: ClientSetup: Exting SetupVpnAndDATask.Run
    [7592] 180407.104053.5291: ClientSetup: Task with Id=ClientDeploy.SetupVpnAndDATask has TaskStatus=Failed
    [7592] 180407.104053.5291: ClientSetup: Task with Id=ClientDeploy.SetupVpnAndDATask has RebootStatus=NoReboot
    [7592] 180407.104053.5291: ClientSetup: Exiting ConnectorWizardForm.RunTasks
    [8472] 180407.104053.5447: ClientSetup: JoinNetwork Tasks returned TaskStatus=Failed
    [8472] 180407.104056.3729: ClientSetup: Back from the Client Deployment Wizard
    [8472] 180407.104056.3729: ClientSetup: Saving Wizard Data
    [8472] 180407.104056.3729: ClientSetup: End of ClientDeploy: ErrorCode=1603

    Sonntag, 8. April 2018 20:50

Alle Antworten

  • Hi,

    Based on your description, Windows 10 1803 filed to connect to WSE 2016. 

    First, thank you for your detail feedback.

    As you had mentioned that, Windows 10 1803 is not released officially until now. Also, there is insider preview version only now. Problem happens on preview version now. I will have a test on my environment and confirm the details.

    Besides, any problem/feedback/bug, you can manually post on 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.

    Montag, 9. April 2018 03:02
    Moderator
  • Hi,

    I had same problem on my test environment - WSE 2016 and Windows 10 1803(insider preview version). With error “VPN Client Utils: Error 632 returned from RasSetEntryProperties”.

    I had post such problem to product team. Also, I am currently performing research on this issue.

    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.

    Mittwoch, 11. April 2018 04:22
    Moderator
  • If you turn off VPN access in the Anywhere Access Configuration it will connect, i ran into the problem, tried other suggestions but they didn't work.  It was turning off the VPN that fixed it.  Microsoft if your listening please fix.
    Montag, 7. Mai 2018 05:34
  • Yes, but it also totally breaks VPN connections (also if it is turned on). This is a severe bug, and I cannot understand Microsoft left it unfixed for release. This broke a lot of functionality.

    @Eve Wang: Can you give us an update if this issue is being worked on and we can expect a fix soon?

    Montag, 7. Mai 2018 06:09