Share via

Windows Server 2016 Essentials Dasboard can't integrate with Office 365

Jesse Flintoff 231 Reputation points
2021-04-02T23:21:16.523+00:00

Hi there.

Can someone help me please? I have multiple fresh built Windows 2016 Essentials server that cannot integrate with 365 via the Dashboard wizard. See two screen shots below.

Existing 2016 essentials production servers that were integrated with 365 before this issue started. Continue to work normally.

There was a recent issue with Anywhere access not working for all Windows 2016 Essentials server. The fix outlined in the link below does not fix the 365 integration issue.

https://learn.microsoft.com/en-us/answers/questions/318584/are-the-problems-with-remotewebaccesscom-domain-an.html

Please can you help me?

84046-essentials-console-365-integration.jpg

84147-365-integration-error.jpg

Windows for business | Windows Server | User experience | Other
Accepted answer
  1. Jesse Flintoff 231 Reputation points
    2021-04-17T07:03:13.25+00:00

    I fixed this issue by installing Microsoft Online Services Sign-In Assistant for IT Professionals RTW

    https://www.microsoft.com/en-us/Download/details.aspx?id=28177

    Credit to Jack Summers - https://pljdesigns.co.uk/blog/2021/04/08/how-to-fix-windows-essentials-server-integration-error/

    2 people found this answer helpful.

4 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ron 11 Reputation points
    2022-03-06T19:53:57.987+00:00

    Server Essentials 2016 Cloud Integration Services FIX. After my integration broke for about a year, I was able to combine several solutions that did the trick.
    All items listed below MUST be active to resolve the issue.

    1. Verify the following is in installed on the Server: Microsoft Identity Manager Password Change Notification Service
    2. Verify the following is in installed on the Server : Microsoft Online Services Sign-in Assistant (msoidcli_64bit.msi)
    3. From Azure Active Directory Admin Center, DISABLE SECURITY DEFAULTS. Setting is found at Azure Active Directory Admin Center/Properties/Manage Security Defaults. Disable the default setting from Yes to No.
    4. Create an Office 365 Administrator Account with the domain “yourdomain.onmicorosoft.com”. Do not use the primary domain “yourcompany.com”.
    5. Do not assign an Office 365 License to the new account. After creating the account, allow 15 minutes to propagate. Do not rush.
    2 people found this answer helpful.
  2. Carl Fan 6,881 Reputation points
    2021-04-05T04:54:07.5+00:00

    Hi,
    Have you checked the registry below:
    Office 365 Integration fails with "Cannot connect to Microsoft online services" in Windows Server 2012 R2 Essentials
    https://learn.microsoft.com/en-us/archive/blogs/sbs/office-365-integration-fails-with-cannot-connect-to-microsoft-online-services-in-windows-server-2012-r2-essentials
    Check below registry key and make sure that the key “Value date” is Windows Server 2016 Essentials’ FQDN (system – full computer name):

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Server\ADContext
    Also you could check if you issue caused from below thread about Password Change Notification Service ?
    2012 R2 Essentials Fails to Integrate with O365
    https://kwsupport.com/2015/05/2012-r2-essentials-fails-to-integrate-with-o365/
    Hope this helps and please help to accept as Answer if the response is useful.
    Best Regards,
    Carl

  3. FancyPlantz 1 Reputation point
    2021-04-06T21:03:49.077+00:00

    Same problem on multiple servers and cant find a fix. This has been ongoing since approximately March 2021.

  4. Andreas Walker 1 Reputation point
    2021-05-16T17:20:13.2+00:00

    I faced the same issue.
    After Installing the Microsoft Online Services Sign-In Assistant for IT Professionals RTW as suggested by @Jesse Flintoff , the Wizard was workling longer but failed agin with the same Error Messge.
    The Inspection of "C:\ProgramData\Microsoft\Windows Server\Logs\SharedServiceHost-EmailProviderServiceConfig.log" included an interesting entry: 

    [10700] 210516.175233.1008: General: Failed to open IDENTITY\BestPasswordPolicy registry key.

    For me this looked like a premission Issue of a registry-key.

    Then I Investigated the issue further and found out, that this message is related to the installation of the Password Change Notification Service (Short PCNS)
    I Then decided to Install this Service manually as described here: https://learn.microsoft.com/en-us/microsoft-identity-manager/deploying-mim-password-change-notification-service-on-domain-controller

    I issued the following commands in an elevated terminal and clicked trough de Wizards: 

    msiexec.exe /i "C:\Program Files\Windows Server\Bin\PCNS\Password Change Notification Service.msi" SCHEMAONLY=TRUE  
msiexec.exe /i "C:\Program Files\Windows Server\Bin\PCNS\Password Change Notification Service.msi"

    Then I rebooted the Server and was able to link my Windows Server 2016 Essentials to my Microsoft 365 Tenant.

    In some cases the PCNS-Files seem to be missing. I uploaded the PCNS.zip file from my Server to my OneDrive: https://walkerit-my.sharepoint.com/:u:/g/personal/andreas_walker_walkerit_ch/EdibZSTue_dJqU4BnsLfTKoB8PlChoump1crJ1VVZkyd4A?e=QFMcmx

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.