A little while back we migrated from Exchange Server 2007 to Exchange Server 2010. I followed all the step-by-step instructions for removing the old Exchange Server 2007 server and I can't locate any trace of it in Active Directory but at times when opening Outlook for the first time for a new user, during autodiscover the name of the old server will surface and it has to be manually changed to the new server's name to properly complete the setup process. Well, just the other day I was looking around in the EMC and in the Microsoft Exchange On-Premises section under Servers Summary it references two servers. We only have the single server.

From where does the Servers Summary section get its information? Knowing that might lead me to where I can find the reference to the old server and remove it once and for all.

I would really like to get our Exchange environment cleaned up because I am currently in the planning phases for migrating to Exchange Server 2013.

Hello

tip:
get-exchangserver dont list old server?
Get-AutodiscoverVirtualDirectory |fl *inter* show new server?
with adsiedit connect to configuration and open CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domainname,DC=local
only new server list?

Thank you for your reply. I looked in all the areas you suggested and could only find references to our new server.

Hello

And if start BPA scan not show server?

I tried a new Best Practices scan and it only shows one server, the new server.

Hello

if get-organizationconfig |fl

OrganizationSummary show 2 server? and update date ?
if start again collect organization health data not refress data?

Here you go to rid off all your legacy server/database/storagegroups/public folder information from "ADSIedit.msc" --> select configuration

Exchange 2010

Open ADSI-Edit and got to configuration

CN=Configuration,DC=DOMAIN,DC=LOCAL
CN=Services
CN=Microsoft Exchange
CN=EXCHANGE_ORG
CN=Administrative Groups
CN=Exchange Administrative Group (FYDIBOHF23SPDLT)
CN=Databases
CN=PUBLIC_FOLDER_DATABASE

Exchange 2007
Open ADSI-Edit and got to configuration

CN=Configuration,DC=DOMAIN,DC=LOCAL
CN=Services
CN=Microsoft Exchange
CN=EXCHANGE_ORG
CN=Administrative Groups
CN=Exchange Administrative Group (FYDIBOHF23SPDLT)
CN=Servers
CN=SERVERNAME
CN=InformationStore
CN=STORAGE_GROUP
CN=PUBLIC_FOLDER_DATABASE

Exchange 2003
Open ADSI-Edit and got to configuration

CN=Configuration,DC=DOMAIN,DC=LOCAL
CN=Services
CN=Microsoft Exchange
CN=EXCHANGE_ORG
CN=Administrative Groups
CN=First administrative Group
CN=Servers
CN=SERVERNAME
CN=InformationStore
CN=STORAGE_GROUP
CN=PUBLIC_FOLDER_DATABASE

The Get-OrganizationConfig | FL OrganizationSummary only showed the new server but the update date was from 2012 which was well before we migrated to Exchange 2010.

I was not sure what you meant by collect organization health data, not refresh data. What I did was to run the Best Practices Analyzer and selected for the Health report to gather new baseline performance data. This caused the run to go for more than two hours. I'm still waiting for it to complete.

Thank you for your input. I followed the ADSI-Edit instructions for Exchange 2010 and only found the new server in that location.

Hello

Thank you for clarifying. I ran that and now the Servers Summary correctly shows a single server. I will try a new user setup tomorrow to see if the old server still shows up during the autodiscover process.

Hi,

According to your description, I understand that outlook client use autodiscover service connect to Exchange server and get the old Exchange server name, however it has been removed.
If I misunderstand you concern, please do not hesitate to let me know.

I want to double confirm whether internal or external Outlook client experience this question.
Outlook client use SCP first, if failed it will use DNS SRV record to get URL for autodiscover service, then get relevant URL for Exchange server. Please run below command to double check:
Get-ClientAccessServer | FL Identity,*URI*

If it get legacy Exchange server SCP, please use ADSI Edit to manual remove. For your reference:
https://social.technet.microsoft.com/Forums/en-US/3559c142-2c42-4749-9476-422ab7449853/autodiscover-url-migration?forum=exchangesvrdeploylegacy

Thanks

Thank you for your suggestion. I ran the Get-ClientAccessServer command and it only returned an entry for my new server.

I also want to point out that you understood the situation properly. Also, it is only happening to internal users when they first run Outlook and it attempts to use autodiscover to set up their Outlook account.

• Edited by dablack 17 hours 23 minutes ago

Thank you for your suggestion. I ran the Get-ClientAccessServer command and it only returned an entry for my new server.

I also want to point out that you understood the situation properly. Also, it is only happening to internal users when they first run Outlook and it attempts to use autodiscover to set up their Outlook account.

• Edited by dablack Thursday, April 09, 2015 2:02 PM

Hello

check dns record  on dns server for old server name.