Recently came across an issue where although the 50GB limit in 0365 had been increased the user (using Outlook 2013) was receiving errors about needing to delete.
Turns out the OST file 50GB limit was in play – the below resolved it perfectly
Recently came across an issue where although the 50GB limit in 0365 had been increased the user (using Outlook 2013) was receiving errors about needing to delete.
Turns out the OST file 50GB limit was in play – the below resolved it perfectly
It is no longer possible to manually enter Exchange Server details. A valid Autodiscovery record is required. Use this site to find out which autodiscovery mechanism you are using.
Verifies that we do have a valid autodiscovery record and that we use the HTTP Redirect method. It also shows that Outlook tries several other autodiscovery methods before the correct (for my organisation) HTTP redirect method.
What is actually happening is that Outlook 2016 on the PC is hanging when performing the HTTPsAutoDiscoverDomain method. We can force it to use the correct method by the following registry entries.
If Outlook is slow finding the autodiscover records, you may need to tell Outlook to exclude the root domain or other records.
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\AutoDiscover\
DWORD: ExcludeHttpsRootDomain
Value: 1
The other records you can exclude, also under the Autodiscover key are as follows. Use a value of 1 to enable, delete the key if you no longer want to exclude these checks.
DWORD: ExcludeScpLookup
DWORD: ExcludeHttpsAutoDiscoverDomain
DWORD: ExcludeHttpRedirect //I DON’T EXCLUDE THIS ONE BECAUSE I USE IT
DWORD: ExcludeSrvRecord
Login to Windows Azure Active Directory Module for Windows PowerShell with Office 365 administrator credentials and run the following command:
Set-MsolUserPrincipalName -UserPrincipalName mary.osgood@contoso.onmicrosoft.com -NewUserPrincipalName mary.smith@contoso.com
Good discussion about sharing calendars with distribution groups and why it doesnt work!