Microsoft Exchange Server 2016

Email remains mission-critical, and on-premises Exchange 2016 environments fail in predictable places: undersized or poorly architected storage, mailbox databases with no replicated copies, and recovery procedures no one has ever practiced. When those gaps surface in production, the result is outages, escalations, and reliance on outside contractors.

Role fit: This administrator-level course suits IT Practitioners and system administrators who run or inherit Exchange 2016, including newer team members with no prior Exchange experience. Team Leads can also use it to standardize how the team handles mailbox databases.

Time investment: About 5.4 hours across six skills. Assign the storage-planning and high availability skills first for staff who own uptime, then the monitoring, troubleshooting, backup, and recovery skill for on-call rotations.

Risk and resilience: The training covers storage validation with JetStress, identifying failure domains, replicating databases in a Database Availability Group (DAG), and testing site recovery switchovers. The instructors stress practicing restores before they're needed, which supports documented, repeatable recovery procedures.

Change-management note: The course weighs design considerations for DAGs with Azure members, including file share witness placement and routing mail through Exchange Online Protection. This helps IT Directors test before committing to a production design.

Learners can build an optional Azure practice lab to rehearse database moves, mounts, and failovers away from production. Training Managers can group these skills into Playlists and use Team Reporting to track progress.

Email remains mission-critical for every organization, and mailbox database failures can turn routine maintenance into business-wide outages. IT teams complete this training to plan Exchange Server 2016 mailbox databases correctly, choose appropriate storage, size databases for growth and performance, and rehearse procedures in a lab before touching production.

In practice, your team will work through scenarios like using the Exchange Server Role Requirements Calculator to plan database size, storage needs, and virtualization requirements. They’ll also see why improved Exchange 2016 IOPS efficiency does not remove the need for careful storage planning, fixed-memory virtualization decisions, and database sizing that accounts for future growth.

• Fewer storage-driven outages: Admins plan storage types, size mailbox databases appropriately, and use Exchange planning tools before production decisions are locked in.
• High availability planning that matches the environment: Teams account for database placement, failure domains, and resiliency requirements instead of assuming the default design is production-ready.
• Risk-based resilience planning: Admins identify which risks should be engineered out and which need a documented recovery plan that fits organizational requirements.
• Faster troubleshooting: Teams connect performance and recovery issues back to the planning decisions that often cause them, including storage selection, database sizing, and virtualization configuration.

An optional, scripted Azure lab gives admins a safe place to install and test Exchange 2016 procedures without touching production.

Knowledge

• Why Exchange 2016 mailbox database storage planning goes beyond disk size: local vs. SAN-attached storage, architecture choices, and their impact on high availability and disaster recovery
• How JetStress simulates production workloads to validate storage, and why most JetStress failures point to the underlying storage architecture rather than the tool
• How to identify failure domains and weigh which risks to engineer out versus cover with a recovery plan, based on budget and deployment
• How database availability groups (DAGs) work, including that database replication to member servers is a manual, per-database configuration
• The caveats of placing DAG members in Azure: premium storage requirements, low-latency connectivity needs, and replication traffic load
• Key factors behind database copy activation behavior, including activation preference and the settings that influence which DAG member hosts an active mailbox database copy

Ability

• Use the Exchange Deployment Assistant as a deployment planning tool and checklist
• Create and configure mailbox databases in the Exchange Admin Center (/ecp) and with PowerShell
• Manage databases with Move-DatabasePath, Set-MailboxDatabase, Mount-Database, and Dismount-Database
• Build a DAG, replicate mailbox databases across members, and run a test site recovery switchover
• Troubleshoot replication issues such as high copy queue lengths caused by limited bandwidth or long-offline copies
• Build a Performance Monitor baseline for proactive database performance monitoring instead of reacting to failures