• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 76
  • Last Modified:

Exchange 2010 hybrid organization, service impact after removing dedicated AD site for Exchange

Hi Experts,

My customer runs a Windows 2008 Forest/domain functional level with a single forest/domain, and following infrastructure:

•Multiple AD sites to represent physical locations
•A dedicated AD site with 4 DC/GC for the use exclusive of Exchange
•An Exchange 2010 hybrid org, with multiple HT/ MBX servers in a DAG.
•A hybrid connector to O365
•An internal ADFS farm of servers and WAP in the DMZ

The original plan was, to upgrade the Exchange 2010 hybrid deployment to Exchange 2013 hybrid deployment, and the plan was to setup a new DAG with new MB servers, and multiple CAS to handle mailflow, but for some reason my client is running into some challenges, and they decided to keep the exchange 2010 hybrid organization.

However, the AD team, is planning to decommission the Messaging site[dedicated to Exchange], and just wonder about possible service impact at Exchange level.

Could you please indicate all possible spots to review and prevent major issues before the decommission of the AD messaging site? Please, indicate what needs to be modified at the Exchange organization, and AD settings

Please, provide step by step instructions with screenshots to your plan of action.

Please, elaborate about service impact of decommission AD messaging site[ Active directory and Messaging service impact]
0
Jerry Seinfield
Asked:
Jerry Seinfield
1 Solution
 
Adam BrownSr Solutions ArchitectCommented:
If it's just a site in AD Sites and Services, you only need to make sure the subnets of your Exchange servers are properly assigned to a new site, preferably whichever site matches the physical location of the Exchange servers. If all of your Exchange servers are in the same AD site, you'll see no impact by moving the subnet for that AD site to another AD site, since the AD Site structure is only used to provide routing data for Exchange environments with servers in multiple AD sites. If all Exchange servers are in the same AD site, they will communicate directly with whichever other servers they need to.

Aside from that, when you're moving from 2010 to 2013, I would highly recommend that you avoid splitting your roles up. Starting with Exchange 2013, it makes no sense whatsoever to have the CAS role on a different server than the MBX role. This is why the role separation was abandoned in Exchange 2016.
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now