Consider the following scenario:

• You have a computer that is running Windows Server 2008 or Windows Server 2008 R2 system that has a Hyper-V role installed.
• You start several Hyper-V virtual machines at the same time.

In this scenario, each Hyper-V virtual machine takes about 1 minute to start. Therefore, if you have more virtual machines, the last virtual machine takes longer to start. For example, when you start 30 virtual machines at the same time, it takes up to 30 minutes for the last virtual machine to start.

When you check the Microsoft-Windows-CAPI2/Operational log after the virtual machines have started, the following event is logged:

Log Name: Microsoft-Windows-CAPI2/Operational
Source: CAPI2
Event ID: 53
Level: Error
User: NETWORK SERVICE
Task Category: Retrieve Object from Network

When you view the event details, the EventAuxInfo ProcessName value is vmwp.exe.

When you start the Hyper-V virtual machines, the certificate store is enumerated to determine the preferred certificate that should be used to manage the virtual machine. If there are issues in verifying certificates in the store, they may cause the virtual machines to take longer than 30 minutes to start.

To work around these issues with certificates, you can configure a Hyper-V role to use the self-signed certificate that is generated by the Hyper-V Virtual Machine Monitor (VMM) service instead of enumerating the whole certificate store when the virtual machines are started.

To configure a Hyper-V role to use the self-signed certificate from the VMN service, follow these steps:

1. To copy the PowerShell script, visit the following Microsoft Web site:
   http://gallery.technet.microsoft.com/ScriptCenter/en-us/5b4a7114-218b-466c-a9c1-7eb2f725e707 (http://gallery.technet.microsoft.com/ScriptCenter/en-us/5b4a7114-218b-466c-a9c1-7eb2f725e707)
2. Paste the script into Notepad, and then save the file as Certfix.ps1.
3. Open an elevated Windows PowerShell command prompt.
4. Run the Certfix.ps1 script.

For example, if you save the script to C:\Scripts, type the following command at the PowerShell command prompt:

C:\Scripts\Certfix.ps1

Note The self-signed certificate that is generated by the Hyper-V VMM service is valid for one year. As soon as the certificate expires and the Hyper-V VMM service generates a new certificate, you must run the Certfix.ps1 script to configure the Hyper-V role to use the new certificate.

To determine the expiration date for the Hyper-V VMM service self-signed certificate, follow these steps:

1. Click Start, click Run, type mmc, and then click OK.
2. On the File menu, click Add/Remove Snap-in.
3. ClickCertificates, and then click Add.
4. ClickService account, and then click Next.
5. ClickLocal Computer, and then click Next.
6. ClickHyper-V Virtual Machine Management, and then click Finish.
7. Click OK to close the Add/Remove Snap-in window.
8. Expand Certificates - Service, expand Vmms\Personal, and then click Certificates.
9. Double-click the VMM Service certificate, and then check the expiration date in the VMM Service certificate window.