Compartir a través de

Hyper-V: The Hyper-V Virtual Machine Management service should be configured to start automatically

  • Artículo

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 2008 R2

Product/Feature

Hyper-V

Severity

Warning

Category

Configuration

Issue

The Hyper-V Virtual Machine Management Service is not configured to start automatically.

Impact

Virtual machines cannot be managed until the service is started.

Virtual machines that are running will continue to run. However, you will be unable to manage the virtualization environment, including your virtual machines, while the service is stopped.

Resolution

Use the Services snap-in or sc config command-line tool to reconfigure the service to start automatically.

By default, membership in the local Administrators group, or equivalent, is the minimum required to complete this procedure.

To reconfigure the service to start automatically using the Windows interface

  1. Open the Services snap-in. (Click Start, click in the Start Search box, type services.msc, and then press ENTER.)

  2. In the details pane, right-click Hyper-V Virtual Machine Management, and then click Properties.

  3. On the General tab, in Startup type, click Automatic.

To reconfigure the service to start automatically using the command line

  1. Open Command Prompt.

  2. Type:

    sc config vmms start=auto