I removed a EX5.5 server but the object still shows within exchang program.


I used ex5.5 Cd to remove one of the exchange servers however, i still see the object with admin program.
Elan-NSAsked:
Who is Participating?
 
Computer101Connect With a Mentor Commented:
PAQed with points refunded (500)

Computer101
EE Admin
0
 
crawforditsCommented:
Did you make sure the ex5.5 was connected to the network when you used the cd to remove ex5.5?
0
 
Scott CSenior Systems EnginerCommented:
It's not recommended (at least by Microsoft) but you can start the admin program in "raw" mode and delete whatever you want to.

You start it by using the -r parameter when starting the admin program.

I used to be on the Premier Support Team for Exchange at Microsoft back in the day and we used this when all else failed.

I'd do some research to make sure you're willing to go this route.

It's kind of like mucking around the registry.  It can fix a lot of things but the potential for damager is there is well if you're not careful.
0
Cloud Class® Course: Microsoft Windows 7 Basic

This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.

 
IPKON_NetworksCommented:
Did you follow the MS recommended method for removing the first in site process? I assume this would be because of one of the following reasons

1. Server was first in site, so needs special process to remove cleanly
2. Was not networked and working when deleted from Exchange Admin
3. Another server has not received replication updates from the rest and still thinks it exists.

Ensure all servers have up to date replication and there is nothing queued up at all.
You will need to go onto each Exchange server (either physically or via remote desktop) and run Admin. Then, from within the server admin console, remove the 'dead' server from the list. Do this on every one in turn.
On every server in turn, rediscover routing tables to force server/site level replication

Once everything settles down, it should all look OK.

Your biggest issues will occur if the server was a first in site, or a bridgehead. This usually causes issues when trying to remove.

btw, I would try all the above before even thinking about using -r (raw) functionality. Don't go there unless you have a VERY good backup and are comfortable playing with your server, and data!

Hope this helps
Barny
0
 
Elan-NSAuthor Commented:
This was the first server and a BH server , but I did followed the microsot article and we made sure all servies has been moved to another server.
We have six different sites around the world with 20 exchange servers all togeather .  So i beleive your option number 3 is the reason for this happeneing. i beleive the other servers still has this object listed and doesn't allow it be removed.
0
 
Elan-NSAuthor Commented:
I tried to Delete the IMC connector within the raw mode and still doesn't allow me becouse can't connect to the IS of the removed server,, any suggestion here?
thanks
0
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.

All Courses

From novice to tech pro — start learning today.