Best Practices Analyzer for Hyper-V: Configuration
Updated: April 27, 2010
Applies To: Windows Server 2008 R2, Windows Server 2012
The topics in this section can help you bring Hyper-V that is running on Windows Server 2012 or Windows Server 2008 R2 into compliance with configuration best practices. Content in this section is most valuable to administrators who have completed a Best Practices Analyzer scan of Hyper-V and who want information about how to interpret and resolve scan results that identify areas of Hyper-V that are noncompliant with configuration best practices.
The Best Practices Analyzer applies configuration rules to identify settings that might require modification for Hyper-V to perform optimally. Configuration rules can help prevent setting conflicts that can result in error messages or prevent Hyper-V from carrying out its prescribed duties in an enterprise.
For more information about Best Practices Analyzer and scans, see Best Practices Analyzer (http://go.microsoft.com/fwlink/?LinkId=122786).
-
Hyper-V: The Hyper-V Virtual Machine Management service should be configured to start automatically
-
Hyper-V: The Hyper-V Networking Management service should be configured to start automatically
-
Hyper-V: The Hyper-V Image Management service should be configured to start automatically
-
Hyper-V: Hyper-V should be the only enabled role
-
Hyper-V: The Server Core installation option is recommended for servers running Hyper-V
-
Hyper-V: Domain membership is recommended for servers running Hyper-V
-
Hyper-V: The number of logical processors in use must not exceed the supported maximum
-
Hyper-V: The number of virtual processors in use must not exceed the supported maximum
-
Hyper-V: More than one network adapter should be available
-
Hyper-V: Reserve one or more external virtual networks for exclusive use by virtual machines
-
Hyper-V: All virtual network adapters should be enabled
-
Hyper-V: The number of virtual machines must be within supported limits
-
Hyper-V: Use RAM that provides error correction
-
Hyper-V: Configure the server with a sufficient amount of dynamic MAC addresses
-
Hyper-V: Avoid pausing a virtual machine
-
Hyper-V: Offer all available integration services to virtual machines
-
Hyper-V: Enable all virtual network adapters configured for a virtual machine
-
Hyper-V: Storage controllers should be enabled in virtual machines to provide access to attached storage
-
Hyper-V: Display adapters should be enabled in virtual machines to provide video capabilities
-
Hyper-V: Run the current version of integration services in all guest operating systems
-
Hyper-V: Enable all integration services in virtual machines
-
Hyper-V: Configure virtual machines running Windows 2000 Server with 1 virtual processor
-
Hyper-V: Configure virtual machines running Windows XP Professional SP2 (x86) with 1 virtual processor
-
Hyper-V: Configure virtual machines running Windows XP Professional SP2 (x64) with 1 or 2 virtual processors
-
Hyper-V: Configure virtual machines running Windows XP Professional SP3 (x86) with 1 or 2 virtual processors
-
Hyper-V: Configure virtual machines running Windows Server 2003 with 1 or 2 virtual processors
-
Hyper-V: Configure virtual machines running Windows Vista with 1 or 2 virtual processors
-
Hyper-V: Avoid using a legacy network adapter on Windows Server 2003 (x64) and Windows XP Professional (x64)
-
Hyper-V: Avoid using legacy network adapters when the guest operating system supports network adapters
-
Hyper-V: Dynamic virtual hard disks are not recommended for virtual machines that run server workloads in a production environment
-
Hyper-V: Avoid using differencing disks on virtual machines that run server workloads in a production environment
-
Hyper-V: Configure a virtual machine with a SCSI controller to be able to hot plug and hot unplug storage
-
Hyper-V: Configure SCSI controllers only when supported by the guest operating system
-
Hyper-V: Windows 2000 Server should be configured with at least the minimum amount of memory
-
Hyper-V: Windows 2000 Server should be configured with the recommended amount of memory
-
Hyper-V: Windows XP should be configured with at least the minimum amount of memory
-
Hyper-V: Windows XP should be configured with the recommended amount of memory
-
Hyper-V: Windows Server 2003 should be configured with at least the minimum amount of memory
-
Hyper-V: Windows Server 2003 should be configured with the recommended amount of memory
-
Hyper-V: Windows Vista should be configured with at least the minimum amount of memory
-
Hyper-V: Windows Vista should be configured with the recommended amount of memory
-
Hyper-V: Windows Server 2008 should be configured with at least the minimum amount of memory
-
Hyper-V: Windows Server 2008 should be configured with the recommended amount of memory
-
Hyper-V: Windows 7 should be configured with at least the minimum amount of memory
-
Hyper-V: Windows 7 should be configured with the recommended amount of memory
-
Hyper-V: Windows Server 2008 R2 should be configured with at least the minimum amount of memory
-
Hyper-V: Windows Server 2008 R2 should be configured with the recommended amount of memory
