E2K3 to E2K7
E2K7 SP2 / W2K8 SP2 Co-existence Multi-Domain I have not been able to go to E2K7 Native mode because of old application dependencies. But, I have been decommissioning old E2K3 servers. Now I need to decommission a E2K3 bridgehead server which is also the only server within an E2K3 Administrative. My system public folders are all set (don't have any user public folders) and I am slowing pulling down the connectors. (I know which each connector is used for because I built them.) This E2K3 bridgehead is not the last E2K3 server to be removed. My question is when I bring this E2K3 server down should I leave the E2K3 Administrative group up within Exchange System Manager? or should I wait until I decommission, the last E2K3 server? thanks
March 29th, 2012 4:16pm

By leaving up, so you mean "not deleting it"? Even after all the 2003 servers are gone, I would recommend that you do not delete any Admin groups in AD. This could cause issues for mailboxes that still reference a legacy admin group in their legacyExchangeDN. No one will see those Admin groups using the 2007 or 2010 tools anyway. Remove the Last Legacy Exchange Server from an Exchange 2010 Organization
Free Windows Admin Tool Kit Click here and download it now
March 29th, 2012 4:26pm

Agreed - please leave the admin groups alone. if you do not correctly move over the PF hierarchy to the new E2010 admin group, you can case the PF database to not mount. I am referring to the steps where the PF hierarchy is dragged over to the 2010 Admin group by using the Exchange 2003 system manager. Cheers, Rhoderick
March 29th, 2012 5:53pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics