locked
Can't remove Exchange 2003 server RRS feed

  • Question

  • We have completed transition from Exchange 2003 Enterprise to Exchange 2010 standard. All databases (also public folders), user mailbox, dist. list are running on Exchange 2010, also users are using Exchange 2010 for more that one week, so I decided to remove Exchange 2003 server from environment.

    After trying to delete Exchange 2003 public folder store, I get the following error: An invalid ADSI pathname was passed. ID no: 80005000

    So I restarted Exchange 2003 server, now public folder store woulnd't mount, with the following error: An internal processing error has occurred. Try restarting Exchange System Manager or the Microsoft Exchange Information Store service, or both.ID no: c1041724

    When I tried to use add/remove to uninstall Exchange 2003 , uninstallation failed with error: 0xc007041d - The service did not respond to the start or control request in a timely fashion. (EXIFS)

    Facility: Microsoft Exchange Setup
    ID no: c107041d
    Microsoft Exchange Setup

     

    Don't know what to do next, in any way I can't remove Exchange 2003 from environment. Any ideas how to solve this?

    Thank you all in advance!

    Regards,Miha

    Monday, September 13, 2010 1:40 PM

Answers

  • Are you replacing Exchange 2003 with another server or a different version of Exchange?

    The following KB is a good place to start, if it fails to remove by Add/Remove programs. There are steps to perform a manual removal.

    How to remove Exchange Server 2003 from your computer

    http://support.microsoft.com/kb/833396


    MCITP: Enterprise Messaging Administrator 2007/2010 | MCITP: Server Administrator | MCTS: Windows Server 2008 Applications Infrastructure, Configuring | MCP | MCDST
    Monday, September 13, 2010 1:46 PM
  • Thanks again. Just to be sure, I need to delete the top level object CN=Exchange2003 with all child-objects below (Advanced Sec, Filder Hierarchies...)?

     

     CN=Exchange2003                         ; this is the old Exchange 2003 Server
            CN=Advanced Security
            CN=Folder Hierarchies
            CN=Policies
            CN=Routing Groups
            CN=Servers
                
    CN=Exchange2003


    The one i marked with bold text is the one you should delete

    Jonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog
    • Marked as answer by MihaB Monday, September 27, 2010 2:08 PM
    Tuesday, September 14, 2010 11:04 AM

All replies

  • Are you replacing Exchange 2003 with another server or a different version of Exchange?

    The following KB is a good place to start, if it fails to remove by Add/Remove programs. There are steps to perform a manual removal.

    How to remove Exchange Server 2003 from your computer

    http://support.microsoft.com/kb/833396


    MCITP: Enterprise Messaging Administrator 2007/2010 | MCITP: Server Administrator | MCTS: Windows Server 2008 Applications Infrastructure, Configuring | MCP | MCDST
    Monday, September 13, 2010 1:46 PM
  • We replaced Exchange 2003 Enterprise Server with Exchange 2010 Standard (transition-migration). Now we have two Exchange servers in our organization: 2k10 that is fully functional, and 2k3 that needs to be deinstalled.

    Regards,Miha

    Tuesday, September 14, 2010 7:26 AM
  • Hi

    Is everything moved to the new server? public folders? hierarchy? etc...

    If yes, then you can remove the server with adsiedit, make sure you just remove the server and nothing else

     


    Jonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog
    Tuesday, September 14, 2010 9:31 AM
  • CN=Configuration, DC=Domain_Name,DC=com
    CN=Services
    CN=Microsoft Exchange
    CN=Your_Organization_Name
    CN=Administrative Groups
    CN=Your_Administrative_Group_Name_Or_Exchange_Name
    CN=Servers

     

    Then delete only the server object and nothing else


    Jonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog
    Tuesday, September 14, 2010 9:34 AM
  • Hi Jonas,

    Thank you for your helpful tips. If you're so kind and explain me what exactly do I need to delete, not to cause collapse of existing 2k10 server?

    Under CN=Administrative Groups I have 2 groups:

        CN=Exchange Administrative Group (FYDIB0HF23SPDLT)    ; this is a new Exchange 2010 Server

        CN=Exchange2003                         ; this is the old Exchange 2003 Server
            CN=Advanced Security
            CN=Folder Hierarchies
            CN=Policies
            CN=Routing Groups
            CN=Servers
                
    CN=Exchange2003
                ...

    So I need to delete the whole 'old server' CN=Exchange2003 object or just under it the CN=Servers object?

    Thank you again for help.
    Regards,Miha

    Tuesday, September 14, 2010 10:13 AM
  • Hi Jonas,

    Thank you for your helpful tips. If you're so kind and explain me what exactly do I need to delete, not to cause collapse of existing 2k10 server?

    Under CN=Administrative Groups I have 2 groups:

        CN=Exchange Administrative Group (FYDIB0HF23SPDLT)    ; this is a new Exchange 2010 Server

        CN=Exchange2003                         ; this is the old Exchange 2003 Server
            CN=Advanced Security
            CN=Folder Hierarchies
            CN=Policies
            CN=Routing Groups
            CN=Servers
                
    CN=Exchange2003
                ...

    So I need to delete the whole 'old server' CN=Exchange2003 object or just under it the CN=Servers object?

    Thank you again for help.
    Regards,Miha


    Yes, you should delete the object called CN=Exchange2003 (the name of your server)

    Jonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog
    Tuesday, September 14, 2010 10:41 AM
  • Thanks again. Just to be sure, I need to delete the top level object CN=Exchange2003 with all child-objects below (Advanced Sec, Filder Hierarchies...)?

     

     CN=Exchange2003                         ; this is the old Exchange 2003 Server
            CN=Advanced Security
            CN=Folder Hierarchies
            CN=Policies
            CN=Routing Groups
            CN=Servers
                
    CN=Exchange2003

    Tuesday, September 14, 2010 11:01 AM
  • Thanks again. Just to be sure, I need to delete the top level object CN=Exchange2003 with all child-objects below (Advanced Sec, Filder Hierarchies...)?

     

     CN=Exchange2003                         ; this is the old Exchange 2003 Server
            CN=Advanced Security
            CN=Folder Hierarchies
            CN=Policies
            CN=Routing Groups
            CN=Servers
                
    CN=Exchange2003


    The one i marked with bold text is the one you should delete

    Jonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog
    • Marked as answer by MihaB Monday, September 27, 2010 2:08 PM
    Tuesday, September 14, 2010 11:04 AM
  • Jonas thank you for your help ! Now it shows only 2010 server running get-exchangeserver.

    I have another question, running BaselineAnalizer for Exchange it shows me that there are still Exchange 2003 object in AD. I'm asuming that because I have deleted only CN=Server (old server) object. Do I also need to delete all other objects regarding Exchange 2003  from Administrative groups (top level CN=Exchange 2003 object) ?

     

    Under CN=Administrative Groups I have 2 groups:

        CN=Exchange Administrative Group (FYDIB0HF23SPDLT)    ; this is a new Exchange 2010 Server

        CN=Exchange2003                         ; this is the old Exchange 2003 Server
            CN=Advanced Security
            CN=Folder Hierarchies
            CN=Policies
            CN=Routing Groups
            CN=Servers
                
    CN=Exchange2003 --> this one has been deleted

     

    Thursday, September 16, 2010 12:40 PM
  • You need also make sure that you have moved the Public folder tree under Exchange Administrative Group otherwise you may face issues with the Public folders
    Exchange Rocks
    Thursday, September 16, 2010 12:50 PM
  • Thanks!
    Monday, September 27, 2010 2:08 PM