Solved

Cleaning up after a Exchange 2010 server failed - Going back to Exchange 2003 and removing all configurations made for Exchange 2010

Posted on 2010-09-14
4
623 Views
Last Modified: 2012-05-10
After a long evening last night as noted here -

(http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_26470470.html)

I need to clean up my Exchange 2003 server after the 2010 server failed. This is a different topic than the original, so I thought it should be a different question.

I removed the failed Exchange 2010 server via this method -

 "if the server is gone you'll also need to clean out active directory
use adsiedit.msc
configuration - services - microsoft exchange - exorgname - administrative groups - exchange admin group... - servers
delete the failed 2010 server from here"

However the administrative group still exists. The failed Exchange 2010 server was also solely hosting the Public Folders (during a migration).

My Questions -

1) How should I remove "Exchange Administravie Group", just delete it from the ESM?

2) Sense the Public Folders were hosted on the failed Exchange 2010, I will need to recreate them as replication had been halted for migration purposes. What is best way to go about this? When I go to do add a new Public Store I get the following Error message "All the public folders tree have been associated public store on this server. you need to create a new public folder tree before creating this new public store". Would this mean deleting the existing Public Folder Store and then recreating it?

3) Mail is flowing fine in and out of this server. However, pubic folders are not accessible from outlook or OWA. Additionally, I'm receiving the following event id

Event Type:      Error
Event Source:      MSExchangeIS Public Store
Event Category:      Logons
Event ID:      1024
Date:            9/14/2010
Time:            12:37:22 PM
User:            N/A
Computer:      SERVER
Description:
CCIC\cyuan was unable to log on as DOMAIN\USER to the Public Folder Store "First Storage Group\Public Folder Store (SERVER)".

For more information, click http://www.microsoft.com/contentredirect.asp.

This happens about 3 times a minute.

Additionally, I'm seeing this error as well -

Event Type:      Error
Event Source:      MSExchangeFBPublish
Event Category:      General
Event ID:      8197
Date:            9/14/2010
Time:            12:34:49 PM
User:            N/A
Computer:      SERVER
Description:
Error initializing session for virtual machine SERVER. The error number is 0x8004011d. Make sure Microsoft Exchange Store is running.


For more information, click http://www.microsoft.com/contentredirect.asp.

every 20 minutes.


Any assistance you could provide would be greatly appreciated!



exchange.jpg
0
Comment
Question by:futureman0
  • 2
  • 2
4 Comments
 
LVL 13

Expert Comment

by:George Sas
Comment Utility
You will first need to remove the exchange routing group connectors between the 2003 and 2010.
Then you will be able to remove the Administrative group of 2010.

Public folders , if you have a copy on your old machine just remove the replication , but as I can see your 2010 server is gone from the organisation , so you can just remove those also and create them on your 2003.
0
 

Author Comment

by:futureman0
Comment Utility
After deleting the exchange routing group from "Exchange Administrative Group" and deleting the overall routing group I see the error message in the picture. Further more once I close the ESM the routing group reappears (but the connections aren't there).
Can you think of any reason why I can't access the public folders though from Outlook or OWA? Could it be a premission problem?

exchange2.jpg
0
 
LVL 13

Accepted Solution

by:
George Sas earned 500 total points
Comment Utility
Use ADSIEDIT to clean it up.
Just don't delete the routing group from Exchange 2003 administrative group :)
0
 

Author Comment

by:futureman0
Comment Utility
using ADSIEDIT did indeed end up fixing my problems. Not only deleting "Exchange Administrative Group (FYIDIBOHF23SPDLT) removed it from the EX2003 ESM, it also got rid of my Public Folder problem (event ID 1024 every couple of seconds). Event log is finally running clear(ish)!
0

Featured Post

Top 6 Sources for Identifying Threat Actor TTPs

Understanding your enemy is essential. These six sources will help you identify the most popular threat actor tactics, techniques, and procedures (TTPs).

Join & Write a Comment

Local Continuous Replication is a cost effective and quick way of backing up Exchange server data. The following article describes the steps required to configure Local Continuous Replication. Also, the article tells you how to restore from a backup…
Marketers need statistics and metrics like everybody else needs oxygen. In this article we explain how to enable marketing campaign statistics for Microsoft Exchange mail.
In this video we show how to create an Address List in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Organization >> Ad…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…

772 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

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now