You may use the following VMware PowerCLI cmdlets to view all of the snapshots managed by vCenter Server or more specifically a cluster. These are sample commands and further information and documentation may be found here.
Get-VM | Get-Snapshot | Format-List
Get-VM | Get-Snapshot | Format-List VM, Name, SizeGB, Created, Description
Get-VM -Location “CLUSTER01” | Get-Snapshot | Format-List
Get-VM -Location “CLUSTER01”| Get-Snapshot | Format-List VM, Name, SizeGB, Created, Description
You may use the Microsoft Exchange Management Shell cmdlets below to view and configure the whitelist for Microsoft Exchange Server 2016 for an entire domain or an individual email address. The whitelist contains a list of trusted domains and/or email addresses as part of the Anti-Spam feature. The domains and/or email addresses configured using these cmdlets have all email delivered irrespective of their contents. Therefore, be sure to plan and test appropriately prior to implementing it’s use in a production environment.
Get-ContentFilterConfig
Set-ContentFilterConfig -BypassedSenderDomains domain.com
Set-ContentFilterConfig -BypassedSenders [email protected]
Set-ContentFilterConfig -BypassedSenderDomains @{Remove=”gmail.com”}
Set-ContentFilterConfig -BypassedSenders @{Remove=”[email protected]”}
Microsoft has created a web based tool that will create a step-by-step checklist for a Microsoft Exchange Server deployment called the Microsoft Exchange Server Deployment Assistant. This web based tool may be found here.
The implementation of Microsoft Exchange Server 2016, like any other critical component of an Information Technology (IT) infrastructure, has prerequisites. These includes prerequisites for Microsoft Active Directory (AD) as well as the operating system.
Microsoft has provided a list of the prerequisites for Microsoft Exchange Server 2016. That documentation may be found here.
Installing Microsoft Exchange Server 2016 requires changes to the Microsoft Active Directory (AD) schema. Typically, schema changes are feared by Microsoft Active Directory (AD) engineers and administrators. However, it doesn’t need to be that way.
Microsoft has provided a list of the schema changes that are made to Active Directory (AD) in preparation for Microsoft Exchange Server 2016. That documentation may be found here.
Sizing your Microsoft Exchange infrastructure is critical to ensuring proper availability and performance. Thankfully, Microsoft provides the Exchange Server Role Requirements Calculator which may be found here. Although it states it is written for Microsoft Exchange Server 2013 this calculator may also be used for Microsoft Exchange Server 2016.
In many environments monitoring solutions are used to help facilitate availability and expected performance levels. Below is a representative list of Microsoft Exchange Server 2016 Mailbox server services that are good candidates for monitoring your Microsoft Exchange environment.
Microsoft Exchange Active Directory Topology
Microsoft Exchange DAG Management
Microsoft Exchange Diagnostics
Microsoft Exchange EdgeSync
Microsoft Exchange Frontend Transport
Microsoft Exchange Health Manager
Microsoft Exchange Information Store
Microsoft Exchange Mailbox Transport Delivery
Microsoft Exchange Mailbox Transport Submission
Microsoft Exchange Replication
Microsoft Exchange Transport
Microsoft Exchange Unified Messaging
You may use the following (2) Microsoft Windows PowerShell cmdlets to view the domain and forest functional levels of a Microsoft Active Directory domain.
Get-ADDomain | Format-List Name, DomainMode
Get-ADForest | Format-List Name, ForestMode
After installing any application it is good practice to perform post installation tasks and Microsoft Exchange Server 2016 is no exception. Below you will find a step-by-step guide for the Microsoft Exchange Server 2016 Mailbox Server role post installation tasks.
The architecture of Microsoft Exchange Server 2016 includes the Edge Transport Role server role. Below you will find a step-by-step tutorial for installing the Edge Transport Role using the command line.
