Decommisioning Exchange 2007 after moving to 2013 - Best practice

Posted on 2016-10-20
Last Modified: 2016-10-21
We've got 5 Exchange 2013 mailbox servers in a DAG. However, we've still got 2x 2007 mailbox servers and 2x 2007 Client Access/Hub servers. All migrations of live users are now finished.

A lot of old users were not migrated and left on 2007. Plan is to keep 2007 for the time being in case access is needed to these old mailboxes.

In the meantime, is there a best practice guide for to finally get rid of 2007? Ideally, as I've said, we'd like to disable but keep the servers for now. Also, what do we need to consider before doing anything? (One thing I thought of is applications sending email directly to 2007 servers)

I wasn't around when 2013 was added to 2007. Are they somehow "linked" now and does this need to be removed?
Question by:paulfoel
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2

Assisted Solution

by:Senior IT System Engineer
Senior IT System Engineer earned 300 total points
ID: 41851751

If you don't have access to the server then the only way to remove it is with ADSIEDIT

Warning If you use the ADSI Edit snap-in and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems

Delete it from AD with ADSIEdit.msc
Run ADSI Edit & expand following items:
Configuration Container -> CN=Services -> CN=Microsoft Exchange -> CN=<Your_Organization_Name> -> CN=Administrative Groups -> CN=<Your_Administrative_Group_Name> -> CN=Servers
Right-click the Exchange server object which you want to delete, and then click Delete & click Yes in every adsiedit dialog box that prompts you to confirm the deletion.

Navigate to this path:

CN=Microsoft Exchange
CN=Administrative Groups

for Exchange 2007
CN=Exchange Administrative Group (FYDIBOHF23SPDLT)

For the Public folder:

CN=Microsoft Exchange
CN=Administrative Groups
CN=Exchange Administrative Group (FYDIBOHF23SPDLT)

Now you can delete the PF-Database you want to get rid off.

Additional reading:

Author Comment

ID: 41851843
We do have access to the server. Im hoping a clean uninstall will do all the necessary ADSIEdit stuff?
I'd rather not go down that road.

Accepted Solution

Senior IT System Engineer earned 300 total points
ID: 41851880

yes, you can also follow the steps described by the Exchange MVP here:

or use this official link:
LVL 63

Assisted Solution

by:Simon Butler (Sembee)
Simon Butler (Sembee) earned 200 total points
ID: 41852119
Disable but keep isn't an option.

Exchange isn't a standalone application and it will complain if it cannot connect to all of the other servers.

Personally what I would do is put all of the Exchange 2007 roles on to a single server, move all of the mailboxes to that one server and then remove the rest using add/remove programs. Add/Remove programs will check that nothing is using the servers.

Put all of the IP addresses of those servers on to the Exchange 2007 server that is left running and then enable logging on the Receive Connector. That will let you see if anything is using them still.

There is no connection between the two servers - you are thinking of routing group connectors between Exchange 2003 and later versions. The architecture is very similar.

If you do move the CAS role, do watch the Autodiscover values aren't changed and SSL certificates are still important even though the server is no longer housing live mailboxes.

Featured Post

U.S. Department of Agriculture and Acronis Access

With the new era of mobile computing, smartphones and tablets, wireless communications and cloud services, the USDA sought to take advantage of a mobilized workforce and the blurring lines between personal and corporate computing resources.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In-place Upgrading Dirsync to Azure AD Connect
A couple of months ago we ran into an issue that necessitated re-creating our Edge Subscriptions. However, when we attempted to execute the command: New-EdgeSubscription -filename C:\NewEdgeSub_01.xml we received an error indicating that the LDAP se…
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

717 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question