- Outlook 2016 not syncing with exchange update#
- Outlook 2016 not syncing with exchange license#
- Outlook 2016 not syncing with exchange download#
Once the license is assigned, it also takes time to sync.įrom experiencing this with multiple clients, I noticed that the web interface updated first compared to the desktop client.
This can be a dedicated teams license or an E5 license. You need to have a license assigned to a user in your Microsoft Office 365 Tenant. Microsoft advises it will take anything from 2-24 hours. Now that the above is done, you need to run the Hybrid Configuration Wizard and then let it all sync. Set-MSOLServicePrincipal -AppPrincipalId $ServiceName -ServicePrincipalNames $x.ServicePrincipalNames $x = Get-MsolServicePrincipal -AppPrincipalId $ServiceName If you are missing values, you need to add what you have set in Exchange. In the same session you need to check what names you have with the following command: Get-MsolServicePrincipal -AppPrincipalId 00000002-0000-0ff1-ce00-000000000000 | select -ExpandProperty ServicePrincipalNames
The next step is very important: You need to ensure that the service principal names you have for Autodiscover and Outlook Web Access (OWA) are added, especially if you have multiple domains, or else you will get certificate errors. New-MsolServicePrincipalCredential -AppPrincipalId $P.AppPrincipalId -Type asymmetric -Usage Verify -Value $credValue $P = Get-MsolServicePrincipal -ServicePrincipalName $ServiceName $CER = New-Object 509Certificates.X509Certificate $CertFile = "\\Server1\c$\OAuthConfig\OAuthCert.cer" $objFSO = New-Object -ComObject Scripting.FileSystemObject $CertFile = "$ENV:SYSTEMDRIVE\OAuthConfig\OAuthCert.cer" You need to connect to your tenant here - that is what the first two lines are doing - and the reset is creating the cert for you and then creating the principal. You must have a cert that needs to be uploaded to Azure/Office 365 Tenant for OAuth. Get-PartnerApplication | ? | Set-PartnerApplication -Enabled $true New-AuthServer -Name "evoSTS" -Type AzureAD -AuthMetadataUrl Here are the first three: New-AuthServer -Name "WindowsAzureACS" -AuthMetadataUrl "" To be able to run some of the commands, you need to do so from your Exchange Server. If there are errors, you need to address them. Let the setup go and create the connectors for you to let it finish.Set Autodiscover for your domain, either to $true or $false depending on your needs, and enter the domain name.Select the SSL certificate that you will use.Sign in to your Office 365 Tenant and let the wizard show no issues for on-premises and Microsoft Office 365.Let the wizard select an optimal Exchange 2016 or Exchange 2019 server.Here are some of the key items in the HCW: In this article, we will not cover the Hybrid Configuration Wizard as it is pretty straightforward to run the setup.
Outlook 2016 not syncing with exchange update#
Also, for Teams and Exchange 2016 or Exchange 2019 to run smoothly, you need to be running the latest Cumulative Update (CU) for that Exchange version.
Microsoft does advise to run the latest HCW.
Outlook 2016 not syncing with exchange download#
Shutterstock First step: Download latest HCWĪs a rule of thumb, I generally download the latest HCW because bugs in earlier versions or issues are addressed in the newer version.
0 kommentar(er)
