Solved

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

Posted on 2016-07-18
1
56 Views
Last Modified: 2016-07-25
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
Comment
Question by:Jerry Seinfield
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 40

Accepted Solution

by:
Adam Brown earned 500 total points
ID: 41717455
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

Creating Instructional Tutorials  

For Any Use & On Any Platform

Contextual Guidance at the moment of need helps your employees/users adopt software o& achieve even the most complex tasks instantly. Boost knowledge retention, software adoption & employee engagement with easy solution.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article explains the steps required to use the default Photos screensaver to display branding/corporate images
Did you know that more than 4 billion data records have been recorded as lost or stolen since 2013? It was a staggering number brought to our attention during last week’s ManageEngine webinar, where attendees received a comprehensive look at the ma…
This video discusses moving either the default database or any database to a new volume.
Are you ready to implement Active Directory best practices without reading 300+ pages? You're in luck. In this webinar hosted by Skyport Systems, you gain insight into Microsoft's latest comprehensive guide, with tips on the best and easiest way…

749 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