none
WSE 2012 CONNECTOR CRASH: Windows Server 2012 R2 Server + Essentials Role + Windows 10 Pro (Latest Updates) RRS feed

  • Question

  • Update: When I started this post I assumed that there were still issues with the WSE Connector... well for me and my experience there still is, but this seems to be an isolated issue with a freshly installed and updated Windows 2012 R2 server with the Essentials Role installed. I just can't get the connector to work proper on Windows 8.1, 10 and even 7 pro machines. It crashes on the 8.1 and 10 machines and hangs on the 7 machine. All of this on a HP ML150 G6/2 Xeons/48GB ram/HyperV 2012R2 host. I am using dynamic drives in a raid1 configuration on the host. DHCP is on my router (192.168.0.1) and gives out the IP info for the DNS servers, gateway and domain Planet-x-.local. In my DHCP I have included the 2 DNS servers as well as the router DNS that uses OpenDNS for external lookups. I also use the OpenDNS as forwarders on my 2 DNS servers. This all seems to be working really well and for the most part the Essentials Remote Web is working and SSL installed and working correctly.

    Basic Network details:
    DC1: 192.168.0.200 (Essentials Server)
    DC2: 192.168.0.201 (Backup DC/Future Sharepoint server)
    DHCP Server: Mikrotik RB751G-2HnD Router - v6.35.4/3.33 firmware. (latest) 
    Clients: DHCP only and 1 has a reservation on the router.
    DHCP scope 192.168.0.100-199, DNS: 192.168.0.200/201, Gtwy: 192.168.0.1
    DNS Forwarders: 208.67.200.200, 208.67.222.222 (openDNS), 192.168.0.1

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

    Any word on when this will be fixed?
    I have 5 Office machines that cannot use the benefits of the Connector and 3 deployments on hold until this is fixed. Latest updates on server and the "updated" connector - Windows10.0-KB2790621-x64.msu does NOT work.


    - Bob





    Thursday, June 30, 2016 11:24 AM

Answers

  • Robert,

    I gave up over the weekend and nuked both DC1 and DC2 server VMs and installed a fresh WSE 2012 R2 server (not an addon role). I do like a challenge but I could not for the life of me figure out why it was crashing the deployment... I know when I am beat and unfortunately had to call it what it was.

    I am hoping the new install I just did this AM will go much better; I am finishing the updates now and will test as soon as I am all up to date. If this works then I will post success and just move on, if not I will zip up and attach all the logs you requested in the next post... fingers crossed.

    Thanks again for all your help and your feedback on this issue... it is much appreciated and nice to have knowledgeable guys like you in the community.

    Update:

    I was able to add the Windows 7 machine using the connector without any issues. (before updates)
    - I will checkpoint and continue with the updates and see if it creates any issues. 

    Update Update: 

    The new installation is working as it should. I used the 2012 R2 Essentials Server install instead of the Windows Server 2912 R2 + Essentials role. Not sure what went wrong (twice) but I will know that in the future not to expect the Essentials Role to work on a Windows Server Standard 2012 R2 on my HyperV box. (I can't assume it is broken anywhere else other than my Server at this point.)

    Thanks again for all your help!


    - Bob






    Tuesday, July 5, 2016 2:41 PM

All replies

  • What specifically is not working?

    Do you have the logs from the client?

    Windows 10 has been able to connect to 2012 R2 since release, with a manual download of the connector software.

    Then an update was released to 2012 R2 so that the updated connector was on box.

    No additional downloads are now required and as far as i am ware nothing needs fixing, in terms of connecting Win10 and 2012 R2.


    Robert Pearman Cloud & Datacentre MVP
    @titlerequired | LinkedIn | Google+
    Facebook | Windows Server Essentials.com

    Thursday, June 30, 2016 3:20 PM
    Moderator
  • The app crashes just after it finds the Server and you hit continue... maybe something wrong server side? (It is a HyperV Guest instance of 2012 R2 w/Essentials Role)
    I triple checked that the server just now and it has the latest updates and the Windows 10 workstation I just tested against is up to date. - Microsoft Windows [Version 10.0.10586]

    I get 3 Events in the Application Event logs...

    ---------

    Log Name:      Application
    Source:        Windows Error Reporting
    Date:          6/30/2016 11:50:25 AM
    Event ID:      1001
    Task Category: None
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      TKI-BOB-LT
    Description:
    Fault bucket 129105591551, type 5
    Event Name: CLR20r3
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: ClientDeploy.exe
    P2: 10.0.10240.16384
    P3: 559f31a8
    P4: mscorlib
    P5: 4.6.1080.0
    P6: 570c49e2
    P7: 2e50
    P8: a1
    P9: N3CTRYE2KN3C34SGL4ZQYRBFTE4M13NB
    P10: 

    Attached files:
    C:\Users\bbrown\AppData\Local\Temp\WERE436.tmp.WERInternalMetadata.xml

    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_ClientDeploy.exe_a1114849c79b6a43f3102f64826d5ec89cfebfc4_1125f824_282ffadb

    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: d8a0a8f4-5a01-4aac-b15d-a7ae8c7858cb
    Report Status: 0
    Hashed bucket: 1357db087d52bbf27402b2f932754c2f
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Windows Error Reporting" />
        <EventID Qualifiers="0">1001</EventID>
        <Level>4</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2016-06-30T15:50:25.461966800Z" />
        <EventRecordID>23197</EventRecordID>
        <Channel>Application</Channel>
        <Computer>TKI-BOB-LT</Computer>
        <Security />
      </System>
      <EventData>
        <Data>129105591551</Data>
        <Data>5</Data>
        <Data>CLR20r3</Data>
        <Data>Not available</Data>
        <Data>0</Data>
        <Data>ClientDeploy.exe</Data>
        <Data>10.0.10240.16384</Data>
        <Data>559f31a8</Data>
        <Data>mscorlib</Data>
        <Data>4.6.1080.0</Data>
        <Data>570c49e2</Data>
        <Data>2e50</Data>
        <Data>a1</Data>
        <Data>N3CTRYE2KN3C34SGL4ZQYRBFTE4M13NB</Data>
        <Data>
        </Data>
        <Data>
    C:\Users\bbrown\AppData\Local\Temp\WERE436.tmp.WERInternalMetadata.xml</Data>
        <Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_ClientDeploy.exe_a1114849c79b6a43f3102f64826d5ec89cfebfc4_1125f824_282ffadb</Data>
        <Data>
        </Data>
        <Data>0</Data>
        <Data>d8a0a8f4-5a01-4aac-b15d-a7ae8c7858cb</Data>
        <Data>0</Data>
        <Data>1357db087d52bbf27402b2f932754c2f</Data>
      </EventData>
    </Event>

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

    Log Name:      Application
    Source:        Application Error
    Date:          6/30/2016 11:50:19 AM
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      TKI-BOB-LT
    Description:
    Faulting application name: ClientDeploy.exe, version: 10.0.10240.16384, time stamp: 0x559f31a8
    Faulting module name: KERNELBASE.dll, version: 10.0.10586.306, time stamp: 0x571af331
    Exception code: 0xe0434352
    Fault offset: 0x0000000000071f28
    Faulting process id: 0x13f4
    Faulting application start time: 0x01d1d2e7193c23b6
    Faulting application path: C:\Windows\system32\Essentials\ClientDeploy.exe
    Faulting module path: C:\Windows\system32\KERNELBASE.dll
    Report Id: d8a0a8f4-5a01-4aac-b15d-a7ae8c7858cb
    Faulting package full name: 
    Faulting package-relative application ID: 
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Application Error" />
        <EventID Qualifiers="0">1000</EventID>
        <Level>2</Level>
        <Task>100</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2016-06-30T15:50:19.362517200Z" />
        <EventRecordID>23196</EventRecordID>
        <Channel>Application</Channel>
        <Computer>TKI-BOB-LT</Computer>
        <Security />
      </System>
      <EventData>
        <Data>ClientDeploy.exe</Data>
        <Data>10.0.10240.16384</Data>
        <Data>559f31a8</Data>
        <Data>KERNELBASE.dll</Data>
        <Data>10.0.10586.306</Data>
        <Data>571af331</Data>
        <Data>e0434352</Data>
        <Data>0000000000071f28</Data>
        <Data>13f4</Data>
        <Data>01d1d2e7193c23b6</Data>
        <Data>C:\Windows\system32\Essentials\ClientDeploy.exe</Data>
        <Data>C:\Windows\system32\KERNELBASE.dll</Data>
        <Data>d8a0a8f4-5a01-4aac-b15d-a7ae8c7858cb</Data>
        <Data>
        </Data>
        <Data>
        </Data>
      </EventData>
    </Event>

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

    Log Name:      Application
    Source:        .NET Runtime
    Date:          6/30/2016 11:50:19 AM
    Event ID:      1026
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      TKI-BOB-LT
    Description:
    Application: ClientDeploy.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.ArgumentException
       at System.Globalization.IdnMapping.GetAsciiUsingOS(System.String)
       at Microsoft.WindowsServerSolutions.Networking.ServerDiscovery.DnsEnvironmentDetector.DetectOpenDns(System.String, System.Collections.Generic.IList`1<System.Net.IPAddress>)
       at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.Helper.SetOpenDNSEnv(Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.WizData)
       at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.PreConfigTask.Run(Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.WizData)
       at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.ConnectorWizardForm.RunTasks(System.Object, System.ComponentModel.DoWorkEventArgs)
       at System.ComponentModel.BackgroundWorker.OnDoWork(System.ComponentModel.DoWorkEventArgs)
       at System.ComponentModel.BackgroundWorker.WorkerThreadStart(System.Object)

    Exception Info: Microsoft.WindowsServerSolutions.ClientSetup.ClientSetupException
       at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.ConnectorWizardForm+<>c__DisplayClass7.<m_wizardPageServerDetecting_PageValidating>b__4(System.Object, System.ComponentModel.RunWorkerCompletedEventArgs)
       at System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(System.ComponentModel.RunWorkerCompletedEventArgs)

    Exception Info: System.Reflection.TargetInvocationException
       at System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)
       at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(System.Object, System.Object[], System.Object[])
       at System.Delegate.DynamicInvokeImpl(System.Object[])
       at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry)
       at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(System.Object)
       at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
       at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry)
       at System.Windows.Forms.Control.InvokeMarshaledCallbacks()
       at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
       at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr, Int32, IntPtr, IntPtr)
       at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
       at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)
       at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
       at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
       at System.Windows.Forms.Form.ShowDialog(System.Windows.Forms.IWin32Window)
       at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.Program.Main()


    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name=".NET Runtime" />
        <EventID Qualifiers="0">1026</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2016-06-30T15:50:19.206265900Z" />
        <EventRecordID>23195</EventRecordID>
        <Channel>Application</Channel>
        <Computer>TKI-BOB-LT</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Application: ClientDeploy.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.ArgumentException
       at System.Globalization.IdnMapping.GetAsciiUsingOS(System.String)
       at Microsoft.WindowsServerSolutions.Networking.ServerDiscovery.DnsEnvironmentDetector.DetectOpenDns(System.String, System.Collections.Generic.IList`1&lt;System.Net.IPAddress&gt;)
       at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.Helper.SetOpenDNSEnv(Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.WizData)
       at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.PreConfigTask.Run(Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.WizData)
       at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.ConnectorWizardForm.RunTasks(System.Object, System.ComponentModel.DoWorkEventArgs)
       at System.ComponentModel.BackgroundWorker.OnDoWork(System.ComponentModel.DoWorkEventArgs)
       at System.ComponentModel.BackgroundWorker.WorkerThreadStart(System.Object)

    Exception Info: Microsoft.WindowsServerSolutions.ClientSetup.ClientSetupException
       at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.ConnectorWizardForm+&lt;&gt;c__DisplayClass7.&lt;m_wizardPageServerDetecting_PageValidating&gt;b__4(System.Object, System.ComponentModel.RunWorkerCompletedEventArgs)
       at System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(System.ComponentModel.RunWorkerCompletedEventArgs)

    Exception Info: System.Reflection.TargetInvocationException
       at System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)
       at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(System.Object, System.Object[], System.Object[])
       at System.Delegate.DynamicInvokeImpl(System.Object[])
       at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry)
       at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(System.Object)
       at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
       at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
       at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry)
       at System.Windows.Forms.Control.InvokeMarshaledCallbacks()
       at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
       at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr, Int32, IntPtr, IntPtr)
       at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
       at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)
       at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
       at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
       at System.Windows.Forms.Form.ShowDialog(System.Windows.Forms.IWin32Window)
       at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.Program.Main()

    </Data>
      </EventData>
    </Event>

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

    report.wer

    Version=1
    EventType=CLR20r3
    EventTime=131117754195812801
    ReportType=2
    Consent=1
    UploadTime=131117754196750355
    ReportIdentifier=58242ed4-3eda-11e6-87b7-a4173111b200
    IntegratorReportIdentifier=d8a0a8f4-5a01-4aac-b15d-a7ae8c7858cb
    NsAppName=ClientDeploy.exe
    Response.BucketId=1357db087d52bbf27402b2f932754c2f
    Response.BucketTable=5
    Response.LegacyBucketId=129105591551
    Response.type=4
    Sig[0].Name=Problem Signature 01
    Sig[0].Value=ClientDeploy.exe
    Sig[1].Name=Problem Signature 02
    Sig[1].Value=10.0.10240.16384
    Sig[2].Name=Problem Signature 03
    Sig[2].Value=559f31a8
    Sig[3].Name=Problem Signature 04
    Sig[3].Value=mscorlib
    Sig[4].Name=Problem Signature 05
    Sig[4].Value=4.6.1080.0
    Sig[5].Name=Problem Signature 06
    Sig[5].Value=570c49e2
    Sig[6].Name=Problem Signature 07
    Sig[6].Value=2e50
    Sig[7].Name=Problem Signature 08
    Sig[7].Value=a1
    Sig[8].Name=Problem Signature 09
    Sig[8].Value=N3CTRYE2KN3C34SGL4ZQYRBFTE4M13NB
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=10.0.10586.2.0.0.256.48
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=1033
    DynamicSig[22].Name=Additional Information 1
    DynamicSig[22].Value=f310
    DynamicSig[23].Name=Additional Information 2
    DynamicSig[23].Value=f31064a8a75bf13105016e8ca5681312
    DynamicSig[24].Name=Additional Information 3
    DynamicSig[24].Value=cc8b
    DynamicSig[25].Name=Additional Information 4
    DynamicSig[25].Value=cc8b3bedcd7218a484e8f7c73725f824
    UI[2]=C:\Windows\system32\Essentials\ClientDeploy.exe
    UI[3]=Windows Server Essentials Connector Configuration Wizard has stopped working
    UI[4]=Windows can check online for a solution to the problem.
    UI[5]=Check online for a solution and close the program
    UI[6]=Check online for a solution later and close the program
    UI[7]=Close the program
    LoadedModule[0]=C:\Windows\system32\Essentials\ClientDeploy.exe
    LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
    LoadedModule[2]=C:\Windows\SYSTEM32\MSCOREE.DLL
    LoadedModule[3]=C:\Windows\system32\KERNEL32.dll
    LoadedModule[4]=C:\Windows\system32\KERNELBASE.dll
    LoadedModule[5]=C:\Windows\system32\apphelp.dll
    LoadedModule[6]=C:\Windows\system32\ADVAPI32.dll
    LoadedModule[7]=C:\Windows\system32\msvcrt.dll
    LoadedModule[8]=C:\Windows\system32\sechost.dll
    LoadedModule[9]=C:\Windows\system32\RPCRT4.dll
    LoadedModule[10]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll
    LoadedModule[11]=C:\Windows\system32\SHLWAPI.dll
    LoadedModule[12]=C:\Windows\system32\combase.dll
    LoadedModule[13]=C:\Windows\system32\bcryptPrimitives.dll
    LoadedModule[14]=C:\Windows\system32\GDI32.dll
    LoadedModule[15]=C:\Windows\system32\USER32.dll
    LoadedModule[16]=C:\Windows\system32\IMM32.DLL
    LoadedModule[17]=C:\Windows\system32\kernel.appcore.dll
    LoadedModule[18]=C:\Windows\SYSTEM32\VERSION.dll
    LoadedModule[19]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
    LoadedModule[20]=C:\Windows\SYSTEM32\MSVCR120_CLR0400.dll
    LoadedModule[21]=C:\Windows\assembly\NativeImages_v4.0.30319_64\mscorlib\43226440664fdfb99f9ad60968b2a60c\mscorlib.ni.dll
    LoadedModule[22]=C:\Windows\system32\ole32.dll
    LoadedModule[23]=C:\Windows\system32\uxtheme.dll
    LoadedModule[24]=C:\Windows\SYSTEM32\CRYPTSP.dll
    LoadedModule[25]=C:\Windows\system32\rsaenh.dll
    LoadedModule[26]=C:\Windows\SYSTEM32\bcrypt.dll
    LoadedModule[27]=C:\Windows\SYSTEM32\CRYPTBASE.dll
    LoadedModule[28]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clrjit.dll
    LoadedModule[29]=C:\Windows\system32\OLEAUT32.dll
    LoadedModule[30]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System\43b8952c0d907f0a02958a98443699ba\System.ni.dll
    LoadedModule[31]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Core\8e325c9a2b96c925621b8214b5785cd7\System.Core.ni.dll
    LoadedModule[32]=C:\Windows\assembly\NativeImages_v4.0.30319_64\WssgCommon\1ff101c18bf224ba9453b95da9471737\WssgCommon.ni.dll
    LoadedModule[33]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Common\b95c444526acb0ebbe1166bb52bf5f8e\Common.ni.dll
    LoadedModule[34]=C:\Windows\assembly\NativeImages_v4.0.30319_64\AdminCommon\98b79624b24c646240929362cabc8210\AdminCommon.ni.dll
    LoadedModule[35]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Drawing\fdc9c3b678ad232cb22146073f71c998\System.Drawing.ni.dll
    LoadedModule[36]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Windows.Forms\9b397cef9e862b789463f8fb670d66f7\System.Windows.Forms.ni.dll
    LoadedModule[37]=C:\Windows\assembly\NativeImages_v4.0.30319_64\SqmProvider\831c47bc25a42e6354085f9644191549\SqmProvider.ni.dll
    LoadedModule[38]=C:\Windows\system32\shell32.dll
    LoadedModule[39]=C:\Windows\system32\cfgmgr32.dll
    LoadedModule[40]=C:\Windows\system32\windows.storage.dll
    LoadedModule[41]=C:\Windows\system32\shcore.dll
    LoadedModule[42]=C:\Windows\system32\powrprof.dll
    LoadedModule[43]=C:\Windows\system32\profapi.dll
    LoadedModule[44]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Configuration\af40f3c8414c2b75e6a9e9c7a79fed97\System.Configuration.ni.dll
    LoadedModule[45]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xml\b6708e6e2b55466cc8c5ac0eed95468b\System.Xml.ni.dll
    LoadedModule[46]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Sku\41b842dd3e41595d8d0cc10e49947be9\Sku.ni.dll
    LoadedModule[47]=C:\Windows\SYSTEM32\SspiCli.dll
    LoadedModule[48]=C:\Windows\assembly\NativeImages_v4.0.30319_64\WindowsBase\347878d1393f6b869d18d658656f2b60\WindowsBase.ni.dll
    LoadedModule[49]=C:\Windows\assembly\NativeImages_v4.0.30319_64\PresentationCore\55717213a974c71f8e82532af3997d5f\PresentationCore.ni.dll
    LoadedModule[50]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Presentatio5ae0f00f#\f5d6f299601b66b7afc4865aac448cf2\PresentationFramework.ni.dll
    LoadedModule[51]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xaml\6fbcda4f052f28aae1402b62a2ae1539\System.Xaml.ni.dll
    LoadedModule[52]=C:\Windows\SYSTEM32\dwrite.dll
    LoadedModule[53]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\wpfgfx_v0400.dll
    LoadedModule[54]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\PresentationNative_v0400.dll
    LoadedModule[55]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.10586.0_none_8c15ae12515e1c22\comctl32.dll
    LoadedModule[56]=C:\Windows\system32\dwmapi.dll
    LoadedModule[57]=C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.10586.20_none_db007f1392e69ef4\gdiplus.dll
    LoadedModule[58]=C:\Windows\system32\MSCTF.dll
    LoadedModule[59]=C:\Windows\SYSTEM32\WindowsCodecs.dll
    LoadedModule[60]=C:\Windows\assembly\NativeImages_v4.0.30319_64\WindowsForm0b574481#\c1095eb154779ae1e29ccf917ea0c034\WindowsFormsIntegration.ni.dll
    LoadedModule[61]=C:\Windows\SYSTEM32\d3d9.dll
    LoadedModule[62]=C:\Windows\SYSTEM32\igdumdim64.dll
    LoadedModule[63]=C:\Windows\SYSTEM32\igdusc64.dll
    LoadedModule[64]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Presentatioaec034ca#\4f8516cc8b23d0b756520eea449ba2a8\PresentationFramework.Aero2.ni.dll
    LoadedModule[65]=C:\Windows\SYSTEM32\mscms.dll
    LoadedModule[66]=C:\Windows\SYSTEM32\USERENV.dll
    LoadedModule[67]=C:\Windows\SYSTEM32\WindowsCodecsExt.dll
    LoadedModule[68]=C:\Windows\SYSTEM32\WtsApi32.dll
    LoadedModule[69]=C:\Windows\SYSTEM32\WINSTA.dll
    LoadedModule[70]=C:\Windows\system32\clbcatq.dll
    LoadedModule[71]=C:\Windows\system32\dataexchange.dll
    LoadedModule[72]=C:\Windows\system32\d3d11.dll
    LoadedModule[73]=C:\Windows\system32\dcomp.dll
    LoadedModule[74]=C:\Windows\system32\dxgi.dll
    LoadedModule[75]=C:\Windows\system32\twinapi.appcore.dll
    LoadedModule[76]=C:\Windows\assembly\NativeImages_v4.0.30319_64\SkuResources\d047d6e0bfc0d28fce53c12db73e3d06\SkuResources.ni.dll
    LoadedModule[77]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Accessibility\3e3651d1764f6eff81eea658c49a04ad\Accessibility.ni.dll
    LoadedModule[78]=C:\Windows\SYSTEM32\rasapi32.dll
    LoadedModule[79]=C:\Windows\SYSTEM32\rasman.dll
    LoadedModule[80]=C:\Windows\SYSTEM32\rtutils.dll
    LoadedModule[81]=C:\Windows\system32\WS2_32.dll
    LoadedModule[82]=C:\Windows\system32\mswsock.dll
    LoadedModule[83]=C:\Windows\SYSTEM32\winhttp.dll
    LoadedModule[84]=C:\Windows\SYSTEM32\ondemandconnroutehelper.dll
    LoadedModule[85]=C:\Windows\SYSTEM32\IPHLPAPI.DLL
    LoadedModule[86]=C:\Windows\system32\NSI.dll
    LoadedModule[87]=C:\Windows\SYSTEM32\dhcpcsvc6.DLL
    LoadedModule[88]=C:\Windows\SYSTEM32\dhcpcsvc.DLL
    LoadedModule[89]=C:\Windows\SYSTEM32\DNSAPI.dll
    LoadedModule[90]=C:\Windows\SYSTEM32\WINNSI.DLL
    LoadedModule[91]=C:\Windows\System32\rasadhlp.dll
    LoadedModule[92]=C:\Windows\System32\fwpuclnt.dll
    LoadedModule[93]=C:\Windows\system32\psapi.dll
    LoadedModule[94]=C:\Windows\SYSTEM32\secur32.dll
    LoadedModule[95]=C:\Windows\system32\schannel.DLL
    LoadedModule[96]=C:\Windows\system32\CRYPT32.dll
    LoadedModule[97]=C:\Windows\system32\MSASN1.dll
    LoadedModule[98]=C:\Windows\SYSTEM32\mskeyprotect.dll
    LoadedModule[99]=C:\Windows\SYSTEM32\ncrypt.dll
    LoadedModule[100]=C:\Windows\SYSTEM32\NTASN1.dll
    LoadedModule[101]=C:\Windows\system32\ncryptsslp.dll
    LoadedModule[102]=C:\Windows\SYSTEM32\cabinet.dll
    LoadedModule[103]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\diasymreader.dll
    State[0].Key=Transport.DoneStage1
    State[0].Value=1
    FriendlyEventName=Stopped working
    ConsentKey=CLR20r3
    AppName=Windows Server Essentials Connector Configuration Wizard
    AppPath=C:\Windows\system32\Essentials\ClientDeploy.exe
    NsPartner=windows
    NsGroup=windows8
    ApplicationIdentity=F3F32F2D935B9DC6B5D3FD6EF1836A94


    - Bob



    • Edited by Bob K Brown Thursday, June 30, 2016 4:09 PM Added report.wer
    Thursday, June 30, 2016 3:54 PM
  • Have a look under c:\programData\Microsoft\Windows Server\Logs - there should be more there.

    Also helpful if you can spin up a Windows 7 guest and see if that can join, to rule out any issues with the server itself.


    Robert Pearman Cloud & Datacentre MVP
    @titlerequired | LinkedIn | Google+
    Facebook | Windows Server Essentials.com

    Thursday, June 30, 2016 6:45 PM
    Moderator
  • ConnectWebsite.log

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

    [4600] 160630.153827.5924: ClientSetup: Key: Throttle_192.168.0.1,  Hit number: 1
    [4600] 160630.153827.5924: ClientSetup: Key: Total_Request_for_Connect_Website,  Hit number: 1
    [4196] 160630.153829.1549: ClientSetup: Key: Throttle_192.168.0.1,  Hit number: 2
    [4196] 160630.153829.1549: ClientSetup: Key: Total_Request_for_Connect_Website,  Hit number: 2
    [4196] 160630.153829.1705: DomainManagerObjectModel: DomainSignupManager ctor called. InstanceID=36963566
    [4196] 160630.153829.1861: ClientSetup: Transmit file from c:\program files (x86)\windows server\bin\webapps\client\package\en-US\ComputerConnector.exe
    [4196] 160630.153904.7953: ClientSetup: Key: Throttle_192.168.0.1,  Hit number: 3
    [4196] 160630.153904.8109: ClientSetup: Key: Total_Request_for_Connect_Website,  Hit number: 3
    [4196] 160630.153904.8109: ClientSetup: Servicing Get Request: /connect/default.aspx?Get=Setup.cab&LanguageId=1033&64bit=1
    [4196] 160630.153904.8109: ClientSetup: Getting setup cab
    [4196] 160630.153904.8265: ClientSetup: DomainDnsName Planet-X-.local, DomainNetBiosName PLANET-X-
    [4196] 160630.153904.8265: DomainManagerObjectModel: DomainSignupManager ctor called. InstanceID=15225125
    [4196] 160630.153904.8734: DomainManagerObjectModel: DomainSignupManager ctor called. InstanceID=26458746
    [4196] 160630.153904.8734: ClientSetup: IsRoamingClient() - url request host: remote.domainname.com (actual removed for security)
    [4196] 160630.153904.8734: DeploymentCommon: Failed to open deployment registry: ClientBackupOff
    [4196] 160630.153904.8734: Exception: 
    ---------------------------------------
    An exception of type 'Type: System.IO.IOException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' has occurred.
    Timestamp: 06/30/2016 15:39:04
    Message: The specified registry key does not exist.
    Stack:    at Microsoft.Win32.RegistryKey.Win32Error(Int32 errorCode, String str)
      at Microsoft.Win32.RegistryKey.GetValueKind(String name)
      at Microsoft.WindowsServerSolutions.Common.DeploymentCommon.GetBooleanDeploymentData(String name, Boolean defaultValue)

    [4196] 160630.153904.9671: ClientSetup: Transmit file from C:\Windows\TEMP\uofzm4gj.boi\Setup.cab

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

    Thanks for the information!
    I went through all the logs and the above was all that I saw that looks fishy.. calling on the 32bit installer? I looked in the 64bit path and the ...\en-us\ folder is empty. Not sure if this is the norm. The date on the ComputerConnector.exe seems to be a bit newer than the one released in Windows10.0-KB2790621-x64.msu update. I did not rely on the /connect installer and used the one that is installed with the KB update that is installed locally. (Both end with the same results ~ Crash)

    Version on server:

    Version on Windows 10:

    I will test the Windows 7 later tonight... have to dig out my Win7pro.iso and get it loaded on the server since I no longer have a Windows 7 system to test with. This is growing into a bigger issue than it should be really. Fresh installs and fully updated servers should not be having issues like this out of the box.

    I appreciate all your help and am glad you have not asked me to do something silly like run SFC /scannow (which I have already done)


    - Bob






    • Edited by Bob K Brown Thursday, June 30, 2016 8:14 PM
    Thursday, June 30, 2016 7:57 PM
  • I just ran it on a Windows 8.1 Pro machine and got the same results as with the Windows 10.


    - Bob

    Thursday, June 30, 2016 8:17 PM
  • I just restored the pre-Essentials Role snapshot on my HyperV Server.

    I am going to start over and see if it makes a difference installing the role on my DC2 server...
    You are telling me that it should work... I see no reason to continue troubleshooting if I do not have to.

    I will report back on a win or loss.


    - Bob

    Thursday, June 30, 2016 8:34 PM
  • http://windowsserveressentials.com/2015/08/06/windows-server-essentials-2012-r2windows-10/

    http://windowsserveressentials.com/2014/02/14/windows-server-essentialsconfiguration-troubleshooter/

    Have a look at these two links, they might be useful.


    Robert Pearman Cloud & Datacentre MVP
    @titlerequired | LinkedIn | Google+
    Facebook | Windows Server Essentials.com

    Friday, July 1, 2016 8:24 AM
    Moderator
  • Hi,

    please post the “ipconfig /all” results on both server and client.

    Best Regards,
    Eve Wang

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

    Friday, July 1, 2016 9:17 AM
    Moderator
  • OK so I had the same issue on my DC2 so I reverted it all back to the pre-WSE role snapshots on both servers.
    (I take regular checkpoints and backups prior to making drastic changes such as this.)

    Rolled back my (2) Windows 2012 R2 servers and I reinstalled the WSE Role back on my DC1 VM and tested with the same results again. Loaded up a Windows 7 Professional VM and that just hangs on "Installing this can take up to 30 minutes..." I waited HOURS and it never got any further, cleared the Windows\temp folder and rebooted. Attempted 3 times with the same results on a Windows 7 Professional VM.

    I have been doing IT for quite a while so I get why you are asking for IP info... I have racked my brain for days trying to get this to work before I came here and have also deployed Essentials at a few customer locations in the past; just never on a HyperV host. Perhaps an issue with Dynamic volumes on my HyperV Host? I am out of ideas but do not want to give up just yet. Has to be something relative to my hardware, driver or something configured on the HyperV host that is conflicting. I am digging log files, system and application event logs and making sure the NIC and Chipset drivers are up to date. 

    I am going to run that Troubleshooter Robert posted now.
    [http://windowsserveressentials.com/2014/02/14/windows-server-essentialsconfiguration-troubleshooter/]

    Here is the IP info... I appreciate your input and time looking at this. I wont claim to be an expert but have been doing IT for over 20 years... I learn new things every day from guys like you.

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

    From Server: 

    Microsoft Windows [Version 6.3.9600]
    (c) 2013 Microsoft Corporation. All rights reserved.

    C:\Users\Administrator>ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : FIRNEN-DC1
       Primary Dns Suffix  . . . . . . . : Planet-X-.local
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : Yes
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : Planet-X-.local

    Ethernet adapter Ethernet:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft Hyper-V Network Adapter
       Physical Address. . . . . . . . . : 00-15-5D-00-03-01
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::9c6e:96b6:29c8:c43b%12(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.0.200(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.0.1
       DHCPv6 IAID . . . . . . . . . . . : 301995357
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-DA-05-AE-00-15-5D-00-03-01

       DNS Servers . . . . . . . . . . . : ::1
                                           127.0.0.1
                                           192.168.0.201
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.{0710DA9E-EBF4-4782-84C3-20851A3BA159}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    C:\Users\Administrator>

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

    From Windows 7 Client:

    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Users\bbrown>ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : Windows7-PC
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : planet-x-.local

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . : planet-x-.local
       Description . . . . . . . . . . . : Microsoft Virtual Machine Bus Network Ada
    pter
       Physical Address. . . . . . . . . : 00-15-5D-00-03-09
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::cdc9:48fe:e475:676c%11(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.0.159(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : Friday, July 01, 2016 9:10:32 AM
       Lease Expires . . . . . . . . . . : Friday, July 08, 2016 9:10:31 AM
       Default Gateway . . . . . . . . . : 192.168.0.1
       DHCP Server . . . . . . . . . . . : 192.168.0.1
       DHCPv6 IAID . . . . . . . . . . . : 234886493
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-07-C1-C4-00-15-5D-00-03-09

       DNS Servers . . . . . . . . . . . : 192.168.0.200
                                           192.168.0.201
                                           192.168.0.1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.planet-x-.local:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : planet-x-.local
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    C:\Users\bbrown>

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


    - Bob



    • Edited by Bob K Brown Saturday, July 2, 2016 10:29 AM
    Friday, July 1, 2016 1:18 PM
  • http://windowsserveressentials.com/2015/08/06/windows-server-essentials-2012-r2windows-10/

    http://windowsserveressentials.com/2014/02/14/windows-server-essentialsconfiguration-troubleshooter/

    Have a look at these two links, they might be useful.


    Robert Pearman Cloud & Datacentre MVP
    @titlerequired | LinkedIn | Google+
    Facebook | Windows Server Essentials.com

    Results... (VERY VERY NICE TOOL! THANK YOU!)

    OS Detected: Microsoft Windows Server 2012 R2 Standard

    This tool will check your current Configuration against known Essentials Server Values.
    Written by Robert Pearman (TitleRequired.com) February 2016

    Version Info: Version: 2.05

    1. Test IIS
    2. Test CA Infrastructure
    3. Test Services
    4. Test Service Ports
    0. Quit

    Enter Task..
    1
    Only Errors will be shown.

    Checking Websites..
    Checking Connect Site..
    Checking Virtual Directories..
    Checking AppPools..
    Checking ISAPI Filters..
    Checking IIS SSL..
    Checking IIS Bindings..
    Checking IIS Authentication..

    Review your results, items in red should be investigated.

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

    Enter Task..
    2
    Testing CA Name..
    Certificate Authority Online  : OK
    Certificate Authority Name    : OK
    Certificate Authority Cert    : OK

    Testing /Connect Certificate Package..
    Connect Computer Certificate  : OK

    Testing CRL Download..
    CRL Location                  : http://FIRNEN-DC1/CertEnroll/Planet-X--FIRNEN-DC1-CA.crl
    CRL Destination               : c:\windows\temp\crl.crl
    CRL Download                  : OK

    Testing CRL Distribution Configuration..
    437.625.0:<2016/7/1, 9:45:20>: 0x80070002 (WIN32: 2 ERROR_FILE_NOT_FOUND): CADescription
    419.6336.0:<2016/7/1, 9:45:20>: 0x80070002 (WIN32: 2 ERROR_FILE_NOT_FOUND)
    437.2132.0:<2016/7/1, 9:45:20>: 0x80070002 (WIN32: 2 ERROR_FILE_NOT_FOUND)
    437.625.0:<2016/7/1, 9:45:20>: 0x80070002 (WIN32: 2 ERROR_FILE_NOT_FOUND): ParentCAName

    It is normal to see some 'File Not Found' messages above when using this CmdLet (Get-CACrlDistributionPoint)

    CRL Extension (CDP)           : OK
    CRL Extension (CRL)           : OK

    Testing Dashboard Certificate..
    Dashboard Certificate         : OK

    Review your results, items in red should be investigated.

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

    Enter Task..
    3
    Testing Services on:  FIRNEN-DC1

    Active Directory Certificate Services : Running Auto
    WSS Computer Backup Service           : Running Auto
    WSS Email Service                     : Stopped Disabled
    WSS Health Service                    : Stopped Auto
    WSS Management Service                : Running Auto
    WSS Media Streaming Service           : Running Auto
    WSS Notification Service              : Running Auto
    WSS Provider Registry Service         : Running Auto
    WSS Storage Service                   : Running Auto

    Review your results, items in red should be investigated.

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

    Enter Task..
    4
    Testing Service Ports on :  FIRNEN-DC1

    TCP 80 (Used for Websites)       : OK
    TCP 443 (Used for Websites)      : OK
    TCP 6602 (Used for Status)       : OK
    TCP 8912 (Used for Backups)      : OK
    TCP 65520 (Used for Mac Website) : OK
    TCP 65500 (Used for CA Website)  : OK

    Review your results, items in red should be investigated.

    - Bob

    Friday, July 1, 2016 1:50 PM
  • What is 192.168.0.201? Why don't you use DHCP?

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

    My bad... I posted the server one twice. FIXED.
    I use DHCP... 201 is my other DC/DNS server. Sorry.

    - Bob


    • Edited by Bob K Brown Saturday, July 2, 2016 10:43 AM
    Saturday, July 2, 2016 10:26 AM
  • This AM I removed the openDNS forwarders from the DHCP scope and also the DNS servers and replaced the network switch with another known good switch and reset everything on the network. Same issue stands. I am at a loss. Open to any suggestions... at this point I think I have tried and exhausted everything I have read online as well as any base knowledge I have. Again, nothing fancy here... basic fresh installation... latest updates.

    First time in a long time that an MS issue has got me stumped. It usually ends up being something silly or a typo or something obvious after a good night's sleep... not this time. VERY challenging.

    Hoping for the AH Ha! OR the update from MS that fixes this issue...

    This is the only thing I see that looks suspicious... 

    [4644] 160702.080453.0501: DomainManagerObjectModel: DomainSignupManager ctor called. InstanceID=49382823
    [4644] 160702.080453.0501: ClientSetup: IsRoamingClient() - url request host: 192.168.0.200
    [4644] 160702.080453.0501: ClientSetup: IsRoamingClient() - current server ip:192.168.0.200 
    [4644] 160702.080453.0501: DeploymentCommon: Failed to open deployment registry: ClientBackupOff
    [4644] 160702.080453.0501: Exception: 
    ---------------------------------------
    An exception of type 'Type: System.IO.IOException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' has occurred.
    Timestamp: 07/02/2016 08:04:53
    Message: The specified registry key does not exist.
    Stack:    at Microsoft.Win32.RegistryKey.Win32Error(Int32 errorCode, String str)
      at Microsoft.Win32.RegistryKey.GetValueKind(String name)
      at Microsoft.WindowsServerSolutions.Common.DeploymentCommon.GetBooleanDeploymentData(String name, Boolean defaultValue)

    [4644] 160702.080453.8157: ClientSetup: Transmit file from C:\Windows\TEMP\1v3pydg3.q0i\Setup.cab

    Here is the Crash files from the Windows 10 64 bit client:

    ClientDeploy.exe Crash Files


    - Bob




    Saturday, July 2, 2016 12:16 PM
  • I agree with removing OpenDNS forwarders for troubleshooting. I'd like to see the full logs from a client, unedited or snipped (replace names if you want) Is this an upgraded Windows 7 to Windows 10? If so did the win7 have the connector?

    Robert Pearman Cloud & Datacentre MVP
    @titlerequired | LinkedIn | Google+
    Facebook | Windows Server Essentials.com

    Sunday, July 3, 2016 6:35 PM
    Moderator
  • Removing the OpenDNS did not make a difference.

    I posted a link above to the CrashDeploy log files... what other log files do you want to see that have not already been posted? 


    - Bob




    Monday, July 4, 2016 2:23 PM
  • These dont seem to be the logs i am looking for.

    in c:\programData\Microsoft\Windows Server\Logs

    on the Client.

    There should be 2 or 3 log files.


    Robert Pearman Cloud & Datacentre MVP
    @titlerequired | LinkedIn | Google+
    Facebook | Windows Server Essentials.com

    Tuesday, July 5, 2016 12:25 PM
    Moderator
  • Robert,

    I gave up over the weekend and nuked both DC1 and DC2 server VMs and installed a fresh WSE 2012 R2 server (not an addon role). I do like a challenge but I could not for the life of me figure out why it was crashing the deployment... I know when I am beat and unfortunately had to call it what it was.

    I am hoping the new install I just did this AM will go much better; I am finishing the updates now and will test as soon as I am all up to date. If this works then I will post success and just move on, if not I will zip up and attach all the logs you requested in the next post... fingers crossed.

    Thanks again for all your help and your feedback on this issue... it is much appreciated and nice to have knowledgeable guys like you in the community.

    Update:

    I was able to add the Windows 7 machine using the connector without any issues. (before updates)
    - I will checkpoint and continue with the updates and see if it creates any issues. 

    Update Update: 

    The new installation is working as it should. I used the 2012 R2 Essentials Server install instead of the Windows Server 2912 R2 + Essentials role. Not sure what went wrong (twice) but I will know that in the future not to expect the Essentials Role to work on a Windows Server Standard 2012 R2 on my HyperV box. (I can't assume it is broken anywhere else other than my Server at this point.)

    Thanks again for all your help!


    - Bob






    Tuesday, July 5, 2016 2:41 PM