Exchange Center

The Exchange 2013 Server Role Requirement Calculator is a one stop calculation tool for Exchange 2013 design. The tool covers design calculations for both the Mailbox and Client Access server role. Exchange 2013 reduced the number of roles from previous versions of Exchange by making the design and implementation as simple as possible. The Server Role Requirement Calculator helps us to size both physically and virtually and it provides in-depth sizing of every component of the hardware like CPU, Memory, Network, Storage, Backup, servers, datacenter etc.

On March 2, 2021 Microsoft released a number of critical security updates for Exchange. These are not just a number of new Security Updates, but these are Security Updates for a zero-day vulnerability and as such rated as ‘critical’.

Built-in tools for CAS Monitoring in Exchange 2016/2019

With some small and medium size businesses unable to afford larger, enterprise solutions for Exchange monitoring, we will explore the local tools built into Exchange to help you leverage Exchange CAS monitoring from within the Exchange program itself. This article is meant as an overview detailing the built-in tools available and may require more independent reading and learning before making any changes to your organization’s solution.

Microsoft Exchange Server 2013 has a very different server role architecture than its previous versions. Exchange 2007 and 2010 had 5 server roles: the Mailbox Server role, Client Access role, Hub Transport role, Edge Transport role, and the Unified Messaging role. That is a lot of roles to need to backup. However, Exchange 2013 has greatly reduced the number of server roles down to two: the Mailbox Server Role and the Client Access Server role. All of the other roles, except the edge transport role which is run on a standalone , have been combined within those two roles. When it comes to backing up and restoring Exchange 2013 this makes Exchange Monitoring much easier for administrators.

Many companies have good reasons to keep their messaging infrastructure on-premises. Exchange 2016 is currently the second latest version of Exchange Server for on-premises deployments.  Common reasons to upgrade Exchange include adding new functionality, such as high availability, moving from an unreliable or insecure system, and moving to a version that Microsoft still supports.

Exchange Server has two core components. First, there is the mailbox component, with all the required client access protocols and well-known mailbox functions. The second major component is the message flow, with receiving, processing, and sending email messages.

Disk space is vital to the health of an Exchange Server. Without disk, you don’t have email, thus Exchange monitoring - disk space is vital. Exchange is dependent on having disk because every time an email is sent it’s written to disk, without it you’re S.O.L.

Now that you’ve finished Part I and Part II of my three-part Managed Availability blog series, I will now provide some information about local .xml monitoring files and overrides of Managed Availability.

How to check, recover, and maintain your Exchange organization

Now that you’ve finished Part I of my three part Managed Availability blog series, I will now go a bit deeper and provide some examples about the functionality and operability of Managed Availability. My virtual test lab contains a two-member DAG based on Windows Server 2012 and Exchange 2013 CU6.

An Exchange Administrator's Task?

Microsoft introduced a new built-in exchange monitoring system called Managed Availability in Exchange 2013, which automatically takes recovery actions for unhealthy services within the Exchange organization.