exchange-server-2007

Disable Autodiscover on Exchange 2007 Server


This tutorial will show you how to disable autodiscover on an Exchange 2007 on-premise server. Microsoft says this can’t be done, but the following steps below do work and have been tested. We were recently involved in a 365 migration and needed to connect to the old Exchange server to export a few PSTs. The problem was, you can’t plug your Exchange server back into your network because it will cause your current autodiscover to break. And yet, you need it connected to the domain to export the PST files correctly. We also ran into another snag where our Exchange 2007 server was 64bit and to export PSTs you have to use 32bit Exchange management tools. So we had to install the 32bit Exchange Management tools on another server to connect and export the PSTs. Follow the steps below to disable autodiscover.

Disable Autodiscover on Exchange 2007 Server

There are three different things you will want to check that could be running and causing your autodiscover to be still pushing out from your on-premise Exchange 2007 server.

  • Exchange Service Point Connection (SCP)
  • IIS App Pool for Autodiscover
  • Internal Autodiscover DNS record

#1 – Exchange Service Point Connection (SCP)

First, if you have an Exchange Service Point Connection running, your Outlook clients in a domain will look first at the SCP point, no matter what your internal DNS record is. Therefore you will have to disable/remove this.

READ ALSO  Fix Microsoft Windows 8.1/10 search protocol and indexer high CPU load problem

See here: http://community.office365.com/en-us/forums/158/t/45554.aspx
Also this is another good article: http://sysadmin-e.com/exchange-scp

#2 – IIS App Pool for Autodiscover

You will want to disable the Autodiscover App pool in IIS on your Exchange 2007 server. Launch IIS.

iis

Click into “Application Pools.”

application-pools

Right click on “MSExchangeAutodiscoverAppPool” and click “Stop.”

msexchangeautodiscoverapppool

I also recommend right clicking on it and setting “Start Automatically” to False. Just in case you have to reboot your server.

app-pool-start-false

#3 – Internal Autodiscover DNS record

Internally you will want to make sure you have a CNAME for “autodiscover” that points to Autodiscover.outlook.com; your new 365 environment. You can read more here: http://community.office365.com/en-us/wikis/manage/correcting-autodiscover-and-dns-settings.aspx

Once you have checked all three of these things, you should be able to safely connect your Exchange 2007 to your network and grab backups.


You may also like:

Office 365 – “This message could not b... Error Message: This message could not be sent. Try sending the message again later, or contact your network administrator. Error is [0x80070005-000000...
Migrate email to Office 365 using WHM If you are like me, then you are simply wanting to migrate your email over to Microsoft Office 365 to take advantage of Exchange. Me and my colleague ...
TheITBros Microsoft Office 365 Migration Guide We just migrated a company to Microsoft Office 365 and we thought we would share our experience and troubleshooting tips. We hope this saves you some ...
Add An Out Of Office Message In Outlook for A Diff... Did an employee just leave for vacation and forget to do something? Below the instructions will show you how to add an out of office message in Outloo...
Add Calendar Permissions in Office 365 via Powersh... This is a tutorial on adding calendar permissions in Office 365 for your users via Powershell. You can add permissions onto a specific mailbox, or you...