Internet of Things IoT. Enabling Remote Work. Small and Medium Business. Humans of IT. Green Tech. MVP Award Program. Video Hub Azure. Microsoft Business. Microsoft Enterprise. Browse All Community Hubs. Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for. Show only Search instead for. Microsoft Exchange Server Service Pack 1 and later versions are supported.
For information about how to deploy Microsoft Exchange Server in a virtualized environment, see Understanding Exchange Virtualization. For information about how to deploy Microsoft Exchange Server in a virtualized environment, see Exchange virtualization. Microsoft ISA Server is supported.
The virtual machine for Microsoft Office Groove Server Relay should be configured to use a physical hard disk, not a virtual hard disk. Windows SharePoint Services 3. Microsoft Operations Manager Service Pack 1 agents only is supported. System Center Operations Manager or a later version is required to manage Windows Server and later versions.
Configuration Manager, current branch, is supported. System Center Configuration Manager Service Pack 1 both server and agents and later versions are supported. Microsoft Systems Center Data Protection Manager is supported when it runs inside a virtual machine, but only if the DPM storage pool disks are made available directly to the DPM virtual machine as one of the following:. You can also perform backups for the virtual machines either by using a DPM agent that is installed on the host computer or by installing the DPM agent into the virtual machine directly.
Microsoft System Center Operations Manager both server and agents and later versions are supported. Microsoft System Center Virtual Machine Manager both server and agents and later versions are supported. Microsoft System Center Service Manager and later versions are supported. Office Online is supported. For more information, see Office Online. Pass-through storage is storage that's configured at the host level and dedicated to one guest machine.
All storage used by an Exchange guest machine for storage of Exchange data must be block-level storage because Exchange doesn't support the use of network attached storage NAS volumes, other than in the SMB 3. Also, NAS storage that's presented to the guest as block-level storage via the hypervisor isn't supported. The only supported usage of SMB 3. Such file shares can't be used for direct storage of Exchange data. When using SMB 3. Storage used by Exchange should be hosted in disk spindles that are separate from the storage that's hosting the guest virtual machine's operating system.
However, there is reduced performance in this configuration if the network stack inside a virtual machine isn't full-featured for example, not all virtual network stacks support jumbo frames.
This technology makes sense for workloads in which memory is needed for brief periods of time and then can be surrendered for other uses. However, it doesn't make sense for workloads that are designed to use memory on an ongoing basis. Exchange like many server applications with optimizations for performance that involve caching of data in memory is susceptible to poor system performance and an unacceptable client experience if it doesn't have full control over the memory allocated to the physical or virtual machine on which it's running.
As a result, using dynamic memory or memory overcommit features for Exchange isn't supported. The following are answers to some frequently asked questions about host-based failover clustering and migration technology with Exchange DAGs:.
Microsoft can't make support statements for the integration of third-party hypervisor products using these technologies with Exchange, because these technologies aren't part of the Server Virtualization Validation Program SVVP. You need to ensure that your hypervisor vendor supports the combination of their migration and clustering technology with Exchange.
If your hypervisor vendor supports their migration technology with Exchange, Microsoft supports Exchange with their migration technology. Host-based failover clustering refers to any technology that provides the automatic ability to react to host-level failures and start affected virtual machines on alternate servers. Use of this technology is supported given that, in a failure scenario, the virtual machine is coming up from a cold boot on the alternate host.
This technology helps to make sure that the virtual machine never comes up from a saved state that's persisted on disk because it will be stale relative to the rest of the DAG members. Migration technology refers to any technology that allows a planned move of a virtual machine from one host machine to another host machine. This move could also be an automated move that occurs as part of resource load balancing, but it isn't related to a failure in the system. Migrations are supported as long as the virtual machines never come up from a saved state that's persisted on disk.
This means that technology that moves a virtual machine by transporting the state and virtual machine memory over the network with no perceived downtime is supported for use with Exchange. A third-party hypervisor vendor must provide support for the migration technology, while Microsoft provides support for Exchange when used in this configuration.
Skip to main content. This browser is no longer supported. Download Microsoft Edge More info.
0コメント