Demoting and Removing Exchange 2007 Server

Oh, I mistakenly saw 2003, and I thought you were removing Exchange 2003.  My bad.
Run the uninstaller on the old system. It will take care of the rest.  It will probably error out and give you reasons, clean up the reasons and run the uninstaller again.  Once it's uninstalled properly, then you can power off the server and everything should be good.  Don't forget your send connectors. I forgot that in my travels once.

At one of our locations we recently migrated all exchange mailboxes to a new Exchange 2007 on new OS platform, moving away from Server 2003. Everything to my knowledge has been migrated, users should be all connecting to new server, all connector headends have been updated, etc. As a test, I shutdown the old Exchange server (without uninstalling) but we ran into issues that day with Outlook constantly (every 5-10 minutes) asking for the user's password, slow loading of folder data, etc.; reboots/application restarts did not resolve. We turned the old Exchange server back on and all is now well. My theory is this is due to the schema still containing info about the old Exchange server. If I uninstall Exchange completely, thus removing it form schema, could I expect to have this issue resolved? Obviously I only get one chance on this, so...
This topic first appeared in the Spiceworks Community

Similar Messages

  • Removing Exchange 2007 Server from Management Console List

    Hello,
    We have an organization with a single Exchange 2007 Server running in production. It is working fine.
    However, we brought up another server (we'll call it the secondary server for purposes of this thread) and linked it into this organization several months ago. Our plans for this box changed and we have kept it powered off, unlicensed, and unused.
    Now, when we manage our production server, the management console keeps complaining about how the secondary server is almost at the end of its trial period, needs licensed, etc.
    Since we might or might not use the secondary server in the future, it is possible to "unlink" it (or set it dormant somehow) from the server list to stop the license warnings? Or is our only recourse to remove Exchange and take it down if we don't
    intend to license it and bring it into production? Our hope is that it can wait in the wings until such time as we decide to user & license it.
    What are the implications if we ignore the license warnings and continue not to use it? Will it impact management of the production server at all or just continue to annoy?
    TIA, Tom W.
    JTW

    Hello,
    "What are the implications if we ignore the license warnings and continue not to use it? Will it impact management of the production server at all or just continue to annoy?"
    You should have all production servers licensed but after trial period expiration the server will have all Exchange capabilities and features. Also trial period expiration should not have any negative impact on your environment. The EMC will simply prompt
    to license that server correctly.
    "Our plans for this box changed and we have kept it powered off, unlicensed, and unused."
    In my opinion it is bad idea to have Exchange server installed but powered off. Note that this server still resides as object in Active Directory and it may complicate any future modifications of your environment (migration to newer versions of Exchange
    etc.). I think you should use this server to provide some kind of high availability (and provide proper license for it) or remove it completely.
    Once again: trial expiration is not a problem from server's functionality perspective, Exchange server powered down - it can be a problem.

  • Removing Exchange 2007 from SBS 2008 (In an Exchange 2010 Coexistance Scenario) - In order to remove 2007 Mailbox Objects from Active Directory and remove the SBS2008 server completely

    I'm trying to remove Exchange 2007 from an SBS 2008 server
    (Server 2008 Standard FE).  My ultimate goal is to completely remove the SBS 2008 Server from the network environment.
    We have an Exchange 2010 Coexistence Scenario and Mailboxes/Public Folders/etc have been moved over to the 2010 mail server, on Server 2008 R2.
    I have moved all Shares, FSMO roles, DHCP, DNS, etc over to their respective servers.  We have two full blown DC's in the environment.
    I'm ready to remove Exchange 2007 from SBS 2008 and DCPROMO the server.  I can NOT seem to find a TechNet article that shows me how
    to proceed in this kind of scenario.  I am trying to use the TechNet article:
    http://technet.microsoft.com/en-us/library/dd728003(v=ws.10).aspx
    This article references Disabling Mailboxes, Removing OAB, Removing Public Folder Databases, then uninstalling Exchange using the Setup Wizard. 
    When I go to Disable Mailboxes I get the following error:
    Microsoft Exchange Error
    Action 'Disable' could not be performed on object 'Username (edited)'.
    Username (edited)
    Failed
    Error:
    Object cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.
    OK
    I really don't see why I need to Disable Mailboxes, Remove OAB and Public Folder Databases since they have been moved to 2010.  I just want
    to remove Exchange 2007 and DCPROMO this server (actually I just want to remove any lingering Exchange AD Objects referring to the SBS 2008 Server, using the easiest and cleanest method possible).
    Can someone point me in the right direction?
    Thanks!

    Hi,
    Based on your description, it seems that you are in a migration process (migrate SBS 2008 to Windows Server
    2008 R2). Now, you want to remove Exchange Server and demote server. If anything I misunderstand, please don’t hesitate to let me know.
    On current situation, please refer to following articles and check if can help you.
    Transition
    from Small Business Server to Standard Windows Server
    Removing SBS 2008 –
    Step 1: Exchange 2007
    Removing SBS 2008 – Step 2:
    ADCS
    Removing
    SBS 2008 – Step 3: remove from domain / DCPROMO
    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft
    does not guarantee the accuracy of this information.
    Hope this helps.
    Best regards,
    Justin Gu

  • Removing Exchange 2007 from SBS 2008 after Migrating to Office 365 Mid Sized with DirSync and SSO

    We have recently completed off a Migration of Exchange 2007 to Office 365 Mid Sized platform.
    I now need to decomission the old SBS 2008 server as they have moved to a Windows Server 2012 R2 server setup for DC, File and print and application servers.
    I need to know what are the ramifications of removing the Exchange 2007 server from the SBS 2008 server and will this remove the LegacyDN details from AD and cause any issues with internal emails between users using Outlook linked through to Office365.
    I understand that after removing Exchange 2007 there will be no friendly GUI to update and maintain proxyAddress, targetAddress and LegacyDN addresses, I am comfortable doing this in ADSI edit or with a script.
    Will this remove the x500 addresses relating to the on premise Exchange Orgainisation and just leave behind the x500 addresses for Exchange Labs which I assume is the x500 addresses for the Azure AD intergration for Office365.

    Hi ,
    Thank you for posting your issue in the forum.
    I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
    Thank you for your understanding and support.
    Best Regards,
    Andy Qi
    Andy Qi
    TechNet Community Support

  • Remove and reconnect Exchange 2007 from Domain

    I have an Exchange 2007 server running on a Windows 2008 server. For some reason the server will not run group policies. It hangs for a very long time when logging in on "Applying Group Policy Printers Policy" And also won't shutdown hanging on
    "Applying Group Policy". The only wany I can shut it down is to manually power off the server.
    I also ran the Group Policy Results Wizard and get a timeout when I run it against the Exchange server. DNS is working fine. I have tested all of the other servers using the same DNS and they all work fine. The server in question has been having other problems
    for a while now, but I have been able to resolve all the other problems except for this one. The server is old and will be replaced this year, but I have to make it work until I get a new server. Maybe 6 months or so.
    I am thinking of removing the server from the domain and then joining the domain again. I'm not sure that will fix it, but I hope it will. The only thing I'm worried about is getting the Exchange database and server running again after I remove and rejoin
    it to the domain. I have heard I can shutdown and disable all Exchange services, then remove the server from the domain and rejoin. But I have never done that and want to be sure it can be done without destroying connectivity to AD and the users. So, is this
    possible?
    Any help is appreciated.
    Doug

    You should try fixing the AD issues instead of removing the Exchange server from the domain. You should start by analyzing what was done to cause the issue in the first place and remedy that.
    Here is a bit similar concern that has been discussed earlier and has been suggested some good steps to sort-out the issue :
    http://community.spiceworks.com/topic/267400-removing-and-re-joining-an-e2k7-server-to-the-domain
    Moreover, when need to recover mailbox items back into previous format, you may also give shot to this automated solution (http://www.exchangeserverrecovery.com/) that could be a good approach while dealing
    in such crucial circumstance.

  • Errors Decommissioning Exchange 2007 Server

    We are attempting to decommission an Exchange 2007 Server (single server). We have already gotten 2010 set up, installed, mailboxes moved and public folders moved. We went through and removed the replicas on the old server as well as removing the mailbox
    database and public folder database.
    From this point we are attempting to Uninstall Exchange 2007 using either the Wizard or through cmd using setup.com /mode:uninstall after navigating to the Bin folder in the Exchange server. Each time however, we get the same error regardless of how we are
    doing it.
    We uncheck all roles, hit Next, and it fails during the Readiness Check within 10 seconds on each role (Mailbox, Client Access, Hub Transport) each time saying: 'An error occurred while running the test. The Computer may be out of Memory, or the XML files
    have been modified. Parameter name: ConfigurationFileLocation'
    I've gone through using ADSI Edit and removed the server from the Configuration>Services>SiteDomain>Administrative Groups>Exchange Administrative Groups>Servers
    and it was none existent in the Databases section.
    Even after all of these steps I'm still getting the error about the memory or XML file issue. Is there a way to replace the XML files with 'clean' ones or a way to repair the existing ones? I'm just simply wanting to uninstall it at this point.
    Thanks!

    Hi,
    From your description, I would like to clarify the following things:
    1. It is not recommended to uninstall Exchange server in ADSIEdit.
    2. The above error indicates that one of the xml files is corrupted, you need to re-download it for troubleshooting.
    Hope my clarification can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Exchange 2007 server problems

    Hello everyone,
    I am having some trouble with our Exchange 2007.
    Since some days ago I am having extrange troubles with out Exchange 2007 server. Users are been asked to write their user and password very oftenly, and I don't know the reason. Additionaly I have realised the OAB is not downloading properly in any Outlook
    client. If I try to do it I am given an error number0x8004010F
    I have been checking exhange server 2007 event viewer and I found a 80040115 error saying OALGen found an error accessing public folders while trying to generate OAL
    Another error comes out inmediately after  saying to check if Public folder store is mounted and there are replicas of Address Lists folders.
    Another event viewer error says there was a problema trying to update availability information for the public folder in the virtual machine NAMESERVER
    We have other 3 Exchange 2003 servers which I cannot remove because of an application we are using, accessing to them. As long as I know public flders are stored in Exchange 2007 server and not replicated in any other server, so I don't know if this has
    something to do with the error.
    Any idea of what might be going on?
    Thank you very much.
    Best regards,
    David.

    I know I'm not addressing your direct issue, but at this point you need to seriously be looking at removing all Exchange 2003 boxes.  Exchange 2003 has left extended support:
    http://blogs.technet.com/b/rmilne/archive/2013/10/08/save-the-date-end-of-exchange-2003-support-t-minus-6-months.aspx
    What exactly is it with this app that causes it to lock on to 2003 only? 
    Cheers,
    Rhoderick
    Microsoft Senior Exchange PFE
    Blog:
    http://blogs.technet.com/rmilne 
    Twitter:   LinkedIn:
      Facebook:
      XING:
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Remove Exchange 2007 from an Exchange 2013 coexistence.

    Hey everyone,
    I've just installed Exchange 2013 on a new server and all is working great.  It is currently in coexistence with our old Exchange 2007 server.  I've since shut the server down and Exchange 2013 has been working without issue.  However, I haven't
    been able to find any articles on this matter so I figured I would ask the question here.
    How do you remove Exchange 2007 from the coexistence.  Do I just uninstall Exchange 2007 from the old server and it will remove itself from the server and the domain?  Any help/link on this matter would be greatly appreciated.
    Thank you,
    Chris

    Hi Simon,
    I am about to do the same exercise as Chris,  I just would like some clarity.  
    1) When you say mailbox Database, do you mean make sure there are no more mailboxes that you want to move over, or are you actually meaning delete the physical DB on the exchange 2007 server.
    2) If there is no use of public folders does anything need to happen?
    Thanks,
    Terry

  • Remove Exchange 2007

    Hi,
    I just moved all mailboxes from exchange 2007 to Office 365 with Exchange 2010 Hybrid setup. I believe that all local Exchange 2007 contact list and Distribution Group are syncing from Dirsyc tool. It is no migration for this type object. From now, we will
    decide to remove Exchange 2007 from network. What we need to do before to safety remove the Exchange 2007 Server ?
    thanks
    Keith

    Hi Keith,
    Agree with both MAS and Gulab Prasad.
    Please shut down Exchange 2007 and monitor whether the new environment works well.
    Then, please remove Exchange 2007 from a server by using Setup Wizard. Details to see:
    http://technet.microsoft.com/en-us/library/bb123893(EXCHG.80).aspx
    (Optional) Last, remove the Exchange 2007 administrative group by using ADSIEdit. The Exchange 2007 administrative group is called
    Exchange Administrative Group (FYDIBOHF23SPDLT)
    Thanks
    Mavis Huang
    TechNet Community Support

  • I have a problem connecting to my company exchange 2007 server from my IPAD2 the same settings worked with the IPAD1

    Hi All
    Can anybody help with this problem when trying to authenticate on the Microsoft Exchange Sever.
    I have been trying to connect the mail client on the IPAD2 to my company email (Exchange 2007 server)
    There appears to be an issue with the SSL settings for the IPAD 2 and Apples new OS
    I know that it’s not supported but I also know that the previous version of the IPAD worked fine using the same settings.
    Just to confirm I can access the email via Safari therefore I know that the Public Key is loaded in the web browser.
    Can anyone confirm that the Public Key has been installed on the IPAD 2 email client?
    Is there anyway to edit the SSL settings?
    Thanks in advance fro your help
    Regards
    Pat

    Try using Static IP and force a connection.
    You can get the settings from your other devices that are connected to the router.

  • Exchange 2013 SP1 Readiness Checks: No Exchange 2007 server detected

    Hi there,
    We are planning to upgrade our current Exchange 2007 server with the new Exchange 2013 SP1. I have been following Exchange Server Deployment Assistant to assist me with this task. Only schema update (setup /PrepareSchema) had been done so
    far. I didn’t run setup /PrepareAD command manually because I wasn’t sure if I need to provide ‘Organisation Name’ with it or not?! I have installed all of the prerequisites as noted in the Microsoft documentation.
    Now, I am a bit confuse with the ‘Readiness Checks’ page during graphical user installation of Exchange 2013 SP1 setup on Windows 2012 R2. Windows 2012 R2 server has all available updates applied.
    ===
    Warning:
    Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
    ===
    I get the message why setup wants to run preparation for the Ex2013 with the ‘Setup /PrepareAD’. But, why ‘No Exchange 2010 server role have been detected in this topology’?! Ok, in my case setup doesn’t detect Exchange 2007 server. Is that ok to proceed
    with the installation or something else needs to be done first?
    Thanks in advance.

    I need Exchange guru advice here please. Since we already have Exchange 2007 SP3 RU 10 in our Windows 2008R2 Active Directory domain here I need to be 100% confident that pushing Exchange 2013 SP1 “Install” will not override our existing Ex2007 environment.
    That would be a huge disaster!
    Microsoft is saying that: “Microsoft Exchange Server 2013 Setup displayed this warning because
    no Exchange Server 2010 or Exchange Server 2007 server roles exist in the organization.”
    http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
    Ok, I get the message about if I continue with Exchange Server 2013 installation, I won’t be able to add Exchange 2010 or Exchange 2007 servers to the organization at a future date..., and why would I need to do that anyway?!
    Microsoft wording about “some solutions may require the use...” are very confusing since we will require to consider “Coexistence or migration requirements"
    Perhaps, before running Exchange 2013 SP1 setup I need to run setup for preparing AD without “Organisation Name” parameter?! Something like this:
    setup /PrepareAD  /IAcceptExchangeServerLicenseTerms

  • Exfolders.exe tool crashes on Exchange 2007 server

    I've downloaded Exfolders.exe and I'm trying to run it on my Exchange 2007 server but it crashes everytime.  I get an APPCRASH with a fault module name of kernel32.dll
    http://gallery.technet.microsoft.com/Exchange-2010-RTM-<//wbr>ExFolders-c76c3649
    I followed all the instructions step by step.
    How do I fix this?

    Hi,
    You didn't see this information?
    ExFolders must be run from an
    Exchange 2010 server - it cannot be run from a workstation as PFDAVAdmin could. It can connect to Exchange 2010 or Exchange 2007, but not older versions.
    PFDavAdmin is the tool to use on Exchange 2007
    http://www.microsoft.com/en-us/download/details.aspx?id=22427
    Martina Miskovic

  • Running Exchange 2007 server in unsynchronized RU levels

    We have Exchange 2013 with legacy 2007/2010. My 2007 servers are at RU10. one of my sites has a need to replace their edge server and wants to install a 2013 edge server, but the internal 2007 hub server will require RU13 to communicate with the 2013 edge.
    Will updating that single hub server to RU10, and leaving the rest of my 2007 environment at RUY10 cause issues?
    Tom

    Hi Tom,
    Thank you for your question.
    We could make internal Exchange at different CU level, but it didn’t recommend by Microsoft, as Hinte’s said. Because there are some improvements at new CU for us to avoid issue, include communicate between internal Exchange 2007 server.
    We could refer to the following link:
    https://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx
    If there are any questions regarding this issue, please be free to let me know. 
    Best Regard,
    Jim
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Jim Xu
    TechNet Community Support

  • Delete old exchange 2007 server

    Hi,
    We have 2 exchange 2007 server(a and b) a is v very old hardware so we have configure new exchange 2007 name is b after configure create new data base and moved all mail box A to B server but if now server A is shutdown user prompting put user name and password. 

    Hi There,
    You need move all the services to the server B before decommission server A.
    The services that you need to move are:
    Offline address book
    Public Folders
    System mailboxes (hidden)
    Change OWA host name to point to server
    When do.
    Uninstall server A.
    Exchange Blog:
    www.ntweekly.com
    MCSA, MCSE, MCITP:SA, MCITP:EA, MCITP:Enterprise Messaging Administrator 2010,MCTS:Virtualization

  • Treo 755p can't sync w/Exchange 2007 Server - AirSAMStat​eMachine.c 1913 14594

    We recently migrated to an Exchange 2007 server and would like our phones to start using ActiveSync. All our Windows Mobile phones have no problem at all. However, we have two users who have the Treo 755p (running Palm OS), and they can't synch.
    After some research I believe this is likely an SSL issue, and so I tried downloading the Palm Certificates Tool and uploading the root cert (GoDaddy whom issues us the cert that we use on our Exchange server), but that didn't work. I tried the actual cert issues to us, and a bunch of other combos, nothing works. The error is the same on both phones. Disabling the SSL in the settings simply gives us another error: AirSAMStateMachine.c 1913 4682
    Any ideas? Maybe I'm uploading the SSL certs wrong? 
    Post relates to: Treo 755p (Sprint)

    I wouldn't give up so soon. Imag here.  Part time Exhange Admin, snowboarder, and denture wearer.
    Your IT crew may have installed the SSL certificate correctly, and then again, maybe not.  I've seen a few 2007 migrations that have missed some crucial steps that are fairly easy to fix.  And given the symptoms you're seeing, it sounds like they missed something (left the default self-signed exchange cert enabled - oopsie-dah)
    Check with your IT staff and ensure they IMPORTED and ENABLED the SSL cert using the Exchange Management Shell. If they applied it via IIS console, that may be the problem right there.  With luck, we can debunk and put an end to this godaddy panic.  Tell your admin they can PM me for additional details if they need any.
    Post relates to: Centro (Sprint)

Maybe you are looking for