I've run into issues with not being able to mail enable legacy public folders
after migration to 2010, and it's starting to look like removing the empty
Servers container may be related to that problem.
From: Michael B. Smith [mailto:mich...@smithcons.com]
Sent: Thursday, August 05, 2010 10:52 AM
To: MS-Exchange Admin Issues
Subject: RE: Manual removal of Exchange 2003
The warnings about those objects are removed in 2010 sp1. But yes, you can
safely remove them for OLD SERVERS. You need to leave the ones for the current
server(s).
You should leave the old AG in place. You may want to remove the SERVERS node
under the old AG (which should be empty anyway) as there are (corner-case)
situations where its presence can cause issues.
Regards,
Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com
From: Paul Steele [mailto:paul.ste...@acadiau.ca]
Sent: Thursday, August 05, 2010 8:41 AM
To: MS-Exchange Admin Issues
Subject: Manual removal of Exchange 2003
Since I was unable to do a properly uninstall of our Exchange 2003 server, I
followed a Microsoft document on how to do it manually. Everything seems to be
working ok, although I'm getting a few more errors in the Exchange 2010 log
than I like to see. Two of the errors involve the SMTP objects that show up
under the Connections folder in ADSIEDIT. They have names like CN=SMTP
(EXCHANGE-{FAA12BA2-B5E7-4EC9-9B3A-7EDB53AF3AF3}). Can these be safely
deleted. I've also left the old First Administrative Group section (although
I've deleted the reference the Exchange 2003 server). One article I've read is
that it's safer to not delete the original Administrative Group just in case
anything still references it. I would rather delete it, but I definitely don't
want to break anything else.
Any further suggestions about cleaning up after manually removing an Exchange
2003 server would be appreciated!
**
Note:
The information contained in this message may be privileged and confidential
and
protected from disclosure. If the reader of this message is not the intended
recipient, or an employee or agent responsible for delivering this message to
the intended recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited. If you
have received this communication in error, please notify us immediately by
replying to the message and deleting it from your computer.
**
**
Note:
The information contained in this message may be privileged and confidential
and
protected from disclosure. If the reader of this message is not the intended
recipient, or an employee or agent responsible for delivering this message to
the intended recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited. If you
have received this communication in error, please notify us immediately by
replying to the message and deleting it from your computer.
**
