Ask a question


How can we help you today?

Ask Question
Manage notifications
Subscribe to this question
Martyn Hudson

2016 Essentials Dash - O365 - Some Aspects Broken

Server 2016 Essentials with Office 365 integration. 

Using TLS 1.2. The following aspects have not worked for some time:

>Users tab>Acount Properties>Microsoft Cloud Tab

>Ditto but Distribution Groups

>Office 365 Tab>Exchange Online details now blank

Everything else works - importing accounts, changng passwords etc. 

Is this because basic auth is now disabled in O365??

This file: "C:\ProgramData\Microsoft\Windows Server\Logs\SharedServiceHost-HealthServiceConfig.log"

Is full of:

Microsoft.WindowsServerSolutions.O365Integration.O365ConfigureException:  Exception thrown :Unkown PSRemotingTransportException
   at Microsoft.WindowsServerSolutions.O365Integration.ExchangeOnlineAdapter.MakePowerShellCall[T](Func`1 adaptorCall, PSOperation pso)
   at Microsoft.WindowsServerSolutions.O365Integration.O365ManagementCore.QueryAllExchangeGroupUsers()
   at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderBase`1.InvokeOperation[TResult](String operationName, Func`1 func)
[14652] 250207.170504.3826: PSRunspace: Openning remote runspace failed due to the error: Connecting to remote server outlook.office365.com failed with the following error message : The WinRM client received an HTTP server error status (500), but the remote service did not include any other information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic. ErrorCode: -2144108176.  1 retry
[14652] 250207.170504.3826: PSRunspace: The status of runspace after close Broken.
[20128] 250207.170512.4783: O365ManagementProvider(IO365Callback): QueryO365Information:cc6142fe-87c6-4c33-b6c8-1b9f4a931025 starts
[12936] 250207.170512.5408: O365ManagementProvider(IO365Callback): QueryAllMailboxStatistics:d95e66ee-c18d-42c5-9f35-7e51685bd9e3 starts
[12936] 250207.170512.5408: PSRunspacePool: The pool status before dispatch is: 0:Busy 1:Free 
[12936] 250207.170512.5408: PSRunspacePool: The pool status after dispatch is: 0:Busy 1:Busy 
[12936] 250207.170512.5408: PSRunspace: Begin Microsoft.WindowsServerSolutions.PowerShell.PSRunspace.ExecuteCmdlets
[12936] 250207.170512.5408: PSRunspace: Begin Microsoft.WindowsServerSolutions.PowerShell.PSRunspace.ReInitializeRunspace
[12936] 250207.170512.5408: ExchangeOnlineAdapter: New WSManConnectionInfo(https://outlook.office365.com/powershell-liveid, http://schemas.microsoft.com/powershell/Microsoft.Exchange, for user redacted@abc123.co.uk)
[12936] 250207.170512.7127: PSRunspace: Openning remote runspace failed due to the error: Connecting to remote server outlook.office365.com failed with the following error message : The WinRM client received an HTTP server error status (500), but the remote service did not include any other information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic. ErrorCode: -2144108176.  1 retry
[12936] 250207.170512.7127: PSRunspace: The status of runspace after close Broken.
[10064] 250207.170513.2752: O365ManagementProvider(IO365Callback): QueryDomainConfiguration:ab0a9f5b-9cff-4480-b796-f05fdd305421 starts
[14652] 250207.170514.4003: ExchangeOnlineAdapter: New WSManConnectionInfo(https://outlook.office365.com/powershell-liveid, http://schemas.microsoft.com/powershell/Microsoft.Exchange, for user redacted@abc123.co.uk)
[14652] 250207.170514.5878: PSRunspace: Openning remote runspace failed due to the error: Connecting to remote server outlook.office365.com failed with the following error message : The WinRM client received an HTTP server error status (500), but the remote service did not include any other information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic. ErrorCode: -2144108176.  2 retry
[14652] 250207.170514.5878: PSRunspace: The status of runspace after close Broken.

 

Can anyone shed any light or know of a work around to get these features back??

asked02/07/2025 17:14
27 views
Add Comment
Last Activity 02/13/2025 08:16

1 Answer(s)

  • Mariette Knap

    Hello Martyn,

    Pls, stop using Windows Server 2016 + Essentials. It will never work anymore. It is much better to migrate to Windows Server 2025 and start using the correct tools like Windows Admin Center and sync your AD with Entra Sync.

    answered 02/07/2025 17:35
    Add Comment
    Martyn Hudson

    We're not quite there yet. Will likely do a hardware refresh with Server 2025 in 12 months time, before the end of 2016 support. 

    Mariette Knap

    I understand. With the numerous changes made to Office365 and remote PowerShell, I believe the Essentials integration may no longer function as intended. All the configurations previously done through the Essentials dashboard now be accomplished using the native tools in Windows Server. Perhaps I can assist you with finding a workaround for specific task? Please let me know what you need to do, and I will search for a solution.

    replied 02/07/2025 17:51
    Martyn Hudson

    I have a work around for these - that is just to log directly into O365 and sort it. 

    BUT - I have 1 major issue that is causing a headache. 50/50… when opening the dashboard, it closes whilst opening. When opening for a second time it appears the USERS plugin has caused it to crash. Disabling this allows the dash to open but getting it enabled again - could take 20 attempts.

    There are no plugin apps other than those supplied with the native product. Sfc/scanow picks nothing up. 

    I suspected the issue above was causing this crash? Any ideas?

    replied 02/12/2025 19:05
    Mariette Knap

    Probably .Net related. Any Dashboard (even on SBS 2008 or 2011) started to give problems like this when newer .Net versions are installed.

    replied 02/13/2025 08:16
    Reply
    replied 02/07/2025 17:43
Add an Answer