Solved

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

Posted on 2016-07-18
1
49 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
1 Comment
 
LVL 39

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

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

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

While rebooting windows server 2003 server , it's showing "active directory rebuilding indices please wait" at startup. It took a little while for this process to complete and once we logged on not all the services were started so another reboot is …
This article outlines the process to identify and resolve account lockout in an Active Directory environment.
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…

777 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