cocosync
asked on
How to manually remove an Exchange Server that was not uninstalled.
Hi,
I'm in a big dilemma now after the procedures were improperly followed.
I didn't remove the Old domain controller, DC1 using DCpromo. and I also
didn't use uninstall from setup CD to remove first Exchange2000 Server which is also on DC1 .
I simply shut down DC1 which was running the first Exchange2000.
Yesterday, I received some instructions on manually removing the Old domain controller from AD
from another question I had posted. But I still haven't manually removed DC1 because I thought this might
avoid some problems that might come up while removing first Exchange2000 which is running on the same server.
Can the first Exchange2000 be manually removed from the Exchange system manager that is
running on the second Exchange2000 server DC2 (running AD too)?
All of the servers are W2000 Std. Ed. and I cannot bring back DC1 which was running the
first Exchange2000 online anymore because it has been recycled. The second Exchange2000 is running smoothly.
Please Help!.
Thanks.
cocosync
I'm in a big dilemma now after the procedures were improperly followed.
I didn't remove the Old domain controller, DC1 using DCpromo. and I also
didn't use uninstall from setup CD to remove first Exchange2000 Server which is also on DC1 .
I simply shut down DC1 which was running the first Exchange2000.
Yesterday, I received some instructions on manually removing the Old domain controller from AD
from another question I had posted. But I still haven't manually removed DC1 because I thought this might
avoid some problems that might come up while removing first Exchange2000 which is running on the same server.
Can the first Exchange2000 be manually removed from the Exchange system manager that is
running on the second Exchange2000 server DC2 (running AD too)?
All of the servers are W2000 Std. Ed. and I cannot bring back DC1 which was running the
first Exchange2000 online anymore because it has been recycled. The second Exchange2000 is running smoothly.
Please Help!.
Thanks.
cocosync
...and if you absolutely have to remove it from ADSIEdit, then I can provide some direction there.
Make sure that you have a good backup before you do any of this. ...once you do this you can not do a setup /disasterrecovery
Make sure that you have a good backup before you do any of this. ...once you do this you can not do a setup /disasterrecovery
ASKER
The current second Exchange2000 server is running alone without any problems
(Except seeing Free/Busy message occasionally on Outlook clients)
after the first Exchange2000 server was shutdown.
I already took care of the network side of the problem such as the Routers and the PIX.
If I understand it correctly, the KB article 260378 shows you how to remove the Exchange Server
that is still alive. These instructions will kill my one and only Exchange Server that is running now
except for the 4 line paragraph in the middle of Pg. 3. Please correct me if I'm wrong.
In my situation, is removing the first Exchange2000 Server using the Exchange System Manager
from the second Exchange2000 server sufficient enough? Please Help.
(Except seeing Free/Busy message occasionally on Outlook clients)
after the first Exchange2000 server was shutdown.
I already took care of the network side of the problem such as the Routers and the PIX.
If I understand it correctly, the KB article 260378 shows you how to remove the Exchange Server
that is still alive. These instructions will kill my one and only Exchange Server that is running now
except for the 4 line paragraph in the middle of Pg. 3. Please correct me if I'm wrong.
In my situation, is removing the first Exchange2000 Server using the Exchange System Manager
from the second Exchange2000 server sufficient enough? Please Help.
DON'T DO ANYTHING TO YOUR EXISTING SERVER!!!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Okay, having said that...
Read all of the information twice. Do not make any changes without having a full, verified, backup. Do not make any changes without a backout plan. ***Do not remove Exchange from your only Exchange server.***
Do, replicate the system folders.
Do, transfer any FSMO roles.
Do remove the old server from ESM.
Read all of the information twice. Do not make any changes without having a full, verified, backup. Do not make any changes without a backout plan. ***Do not remove Exchange from your only Exchange server.***
Do, replicate the system folders.
Do, transfer any FSMO roles.
Do remove the old server from ESM.
ASKER
I'm sorry. I meant recycled by erasing the drive array and reloading it with a new O/S for
use as a file and print server.
Everything is working great without having that first Exchange2000 Server
being around which shows that all FSMOs and GCs were transfered properly and are opeational.
Please correct me if I am wrong. From what you've seen so far, is following the
4 sentence paragraph on Pg.3 of KB260378 all I left to do?
According to it, removing this server from ESM also removes it from A.D.
I hope it doesn't sound illogical asking this.
Do you think I might still need to use AD users and computers or ntds utility to remove it?
Thank you.
use as a file and print server.
Everything is working great without having that first Exchange2000 Server
being around which shows that all FSMOs and GCs were transfered properly and are opeational.
Please correct me if I am wrong. From what you've seen so far, is following the
4 sentence paragraph on Pg.3 of KB260378 all I left to do?
According to it, removing this server from ESM also removes it from A.D.
I hope it doesn't sound illogical asking this.
Do you think I might still need to use AD users and computers or ntds utility to remove it?
Thank you.
ASKER
I forgot to mention one thing. We do not use public folders but the message
"Unable to update public Free/Busy data......" shows up occasionally. I believe
this is related to the first Exchange2000 Server. Can you show me how I could get
rid of this message?
Thank you.
"Unable to update public Free/Busy data......" shows up occasionally. I believe
this is related to the first Exchange2000 Server. Can you show me how I could get
rid of this message?
Thank you.
The free busy data is an issue noted in the links I have mentioned. You will need to add a replica of the new server to it. After that it should start to rebuild. If it does not, then you have some deeper problems.
READ through this article below, as well as the links contained in the article:
http://support.microsoft.com/kb/275171
You may be able to add just the replica, but you may have to rebuild the System folder for the free/busy information.
Yes, you should also remove the old server. Since it is a DC then you will have to clean the DC object out of metadata.
That is a topic outside of the Exchange TA.
http://www.petri.co.il/fix_unsuccessful_demotion.htm
https://www.experts-exchange.com/Operating_Systems/Windows_Server_2003/
READ through this article below, as well as the links contained in the article:
http://support.microsoft.com/kb/275171
You may be able to add just the replica, but you may have to rebuild the System folder for the free/busy information.
Yes, you should also remove the old server. Since it is a DC then you will have to clean the DC object out of metadata.
That is a topic outside of the Exchange TA.
http://www.petri.co.il/fix_unsuccessful_demotion.htm
https://www.experts-exchange.com/Operating_Systems/Windows_Server_2003/
The problem that you are going to run into is that, if it was the first system, you are going to have to rehome some of your public folders, your OAB, and possibly change your firewall rules to route mail to the server which is up.
This is for Exchange 2003, but the principles are the same.
http://support.microsoft.com/kb/822931