User can’t access on-prem mailbox after migration to Exchange Online
After migrating a user mailbox to Exchange Online (from Exchange 2016) the user could no longer access some shared mailboxes that are still hosted on-premise in Exchange 2016 (permissions are fine, they could access them prior to being migrated). When…
User can’t access mailbox after migration to Exchange Online
After migrating a user mailbox to Exchange Online (from Exchange 2016) the user could no longer access their mailbox in Outlook, it gave no error just behaved as if it was offline. I tried removing the profile and creating it…
Users have two mailboxes, one online and one on-premise
While working with an Exchange hybrid environment (Exchange 2016 on-premise and Exchange Online) it became apparent that some users had two mailboxes; one on-premise and one in Exchange Online. Their primary mailbox was in the on-premise environment, the one online…
You can’t use the domain because it’s not an accepted domain for your organization
While trying to migrate a mailbox from Exchange 2016 on-premise to Exchange Online using the New-MoveRequest cmdlet it failed and returned this message: You can’t use the domain because it’s not an accepted domain for your organization While checking the…
Exchange Hybrid Wizard – The WinRM client received an HTTP status code of 502 from the remote WS-Management service
I’m running the Office 365 Hybrid Configuration Wizard (HCW) on an Exchange 2016 and receive the following message: Connecting to the remote server failed with the following error message: Connecting to remote server <servername> failed with the following error message:…
Exchange 2016 – “Application cannot be started” when running Hybrid wizard
While trying to run the Hybrid Wizard in Exchange 2016 I get a message box: Application cannot be started. Contact the application vendor. Clicking the Details button opens a log file, and this line half way down stands out to…
Exchange 2016 – Error 500 when running Hybrid wizard
While trying to run the Hybrid wizard in Exchange 2016 (the link at the bottom left of the Exchange Admin Centre) I get a HTTP 500 error after logging in with my Office 365 credentials: It may be just coincidence…
Office 365 – New-ExoPSSession error – The WinRM client cannot process the request. Basic authentication is currently disabled in the client configuration
While attempting to connect to Exchange Online using PowerShell the New-ExoPSSession cmdlet fails with the following error: New-ExoPSSession : Connecting to remote server outlook.office365.com failed with the following error message : The WinRM client cannot process the request. Basic authentication…
Connect to Office 365 Exchange Online using PowerShell
Any Exchange admin will be used to administering their environment with PowerShell. Here is how to connect to your Office 365 Exchange Online environment with just a few commands: $UserCredential = Get-Credential $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential…