Jump to content
RESET Forums (homeservershow.com)
Deepthought

Windows 10 anniversary update and the connector

Recommended Posts

Deepthought

After many bad words, it turns out that after the uninstall, DNS defaulted from the server to my internet provider. I forced the DNS back to the server and reran the wizard, and this time it completed successfully.

 

Done until the next Microsoft update............

 

Thanks to all for their help with this.

 

Matt

Edited by Deepthought

Share this post


Link to post
Share on other sites
Drashna Jaelre

Done until the next Microsoft update............

 

Well, that's what the fix is.  Instead of the connector being treated as an feature/update of the OS, that above hotfix for the server treats the connector software as what it should be: Software installed on the system. 

 

Future OS updates should not cause this issue as long as you're using the updated code (eg, the stuff located in "C:\Program Files\Windows Server\" rather than "C:\Windows\System32\Essentials". 

Share this post


Link to post
Share on other sites
Robert Pearman

What do the logs say?

Share this post


Link to post
Share on other sites
jmwills

After many bad words, it turns out that after the uninstall, DNS defaulted from the server to my internet provider. I forced the DNS back to the server and reran the wizard, and this time it completed successfully.

 

Done until the next Microsoft update............

 

Thanks to all for their help with this.

 

Matt

Stand to reason the DNS settings changed since you basically got a new OS, however, installing the Connector should have done that for you.

Share this post


Link to post
Share on other sites
DonTen

I have a similar problem with a Windows 10 Home client. I had not uninstalled and reinstalled the connector with KB3172614 on the server in advance. The Anniversary Update broke the connector but there are still services installed etc. I have read the posts here and the links but stopping / restarting and setting to Automatic the 5 Windows Server Essentials services made no difference to the attempted connector reinstallation which fails at the configuration stage (after sign in and backup options and warning about the computer's pre-existence on the server). The server is fully updated with KB3172614 and other current updates.

I would have tried reinstalling the previous Windows 10 connector from the standalone installer in order then to uninstall completely it but the download link has been disabled.

If anyone has any suggestions I would be very grateful.

Share this post


Link to post
Share on other sites
DonTen

Solved with the help of https://social.technet.microsoft.com/Forums/windowsserver/en-US/041fd2d3-a38c-46ce-bc26-4fc302a6e7a0/not-able-installreinstall-client-connector-on-windows-10-anniversary-update?forum=winserveressentials&prof=required

 

 

I have a similar problem with a Windows 10 Home client. I had not uninstalled and reinstalled the connector with KB3172614 on the server in advance. The Anniversary Update broke the connector but there are still services installed etc. I have read the posts here and the links but stopping / restarting and setting to Automatic the 5 Windows Server Essentials services made no difference to the attempted connector reinstallation which fails at the configuration stage (after sign in and backup options and warning about the computer's pre-existence on the server). The server is fully updated with KB3172614 and other current updates.

I would have tried reinstalling the previous Windows 10 connector from the standalone installer in order then to uninstall completely it but the download link has been disabled.

If anyone has any suggestions I would be very grateful.

 

 

Solved with the help of https://social.technet.microsoft.com/Forums/windowsserver/en-US/041fd2d3-a38c-46ce-bc26-4fc302a6e7a0/not-able-installreinstall-client-connector-on-windows-10-anniversary-update?forum=winserveressentials&prof=required

Share this post


Link to post
Share on other sites
xPETEZx

Not read the whole topic, but will share my experience.

 

I have now upgraded 5 PCs which where connected to my Server to the Windows 10 Anniversary update.

 

On 4 of them, the connector needed to be re-installed. But this was a breeze. No errors / problems backing up the systems after either.

 

On the last system I did, the connector stayed installed. Not sure if it was because I literally installed the connector and was then prompted to update to 10 Ani Update about 2 hours later.

 

Anyway, so far 100% trouble free going to the update.

 

When I first saw this topic, I did hold off updating any systems. 

Share this post


Link to post
Share on other sites
Chris karst

Every single machine I have stopped connecting after updating to Win 10 - 1903

I found this site after lots of Google'ing:   (It's not English, but Google translates it well)

 

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

 

which led me to create this registry file:   (import to each client,  it re-registers services for the connector)

 

 

 

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ServiceProviderRegistry]
"DisplayName"="Windows Server Essentials Provider Registry Service"
"Description"="@%ProgramFiles%\\Windows Server\\Bin\\CommonRes.dll,-20"
"FailureActions"=hex:80,51,01,00,01,00,00,00,01,00,00,00,03,00,00,00,14,00,00,\
  00,01,00,00,00,60,ea,00,00,01,00,00,00,60,ea,00,00,00,00,00,00,00,00,00,00
"DelayedAutostart"=dword:00000001
"Type"=dword:00000010
"Start"=dword:00000003
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):22,00,43,00,3a,00,5c,00,50,00,72,00,6f,00,67,00,72,00,61,00,\
  6d,00,20,00,46,00,69,00,6c,00,65,00,73,00,5c,00,57,00,69,00,6e,00,64,00,6f,\
  00,77,00,73,00,20,00,53,00,65,00,72,00,76,00,65,00,72,00,5c,00,42,00,69,00,\
  6e,00,5c,00,57,00,73,00,65,00,43,00,6c,00,69,00,65,00,6e,00,74,00,53,00,76,\
  00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,22,00,43,00,3a,00,5c,00,50,00,\
  72,00,6f,00,67,00,72,00,61,00,6d,00,20,00,46,00,69,00,6c,00,65,00,73,00,5c,\
  00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,53,00,65,00,72,00,76,00,\
  65,00,72,00,5c,00,42,00,69,00,6e,00,5c,00,50,00,72,00,6f,00,76,00,69,00,64,\
  00,65,00,72,00,52,00,65,00,67,00,69,00,73,00,74,00,72,00,79,00,53,00,65,00,\
  72,00,76,00,69,00,63,00,65,00,2e,00,65,00,78,00,65,00,22,00,00,00
"DependOnService"=hex(7):4b,00,65,00,79,00,49,00,73,00,6f,00,00,00,4e,00,65,00,\
  74,00,54,00,63,00,70,00,50,00,6f,00,72,00,74,00,53,00,68,00,61,00,72,00,69,\
  00,6e,00,67,00,00,00,00,00
"ObjectName"="LocalSystem"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ServiceProviderRegistry\TriggerInfo]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ServiceProviderRegistry\TriggerInfo\0]
"Type"=dword:00000014
"Action"=dword:00000001
"Guid"=hex:06,0c,f5,9e,30,16,37,4a,b2,47,43,cd,8e,27,b5,d1
"Data0"=hex:53,00,54,00,41,00,52,00,54,00,5f,00,50,00,52,00,53,00,00,00
"DataType0"=dword:00000002


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WseClientMgmtSvc]
"DisplayName"="Windows Server Essentials Client Computer Management Service"
"Description"="@%ProgramFiles%\\Windows Server\\Bin\\CommonRes.dll,-4"
"FailureActions"=hex:80,51,01,00,01,00,00,00,01,00,00,00,03,00,00,00,14,00,00,\
  00,01,00,00,00,60,ea,00,00,01,00,00,00,60,ea,00,00,00,00,00,00,00,00,00,00
"DelayedAutostart"=dword:00000001
"Type"=dword:00000010
"Start"=dword:00000003
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):22,00,43,00,3a,00,5c,00,50,00,72,00,6f,00,67,00,72,00,61,00,\
  6d,00,20,00,46,00,69,00,6c,00,65,00,73,00,5c,00,57,00,69,00,6e,00,64,00,6f,\
  00,77,00,73,00,20,00,53,00,65,00,72,00,76,00,65,00,72,00,5c,00,42,00,69,00,\
  6e,00,5c,00,57,00,73,00,65,00,43,00,6c,00,69,00,65,00,6e,00,74,00,53,00,76,\
  00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,22,00,43,00,3a,00,5c,00,50,00,\
  72,00,6f,00,67,00,72,00,61,00,6d,00,20,00,46,00,69,00,6c,00,65,00,73,00,5c,\
  00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,53,00,65,00,72,00,76,00,\
  65,00,72,00,5c,00,42,00,69,00,6e,00,5c,00,53,00,68,00,61,00,72,00,65,00,64,\
  00,53,00,65,00,72,00,76,00,69,00,63,00,65,00,48,00,6f,00,73,00,74,00,2e,00,\
  65,00,78,00,65,00,22,00,20,00,22,00,43,00,3a,00,5c,00,50,00,72,00,6f,00,67,\
  00,72,00,61,00,6d,00,20,00,46,00,69,00,6c,00,65,00,73,00,5c,00,57,00,69,00,\
  6e,00,64,00,6f,00,77,00,73,00,20,00,53,00,65,00,72,00,76,00,65,00,72,00,5c,\
  00,42,00,69,00,6e,00,5c,00,43,00,6c,00,69,00,65,00,6e,00,74,00,4d,00,67,00,\
  6d,00,74,00,53,00,65,00,72,00,76,00,69,00,63,00,65,00,43,00,6f,00,6e,00,66,\
  00,69,00,67,00,22,00,00,00
"DependOnService"=hex(7):4b,00,65,00,79,00,49,00,73,00,6f,00,00,00,4e,00,65,00,\
  74,00,54,00,63,00,70,00,50,00,6f,00,72,00,74,00,53,00,68,00,61,00,72,00,69,\
  00,6e,00,67,00,00,00,00,00
"ObjectName"="LocalSystem"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WseClientMgmtSvc\TriggerInfo]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WseClientMgmtSvc\TriggerInfo\0]
"Type"=dword:00000014
"Action"=dword:00000001
"Guid"=hex:06,0c,f5,9e,30,16,37,4a,b2,47,43,cd,8e,27,b5,d1
"Data0"=hex:53,00,54,00,41,00,52,00,54,00,5f,00,42,00,41,00,43,00,4b,00,55,00,\
  50,00,5f,00,53,00,56,00,43,00,00,00
"DataType0"=dword:00000002


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WseClientMonitorSvc]
"DisplayName"="Windows Server Essentials Client Computer Monitoring Service"
"Description"="@%ProgramFiles%\\Windows Server\\Bin\\CommonRes.dll,-28"
"FailureActions"=hex:80,51,01,00,01,00,00,00,01,00,00,00,03,00,00,00,14,00,00,\
  00,01,00,00,00,60,ea,00,00,01,00,00,00,60,ea,00,00,00,00,00,00,00,00,00,00
"DelayedAutostart"=dword:00000001
"Type"=dword:00000010
"Start"=dword:00000003
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):22,00,43,00,3a,00,5c,00,50,00,72,00,6f,00,67,00,72,00,61,00,\
  6d,00,20,00,46,00,69,00,6c,00,65,00,73,00,5c,00,57,00,69,00,6e,00,64,00,6f,\
  00,77,00,73,00,20,00,53,00,65,00,72,00,76,00,65,00,72,00,5c,00,42,00,69,00,\
  6e,00,5c,00,57,00,73,00,65,00,43,00,6c,00,69,00,65,00,6e,00,74,00,53,00,76,\
  00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,22,00,43,00,3a,00,5c,00,50,00,\
  72,00,6f,00,67,00,72,00,61,00,6d,00,20,00,46,00,69,00,6c,00,65,00,73,00,5c,\
  00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,53,00,65,00,72,00,76,00,\
  65,00,72,00,5c,00,42,00,69,00,6e,00,5c,00,57,00,73,00,65,00,43,00,6c,00,69,\
  00,65,00,6e,00,74,00,4d,00,6f,00,6e,00,69,00,74,00,6f,00,72,00,53,00,76,00,\
  63,00,2e,00,65,00,78,00,65,00,22,00,20,00,22,00,43,00,3a,00,5c,00,50,00,72,\
  00,6f,00,67,00,72,00,61,00,6d,00,20,00,46,00,69,00,6c,00,65,00,73,00,5c,00,\
  57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,53,00,65,00,72,00,76,00,65,\
  00,72,00,5c,00,42,00,69,00,6e,00,5c,00,4e,00,6f,00,74,00,69,00,66,00,69,00,\
  63,00,61,00,74,00,69,00,6f,00,6e,00,53,00,65,00,72,00,76,00,69,00,63,00,65,\
  00,43,00,6f,00,6e,00,66,00,69,00,67,00,22,00,00,00
"DependOnService"=hex(7):53,00,53,00,44,00,50,00,53,00,52,00,56,00,00,00,4e,00,\
  65,00,74,00,54,00,63,00,70,00,50,00,6f,00,72,00,74,00,53,00,68,00,61,00,72,\
  00,69,00,6e,00,67,00,00,00,00,00
"ObjectName"="LocalSystem"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WseClientMonitorSvc\TriggerInfo]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WseClientMonitorSvc\TriggerInfo\0]
"Type"=dword:00000002
"Action"=dword:00000001
"Guid"=hex:de,f2,27,4f,e2,14,0b,43,a5,49,7c,d4,8c,bc,82,45

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WseClientMonitorSvc\TriggerInfo\1]
"Type"=dword:00000002
"Action"=dword:00000002
"Guid"=hex:2a,a6,4b,cc,2e,16,48,46,84,7a,b6,bd,f9,93,e3,35


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WseHealthSvc]
"DisplayName"="Windows Server Essentials Health Service"
"Description"="@%ProgramFiles%\\Windows Server\\Bin\\CommonRes.dll,-8"
"FailureActions"=hex:80,51,01,00,01,00,00,00,01,00,00,00,03,00,00,00,14,00,00,\
  00,01,00,00,00,60,ea,00,00,01,00,00,00,60,ea,00,00,00,00,00,00,00,00,00,00
"DelayedAutostart"=dword:00000001
"Type"=dword:00000010
"Start"=dword:00000003
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):22,00,43,00,3a,00,5c,00,50,00,72,00,6f,00,67,00,72,00,61,00,\
  6d,00,20,00,46,00,69,00,6c,00,65,00,73,00,5c,00,57,00,69,00,6e,00,64,00,6f,\
  00,77,00,73,00,20,00,53,00,65,00,72,00,76,00,65,00,72,00,5c,00,42,00,69,00,\
  6e,00,5c,00,57,00,73,00,65,00,43,00,6c,00,69,00,65,00,6e,00,74,00,53,00,76,\
  00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,22,00,43,00,3a,00,5c,00,50,00,\
  72,00,6f,00,67,00,72,00,61,00,6d,00,20,00,46,00,69,00,6c,00,65,00,73,00,5c,\
  00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,53,00,65,00,72,00,76,00,\
  65,00,72,00,5c,00,42,00,69,00,6e,00,5c,00,53,00,68,00,61,00,72,00,65,00,64,\
  00,53,00,65,00,72,00,76,00,69,00,63,00,65,00,48,00,6f,00,73,00,74,00,2e,00,\
  65,00,78,00,65,00,22,00,20,00,22,00,43,00,3a,00,5c,00,50,00,72,00,6f,00,67,\
  00,72,00,61,00,6d,00,20,00,46,00,69,00,6c,00,65,00,73,00,5c,00,57,00,69,00,\
  6e,00,64,00,6f,00,77,00,73,00,20,00,53,00,65,00,72,00,76,00,65,00,72,00,5c,\
  00,42,00,69,00,6e,00,5c,00,48,00,65,00,61,00,6c,00,74,00,68,00,53,00,65,00,\
  72,00,76,00,69,00,63,00,65,00,43,00,6f,00,6e,00,66,00,69,00,67,00,22,00,00,\
  00
"DependOnService"=hex(7):4b,00,65,00,79,00,49,00,73,00,6f,00,00,00,4e,00,65,00,\
  74,00,54,00,63,00,70,00,50,00,6f,00,72,00,74,00,53,00,68,00,61,00,72,00,69,\
  00,6e,00,67,00,00,00,00,00
"ObjectName"="LocalSystem"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WseHealthSvc\TriggerInfo]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WseHealthSvc\TriggerInfo\0]
"Type"=dword:00000014
"Action"=dword:00000001
"Guid"=hex:06,0c,f5,9e,30,16,37,4a,b2,47,43,cd,8e,27,b5,d1
"Data0"=hex:53,00,54,00,41,00,52,00,54,00,5f,00,48,00,45,00,41,00,4c,00,54,00,\
  48,00,5f,00,50,00,52,00,4f,00,56,00,49,00,44,00,45,00,52,00,00,00
"DataType0"=dword:00000002


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WseNtfSvc]
"DisplayName"="Windows Server Essentials Notification Service"
"Description"="@%ProgramFiles%\\Windows Server\\Bin\\CommonRes.dll,-22"
"FailureActions"=hex:80,51,01,00,01,00,00,00,01,00,00,00,03,00,00,00,14,00,00,\
  00,01,00,00,00,60,ea,00,00,01,00,00,00,60,ea,00,00,00,00,00,00,00,00,00,00
"DelayedAutostart"=dword:00000001
"Type"=dword:00000010
"Start"=dword:00000003
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):22,00,43,00,3a,00,5c,00,50,00,72,00,6f,00,67,00,72,00,61,00,\
  6d,00,20,00,46,00,69,00,6c,00,65,00,73,00,5c,00,57,00,69,00,6e,00,64,00,6f,\
  00,77,00,73,00,20,00,53,00,65,00,72,00,76,00,65,00,72,00,5c,00,42,00,69,00,\
  6e,00,5c,00,57,00,73,00,65,00,43,00,6c,00,69,00,65,00,6e,00,74,00,53,00,76,\
  00,63,00,2e,00,65,00,78,00,65,00,22,00,20,00,22,00,43,00,3a,00,5c,00,50,00,\
  72,00,6f,00,67,00,72,00,61,00,6d,00,20,00,46,00,69,00,6c,00,65,00,73,00,5c,\
  00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,20,00,53,00,65,00,72,00,76,00,\
  65,00,72,00,5c,00,42,00,69,00,6e,00,5c,00,53,00,68,00,61,00,72,00,65,00,64,\
  00,53,00,65,00,72,00,76,00,69,00,63,00,65,00,48,00,6f,00,73,00,74,00,2e,00,\
  65,00,78,00,65,00,22,00,20,00,22,00,43,00,3a,00,5c,00,50,00,72,00,6f,00,67,\
  00,72,00,61,00,6d,00,20,00,46,00,69,00,6c,00,65,00,73,00,5c,00,57,00,69,00,\
  6e,00,64,00,6f,00,77,00,73,00,20,00,53,00,65,00,72,00,76,00,65,00,72,00,5c,\
  00,42,00,69,00,6e,00,5c,00,4e,00,6f,00,74,00,69,00,66,00,69,00,63,00,61,00,\
  74,00,69,00,6f,00,6e,00,53,00,65,00,72,00,76,00,69,00,63,00,65,00,43,00,6f,\
  00,6e,00,66,00,69,00,67,00,22,00,00,00
"DependOnService"=hex(7):4b,00,65,00,79,00,49,00,73,00,6f,00,00,00,4e,00,65,00,\
  74,00,54,00,63,00,70,00,50,00,6f,00,72,00,74,00,53,00,68,00,61,00,72,00,69,\
  00,6e,00,67,00,00,00,00,00
"ObjectName"="LocalSystem"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WseNtfSvc\TriggerInfo]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WseNtfSvc\TriggerInfo\0]
"Type"=dword:00000014
"Action"=dword:00000001
"Guid"=hex:06,0c,f5,9e,30,16,37,4a,b2,47,43,cd,8e,27,b5,d1
"Data0"=hex:53,00,54,00,41,00,52,00,54,00,5f,00,4e,00,54,00,46,00,5f,00,53,00,\
  56,00,43,00,00,00
"DataType0"=dword:00000002

Share this post


Link to post
Share on other sites
zeus163

Wow. I'm actually glad you posted this. I was thinking everything was fine, until I realized my status was offline. Do I create a text file, copy this into it and rename it with a .reg extension?

 

Sorry if this is a stupid question.

Share this post


Link to post
Share on other sites
Chris karst
45 minutes ago, zeus163 said:

Wow. I'm actually glad you posted this. I was thinking everything was fine, until I realized my status was offline. Do I create a text file, copy this into it and rename it with a .reg extension?

 

Sorry if this is a stupid question.

that should do it.

It would not let me attach a .reg file.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...