Remove Exchange 2007 from AD (manually)

In the lab I had Exchange 2007 running and someone pulled my VM.  It's not the end of the world because I'm done with what I was doing in 2007 however I've got other things running in the lab and I'd rather not rebuild the domain.
Does anyone know what the process would be to clean up AD (remove the Exchange org) without having the Exchange server to do an uninstall on?  Can I Install the Exchange admin console on another box and than remove the mail attributes from the accounts that has them and just remove the Exchange Systems Object container in AD or is there more?
Erik

I did run into one problem while trying to install RTM:
Organization Preparation
Failed
Error:
The well-known object entry B:32:A7D2016C83F003458132789EEB127B84:CN=Exchange Servers\0ADEL:e60b372e-cd97-4fc2-bc8f-907728f0bc8d,CN=Deleted Objects,DC=domain,DC=com of the otherWellKnownObjects attribute on container object CN=Configuration,DC=domain,DC=com
points to an invalid DN or a deleted object.  Please remove the entry and rerun the task.
I was able to resolve the issue by launching adsiedit.msc (part of the support tools) and going to the Configuration partion and bringng up the properties for Configuration,DC=domain,DC=com
I edited the "othereWellKnownObjects" attribute to be "not set" (which it should be) by leaving it blank and clicking "add" (adding nothing) than applying the changes and re-running setup.
Kudos to this thread for the fix:
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=839779&SiteID=17
Cheers,
Erik
otherWellKnownObjects is a multi-valued object.  You need to remove the bad value, NOT ALL OF THEM!!
Mike Crowley | MVP
My Blog --
Planet Technologies

Similar Messages

  • 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

  • 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

  • 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 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

  • 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.

  • Remove various accepted domains (exchange 2007) from a list file via powershell

    hello!
    i'm a newbie with powershell and i'm trying to find if is it possible to remove a lot of exchange 2007 accepted domains from a csv file using powershell.
    I want to delete accepted domains contained in a csv, it has only domains name and powershell requires the name , that is different from the domain.
    example of accepted domain in my organization:
    Name                           DomainName                DomainType            Default
    Domain0001        
    domain1.com     Authoritative         False 
    Domain0002 hello1.com
    Authoritative False
    I've only a csv with domains name:
    domain.csv:
    Domain
    domain1.com
    hello1.com
    Deleting an accepted domain via powershell requires the name so I need to extract first the name of , i've tried with this command and it works:
    Get-AcceptedDomain | Where{$_.DomainName -eq 'domain1.com'}
    This works only for 1 domain, I've a lot of domains to delete so it's inviable
    Now, i'm trying to launch this command without success:
    import-csv domain.csv | foreach {Get-AcceptedDomain | Where{$_.DomainName -eq '$_.Domain'}}
    Probably there is a syntax error, or maybe I just can't do it. 
    Any help? 
    Many thanks in advance!!

    Don't know what to tell you, then.  If I create a test file with that data, the Import-CSV works for me:
    Domain
    3414257440.domain.com
    domain1.domain.com
    '@ | set-content c:\testfiles\domain.csv
    $DomainNames =
    Import-CSV 'c:\testfiles\domain.csv' |
    Select -ExpandProperty Domain
    $DomainNames
    3414257440.domain.com
    domain1.domain.com
    [string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

  • 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.

  • Manually removing Exchange Server from Exchange 2010 Organization

    Hi everybody, I need some help with a problem removing my last Exchange Server 2003 (the only one now, back-end) from my mixed environment, actually I have one Exchange 2010 server with all the mailboxes, I have replicated public folders and OAB and List
    Address Books to it, after that i removed my front end server from my environment but when I tryed to remove my back-end, I have the error 0x80072030 (8240) when I ran the uninstallation of Exchange from Add/remove Programs:  I read
    tons of articles but anyone helps (i have removed all mailboxes from that server), my last resource is removing the last Exchange Server 2003 from my mixed (2003/2010) organization, I have read articles about to remove Exchange from one server and to remove
    Exchange from one site, also to remove Exchange to reinstall after, but my goal is remove Exchange at all because I have Exchange Server 2010 too and finally need to migrate to Exchange 2013 so I need to clean Exchange 2003 manually from my
    organizatión.
    Please somebody knows a procedure to remove Exchange Server 2003 from Active Directory and left only Exchange 2010 to be able to migrate to Exchange 2013.
    thanks in advance.
    Felxs
    Felx

    Hi,
    Let’s begin with the following similar thread:
    http://social.technet.microsoft.com/Forums/exchange/en-US/1c10c868-9b1d-43fe-afe1-d630626e2c28/exchange-2003-removal-fails-w-error-code-0x80072030-8240-there-is-no-such-object-on-the-server?forum=exchangesvrdeploylegacy
    And we can check the following possible reasons:
    1. HomeMDBBL attribute
    http://social.technet.microsoft.com/Forums/en-US/exchangesvrmigration/thread/f0e3edd7-34e5-46b8-8061-1991aaffc30f
    2.  msExchHomeServerName attribute (all pointing to Exchange 2010 server)
    3.  the "famous" postmaster issue: 
    http://support.microsoft.com/kb/283089/en-us
    We can also try to manually remove the old Exchange Server by:
    http://support.microsoft.com/kb/833396
    Thanks,
    Angela Shi
    TechNet Community Support

  • 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

  • Issue removing Exchange 2007 after migration to 2013

    After migrating relatively successfully from Exchange 2007 to 2013, I am in the process of trying to decommission and uninstall 2007 from the servers. Through this process I have been following a guide found
    here. Our old 2007 servers have been off for over two weeks and it seems like a good time to remove them and reclaim some space. I removed the old OAB and Mailbox DB, however when I attempted to remove the Public Folders so I could take the PF DB out the
    following error appeared.
    Get-PublicFolder : There is no existing PublicFolder that matches the following Identity: '\'.
    I know that there are Public Folders existing as I can see them when I run Get-PublicFolderStatistics:
    I've been back and forth across the forums and web and haven't been able to find a solution to this. Ultimately we never have and are not interested in using public folders but they were originally configured when we had a contractor move us from 2003 >
    2007 several years ago. What I would like is to remove all traces of this garbage and just be able to uninstall/delete the old servers and move on with life.
    Any help is greatly appreciated. Thank you in advance.
    Jon Howard

    Hi,
    Have you tried to use Exfolders tool to remove PF?
    More details about exfolders tool refer to the following article:
    http://gallery.technet.microsoft.com/office/Exchange-2010-SP1-ExFolders-e6bfd405
    Thanks.
    Niko Cheng
    TechNet Community Support

  • How do we remove GST / Tax from a manual order?

    Hi,
    Does anyone know how we can remove GST from a manual order?
    The tax is greyed out at 10% and can't be changed but this customer is an overseas customer that pays our Australian pricing but does not pay tax.
    Any ideas?

    Hey DandyDahlia,
    Please reach out to Support over live chat or submit a support ticket via the admin console of your site/Partner Portal > Help & Support and we'll be able to review your site and suggest what changes may be required in order to setup your shopping cart so that overseas customers do not get charged Australian tax.
    However it sounds like you will need to modify the {tag_shippingoptions} tag on your Shopping Cart layout to {tag_shippingoptions,true} in order to enable the Country selection drop down. Also ensure that the Tax Code for your products are set to 'Not Applicable'. If you implement this, then when a customer proceeds to the Shopping Cart layout, if they select Australia from the Country Drop Down, they will then need to select a tax option (i.e. GST). If they don't select Australia, then they won't need to select a tax option. Additional information on this can be found in the following article: http://helpx.adobe.com/business-catalyst/partner/displaying-shipping-options-inside-shoppi ng.html
    Cheers.

  • Removing Exchange 2007 hub server

    Hi, my company has last remaining hub 2007 server while the rest is already migrated to Hub 2010 servers. All hub servers subscribed to Edge 2007 servers. i have issue when i want to remove last hub 2007 servers with error like "This
    computer is configured as a source transport server for 1 connector(s) in the organization. These must be moved or deleted before Setup can continue". i read other post that i need to remove 'send connectors' from hub 2007. Do i need to remove
    edge subscriptions too in hub 2007 server ? If i remove send and egde subscription from hub 2007 server, is it the action will impact the hub 2010 servers ?
    2nd question, let say if i want to remove edge server, do i need to re-create send and receive connectors in hub 2010 servers?

    If you are removing edge servers, you need to configure your systems so that Internet email bypasses them (in both directions).  In answer to your #2 above, your send and receive connectors have to be configured for this
    before you remove the edge servers.  Whether you create new ones or modify existing ones for this depends on how the rest of your architecture is designed.  Once this is done, you can remove your edge subscriptions and uninstall your
    edge servers.

  • How to import PST to Exchange 2007 from Exchange 2010

    Hello everyone,
    I have a problem with importing PSTs to Exchange 2007 mailboxes.
    I exported PSTs without problem on Exchange 2010 using New-MailboxExportRequest but I run in several problems with importing PSTs on Exchange 2007.
    I created VM with Windows XP, 32bit Exchange Management tools and Outlook 2007 because it's needed for importing/exporting in Ex2007 Envinroment. I created separate account for imporing PSTs, grant him rights to Exchange server and specific mailbox but I still
    got this error while importing: Error occurred in the step: Approving object. An unknown error has occurred., error code: -2147219968 or sometimes import run without any error but no messages are imported (also it is processed very fast).
    I use Import-Mailbox -identity <user> -PSTFolderPath <Path>
    Do you know what causing this issue and how to fix it or how to import PST to Exchange using different aproach?
    Thank you

    Hi,
    Please make sure that your account has proper permissions
    Exchange Server Administrators role
    Local Administrators group for the target server
    Full access to the target mailbox
    In addition. what’s size of that PST file? If it is too large, it might be corrupted and we may need to export it again from Exchange 2010.
    Best Regards.  
    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]
    Lynn-Li
    TechNet Community Support

  • Uppgrading Exchange 2007 from sp1 to sp3 on small business server 2008 sp1

    Hello everyone
    I know this topic has been discused many time in this froum. but i have to ask it again in my exact situation. 
    I have a realy unstable and unsafe server which i am planing to migrate all the apps and services to some virtual servers soon.
    first migrating is Exchange. i have Exchange 2007 sp1 on my server sbs 2008. i have my DC,AD, dns, DHCP, File, etc on the same server as well . So that is way it is scary for me (as i am not really experienced) to even upgrade one service pack.
    Now, i want to know if anyone did it before. What should i expect during upgrading or after that? so i can be ready for that?
    which kind of backup can save me if somethings happens to my Exchange? is there any way to install the new Exchange 2007 and sp3 rollup 10 and then migrate all databases and mailboxes to that new server? if yes, how to do that?
    Thanks 
    Nima

    Hi Nima,
    Ok, I know your concern. Please make sure you have read the above KB I provided before installing SP3 for Exchange 2007. What's more, you need to make sure you right mouse click and run as admin to install it.
    Moreover, here is a thread about migrating Exchange 2007 SP3 to Exchange 2013 for your reference.
    Migrate SBS 2008 R2 running Exchange 2007 to Windows Server 2012 Exchange 2013
    http://social.technet.microsoft.com/Forums/en-US/4c9b96c2-fd5e-4fbe-8b3a-fb5b3ab29da8/migrate-sbs-2008-r2-running-exchange-2007-to-windows-server-2012-exchange-2013?forum=smallbusinessserver
    Hope it helps.
    Best regards,
    Amy Wang
    TechNet Community Support

Maybe you are looking for

  • Help with setting up active directory domain controller/DNS - need this for Clustering

    Disclaimer: I am new to Active Directory, so please dont rule out the obvious things I may have overlooked. I need to set up Active Directory Domain controller on at least one server so I can run clustering. I set up the domain controller and ran Clu

  • ABAP ECC 6.0 - Dos and Don'ts

    Dear SAP Community Network, Good Day, I would like to know what are the latest list of Dos and Don'ts in general for ABAP ECC 6.0. Please advice. I appreciate your time, help and support. Thank you and have a great day. Best Regards, Ranmit Singh Mod

  • Word to PDF not working

    Hi there, I tried to convert a Word document into a PDF with "Save as.." and then choosing PDF as the output format but it returns me the error "Unable to communicate with the printer". What can I do? Thanks FR

  • Lumea 920 needs reset after charging wireless

    I received a free Wireless charger with my Lumea 920. I put it on every night. Every time I pick it up in the morning, it doesn't respond anymore and I can only revive it by resetting it, by pushing on button and volume low button simultaneously.

  • Auto-proxy via file broken? Fix for crashing Tweetie and iTunes

    After upgrading to 10.6, Tweetie and iTunes would crash on launch. I was using a proxy.pac file to automatically set up a proxy when I'm at home (I've got Squid running on my file server). Disabling this (System Preferences > Network > Advanced > Pro