Expiring Today—Celebrate National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17


Remove all Exchange data from AD and user accounts then re-install with fresh exchange Org

Posted on 2014-03-17
Medium Priority
Last Modified: 2014-04-02
HI All

I need to remove all data from AD relating to the Exchange 2010 org and then re-create as new.

Background Info...We have a single forest / domain running on Windows 2008R2 dcs although the DFL / FFL are both Windows 2003 server.

Recently I powered off one of our DC's that was a VM and stuck it in an isolated Test environment at the request of the management as they wanted to test Integration between our HR system and AD. I seized all the FSMO roles and manually cleaned up AD / DNS of all the DC's and sites not in use in the test lab so i was left with a single DC that was in a healthy state, i then renamed the domain from abc.com to testabc.com

All is good so far, everything looks healthy from a logs perspective and dcdiag etc

Now that has finished they have thrown me  curve ball i was not expecting and requested Exchange be added to the test LAB. In prod we have 4 CAS / HT servers and 3 mailbox servers in a DAG so i do not want to P2V those into the LAB.

My preference would be to remove all exchange data from AD in test lab and all the attributes from user accounts and then install a fresh Install of exchange in a new Org and then re create blank mailboxes.

Anyone help me on how to go about this.

Question by:ncomper
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
LVL 37

Expert Comment

ID: 39936207
P2V or simply dragging production exchange servers into test lab won't work because you have renamed your domain

When you renamed domain, your Exchange has braked at that moment
Also even if you wipe out Exchange attributes from user properties and cleanup exchange setup from adsiedit.msc, your schema is already upgraded to work with Exchange and that changes can't be undone

At a maximum you can try by removing Exchange completely through adsiedit.msc\configuration container\service container
Then try to reinstall MS Exchange again, then delete all Exchange attributes from users and groups through Exchange EMC
The best way to deal with your situation I can see:
Prepare new domain as same name as your production domain \ the name whichever you want in isolated network
Modify AD schema with MS Exchange setup
Install brand new Exchange ORG
create required test users, groups OU structure for testing
setup application integration \ whatever testing you want
Once done replicate the changes to production environment

LVL 12

Expert Comment

by:Md. Mojahid
ID: 39936272
If you have setup new AD that is good to fresh exchange installation although you can install on same add after remove old exchange server complete information from Remove (legacy) Exchange server using ADSIEdit.
LVL 26

Expert Comment

by:Leon Fester
ID: 39937157
Do you also have a lab version of the HR software?

The best options to properly replicate the environments for simulation testing is to use the same domains.

This means isolating your LAB Domain, LAB Exchange and LAB HR system onto a single switch that is not connect to your production network.

In this scenario, you do the AD clean-up tasks as done previously and then run Exchange installation with the recoverserver options. It will read from AD and rebuild your first Exchange Server. I've not tried the Exchange disaster recover installation on a renamed domain, but it's an option you could try.
You can recover a lost server by using the Setup /m:RecoverServer switch in Microsoft Exchange Server 2010. Most of the settings for a computer running Exchange 2010 are stored in Active Directory. The /m:RecoverServer switch rebuilds an Exchange server with the same name by using the settings and other information stored in Active Directory.

Recovering a lost Exchange server is often accomplished by using new hardware. However, you can also use an existing server.

This topic shows you how to recover a lost Exchange 2010 server that isn't a member of a database availability group (DAG). For detailed steps about how to recover a server that was a member of a DAG, see Recover a Database Availability Group Member Server.


By rebuilding all the servers entirely you're actually not replicating your environment and other issue could appear when you try your integration.
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

LVL 27

Accepted Solution

Steve earned 2000 total points
ID: 39937506
You're in a difficult position as it's all a bit complicated.

Firstly, it's true that you cannot P2V your exchange to add it to your lab as you have changed the domain name. Exchange cannot handle that so that option is out.
Secondly, the proper way to remove exchange attributes is part of exchange, so you cannot do this safely without the exchange server(s)
Lastly, wiping exchange and reinstalling may not be a very good replica of your existing system, so be aware that your testing of the new HR system may not reveal all the issues that your real system may experience.

Sack off your existing Lab and create it again including one of the exchange boxes. You may be able to get away without P2Ving them all but it can be a pain with so many. (this would mean you cannot amend the domain name though.

Remove the exchange system manually. The organisation can be removed using ADSIedit and the attributes can be removed using 3rd party tools. Hou can then reinstall exchange from scratch (take care with these options as messing with AD can screw your domain completely)

Sack off the existing lab and create a new one from scratch (wont be a proper version of your existing system so may not really serve as a suitable testbed.)

Remote attribute tool:

remove exchange organisation:
LVL 37

Expert Comment

ID: 39937563
Even if you replicate your environment in lab, you cannot guarantee that you will not face any issues in production

The lab is after all test lab and production setup is production setup and the scale of both setup have drastic difference

The Idea of test lab is to check basic functionality and to build confidence

Author Closing Comment

ID: 39971864
Thanks, ill try that tool

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This process allows computer passwords to be managed and secured without using LAPS. This is an improvement on an existing process, enhanced to store password encrypted, instead of clear-text files within SQL
New style of hardware planning for Microsoft Exchange server.
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
Suggested Courses

719 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question