Removing an Exchange 2003 Server

I have an exchange server that I need to remove from my environment.  It is running Exchange 2003 SP 2, and is not the first Exchange Server.  I have re-homed and/or deleted all user mailboxes on the server but when I beging the add/remove procedure it errors out telling me that there are one or more users with a mailbox still on this server.  I have one Storage Group, with one Information Store on this server.  In the Information Store I have the standard SMTP and System Attendant boxes under the Mailboxes folder, but there is also a SystemMailbox with what looks like a SID entry after it.  Right clicking on the store and choosing delete throws error c1034a7f telling me that I have a mailbox in the store.  Right clicking on the object itself gives me a greyed out "all tasks" menu.  Locating the object in AD, right clicking and choosing Exchange Tasks gives me a menu with a blank box where the exchange tasks would normall be.  I have researched this in microsofts knowledge base and have the insructions for removing the msexchhomeserver from adsiedit.msc but the KB states that you do not need to remove SystemMailboxes in order to remove Exchange.  My question is this.  If I remove the msexchhomeserver attrubute via ADSIEDIT.MSC will I cause any undo pain to my AD environment, or my other Exchange servers?  My assumption is that it won't but I wanted to reach out to the Experts here to see if there is a better way to remove, if what I am doing is correct, and if anyone has had a similar experiance.  I should also note, that this server is not part of any routing groups, it has no public folder replica that it is hosting.  It currently has a function-less existance.  Any help or insight would be greatly appreciated.    Screenshots are attached.
2.JPG
1.JPG
mmazahrehAsked:
Who is Participating?
 
wfcraven12Commented:
That sucks.

First go to Microsoft Exchange System Objects OU in the AD users
and computers, & remove the system mailbox {GUID} WITH the CNF:198904dc..... behind it


* Force the domain controller replication in the local site and run
cleanup agent on the exchange system manager. If you see the second system
mailbox disconnected. Right click it and purged it.

0
 
CompanionCubeCommented:
Notes from my last E2K3 cleanup:

Removed old SGs
Removed old Stores
Removed old Routing Groups
Removed RUS
Used adsiedit to kill off old exch objects...
"How to Remove the Last Legacy Exchange Server from an Organization"
http://technet.microsoft.com/en-us/library/bb288905.aspx


Had to find users in AD which thought they still had an Exchange Home on the old E2K3 server.
  ADUC, find, Advanced, Field, User, exchange home server, ends with, <exch servr name>
  They were old ref.s to service accounts

Nuked the old Exch servers
  Add/Remove Programs, remove Exchange
  Disjoined the servers from the domain
0
 
mmazahrehAuthor Commented:
Right, that is the process that I am trying to follow however I cannot remove the store in order to remove the SG.I have located the Object in ADUC that believes it is still resident on the exchange server and have verified that in ADSIEDIT that the msexchhomeserver attrubute for that object indeed says that it is on that server however my concern is if I delete out that attribute will it have a negative effect on my production exchange environment?  My sense says no, but the KB article that I have from MS says that you don't do this with SystemMailbox objects.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
CompanionCubeCommented:
Ensure you always have a backup of your AD environment...!
The last time I ran into this I just deleted the user accout/resource account which thought it still had a mailbox on the store. We just ended up recreating the user/resource account object.
0
 
wfcraven12Commented:
Ran into this problem earlier in the year.  Such a pain.  I found the below article & all was well in Exchangeworld.

http://exchangeserverinfo.com/2009/09/08/error-c1034a7f--unable-to-delete-mailbox-store.aspx

Hope this helps
0
 
mmazahrehAuthor Commented:
wfCraven12 I ran thru the steps in the link that you posted.  The results I got are in the attached screenshot.

The last line in the link you posted is the following:
NOTE: SystemMailbox, SMTP Mailbox & System Attendant are the Exchange Special mailboxes and should not be consider for moving.

Coincidentally they are the 2 mailboxes that are still there.  Ugh.....
3.JPG
0
 
mmazahrehAuthor Commented:
remove the object itself or try to remove the mailbox thru exchange tasks?  Exchange task wizard shows no options for mailbox removal so I am assuming that I need to remove the actual object out of AD correct?
0
 
wfcraven12Commented:
Through Active Directory

Then go to AD Sites & Services to Replicate

Then go to ESM.  the SystemMailbox should show as disconnected.
0
 
CompanionCubeCommented:
Last time I had to do this I had to remove the object from AD. At the end of the day, it allowed me to decommission the E2K3 server, and no one was effected.
0
 
mmazahrehAuthor Commented:
The oject in question has sat disabled in the Microsoft Exchange System Objects container in AD since Dec 24th.  Today is the 28th.  My event logs look clear (as in no reliance on the disabled object) so I think I am clear to delete the object.  I am going to do that and come back here and award points accordingly.
0
 
wfcraven12Commented:
Good luck.
0
 
mmazahrehAuthor Commented:
OK, tried deleting the Object with CNF after the GUID name.  Won't delete.  Gives me an error  Tried moving it to Lost and Found.  Same deal.  Same error only the word delete has been replaced by move.  Screenshot attached.
4.JPG
0
 
mmazahrehAuthor Commented:
That did it.  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.