Hyper-V: Hyper-V should be the only enabled role

Article
09/19/2012

Applies To: Windows Server 2008 R2, Windows Server 2012

This topic is intended to address a specific issue identified by a Best Practices Analyzer scan. You should apply the information in this topic only to computers that have had the Hyper-V Best Practices Analyzer run against them and are experiencing the issue addressed by this topic. For more information about best practices and scans, see Best Practices Analyzer.

Operating System	Windows Server 2012 or Windows Server 2008 R2
Product/Feature	Hyper-V
Severity	Warning
Category	Configuration

Note

An update is available for Hyper-V Best Practices Analyzer (BPA) for Windows Server 2008 R2 and Microsoft Hyper-V Server 2008 R2. The update is appropriate for servers that run Hyper-V in Windows Server 2008 R2 with Service Pack 1 (SP1) and that have the Hyper-V BPA installed. The update includes addresses issues between the Hyper-V BPA and new features that were introduced in SP1. This update also fixes several other issues in BPA. For more information, see article 2485986 in the Microsoft Knowledge Base.

Issue

Roles other than Hyper-V are enabled on this server.

In most cases, it is not advisable to install other roles on a server running the Hyper-V role. The exception is when the Remote Desktop Virtualization Host role service is installed. The Remote Desktop Virtualization Host role service is part of the Remote Desktop Services role and requires Hyper-V to be installed on the same server.

Impact

The Hyper-V role should be the only role enabled on a server.

This best practice is recommended because it helps keep the management operating system free of components (such as roles, features, and applications) that are not required to run Hyper-V. By following this best practice, as well as running Hyper-V on a Server Core installation of Windows Server 2008, you will need fewer updates to the management operating system because nothing requires software updates except the Server Core installation, the Hyper-V service components, and the Windows hypervisor.

Resolution

Use Server Manager to remove all roles except Hyper-V.

Server Manager includes the Remove Roles Wizard. This wizard simplifies the removal of roles from your server and allows you to remove multiple roles at one time. Before removing any roles, the Remove Roles Wizard verifies that no software components that are required by any of the remaining roles are removed accidentally. If it is necessary, the wizard prompts you to approve the removal of other roles, role services, or software programs that are required by roles that remain installed. The risk of removing software upon which other roles depend is almost eliminated.

To use Server Manager, you must be logged on to the computer as an administrator.

To remove a role

In the Roles Summary area of the Server Manager main window, click Remove Roles. Follow the instructions that are provided by the wizard as you progress through the removal.

Tip

You can open Server Manager by using shortcuts on the Start menu, on the Windows taskbar, or in Administrative Tools.

Additional references

For instructions on using the command interface or Windows PowerShell to remove a role, see Removing Server Roles and Features (https://go.microsoft.com/fwlink/?LinkID=134107).

Partager via