asked on

Problem uninstalling Exchange 2007 following migration to Exchange 2013

I have migrated all data from a legacy Exchange 2007 SP3 server to a new Exchange 2013 server. However, when attempting to uninstall Exchange 2007 SP3 from the legacy server as the final step of decommissioning it, the uninstall fails with the resulting error message:

C:\>setup.com /mode:uninstall

Welcome to Microsoft Exchange Server 2007 Unattended Setup

Preparing Exchange Setup

The following server roles will be removed
Mailbox Role
Hub Transport Role
Management Tools

Performing Microsoft Exchange Server Prerequisite Check

Mailbox Role Checks ......................... FAILED
Cannot find at least one global catalog server running Windows Server 2003 Service Pack 1 or later in the local Active Directory site.

Hub Transport Role Checks ......................... FAILED
Cannot find at least one global catalog server running Windows Server 2003 Service Pack 1 or later in the local Active Directory site.

The Exchange Server Setup operation did not complete. For more information, visit http://support.microsoft.com and enter the Error ID.

Exchange Server setup encountered an error.

I have a feeling this may be due to the 2003 R2 domain controllers having been replaced with Window Server 2016 DC's, and the Exchange server not being able to talk to them. Is there something I'm missing? Any suggestions for successfully installing the Exchange 2007 SP3 server, or do I need to do a manual removal and cleanup?

J0rtIT

I think this answer will point you in the good way:
https://www.experts-exchange.com/questions/28401051/How-to-safely-change-the-Domain-Controller-Global-Catalog-servers-being-used-by-Exchange-Server-2007.html

And the answer to this question:

1. First please ensure that all the AD related roles have been all transfer to the new DC/GC.
2. Please ensure that the new DC/GC has replicated all the information from the old one.
3. Try to turn off the old one, and then monitor if Exchange can work normally.
3. Once everything is running, you could then go ahead and run dcpromo to demote the DC and remove it from the domain.

More information to share with you:

How to replace single domain controller in domain with a single domain controller?
http://support.microsoft.com/kb/555549

Exchange Active Directory Provider could not find an available domain controller in the domain
http://technet.microsoft.com/en-us/library/bb218301.aspx

Regards,
Xiu

Source: https://social.technet.microsoft.com/Forums/exchange/en-US/91b9eb98-5d08-4635-9f8c-7b72434a0283/change-global-catalog-in-exchange-2007?forum=exchangesvrgenerallegacy

http://www.itprotoday.com/management-mobility/q-how-can-i-specify-global-catalog-gc-i-want-my-microsoft-exchange-server-system

Rich

ASKER

1. Currently, there is only one Domain Controller and Global Catalog server running in the environment. This is on a Windows Server 2016 server. All other domain controllers that were in operation have been demoted to member servers and decommissioned.

2. The single domain controller holds all of the FSMO roles currently.

I reviewed the linked articles. However, there did not seem to be any problems with the legacy Exchange server communicating to the domain controller, except when attempting to perform the uninstall.

Any attempt to uninstall Exchange 2007 SP3 from the legacy Exchange server still results in the message "Cannot find at least one global catalog server running Windows Server 2003 Service Pack 1 or later in the local Active Directory site."

Any other thoughts?

SOLUTION

Todd Nelson

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ASKER CERTIFIED SOLUTION

Rich

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Rich

ASKER

Found the solution to resolve the issue by downgrading the domain and then uninstalling Exchange. Todd Nelson's solution helped point me in the direction of looking for a way to downgrade the domain level.