New Exchange Server 2003 replacing failed Exchange Server 2000

We had a W2K server (S1) that went down last week that was our both our Active Directory Server and our Exchange Server. We did have a separate W2K server (S2) that was also an Active Directory Server but had no Exchange Server components on it. Since that time we have "seized" all the Active Directory primary functions on S2. We have formatted a new W2K server (S3) that is now an Active Directory Server and an Exchange Server 2003. The problem we are having now is that the Active Directory account are looking for S1 the Exchange Server. We are NOT trying to move any of the old server information stores. We just want to start from brand new.

Any idea what we need to do?

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

You will have to remove all the Exchange attributes from the AD domain and the users.
Once you have done so, you can start again with Exchange 2003.

A couple of articles to look at

Manually removing Exchange 2000 (there is information on what to remove from AD)

How to completely remove Exchange from AD. It seems to mention Exchange 5.5 as well which is a bit odd.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
There are a few ways to approach this recovery, but from my experience the first thing I would do is seperate Active Directory from Exchange. Not sure how many users you have but I find you get much better performance if exchange and Active Directory are on seperate machines. This also makes recovery much easier. Since you've already experienced a failure I would suggest this to be the perfect time to start over and seperate these roles to seperate hosts.

I agree with Sembee a manual directory hack is required to remove Exchange, follow through with Microsoft's Knowledge Base article.
bbaldwinAuthor Commented:
Sorry I did not get back to you sooner. We did take Sembee's approach after much investigation on our own but I will award you both some points. Thanks for responding!!!

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.