Outlook 2010 / 2007 Autodiscover für Netzwerge Exchange

Der folgende Weg gilt für Kunden, die bereits ein Netzwerge Exchange-Konto auf dem alten Exchange-Server ohne Autodiscover hatten und unter Outlook 2007 oder 2010 jetzt Probleme mit dem Abwesenheitsassistenten und dem Offline-Addressbuch haben. Unter Outlook 2007 heißen die Pfade nicht Office14 sondern Office12 sowie Office\12.0 statt Office\14.0.

Eine Datei mit folgendem Inhalt in den Ordner C:\Program Files\Microsoft Office\Office14\OutlookAutoDiscover unter dem Namen netzwerge.de.xml erstellen.

<?xml version="1.0" encoding="utf-8" ?>
<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
  <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">

In die Registry folgenden Eintrag vornehmen, wobei der Name der zu erstellenden Zeichenfolge anstatt netzwerge.de die Domainendung der Mail-Adresse des bereits angelegten Kontos sein muss.

Windows Registry Editor Version 5.00


Danach sollte Autodiscover automatisch aktiviert sein und auch das Offline-Adressbuch und der Abwesenheitsassistent sollten wieder laufen.

Zusätzlich können noch folgende Einstellungen in der Registry als DWORD gesetzt werden, wenn man auf jeden Fall möchte, dass die lokale Datei verwendet wird.


Hier alle möglichen Autodiscover-Einstellungen und ihre Bedeutung (Hier gefunden):

  • PreferLocalXML – This one doesn’t show up in the above GPO setting, but can be used if you wish to deploy a local XML file that defines Autodiscover. This is usually more work than it’s worth, so I don’t recommend it.
  • ExcludeHttpRedirect – The same as “Exclude the HTTP redirect method” above. This prevents Outlook from allowing an Autodiscover redirect from occurring. This technique allows someone to create a site to accept traffic for Autodiscover and send it to a different site. Exchange Hosting organizations (Other than O365) will use this regularly, and blocking this will prevent access to environments that use this technique.
  • ExcludeHttpsAutoDiscoverDomain – This will prevent Autodiscover from checking autodiscover.domain.com for the Autodiscover.xml file. This is where autodiscover takes the email domain, adds Autodiscover. to the front, and looks at that URL. This is the most common Autodiscover technique in use today. Does the same thing as “Exclude the query for the Autodiscover domain” in the GPO.
  • ExcludeHttpsRootDomain – Prevents Outlook from looking at the root email domain.com URL for the Autodiscover.xml file. It’s not particularly common for this setting to apply, but the lookup for it occurs before the most common technique. You’ll want to use this if you are hosting a web server that uses domain.com for its URL and accepts request for all child URLs. This step trips up a lot of people, so I recommend disabling this step in most situations because it will speed up Autodiscover and prevent incorrect lookups. This one is equal to the “Exclude the root domain query based on your Primary SMTP address” GPO policy.
  • ExcludeScpLookup – The AD SCP is another extremely common tool for pointing to the Autodiscover.xml file. This method applies to lookup attempts for users that are logged in to computers in an Active Directory domain. The SCP is customizable, and can cause issues shortly after deploying new servers (until you set the SCP value to function properly), so you may want to disable this lookup before doing that. “Exclude the SCP object lookup” GPO setting will do the same thing.
  • ExcludeSrvRecord – The SRV record technique lets you set a server for Autodiscover in a DNS SRV record. This is useful if you have a certificate with a single server name listed on it that isn’t autodiscover.domain.com. This is actually the last lookup done for Autodiscover, and disabling it is unnecessary in the vast majority of situations (unless you’re trying to disable Autodiscover, which is a bad idea at this point). This is the “Exclude the SRV record query in DNS” GPO setting.
  • ExcludeLastKnownGoodURL – Autodiscover records the last URL that received a 200 code (AKA – Good URL event code for HTTPS). If you are stuck with a bad URL in Autodiscover (happens if you’re dealing with the root domain situation listed above), setting this will let things go through normally. Equals the “Exclude last known good URL” setting in the GPO.
  • ExcludeExplicitO365Endpoint – Prevents Outlook 2016 and later from checking Office 365 for a matching email address or user account. The function that this disabled can be a real pain in the neck if you have Office 365 with your domain added, but no Exchange mailboxes in the cloud. Disable it with this registry setting or “Exclude initial check to Office 365 Autodiscover URL”.

Datum: Montag, 10. Oktober 2011 17:26
Trackback: Trackback-URL Themengebiet: Windows

Feed zum Beitrag: RSS 2.0 Diesen Artikel kommentieren

Kommentar abgeben