Decommissioning 2003 Exchange server that's been offline for almost 3 years

We have three Exchange 2003 SP2 servers. Two are back end one is a front end. Almost three years ago, we had only a front end and back end server. Our office was moving so we brought a third server online to deliver mail to the new location as we moved. Once that was completed, we turned the server off.

During the time it's been off we've upgraded our domain from W2K to W2K8.

Now we are ready to move to Exchange 2007. My question is this, can we turn on the dormant Exchange 2003 server, have it touch the network and after a couple of hours attempt to un-install Exchange from it? Seems it would be better to attempt a graceful un-install rather than rip it out of AD.

However I wanted to see if others have had to make this choice and if there are any potential "gotchas" to having the old server back online.

Thanks in advance.
lucado01Asked:
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.

rakeshmiglaniCommented:
if there is nothing in the old server, and you plan to format it, why do you want to waste time in unstalling exchange from it.
just remove it from adsiedit.msc
path is
open adsiedit.msc
expand configuration
expand services
expand microsoft exchange
expand the exchange org
expand administrative groups
expand your administrative group
expand servers

over here you would see the servers listed
delete the one that is not required.
0
XCHExpertCommented:
You can choose alternate way of gracefull uninstallation by removing exchange manually.
http://support.microsoft.com/kb/833396
0
lucado01Author Commented:
rakeshmiglani,

Fair enough. I failed to mention that there is a legacy routing group that this server is a part of and that one existing Public calendar on the production server was synced with the old server before it went offline.

OK to use adsiedit anyway?

Thanks for the prompt reply.
0
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

rakeshmiglaniCommented:
from the properties of the public folder calendar, remove the old server as the replication partner.
is the new server also a part of the routing group?
0
lucado01Author Commented:
The current 2003 server is part of the routing group connector that the old server is in.

Sorry, I said routing group when I meant routing group connector.
0
rakeshmiglaniCommented:
remove the old server from connector. should not cause any problems as the new server is also a member and everything is working fine when the old server is down.
any messages in the queues for the old server?
0
lucado01Author Commented:
Probably not but will verify that first.
0
lucado01Author Commented:
rakeshmiglani,

It will take a little time for me to get that server back online. Assuming there are no messages, do you still recommend removing the old server from ADSI Edit?

Even if that's the best solution, would it be "safe" to perform an un-install from the old server, just more time consuming and unnecessary?

If the answer is yes to both I will award you the points and close the issue.
0
ChiefITCommented:
I have a linux based mail server, now, so correct me if I am wrong.

Doesn't Exchange use AD for its LDAP? So, wont it have to be demoted out of the domain as well?

Looking at it from an AD point of view, it's been over the 30 day replication period and this server is a tombstoned DC, right? So, I think you will have to perform a metadata cleanup.
0
lucado01Author Commented:
Sorry, didn't provide that detail.

Old server in question is a member server, not a DC.
0
rakeshmiglaniCommented:
well, If everything is working fine and I need to remove an old server that has been down for quite some time,  don't uninstall, i just remove it from adsiedit.
uninstall is also an option and you can use that.

i recommended adsiedit.msc path just to save time.
recommended is to uninstall gracefully.

and to remove the server from adsiedit.msc, you don't need to turn on the old box as you can open adsiedit.msc from any server that has the windows support tools installed.
0

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

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.