Solved

old exchange 200 still in AD

Posted on 2013-11-12
7
375 Views
Last Modified: 2013-11-13
Hi,

I am in the process of going from exchange 2003 to exchange 2010 (then 2013) but my AD still has an Exchange 2000 in it, even when you look in exchange system management on the 2003 box you can see an entry for the Exchange 2000.

The exchange 2000 server does not physically (or virtually) exist but it is still a computer in AD.

How can I safely remove all traces of this exchange 2000 server? I assume I cant just delete it from AD and thats it.
0
Comment
Question by:Carpe--Diem
[X]
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
  • 3
  • 3
7 Comments
 
LVL 14

Expert Comment

by:Raj-GT
ID: 39641749
You can remove Exchange 200 from AD by following the instructions here - http://support.microsoft.com/kb/273478
0
 
LVL 35

Expert Comment

by:Seth Simmons
ID: 39642035
that kb article doesn't apply
it refers to manually removing services and registry entries which of course you can't do since you stated the server no longer exists

you need to remove from AD manually using ADSI Edit

open ADSI Edit then right click ADSI Edit on the left and select connect to
under 'select a well known naming context' choose configuration then ok

expand CN=Configuration then CN=Services
then CN=Microsoft Exchange and CN=<your org name>
then CN=Administrative Groups then CN=<exchange admin group> and finally CN=Servers
under that you should see your 2000 and 2003 servers
right click on the 2000 server object and delete it

you can also delete the computer account from AD though the steps above will remove from the Org and won't show in ESM and won't cause an issues when you move to 2013
0
 
LVL 14

Expert Comment

by:Raj-GT
ID: 39642082
The article linked doesn't talk about manually removing the services and registry entries it says how you can remove an Exchange 2000 organisation from AD by running update.exe /removeorg from Exchange 2000 SP2 media. It's more or less doing what you are suggesting without using ADSI Edit.
0
Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

 
LVL 35

Expert Comment

by:Seth Simmons
ID: 39642135
the beginning of that article clearly states:

Note This procedure will completely remove all instances of Microsoft Exchange 2000 Server and of Microsoft Exchange Server 2003 from Active Directory.

the objective here is to remove the server, not the entire exchange organization

if that were executed here the user would have a non-functioning 2003 server

Important Do not use the removeorg option unless you intend to remove Exchange completely from your organization.

Important Make sure that there are no Exchange 2000 mailboxes, Exchange 2003 mailboxes, or any other functionality being used on Exchange before you run the removeorg option.

http://support.microsoft.com/kb/830185
0
 
LVL 14

Expert Comment

by:Raj-GT
ID: 39642162
My bad - apologies. Since you already have other Exchange servers in your Org, using ADSI Edit is the safest option.
0
 
LVL 24

Accepted Solution

by:
Sandeshdubey earned 500 total points
ID: 39643565
0
 
LVL 35

Expert Comment

by:Seth Simmons
ID: 39643601
that first link has additional references that assume the server is still online by moving components elsewhere or details on removing exchange attributes from user accounts

the second link applies to exchange 2007 and assumes the 2000 (or 2003) server is still physically present
0

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

After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
A couple of months ago we ran into an issue that necessitated re-creating our Edge Subscriptions. However, when we attempted to execute the command: New-EdgeSubscription -filename C:\NewEdgeSub_01.xml we received an error indicating that the LDAP se…
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
Suggested Courses

622 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