Outlook search problem after 1709 is installed

On March 13, 2018, in news, by susan

I’ve seen many folks bit by this one so again, blogging it to share with others.  After the install of 1709 the MSI version of Outlook 2016 fails to search properly.

Outlook Search: These regekys are missing after the upgrade. You need to add them back in once the upgrade is complete.
REG ADD “HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\Windows Search\Preferences” /v “{0077B49E-E474-CE11-8C5E-00AA004254E2}” /t REG_DWORD /d 1 /f
REG ADD “HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\Windows Search\Preferences” /v “{4154494E-BFF9-01B8-00AA-0037D96E0000}” /t REG_DWORD /d 1 /f
REG ADD “HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\Windows Search\Preferences” /v “{70fab278-f7af-cd11-9bc8-00aa002fc45a}” /t REG_DWORD /d 1 /f
REG ADD “HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\Windows Search\Preferences” /v “{C0A19454-7F29-1B10-A587-08002B2A2517}” /t REG_DWORD /d 1 /f
REG ADD “HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\Windows Search\Preferences” /v “{c34f5c97-eb05-bb4b-b199-2a7570ec7cf9}” /t REG_DWORD /d 1 /f


PROBLEM: Unable to integrate Dashboard with 0365

On March 13, 2018, in news, by susan

This has happened too many times recently so blogging this to share with others:


See if this is the issue nailing you

PROBLEM: Unable to integrate Dashboard with 0365




Under C:\ProgramData\Microsoft\Windows Server\Logs\SharedServiceHost-EmailProviderServiceConfig.log :


BecWebServiceAdapter: Connect to BECWS failed due to known exception : System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at https://bws902-relay.microsoftonline.com/ProvisioningWebservice.svc?Redir=1098557810&Time=636356539931802459 that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. —> System.Net.WebException: Unable to connect to the remote server —> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused


>> Launch the registry editor console and took backup of the following key:


    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Server\Productivity\O365Integration


>>Under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Server\Productivity\O365Integration\Settings


>> Delete the BecEndPointAddress key


Tried integrating with 0365



>Needs to manually connect all the Dashboard users to their respective Office 365 mailboxes

I’ve not always seen that this last step is needed.


1709 and backups

On December 31, 2017, in news, by susan

I’m monitoring a possible issue (again hat tip to Peter Perry again) with client backups (and backups in general) once 1709 is installed.


In my 1709 testing I’m not seeing this, but I haven’t rolled it out firmwide to get a good feel.  Anyone else seeing this in their networks?


1709 and Essentials 2012 R2

On December 31, 2017, in news, by susan

I’ve seen several posts and had several people indicate that the upgrade to 1709 kills the connector software on Essentials 2012 R2.   However, I’m finding in my own tests that when I have rebooted three times after installing the 1709, the connector lights up again and is connected.

If you have issues, some in this thread have indicated that the following works:

“But you can start the following exe (on the client) to reregister the client:

C:\Program Files\Windows Server\Bin\ClientDeploy.exe

After this the client is online in the dashboard and the backup works also.”


UPS worldship and 1709 Windows 10

On December 31, 2017, in news, by susan

UPS worldship and 1709 Windows 10

Thanks to Peter Perry for another 1709 workaround:

“UPS Support Level 2 fixed the issue. They acknowledged 1709 exacerbates the problem. It requires deleting a bunch of config files in the Program Data folder, disabling BITS, rebooting, run UPS WorldShip (which then works), the re-enable BITS. It continues to work thereafter.”


1709 known issues – follow up

On December 5, 2017, in news, by susan


KB4051963 has helped some users with the RDP crashing issue.  However a few folks still have rdp crashing issues when printing is redirected.  To figure out WHAT printer is the problem, follow this guideline:

Follow this:

If anyone else runs into this issue I would suggest the following steps:
1. Disable the “printers” check box on your Remote Desktop Connection by navigating to Options>Local Resources>Local Devices and resources. Then try to connect.
2. If connection is successful with the printers disable, start removing printers on your local machine one by one in order to figure out which printer is causing the problem.
3. Once you have figured out the problem printer driver, reinstall with a different driver.

It’s helped a few folks here in this forum https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/windows-10-fall-creators-update-remote-desktop/d8e0273d-a82a-4ae6-88ce-450b846946ac?messageId=af70b487-1a9f-4026-94ae-e8bf37d62554


1709 and Essentials

On October 19, 2017, in news, by susan

Getting multiple reports that after the install of 1709 the client connector from the Essentials 2012 R2 is gone and can’t be reinstalled.

Hang loose, seeing about getting cases opened up to investigate.


1709 side effects (at this time)

On October 18, 2017, in news, by susan

Just a heads up, installing Windows 10 1709 fall release causes the classic rdp/rdgateway application to constantly crash.  This impacts RWW/RWA on SBS and Essentials.  As a workaround you can use the RDP app from the Windows store, however it doesn’t remote print.

So once again a strong… hold off on installing the fall release … until we get some of these early bugs worked out.

Temp disable remote printing as a workaround