How to troubleshoot issues when adding a Hyper-V host in System Center Virtual Machine Manager 2008 or System Center Virtual Machine Manager 2008 R2

July 20, 2011, 11:28 am

≫ Next: Hyper-V top "gotchas" or "known issues"

≪ Previous: New KB: How to troubleshoot the "Not Responding" host status in SCVMM 2008 and in SCVMM 2008 R2

I just wanted to let you know about a new Knowledge Base article we published today. You’ll definitely want to bookmark this one as it tells you how to troubleshoot a couple of the more common issues we see when adding a Hyper-V host in SCVMM 2008 or SCVMM 2008 R2:

=====

Summary

This article covers how to troubleshoot issues when adding a Hyper-V host in System Center Virtual Machine 2008 or System Center Virtual Machine 2008 R2.
Common errors that are logged in the VMM Administrator Console when an “Add virtual machine host” job fails include the following:

Error (421)
Agent installation failed on server.domain.com because of a WS-Management configuration error.

Error (2912)
An internal error has occurred trying to contact an agent on the server.domain.com server.

Error (2916)
VMM is unable to complete the request. The connection to the agent server.domain.com was lost.

Error (2927)
A Hardware Management error has occurred trying to contact server server.domain.com.

More Information

Step 1: Review the VMM Agent installation log file

On the Hyper-V host, review the “vmmAgent.msi_%date%_%time%.log” file that’s located in the %systemdrive%\ProgramData\VMMLogs directory.

Note: This log file may not exist if the failure occurs early in the installation process.

Step 2: Use the System Center Virtual Machine Configuration Analyzer (VMMCA)

The Virtual Machine Manager Configuration Analyzer is a diagnostic tool that administrators can use to evaluate important configuration settings for computers that either are serving or might serve VMM roles or other VMM functions. The Virtual Machine Manager Configuration Analyzer does the following:

· Scans the hardware and software configurations of the computers that you specify
· Evaluates these configurations against a set of predefined rules
· Displays error messages and warnings for any configurations that are not optimal for the VMM role or for other VMM functions that you specified for the computer

To download the Virtual Machine Manager Configuration Analyzer, visit the following Microsoft website:
http://www.microsoft.com/downloads/details.aspx?FamilyID=02d83950-c03d-454e-803b-96d1c1d5be24&displaylang=en

Step 3: Verify the recommended hotfixes are installed on the VMM and Hyper-V servers

On the VMM and Hyper-V servers, verify the recommended hotfixes are installed:

2397711 Recommended hotfixes for System Center Virtual Machine Manager 2008 R2
962941 Recommended hotfixes for System Center Virtual Machine Manager 2008

Step 4: Verify the ports used by VMM are not blocked by a firewall

Verify the ports used by VMM to communicate with the Hyper-V host are not blocked by a firewall. By default, VMM uses the following ports to communicate with the Hyper-V host:

TCP port 80
TCP port 443
TCP port 2179

The following knowledge base article covers some tests to verify communication between the VMM and Hyper-V hosts:

2465160 Add Host or other action fails with (2916) 0x80338126 in System Center Virtual Machine Manager 2008

For more information on the ports used by VMM, please reference the following TechNet article: http://technet.microsoft.com/en-us/library/cc764268.aspx

Step 5: Check for duplicate SPNs

Perform the steps documented in the following article to check for duplicate SPNs:

970923 Unable to add a managed host in SCVMM 2008 and SCVMM 2008 R2, Error 2927 (0x8033809d)

Step 6: Check for corrupted performance counters on the Hyper-V host

Review the following knowledge base article to determine if the Hyper-V host has corrupted performance counters:

2001247 SCVMM: Adding a host to System Center Virtual Machine Manager 2008 may fail with error 2912 / 0xc0000BBF

Step 7: Manually install the VMM Agent on the Hyper-V host

If the Add-VMHost job continues to fail, manually install the agent on the Hyper-V host by performing the steps documented in the following TechNet article: http://technet.microsoft.com/en-us/library/cc764218.aspx

Query Words

SCVMM Add-VMHost VMM 2008 R2 VM VMM2008

=====

For the latest information please see the following KB article:

KB2584907: How to troubleshoot issues when adding a Hyper-V host in System Center Virtual Machine Manager 2008 or System Center Virtual Machine Manager 2008 R2

J.C. Hornbeck | System Center Knowledge Engineer

↧

Hyper-V top "gotchas" or "known issues"

August 17, 2011, 7:08 am

≫ Next: Two articles on troubleshooting Virtual Machine Manager

≪ Previous: How to troubleshoot issues when adding a Hyper-V host in System Center Virtual Machine Manager 2008 or System Center Virtual Machine Manager 2008 R2

I know this one isn’t necessarily SCVMM specific but if you’re doing any work with Hyper-V then you’re going to want to know about these. These are the top "gotchas" or "known issues" that folks seem to have the most trouble with. "Gotchas" are also sometimes called "lessons learned" and "best practices" but whatever you call it, it’s a best practice to avoid a known "gotcha".

Hyper-V: Gotchas on the TechNet Wiki

J.C. Hornbeck| System Center Knowledge Engineer

↧

Two articles on troubleshooting Virtual Machine Manager

April 4, 2012, 6:55 am

≫ Next: VMM: Troubleshooting BITS and WMI

≪ Previous: Hyper-V top "gotchas" or "known issues"

Here’s a quick FYI on a couple new System Center 2012 Virtual Machine Manager (VMM) articles I found over in our community-driven TechNet Wiki. If you are planning on rolling out VMM, or if you already have, you’ll probably want to add these to your Favorites:

Troubleshoot VMM: DebugView for Windows (en-US) : http://social.technet.microsoft.com/wiki/contents/articles/9004.troubleshoot-vmm-debugview-for-windows-en-us.aspx

System Center 2012 Virtual Machine Manager (VMM) General Troubleshooting Guide (en-US) : http://social.technet.microsoft.com/wiki/contents/articles/8826.system-center-2012-virtual-machine-manager-vmm-general-troubleshooting-guide-en-us.aspx

J.C. Hornbeck| System Center & Security Knowledge Engineer

Get the latest System Center news onFacebookandTwitter:

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

↧

VMM: Troubleshooting BITS and WMI

April 5, 2012, 9:41 am

≫ Next: A couple more VMM troubleshooting articles : WinRM and configuring fabric resources

≪ Previous: Two articles on troubleshooting Virtual Machine Manager

Here are a couple more VMM troubleshooting articles I stumbled across over in our TechNet Wiki this morning. The first is on troubleshooting BITS and the second is on WMI:

Troubleshoot VMM: BITS Troubleshooting : http://social.technet.microsoft.com/wiki/contents/articles/9058.troubleshoot-vmm-bits-troubleshooting.aspx

WMI Troubleshooting for VMM (en-US) : http://social.technet.microsoft.com/wiki/contents/articles/9048.wmi-troubleshooting-for-vmm-en-us.aspx

Enjoy!

J.C. Hornbeck| System Center & Security Knowledge Engineer

Get the latest System Center news onFacebookandTwitter:

↧

A couple more VMM troubleshooting articles : WinRM and configuring fabric resources

April 12, 2012, 9:14 am

≫ Next: VMM Troubleshooting: Deploying Virtual Machines and Services in a Private Cloud

≪ Previous: VMM: Troubleshooting BITS and WMI

Just a quick FYI on a couple more System Center 2012 Virtual Machine Manager (VMM) articles I found over in our community-driven TechNet Wiki. If you are planning on rolling out VMM, or if you already have, you’ll definitely want to check these out

VMM Troubleshooting: Windows Remote Management (WinRM) : http://social.technet.microsoft.com/wiki/contents/articles/9126.vmm-troubleshooting-windows-remote-management-winrm.aspx

VMM Troubleshooting: Configuring Fabric Resources : http://social.technet.microsoft.com/wiki/contents/articles/9127.vmm-troubleshooting-configuring-fabric-resources.aspx

J.C. Hornbeck| System Center & Security Knowledge Engineer

Get the latest System Center news onFacebookandTwitter:

↧

VMM Troubleshooting: Deploying Virtual Machines and Services in a Private Cloud

April 12, 2012, 11:06 am

≫ Next: Troubleshooting service templates in System Center 2012 Virtual Machine Manager

≪ Previous: A couple more VMM troubleshooting articles : WinRM and configuring fabric resources

Here’s another great article I found while perusing all the new stuff in our TechNet Wiki. This one was authored by Tim Sherer and goes through some common and maybe not so common issues you may run into when deploying VMM virtual machines and services in a private cloud:

VMM Troubleshooting: Deploying Virtual Machines and Services in a Private Cloud (en-US) : http://social.technet.microsoft.com/wiki/contents/articles/9129.vmm-troubleshooting-deploying-virtual-machines-and-services-in-a-private-cloud-en-us.aspx

UPDATE: It looks like the information at the link above has been moved here: http://technet.microsoft.com/en-us/library/gg696970.aspx

Enjoy!

J.C. Hornbeck| System Center & Security Knowledge Engineer

Get the latest System Center news onFacebookandTwitter:

↧

Troubleshooting service templates in System Center 2012 Virtual Machine Manager

April 19, 2012, 10:01 am

≫ Next: KB: How to troubleshoot the “Needs Attention” and “Not Responding” host status in System Center 2012 Virtual Machine Manager

≪ Previous: VMM Troubleshooting: Deploying Virtual Machines and Services in a Private Cloud

Hi there, this is Alvin Morales and today I want to talk about how to troubleshoot a service template deployment in System Center 2012 Virtual Machine Manager (VMM). In VMM, we have a new feature for deploying virtual machines (VMs) as a service. There are several blog posts already on this and you can read more about it at the links below:

http://technet.microsoft.com/en-us/library/gg675105.aspx

http://technet.microsoft.com/en-us/library/gg650474.aspx

http://social.technet.microsoft.com/wiki/contents/articles/using-services-templates-in-system-center-virtual-machine-manager-2012.aspx

I won't focus this blog on how to create a service template but more on how you can track the changes that happen behind the scenes to troubleshoot any issues.

Let's first create a scenario. For simplicity sake, we will use a single VM as this will help us understand the process and use it to track any other deployment. The service template will create a VM with Windows Server 2008 R2 SP1, install the Server App-V agent and then import a Server App-V package to the server.

Once you go through the deployment process and the job starts in the background, this is what occurs:

1) The VHD is transferred from the library to the host via BITS. This process is similar to creating a VM from a template.

2) Once the VM is created on the host, the process will add a virtual floppy to apply all the customization provided in the OS configuration of the template. This will include the addition of roles and features. You can view steps 1 and 2 by connecting to the VM using Hyper-V.

Once SysPrep is complete, the VM is domain joined and running the process that will install a guest VMM agent. You can confirm that this process occurred by connecting to the VM and navigating to %programdata%\vmmlogs. The guest agent will serve as the listener to the SCVMM service to perform actions on the guest VM.

3) Once the agent is installed it will proceed to run scripts in the VM, but before it runs these scripts it needs to transfer them to the guest VM. This step allows you to restart the job if an error occurs. This is done by transferring the custom resource folder from the library to the VM and these files are stored under c:\windows\temp under a folder called scvmmxxx\xxx.cr folder.

4) Once the script files are copied, the Server App-V agent install script will launch the script using c:\windows\temp\ as its working directory. Here it will create two files named GCE_stderrorXXX and GCE_stdoutXXX. These are text files that capture the output of the running script. The GCE_stdoutxxx contains the information of the current actions being performed by the process and the GCE_stderrorxxx file will have any error encountered by the script. If the script encounters an error and stops the process, it will leave this last log in the directory for review. If the process completes successfully it deletes all the contents inside windows\temp

5) Assuming that the process succeeds, we then proceed to transfer the application files specified in the application section of the template. In this case, this is a Server App-V package so it will transfer the package files from the library and store them in the local drive. These files will be stored in c:\windows\MSSCVMMApplications.

Inside this folder you will have two additional folders. One is for Server App-V and it’s here that we store our App-V files. The other is a Webdeploy folder that will store any web apps you have specified in the template.

Since we are using Server App-V, it will launch all PowerShell command to import the application into the Server App-V cache.

NOTE If we were installing a SQL dacpack, the files will be deployed to c:\windows\ MSSCVMMSQLInstance

If the process was successful, you will see the Server App-V application running a service or an icon on the Server App-V agent application list.

The service template process will store logs in c:\programdata\Microsoft\Virtual Machine Manager to track the process of an application installation.

Sample entry of a VMMapplicationmanager.log:

If you are configuring a SQL instance in the service template as part of your deployment, you can gather SQL logs by going to c:\program files\Microsoft SQL Server\100\Setup Bootstrap\log and look in Summary.txt for errors or failures.

Alvin Morales | Senior Support Escalation Engineer

Get the latest System Center news onFacebookandTwitter:

↧

KB: How to troubleshoot the “Needs Attention” and “Not Responding” host status in System Center 2012 Virtual Machine Manager

August 13, 2012, 11:04 am

≫ Next: KB: How to troubleshoot issues when adding a Hyper-V host in System Center 2012 Virtual Machine Manager

≪ Previous: Troubleshooting service templates in System Center 2012 Virtual Machine Manager

Here’s a new Knowledge Base article we published that talks about how to troubleshoot the “Needs Attention” and “Not Responding” host status in System Center 2012 Virtual Machine Manager. This is one you’ll probably want to add to your Favorites.

=====

Summary

This article discusses how to troubleshoot the “Needs Attention” and “Not Responding” host status in System Center 2012 Virtual Machine Manager. The “Needs Attention” and “Not Responding” host status in the VMM console occurs because the VMM Server is unable to communicate with the host machine or components (WMI, WinRM, etc.) on the host machine that are used to communicate with the VMM Server are not functioning correctly.

Common errors that are logged in the Jobs views in the VMM Console when the host status is “Needs Attention” or “Not Responding:”

Warning (2915)
The Windows Remote Management (WS-Management) service cannot process the request. The object was not found on the server (servername.domain.com).
Unknown error (0x80041002) or Unknown error (0x80338000)

Error (2916)
VMM is unable to complete the request. The connection to the agent servername.domain.com was lost.
Unknown error (0x80338126) or Unknown error (0x80338012)

Warning (12710)
VMM does not have appropriate permissions to access the Windows Remote Management resources on the server (servername.domain.com).
Unknown error (0x80338104)

Warning (13926)
Host cluster servername.domain.com was not fully refreshed because not all of the nodes could be contacted. Highly available storage and virtual network information reported for this cluster might be inaccurate.

Error (20506)
Virtual Machine Manager cannot complete the Windows Remote Management (WinRM) request on the computer servername.domain.com.

Perform the steps documented in the More Information section to identify the cause of the “Needs Attention” or “Not Responding” host status.

More Information

Step 1: Check the Health status of the Host

To check the Health status of a host, perform the following steps:

1. Open the VMM Console.
2. Select the Fabric view, right-click the host that’s experiencing issues and chose properties.
3. Within the host properties, select Status.
4. Select the category that has the Red exclamation to view the error details.

For more information on the host health check feature, please reference the following blog: http://blogs.technet.com/b/scvmm/archive/2011/12/19/host-properties-new-in-vmm-2012-expanded-health-checks.aspx

Step 2: Use the Virtual Machine Manager Configuration Analyzer (VMMCA)

VMMCA is a diagnostic tool you can use to evaluate important configuration settings for computers that are either running VMM server roles or are acting as virtual machine hosts. The VMMCA scans the hardware and software configurations of the computers you specify, evaluates them against a set of predefined rules, and then provides you with error messages and warnings for any configurations that are not optimal.
To download the Virtual Machine Manager Configuration Analyzer, visit the following Microsoft website:
http://www.microsoft.com/en-us/download/details.aspx?id=29309

Step 3: Verify the VMM service account is a member of the local administrators group on the host

• If the VMM service is running under a domain account, verify the domain account is a member of the local administrators group on the host.
• If the VMM is running under the local system account, verify the computer account is a member of the local administrators group on the host.
If the VMM service account is removed from the local administrators group on the host, this issue could be caused by a “Restricted Groups” group policy.
To resolve this issue, perform one of the following steps:

• Add the VMM service account to the Administrators "restricted groups" group policy setting.
• Create a new organizational unit in the domain, move the host computer object to the new OU and then configure the new organizational unit to block policy inheritance.

Step 4: Check for corrupted performance counters

Check the Application event log on the host to see if the following event is logged:

Log Name: Application
Source: Microsoft-Windows-LoadPerf
Event ID: 3012
Description:
The performance strings in the Performance registry value is corrupted when process Performance extension counter provider. The BaseIndex value from the Performance registry is the first DWORD in the Data section, LastCounter value is the second DWORD in the Data section, and LastHelp value is the third DWORD in the Data section.

If the Event ID 3012 is logged on the host machine, perform the steps documented in the following knowledge base article to rebuild the performance counters:

2554336 How to manually rebuild Performance Counters for Windows Server 2008 64bit or Windows Server 2008 R2 systems

Step 5: Check the Svchost.exe process of the Windows Remote Management service

VMM depends on the Windows Remote Management service for host communication. Therefore, the "Not Responding" status is very likely to occur because of an error in the underlying Windows Remote Management communication between the VMM server and the host computer. In this scenario, the host status is "OK" shortly after you restart the host computer. However, the status changes to "Not Responding" after three to four hours, and jobs on the VMM server fail and return an error that resembles the following:

Error (2927)
A Hardware Management error has occurred trying to contact server servername.domain.com.
Unknown error (0x803381a6)

Additionally, if you stop the Windows Remote Management service at a command prompt, this process takes much longer than usual to be completed. Sometimes, it can take up to five minutes to stop.
This problem can occur if the shared Svchost.exe process that hosts the Windows Remote Management service is experiencing issues.
To resolve this problem, configure the Windows Remote Management service to run in a separate Svchost.exe process. To do this, open an elevated command prompt, type the following command and then press ENTER.

sc config winrm type= own

Note Make sure that you type the command exactly as it appears here. Notice the space after the equal sign (=) symbol.
If the command is completed successfully, you should see the following output:
[SC] ChangeServiceConfig SUCCESS

Step 6: Increase the default values for WinRM

On each server, open an elevated command prompt, type the following commands and then press Enter after each command:
winrm set winrm/config @{MaxTimeoutms = "1800000"}
winrm set winrm/config/Service @{MaxConcurrentOperationsPerUser="400"}
net stop winrm
net start winrm
net start scvmmagent

=====

For the most current version of this article please see the following:

2742246 - How to troubleshoot the “Needs Attention” and “Not Responding” host status in System Center 2012 Virtual Machine Manager

J.C. Hornbeck| Knowledge Engineer | Management and Security Division

Get the latest System Center news onFacebookandTwitter:

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity- support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

↧

KB: How to troubleshoot issues when adding a Hyper-V host in System Center 2012 Virtual Machine Manager

August 14, 2012, 10:05 am

≫ Next: Support Tip: Connecting to a VM running on a VMware cluster from VMM 2012 fails with error 20700

≪ Previous: KB: How to troubleshoot the “Needs Attention” and “Not Responding” host status in System Center 2012 Virtual Machine Manager

Here’s a new Knowledge Base article we published. This one covers how to troubleshoot issues when adding a Hyper-V host in System Center 2012 Virtual Machine Manager.

=====

Summary

This article covers how to troubleshoot issues when adding a Hyper-V host in System Center 2012 Virtual Machine Manager.
Common errors that are logged in the VMM Console when an “Add virtual machine host” job fails:

Error (421)
Agent installation failed on servername.domain.com because of a WS-Management configuration error.

Error (2912)
An internal error has occurred trying to contact an agent on the servername.domain.com server.

Error (2916)
VMM is unable to complete the request. The connection to the agent servername.domain.com was lost.

Error (2927)
A Hardware Management error has occurred trying to contact server servername.domain.com.

Perform the steps documented in the More Information section to identify the cause of the issue.

More Information

Step 1: Review the VMM Agent installation log file

On the Hyper-V host, review the “vmmAgent.msi_date_time.log” file that’s located in the %systemdrive%\ProgramData\VMMLogs directory.

Note: This log file may not exist if the failure occurs early in the installation process.

Step 2: Use the Virtual Machine Manager Configuration Analyzer (VMMCA)

To download the Virtual Machine Manager Configuration Analyzer, visit the following Microsoft website:

http://www.microsoft.com/en-us/download/details.aspx?id=29309

Step 3: Verify the ports used by VMM are not blocked by a firewall

Verify the ports used by VMM to communicate with the Hyper-V host are not blocked by a firewall. By default, VMM uses the following ports to communicate with the Hyper-V host:

TCP port 443
TCP port 5985
TCP port 5986

For more information on the ports used by VMM, please reference the following TechNet article: http://technet.microsoft.com/en-US/library/gg710871.aspx

Step 4: Check for duplicate SPNs

Perform the steps documented in the following article to check for duplicate SPNs:

970923 Unable to add a managed host in SCVMM 2008 and SCVMM 2012, Error 2927 (0x8033809d)

Step 5: Check for corrupted performance counters on the Hyper-V host

Check the Application event log on the host to see if the following event is logged:

If the Event ID 3012 is logged on the host machine, perform the steps documented in the following knowledge base article to rebuild the performance counters:

2554336 How to manually rebuild Performance Counters for Windows Server 2008 64bit or Windows Server 2008 R2 systems

Step 6: Manually install the VMM Agent on the Hyper-V host

If the Add-SCVMHost job continues to fail, manually install the agent on the Hyper-V host by performing the steps documented in the following TechNet article: http://technet.microsoft.com/en-us/library/bb740757.aspx

=====

For the most current version of this article please see the following:

2742275 - How to troubleshoot issues when adding a Hyper-V host in System Center 2012 Virtual Machine Manager

J.C. Hornbeck| Knowledge Engineer | Management and Security Division

Get the latest System Center news onFacebookandTwitter:

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity- support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

↧

Support Tip: Connecting to a VM running on a VMware cluster from VMM 2012 fails with error 20700

September 4, 2012, 9:35 am

≫ Next: Hyper-V Capability Profile No Longer a Requirement to Configure Clouds in HRM

≪ Previous: KB: How to troubleshoot issues when adding a Hyper-V host in System Center 2012 Virtual Machine Manager

Hi folks, this is Vladimir from the VMM team and today I want to discuss an issue with System Center 2012 Virtual Machine Manager (VMM 2012) and VMware vCenter 4.1 that I saw few weeks ago. The summary of the issue is this: A VMM 2012 Self-Service user receives the following error when trying to connect via console to a VM running on a VMware cluster of two ESX 4.1 hosts either from the VMM Self-Service Portal, the VMM console, or System Center 2012 AppController:

VMConsoleParamsFetchFailure (20700)
Could not retrieve console parameters for virtual machine %VMName;.
Ensure that the virtual machine exists and that the host %VMHostName; can be contacted, and then try the operation again.

The VMM 2012 Administrator is able to connect via the console to the same VM without any issues. My initial thought was that this is related to the permissions issue somewhere between VMM and vCenter, and my guess ended up being correct. A VMM trace showed the following:

GetVmConsoleParameters.cs,126,0x00000000,Trying to get run as account with username SCVMM.vm-41 and associated with vm 247ac427-fa90-4522-9a28-77903973aea7

ClientConnection.cs,267,0x00000000,Exception during context of an indigo call; carmine error code returned 20700
ClientConnection.cs,267,0x00000000,Microsoft.VirtualManager.Utils.CarmineException: Could not retrieve console parameters for virtual machine <VM_NAME>.

    at Microsoft.VirtualManager.Engine.VmOperations.VMConsoleOperations.GetConsoleParameters(Guid vmObjectId; ConnectionProperties connProperties)
at Microsoft.VirtualManager.Engine.Remoting.ClientConnection.GetVMConsoleParameters(Guid vmObjectId)
    at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance; Object[] inputs; Object[]& outputs)
    at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
    at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
    at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage4(MessageRpc& rpc)
    at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)
*** Carmine error was: VMConsoleParamsFetchFailure (20700)

I have two environments. One where the issue is occurring and one where the Self-Service users are able to connect via console to VMs, so I started comparing them.

After some troubleshooting I was able to understand what is causing this. In short, when we add vCenter to VMM 2012, we have to use an account that is a local administrator on the Windows server where vCenter server is running. That account needs to be a vCenter Administrator as well. The reason why we experienced error 20700 is because VMM 2012 was not able to create and configure the required users, user roles, and permission on the vCenter server. The account used to add vCenter to VMM2012 possibly did not have all the rights that VMM needs. When the account has enough permissions, this is what VMM 2012 does on vCenter to enable VMM Self-Service users to connect via the console to VMs on the ESX hosts:

1. VMM creates a run-as account (SCVMM.vm-xx) that it uses to enable Self-Service users to connect to vCenter. It also specifies for which VMs this run-as account should be used.

2. Then on the Windows machine where vCenter server is running, VMM creates a local user account with the same name as the run-as account created above.

3. In vCenter, VMM creates two user roles (SCVMMSelfServiceUser and SCVMMConsoleUser), gives those user roles Console Interaction permission, adds local account SCVMM.vm-xx to the SCVMMConsoleUser role and then assigns SCVMM.vm-xx permission to the VM to which the VMM Self-Service user has access to.

NOTE Most of these users, user roles, and permissions are created/configured when the VMM Self-Service user tries to connect to a VM via console from the Self-Service Portal, VMM console, or System Center 2012 AppController.

In my case, we resolved this issue by removing vCenter server from VMM and then adding it back using a domain account that was a local Administrator on Windows machine where vCenter running and also a vCenter Administrator. In theory, you can use a local account too, but for some reason using the local account in one of the environments caused this issue. The steps to add a vCenter server to VMM are described here: http://technet.microsoft.com/en-us/library/gg610681

I hope you found this post interesting and helpful. See you soon!

Vladimir Petrosyan | Support Engineer | Management and Security Division

Get the latest System Center news onFacebookandTwitter:

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity- support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

↧

Hyper-V Capability Profile No Longer a Requirement to Configure Clouds in HRM

April 14, 2014, 11:50 pm

≫ Next: Update Rollup 10 for Windows Azure Pack is now available

≪ Previous: Support Tip: Connecting to a VM running on a VMware cluster from VMM 2012 fails with error 20700

One of the key design principles that we focused on when developing the Windows Azure Hyper-V Recovery Manager (HRM) disaster recovery service was a Service-Oriented Extensible Architecture. Combining this service-oriented approach with a close attention on telemetry data after each release gives us the opportunity to enable new scenarios for continuous service improvement, and quickly identify gaps in existing functionality that our customers would like us to address.

HRM has been Generally Available since January 2014, and one of the most common error scenarios that many of our customers have faced has been around the strict requirement for selecting Hyper-V Capability Profile when creating a Private Cloud in System Center Virtual Machine Manager (VMM). Leaving this setting unselected, when planning the VMM infrastructure, would normally result in an error when configuring cloud protection in the HRM portal. This requirement also limited our interoperability with Windows Azure Pack (WAP) since VM role deployment fails in WAP if the cloud associated with a WAP plan has the Hyper-V Capability Profile selected.

In our March Service update, we have addressed this by removing the requirement of enabling the Hyper-V Capability Profile on the VMM Cloud. Customers would no longer be required to configure this setting in VMM, and for those who already have, we will ensure backward compatibility when configuring clouds and enabling virtual machine protection. Clouds that are associated with a plan in WAP can also now be configured for disaster recovery and protection in HRM without making any changes to their capability profile settings in VMM. Virtual Machines deployed on Virtual Machine Clouds associated with a WAP plan, can be enabled for protection and can be added to Recovery Plans in HRM for one-click failover automation. Our singular goal with HRM is to simplify the setup and operation of your disaster recovery infrastructure, and this update is one of the many ways in which we are working towards achieving that goal.

To start using this and other new enhancements to the service, you will need a new version of the Windows Azure Hyper-V Recovery Manager Provider that you can download from the HRM Portal. If you haven’t already, you can also opt-in to receive automatic Provider Updates via Microsoft Updates for quicker access to new functionality and added features. Customers will need to install Update Rollup 1 on their primary and secondary VMM Servers to leverage this enhancement. Existing functionality, based on enabling the Capability Profile setting will continue to work for customers who choose to not update their Provider. More information about Update Rollup 1 is available in the following Knowledge Base Article: http://support.microsoft.com/kb/2936967

You can read more about Windows Azure Hyper-V Recovery Manager in Brad Anderson’s 9-part series, Transform the datacenter. To learn more about setting up Hyper-V Recovery Manager in your deployment follow our detailed step-by-step guide. You can also visit the HRM forum on MSDN for additional information and to engage with other customers.

↧

Update Rollup 10 for Windows Azure Pack is now available

May 25, 2016, 12:09 pm

≫ Next: Important update regarding Microsoft Virtual Machine Converter (MVMC)

≪ Previous: Hyper-V Capability Profile No Longer a Requirement to Configure Clouds in HRM

Update Rollup 10 for Windows Azure Pack (WAP) is now available to download.

Issues that are fixed in this update rollup

Issue 1: Windows Server 2016 only: Support for Encryption Supported VMs. Windows Server 2016, Virtual Machine Manager and Service Provider Foundation provide support for Encrypted Supported VMs, now WAP provides support for the three type of VMs in Windows Server 2016: regular VMs, Shielded VMs, and Encryption Supported VMs.
Issue 2: Windows Server 2016 only: Fix to incorrect Format of volume Signature in PDK File downloaded through WAP.
Issue 3: When a tenant updates a VM Size, the Hardware Profile ID is passed along to the SPF/VMM Virtual Machine Update event, allowing custom runbooks to change other properties as necessary.
Issue 4: Fix to Virtual Network property labels in the Quota page. The quotas for “Site-to-Site VPN” and “External IP addresses” labels in the Admin Portal VM Resource Provider are misleading because they read “per network.” They actually are “per subscription.”
Issue 5: Fix: When you update the VM Cloud Resource Provider, a duplicate Port setting is added leading ManagementOData to fail and return an error message that reads, “An item with the same key has already been added.”
Issue 6: Ability for the tenant user to add a network adapter to a VM while the VM is running. In UR 9.1 and previous versions, new NICs could be added only after the VM was stopped.
Issue 7: Ability for the WAP Admin to include a SQL Server into multiple availability groups for HA configurations.
Issue 8: Ability for the WAP Admin to include a server that’s running Microsoft SQL Server into multiple availability groups for HA configurations.
Issue 9: Ability for the WAP user to enable the “Always On” feature of WAP websites.

For complete details including installation instructions as well as a download link, please see the following:

3158609 – Update Rollup 10 for Windows Azure Pack (https://support.microsoft.com/en-us/kb/3158609)

For information regarding all System Center fixes included in Update Rollup 10, please see the following:

3164172 – Description of Update Rollup 10 for Microsoft System Center 2012 R2 (https://support.microsoft.com/en-us/kb/3164172)

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

↧

Important update regarding Microsoft Virtual Machine Converter (MVMC)

June 3, 2016, 6:04 pm

≫ Next: Cumulative Update 2 for System Center 2016 Virtual Machine Manager Technical Preview 5 is now available

≪ Previous: Update Rollup 10 for Windows Azure Pack is now available

Today, Microsoft is announcing the upcoming retirement of Microsoft Virtual Machine Converter (MVMC). This announcement covers all released versions of MVMC (1.0, 2.0, 3.0, 3.1). Moving forward, we recommend using Azure Recovery Services (ASR) as the tool of choice for migrating your physical and virtual workloads.

Microsoft will continue to support MVMC for a full calendar year after this announcement. Support will officially end on June 03, 2017. At that time, we will no longer offer MVMC on the download center and we will also retire associated content.

FAQ:

Q: What is Microsoft’s roadmap for virtual machine conversion utilities?

A: Azure Site Recovery is Microsoft’s standard for converting physical and virtual machines. We suggest using this tool for physical-to-virtual (P2V), Hyper-V, and VMware conversions to both Azure and on-premises deployments. We continue to invest in this technology and regularly add capabilities and features. In addition, Microsoft Virtual Machine Manager (SC 2012 R2 VMM) will continue to support migrations from VMware vCenter deployments to Hyper-V.

Q: Will MVMC remain available?

A: Yes. MVMC will remain a free download until the retirement date next year.

Q: Will there be a other means to obtain the tool after MVMC is retired?

A: No, the download will be removed. An archive will not be available.

Mark Stanfill, Supportability Program Manager
Microsoft Enterprise Cloud Group

↧

Cumulative Update 2 for System Center 2016 Virtual Machine Manager Technical Preview 5 is now available

June 21, 2016, 8:31 am

≫ Next: How to prepare a Windows VHD for upload to Microsoft Azure

≪ Previous: Important update regarding Microsoft Virtual Machine Converter (MVMC)

Cumulative Update 2 (CU2) for Microsoft System Center 2016 Virtual Machine Manager Technical Preview 5 is now available. There are two updates available for Cumulative Update 2 for System Center 2016 Virtual Machine Manager Technical Preview 5: An update for VMM Server and an update for the Administrator console.

For a complete list of scenarios enabled, issues fixed, known problems as well as download and installation instructions, please see the following:

3160164 – Cumulative Update 2 for System Center 2016 Virtual Machine Manager Technical Preview 5 (https://support.microsoft.com/en-us/kb/3160164)

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

↧

How to prepare a Windows VHD for upload to Microsoft Azure

August 22, 2016, 10:28 am

≫ Next: Now Available: Update Rollup 11 for Microsoft System Center 2012 R2 Virtual Machine Manager

≪ Previous: Cumulative Update 2 for System Center 2016 Virtual Machine Manager Technical Preview 5 is now available

Just a quick note to let you know that we have a new article available that describes how to prepare a Windows VHD for upload to Microsoft Azure. The steps in this article are highly recommended before uploading a Virtual Machine to Azure using Azure Recovery Services (ASR). You can find the article here: https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-windows-prepare-for-upload-vhd-image/... Read more

↧

Now Available: Update Rollup 11 for Microsoft System Center 2012 R2 Virtual Machine Manager

August 24, 2016, 7:35 am

≫ Next: Microsoft Virtual Machine Manager and support for .NET Framework

≪ Previous: How to prepare a Windows VHD for upload to Microsoft Azure

Update Rollup 11 for Microsoft System Center 2012 R2 Virtual Machine Manager is now available. The KB article below describes the issues that are fixed in VMM 2012 R2 Update Rollup 11 (UR11) and there are two updates: One update for VMM Server and one for the Administrator console. Please note that these updates are available only for manual download through the Microsoft Download Center and are not available on Microsoft Update. For additional details regarding the issues fixed as well as download and installation instructions, please see the following:

3184831 – Update Rollup 11 for System Center 2012 R2 Virtual Machine Manager (https://support.microsoft.com/en-us/kb/3184831)

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

↧

Microsoft Virtual Machine Manager and support for .NET Framework

September 27, 2016, 10:58 am

≫ Next: Announcing VMM SDN Express for VMM 2016

≪ Previous: Now Available: Update Rollup 11 for Microsoft System Center 2012 R2 Virtual Machine Manager

Today we’re happy to announce that both .NET Framework 4.6.1 and .NET Framework 4.6.2 are officially supported on servers running Microsoft System Center 2012 R2 Virtual Machine Manager (VMM 2012 R2). We have also validated Windows Management Framework 5.0 (WMF 5.0) with Windows Server 2012 R2 computers so that is supported as well. The official... Read more

↧

Announcing VMM SDN Express for VMM 2016

November 28, 2016, 10:15 am

≫ Next: How to recover an HNV Gateway that was deployed through Microsoft VMM 2016

≪ Previous: Microsoft Virtual Machine Manager and support for .NET Framework

Author: Manish Jha | Program Manager

We are happy to announce the release of VMM SDN Express for Microsoft System Center Virtual Machine Manager 2016 (VMM 2016)! Do you want a VMM solution that can deploy an entire SDN fabric without you having to move through multiple VMM wizards or having to wait for very long? What if you could specify all the parameters in a single file and let VMM take over all the SDN deployment tasks, where you simply come back later and see the complete VMM SDN stack deployed? VMM SDN Express does exactly that, and then some. The successful deployment is completely manageable with the VMM UI post deployment, and failed deployments roll back entirely leaving your fabric ready for another deployment attempt while providing you with the required logs to investigate the causes of failure.

You can find related resources on Github, including the required documentation and example parameter files. There you will find following:

The script deploys SDN stack using VMM through a single configuration file.

Apart from reducing points of human error caused by multiple input wizards, the script also saves significant time for fabric admins as they are able to specify all of the parameters at one time and then come back later to a complete SDN stack, including Network Controller, Software Load Balancer and Gateway, all deployed through VMM. Once you deploy SDN using this script, the complete stack is manageable via the VMM UI just as it would if you had deployed SDN using the VMM UI wizards!

So use this script if you want to leverage best of both worlds – SDN Express like agility for deployment and rich management capability using VMM UI afterwards.

This script deploys all the Logical Networks and artifacts as described in the VMM SDN deployment guide. You also have the option to repurpose existing a Management Logical Network and Logical Switch if you already have those configured.

Note that if script suffers a failure due to wrong input or infra issues, all the changed settings are rolled back and you can start a fresh deployment all over again.

Also, please be aware that SET enabled switch deployment is currently not supported in this script. The script finds the first pNIC in Trunk mode on the host and deploys Logical Switch in the standalone mode on the host. In case the script can’t find such a pNIC on any host, the switch deployment will fail. If you need SET enabled deployment, you need to deploy the SET enabled switch out of band and then specify the name of the switch in the script at the time of deployment.

We’re looking forward to hearing about deployments from you guys in case you are planning to deploy SDN in your environment so please share your feedback.

Manish Jha | Program Manager | Microsoft

↧

How to recover an HNV Gateway that was deployed through Microsoft VMM 2016

December 12, 2016, 9:54 am

≫ Next: Hotfix 1 for System Center 2016 Virtual Machine Manager Update Rollup 1 is now available

≪ Previous: Announcing VMM SDN Express for VMM 2016

Author: Manish Jha | Program Manager

This post contains information about HNV gateways that are deployed through Microsoft System Center Virtual Machine Manager 2016 (VMM 2016). Please note that with Windows Server 2016 and VMM 2016, you now have an option to use Azure style gateways that are managed by Network Controller. Steps in this guide, however, focus on the HNV style gateways that could be deployed with Windows Server 2012 R2 and VMM 2012 R2 in the past. The 2012 R2 style HNV gateways can be deployed even with Windows Server 2016 and VMM 2016 since this capability is fully compatible with our latest release. Please refer here for more information on gateways.

This post describes two ways of recovering a HNV Gateway:

How to recover a gateway after failure of both virtual machines that support the gateway
How to recover a gateway after failure of one virtual machine that supports the gateway

How to recover a gateway after failure of both virtual machines that support the gateway

We will assume that you deployed HNV gateway using a VMM Service Template. This service template helps you create a pair of virtual machines on a host cluster, and together the virtual machines and the cluster help provide high availability for the gateway that runs on them.

If both virtual machines that make up the gateway fail, you can recreate the failed gateway by deploying a service template again. When you recreate the gateway, the names of the virtual machines can differ from before, and you can deploy them to a different host cluster. Other settings, such as the subnets that are specified in the network sites, must remain the same as when you originally deployed the gateway. The following procedures provide details.

How to collect information to prepare for gateway recovery after failure of both virtual machines

1. In the Fabric workspace in VMM, select Network Service in the console tree under Networking.

2. In the Network Services pane, find the listing for the gateway that you want to recover and record the name of the gateway. In this article, this name is known as GATEWAY-NAME.

3. Right-click the listing for the gateway and then click Properties.

4. Click Connectivity, then record the information that is displayed for the frontend and the backend (network adapters and network sites).

5. Close the Properties page.

6. Make sure that you downloaded the following Windows PowerShell script:

RecoverGatewayScript.psm1

Note that this script remains unchanged from VMM 2012 R2 usage.

7. Determine the MAC address of the gateway by running the following script commands. Make sure that you substitute the correct path for PATH and the name of the gateway for GATEWAY-NAME.

Import-Module PATH\GatewayRecovery.psm1
$svcName = “GATEWAY-NAME”
$hostCredential = Get-Credential
GetMacAddress $svcName $hostCredential

How to recover after failure of both virtual machines that support the gateway

1. In VMM, delete the service listing for the two virtual machines that supported the failed gateway. To do this, click Show on the Home tab in the VMs and Services workspace, then click Services. Locate the host on which the virtual machines are deployed. In the details pane, right-click the service (not the individual virtual machines), then click Delete. When you are prompted, confirm the deletion.

2. Optionally, if you are using the same virtual machine names that you used before, and you expect that the existing DNS entries will cause problems when you redeploy, arrange to have these DNS entries removed.

3. If you are using a new host cluster instead of recovering the gateway on the existing host cluster, make sure that the new hosts are configured as dedicated network virtualization gateways. To do this, follow these steps:

In the Fabric workspace in VMM, make sure that Fabric Resources is selected in Show on the Home tab.
In the Fabric pane, click Servers, expand the host group that contains the new host cluster, and then click the host cluster.
In the Hosts pane, right-click one of the hosts (not the host cluster), and then click Properties.
Click the Host Access tab, and then click to select the This host is a dedicated network virtualization gateway, so it is not available for placement of virtual machines requiring network virtualization check box. Then click OK.
Repeat the process on the other host.

4. As you did for the original deployment, choose the appropriate service template (2-NIC or 3-NIC) for your environment. Review the settings in the service template to make sure that they are what you want for this deployment of the gateway.

IMPORTANT When you re-create the gateway, you must specify the same subnets in the network sites that you specified for the gateway that failed. However, the names of the virtual machines can be different, and you can deploy them to a different host cluster.

5. As you did for the original deployment, use the service template to deploy the virtual machines that will support the new gateway. Make sure that you deploy them on the intended hosts.

6. Do the following verification tasks to make sure that the service deployment was successful:

Confirm that the back-end virtual network adapter on the gateway is not connected. (It should not be connected yet.) To do this, follow these steps:

In the VMs and Services workspace in VMM, click Services in the Show group on the Home tab.
Expand All Hosts, and then click the host group that the host cluster is in.
In the Services pane, expand the service until you can see the gateway virtual machines.
Right-click a gateway virtual machine, click Properties, and then click the Hardware Configuration tab in the properties sheet.
Under Network Adapters, confirm that there are three network adapters and that one of them is labeled Not connected. Record the name of the adapter that is not connected.

Start the new service, and then confirm that the virtual machines enter the Running state.
With the virtual machines still running, open a command prompt on the VMM server as an administrator, then type PING, followed by the name or IP address of the gateway itself. Press Enter, then confirm that a response is received from the gateway. If a response is not received, review possible causes, such as DNS settings, firewall settings and the state of the gateway cluster.

7. Choose one of the new virtual machines as “primary.” Run the following Windows PowerShell commands, substituting the name of the chosen virtual machine for VMNAME:

$vm = Get-SCVirtualMachine –Name “VMNAME”
$vm.VirtualNetworkAdapters | ft Name,VMNetwork,VirtualNetwork

8. In the resulting display, look for the adapter that is not connected. For that adapter, VMNetwork and VirtualNetwork will be blank. Identify the number of that adapter as follows:

Adapter	Number
First adapter that is shown in the list:	0
Second adapter that is show in the list:	1
Third adapter that is shown in the list:	2

9. Grant the MAC address that you identified in the earlier procedure to the network adapter that is not connected. To do this, run the following Windows PowerShell command. For MACADDRESS, substitute the MAC address, and for NUMBER, substitute the number (0, 1, or 2) that you identified in the previous step:

$mac = Grant-SCMACAddress -MACAddress MACADDRESS -MACAddressPool
(Get-SCMACAddressPool -Name “Default MAC address pool”) -VirtualNetworkAdapter
$vm.VirtualNetworkAdapters[NUMBER]

10. Make sure that the virtual machine is stopped, and then apply the MAC address to the network adapter that is not connected. To do this, run the following Windows PowerShell commands. For NUMBER, substitute the same number (0, 1, or 2) that you used in the previous step:

Stop-SCVirtualMachine –vm $vm
Set-SCVirtualNetworkAdapter -VirtualNetworkAdapter
$vm.VirtualNetworkAdapters[NUMBER] –EthernetAddress $mac.Address

11. Delete the old gateway configuration information so that it will not interfere with the new gateway. To do this, you will need to know the names of the hosts in the cluster that the gateway was on before it failed. (This might be the same cluster that it is currently on.) To do this, follow these steps:

In any workspace in VMM, click Window on the Home tab, and then click PowerShell.
Run the following commands. For GATEWAY-NAME, substitute the gateway name. For HOST1 and HOST2, substitute the computer names of the physical hosts that were in the host cluster when the gateway failed. Run these commands even if you are using the same cluster you were using before the gateway failed.

$svcName = “GATEWAY-NAME”
$hostCredential = Get-Credential
$gwHosts = @(“HOST1”, “HOST2”)
CleanupGatewaysBeforeMigration $svcName $gwHosts $hostCredential

12. Restart the virtual machine by running the following command:

Start-SCVirtualMachine –vm $vm

13. Update the connection string for the gateway as follows. Do this even if you are using the same host cluster and the same computer names for the virtual machines.

Look up the existing connection string by running the following commands:

$ns = Get-SCNetworkService -Name $svcName
$ns.ConnectionString

For example, the connection string might resemble the following:

VMHost=GW-HV-CL01.contoso.com;GatewayVM=GW-VM-CL01.contoso.com;BackendSwitch=DatacenterSwitch

Construct an updated version of the connection string by pasting the old string into a text editor such as Notepad and then updating it as follows (make sure that you leave the semicolons as-is).

If the cluster name of the host cluster differs from what it was before, change the VMHost= setting.
If the computer name of the “primary” virtual machine differs from what it was before, change the GatewayVM= setting to the new name.

Update the connection string by running the following command. When you run the command, substitute the correct connection string for CONNECTIONSTRING.

Make sure that you include ;Migrate=true at the end of the string inside the quotation marks, and -Force at the end after the last quotation mark.

Set-SCNetworkService -NetworkService $ns -ConnectionString
“CONNECTIONSTRING;Migrate=true” -Force

If the Set-SCNetworkService command reports any errors, fix them and run the command again.

14. From a tenant virtual machine that uses the gateway, test the gateway. For example, use a network command such as PING.

How to recover a gateway after failure of one virtual machine that supports the gateway

If one of the virtual machines that support the gateway is functioning correctly but the other is not, you can use capabilities that are built into VMM services to “scale out” the gateway so that it again provides redundancy. To do this, follow these steps:

1. In VMM, remove the virtual machine that no longer functions. To do this, follow these steps:

In the VMs and Services workspace, select the host group where you deployed the service that runs the gateway.
In the Show group on the Home tab, click Services.
In the Services pane, expand the service.
Right-click the virtual machine that has failed, and then click Delete.
When you are prompted, confirm the deletion.

2. In Failover Cluster Manager, evict the failed node from the guest cluster that supports the gateway. To do this, follow these steps:

Open Failover Cluster Manager, expand the cluster in the console tree, expand Nodes, and then look at the status for each node. One node will be Up, and one node will be Down.
Right-click the node that has a status of Down, click More Actions, and then click Evict.

3. In the Services pane, right-click the gateway service itself (not a virtual machine), then click Scale Out.

4. On the Select Tier page in the Scale Out Tier Wizard, click Next.

5. On the Identity page, enter a name for the new virtual machine and click Next.

6. On the Select Host page, make sure that you select the host that held the virtual machine that failed, then click Next.

7. If the Configure Settings page appears, enter the computer name for the new virtual machine under Operating System Settings. Make sure that this computer name is not already being used by a computer in your environment.

8. Click Next.

9. On the Add Properties page, click Next.

10. On the Summary page, review your settings, and then click Scale Out.

NOTE You can track the progress of the scale out operation in the Jobs window. The operation can take 15 minutes or longer. You can perform other tasks in the VMM console while you monitor the job.

11. After the Create virtual machine job is completed successfully, verify that the new virtual machine was added and that it is started in the VMs and Services workspace. The new node will probably start to function within about five minutes.

12. To verify that the gateway is functioning, connect to the new virtual machine, and then run Get-NetCompartment at a Windows PowerShell prompt. If multiple compartments are listed, the new virtual machine is functioning and will help provide high availability for the gateway.

Manish Jha | Program Manager | Microsoft

↧

Hotfix 1 for System Center 2016 Virtual Machine Manager Update Rollup 1 is now available

December 13, 2016, 11:14 am

≫ Next: Troubleshooting ‘Unsupported Cluster Configuration’ errors in Virtual Machine Manager 2012 R2

≪ Previous: How to recover an HNV Gateway that was deployed through Microsoft VMM 2016

We published a new KB article that describes the fix that’s included in Hotfix 1 for Microsoft System Center 2016 Virtual Machine Manager Update Rollup 1. Additionally, the article contains information about how to obtain the hotfix as well as installation instructions. There are no updates to the Administrator Console or Guest Agent as part of this hotfix, however installation of this hotfix requires you to update the Host agent on all the VMM-managed hosts. Also note that you must have Update Rollup 1 for System Center 2016 Virtual Machine Manager installed to apply this hotfix.

For complete details please see the following:

3208888 – Hotfix 1 for System Center 2016 Virtual Machine Manager Update Rollup 1 (https://support.microsoft.com/en-us/kb/3208888)

J.C. Hornbeck, Solution Asset PM
Microsoft Enterprise Cloud Group

VMM 2016 UR1

↧