npkrot.blogg.se

ObjectClass : Īllen, here is the Autodiscover URI C:\Windows\system32>Get-ClientAccessServer | FL Identity,AutoDiscoverServiceInternalUri ObjectCategory : DOMAIN.COM/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory MetabasePath : IIS:///W3SVC/1/ROOT/RpcĭistinguishedName : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=SERVER,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=DOMAIN,CN=MicrosoftĮxchange,CN=Services,CN=Configuration,DC=impact,DC=dc C:\Windows\system32>Get-OutlookAnywhere | fl You must be signed in to an Office 365 account to activate this feature”Įd, it is enabled and configured.

“The Simplified Account Creation feature was first introduced in Click-to-Run installations of Outlook, starting with version. The fact that PG offers the possibility to disable this feature is not an workaround, but the possibility to use the product in a different way than designed. The registry change via GPO can be applied if an automation is needed.Īs we have stated in the article, this is a feature introduced and not an issue. This is not a workaround but a solution provided by PG as it is officially published.Īs a general idea, starting Outlook 2016 autodiscover looks for Office365 first and starting Outlook 2019 we will not have MSI version. The behavior is PG’s direction to go towards Office365. But at least I have a next step.Īnd here is the response from CSS: I can confirm that this behavior is by design. CSS was unable to assist with troubleshooting that. It doesn't explain why "Simplified Profile Creation" fails when the Connectivity Analyzer succeeds. I opened a ticket with MS and was advised to disable Simplified Profile Creation through GPO. It uses a different process to create the profile.

The problem is that "Simplified Profile Creation" was added to the click-to-run version.

?p=organize/retentionpolicytags.slab&exsvurl=1

&MsgID=&Mbx=

?p=personalsettings/EmailSubscriptions.slab&exsvurl=1 o=DOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=EXCHANGE02/cn=Microsoft Private MDB o=DOMAIN/ou=Exchange Administrative Group Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=EXCHANGE02 When configuring from Control Panel > Mail i can see the expected HTTP/HTTPS traffic to the expected Using Wireshark and Fiddler, i can see that when configuring the profile from the outlook start screen there is no HTTP/HTTPS traffic to the Exchange Server. The problem is that since domain joined users are defaulting to IMAP, they don't have access to all Exchange features. The issueĭoes not occur when setting up a profile from Control Panel > Mail.īoth IMAP and MAPI function. This behaviour only occurs when setting up a profile from the Outlook start screen. When configuring Outlook for the first time from a domain joined PC, Outlook defaults its configuration to IMAP rather than MAPI. I am having a problem with Outlook 2016 Version 1708 (Build 8431.2242 Click-to-Run) clients connecting to Exchange 2010 SP3 RU 20.