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?
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?
ExchangeWindows OS
Last Comment
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?
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
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
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.
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:
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