Recovered and Retired Exchange 2010 Server Listed as Provisioned RRS feed

  • Question

  • I'm trying to clean up an Exchange 2010 > 2013 migration. The 2010 servers were physically removed and trashed without uninstalling Exchange after the migration was considered complete. There were still a ton of references to 2010 servers and databases so I was tasked with cleaning it up.

    I followed steps to recover the servers by creating VMs with same OS and name as the old 2010s. I ran the recover install on the mailbox database server and then retired it without rebooting (this may have been a mistake?). It appears that deleting the databases and uninstalling Exchange from the mailbox database server worked as its databases no longer appear in the 2013 ECP.

    But the mailbox database server is still listed in the 2013 ECP as a "provisioned server". I have since run the 2010 setup on the server with the /RemoveProvisionedServer switch and it says it completed but it remains in the 2013 ECP. I have also run the 2013 setup on an existing 2013 server with the /RemoveProvisionedServer switch but it fails with an error which I'm not entirely sure about:

    [10/18/2019 01:02:45.0234] [0] Starting Microsoft Exchange Server 2013 Service Pack 1 Setup
    [10/18/2019 01:02:45.0234] [0] **********************************************
    [10/18/2019 01:02:45.0234] [0] Local time zone:
    [10/18/2019 01:02:45.0234] [0] Operating system version: Microsoft Windows NT 6.2.9200.0.
    [10/18/2019 01:02:45.0250] [0] Setup version: 15.0.847.32.
    [10/18/2019 01:02:45.0250] [0] Logged on user: DOMAIN\administrator.
    [10/18/2019 01:02:45.0281] [0] Command Line Parameter Name='removeprovisionedserver', Value='SRV-2010MBDB'.
    [10/18/2019 01:02:45.0281] [0] Command Line Parameter Name='sourcedir', Value='F:\'.
    [10/18/2019 01:02:45.0516] [0] RuntimeAssembly was started with the following command: '/removeprovisionedserver:SRV-2010MBDB.DOMAIN.LOCAL /sourcedir:F:"'.
    [10/18/2019 01:02:45.0516] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0, wasn't found.
    [10/18/2019 01:02:45.0516] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14, wasn't found.
    [10/18/2019 01:02:45.0516] [0] Copying Files...
    [10/18/2019 01:02:45.0531] [0] Starting copy from F:\Setup\ServerRoles\Common to C:\Windows\Temp\ExchangeSetup.
    [10/18/2019 01:02:47.0844] [0] Finished copy from F:\Setup\ServerRoles\Common to C:\Windows\Temp\ExchangeSetup.
    [10/18/2019 01:02:47.0844] [0] File copy complete. Setup will now collect additional information needed for installation.
    [10/18/2019 01:02:47.0860] [0] Assembly dll file location is C:\Windows\Temp\ExchangeSetup\Microsoft.Exchange.Setup.Console.dll
    [10/18/2019 01:02:49.0891] [0] Setup is choosing the domain controller to use
    [10/18/2019 01:02:50.0063] [0] The MSExchangeADTopology has a persisted domain controller: SRV-DC2.DOMAIN.LOCAL
    [10/18/2019 01:02:50.0094] [0] [ERROR] Exception has been thrown by the target of an invocation.
    [10/18/2019 01:02:50.0094] [0] [ERROR] Method not found: 'Boolean Microsoft.Exchange.Data.Mime.MimeAddressParser.IsValidDomain(System.String, Int32, Boolean)'.
    [10/18/2019 01:02:50.0094] [0] CurrentResult SetupLauncherHelper.loadassembly:444: 1
    [10/18/2019 01:02:50.0094] [0] The Exchange Server setup operation didn't complete.  More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
    [10/18/2019 01:02:50.0094] [0] CurrentResult 1
    [10/18/2019 01:02:50.0094] [0] CurrentResult setupbase.maincore:396: 1
    [10/18/2019 01:02:50.0094] [0] End of Setup

    I still have the Frontend/CAS server to recover and then retire.

    • Edited by -jkm- Friday, October 18, 2019 7:52 AM
    Friday, October 18, 2019 7:51 AM

All replies

  • Hi,

    Do you mean Exchange 2010 is a provisioned Exchange server object, so you used /RemoveProvisionedServer?

    Do you mean you tried to remove databases and Exchange 2010 mailbox sever, but Exchange 2010 mailbox sever still can be seen from Exchange 2013 ECP?

    Please use the following command to check if Exchange 2010 mailbox server can be seen from Exchange 2013 EMS:

    Get-ExchangeServer | Format-List Name,ServerRole

    Please check the Control Panel to make sure the Exchange 2010 is removed. Control Panel > Programs > Programs and Features. Please check if the Exchange 2010 mailbox server is removed from AD as well.

    Here is a blog about uninstalling legacy Exchange servers, hope you can get useful information from it: Decommissioning Legacy Exchange Servers


    Lydia Zhou

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact

    Monday, October 21, 2019 4:48 AM
  • I already attempted /RemoveProvisionedServer switch and as I said it either says it completed but makes no change, or throws the error I put in my initial post.

    Exchange 2010 was removed and deleted from the servers. After I removed Exchange 2010, I had the servers leave the domain.

    I will probably need to use ADSIEdit at this point.

    Wednesday, October 23, 2019 2:49 AM
  • Can you check the removed Exchange 2010 from Exchange management shell as well?

    Please make sure the AD replication works well in your organization. 

    The supported way is to use control panel to uninstall. Since lots of important information are included in ADSI Edit, and it may cause more serious issues if something is done in a wrong way, we generally strongly discouraged to use ADSI Edit to uninstall an Exchange server that can be restored.


    Lydia Zhou

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact

    Friday, October 25, 2019 9:34 AM
  • Just checking in to see if above information was helpful. Please let us know if you would like further assistance. 


    Lydia Zhou

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact

    Thursday, October 31, 2019 9:23 AM