Skip to main content

Unable to configure office 365 Mailbox in Outlook

1.      How many users are affected?
2.      Check if the autodiscover records are updated for the domain.
3.      Check the Cname records “autodiscover.domain.com” should point to “autodiscover.outlook.com”If these records are not updated, please update these records in domain DNS file.
4.      Check if the profile can be configured on a non-domain and domain joined machine.

If the profile is not getting configure please share the details of the below mentioned tests.
Autodiscover test.

Please open the below link and go to office 365.
Select: Microsoft Office Outlook Connectivity Tests
Please share the results for both the test. 
Outlook Connectivity
Outlook autodiscover 
Note: Please use the end user’s credentials only.

Try to Disable MAPI for the user. Run PowerShell as admin.

Set-ExecutionPolicy RemoteSigned
 $cred = Get-Credential 
 $ExchangeSession = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri "https://outlook.office365.com/powershell-liveid/" -Credential $credential -Authentication "Basic" -AllowRedirection
 Import-PSSession $ExchangeSession

Disable the MAPI connectivity.
Set-CASMailbox -Identity aliciap@ppmechanical.com -MAPIEnabled $false

Enable the MAPI connectivity.
Set-CASMailbox -Identity aliciap@ppmechanical.com -MAPIEnabled $true

Try to configure the profile now.

Test the Mapi connectivity.
Connect office 365 to PowerShell
Start-Transcript
Set-ExecutionPolicy RemoteSigned
$cred = Get-Credential 
$ExchangeSession = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri "https://outlook.office365.com/powershell-liveid/" -Credential $credential -Authentication "Basic" -AllowRedirection
Import-PSSession $ExchangeSession
Test-MapiConnectivity
Stop –Transcript

If we are not able to configure the profile on a domain joined machine then the possible cause can be the SCP lookup.

If you have local Active Directory structure, and the computers are joined to a local AD domain, when Outlook client starts the autodiscover process, it will first try to find the information used for autodiscover by using Service Connection Point (SCP), instead of DNS lookup. Actually, SCP is always the first thing that autodiscover checks for, and if it isn't found then it moves on to a DNS check.
Therefore, Outlook clients may directly connect to SCP instead of through DNS to use autodiscover service. You can bypass the SCP check by modifying the registry key:

1. Click Start, and then click Run.
2. In the Run dialog box, type regedit, and then click OK.
3. In Registry Editor, go to the following registry key: HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\AutoDiscover]
4. Add the following autodiscover entries: "ExcludeScpLookup"=dword:00000001


Comments

Post a Comment

Popular posts from this blog

Error - QuarantinedAttributeValueMustBeUnique

Case History. 1. Client already had users created in office 365 2. Client wanted to setup SSO for office 365 users Approach for requirement fullfilment   1. Deployed and configured Azure AD connect      95% users were synced and soft match was successfully done  5% users were getting error - QuarantinedAttributeValueMustBeUnique  (to view the sync issues -  https://aad.portal.azure.com/#blade/Microsoft_Azure_ADHybridHealth/AadHealthMenuBlade/SyncErros )  When we checked 2 users were found under Active users  1. one in Cloud (this was created earlier/ already existed ) with active licenses and Mailbox 2. one unlicensed synced with AD Solution - 1. Delete the unwanted user in Azure or AD as per this document.  https://blogs.msdn.microsoft.com/hkong/2017/03/23/how-to-fix-attributevaluemustbeunique-error-message-when-trying-to-sync-an-object-from-on-premises-active-directory-to-office-365/ ...
Post a Comment
Read more

Error - AttributeValueMustBeUnique in Azure AD connect sync

My customer had already created accounts in office 365 and managing them in Azure, however due to some changes in business they wanted to sync AD with Azure to sync Password and Manage Identity form AD. Solution - Deploy Azure AD connect on ADDC, and post that it will do a Soft Match. However there were error with some users, their identities did not sync and their status still reflected as Azure AD. Error -  Unable to update this object because the following attributes associated with this object have values that may already be associated with another object in your local directory services: [ProxyAddresses SMTP:user@domain.com;].  Correct or remove the duplicate values in your local directory.  Please refer to http://support.microsoft.com/kb/2647098 for more information on identifying objects with duplicate attribute values. Tracking Id: b8367c95-ae67-46e1-xxxx-xxxxxxxxxx ExtraErrorDetails: [{"Key":"ObjectId","Value":["cd088468-bb6a-4...
4 comments
Read more

Microsoft office 365 product shows as not activated after few days.

Solution Opened CMD Navigated to Path - cd C:\Program Files (x86)\Microsoft Office\Office16\14\15 To view the installed product key, execute cscript ospp.vbs /dstatus To uninstall an installed product key, execute cscript ospp.vbs /unpkey:XXXXX Replace the XXXXX with the last five character of the currently installed product key (found in step 3). Last 5 digits only To activate Office with the new product key, execute cscript ospp.vbs /act
2 comments
Read more