VMM Server cluster failover fails with Error Code: 0x8007138d

I have installed a 2-node VMM Server 2016 failover cluster on Windows Server 2016 today, I found that I could not manually failover the VMM cluster service from node 1 to node 2, and failed with the following information:

The operation has failed

The action ‘Move’ did not complete

The operation failed because either the specified cluster node is not the owner of the group, or the node is not a possible owner of the group

Here is a screenshot:

FailOver SCVMM

The error is a bit strange to me as I can see the Node 2 was listed there when I performed the Move operation, and the cluster installation was successfully on both nodes.

At this point, I did some research, and found someone mentioned that the Node 2 might be not a possible owner for one or more of VMM Server failover cluster dependencies.

After several clicks, I found that the failed Node 2 was not a possible owner of IP address of VMM Server virtual server name like below, once I selected it back, the failover succeeded.

FailOver SCVMM1FailOver SCVMM2FailOver SCVMM3

Then again Try to failover and Test.

Hope this Help’s 🙂

Setting up a Highly-Available 2016 VMM Environment

System Center Virtual Machine Manager is now starting to get more traction than ever, especially so given some of its management capabilities around Storage and Networking, Moreover when the Windows Azure Pack is used in production, Virtual Machine Manager must be installed in high availability in order to your tenants have almost always access to their VM management. To do this VMM uses the Failover Cluster feature integrated in Windows Server.

Before you begin there are some important things to note:

  1. Not only should the VMM Management Server should be highly available, but also the SQL Server where the VMM database will be installed and the file share for the Library Share too.
  2. Whilst it is possible to have two or more VMM Management servers in a cluster, only one node will ever be active.
  3. You will need to configure Distributed Key Management.  The distributed key management is used to store encryption keys in AD instead of storing the encryption keys on the machine/VM where the Management Server is installed.

The high level steps we will be carrying out in this post are:

  • Install all the SCVMM prerequisites (ADK)
  • Create a VMM Service Account which has local admin rights on the SCVMM nodes.
  • Create a container in Active Directory Domain Services for the Distributed Key Management.
  • Set all IP addresses, you may also configure an independent Heartbeat network
  • Install & configure the Failover Cluster feature on both servers.
  • Install SCVMM 2016

First Install ADK and MSODBCSQL & MSSQLCMD on both VMM Server’s.

You can also download the ADK to an alertnate path and install on your VMM Server’sif your machine is not connected with internet.

1

 

Capture

23

Install Failover Clustering feature on Both VMM Server’s.

010234567

Start Installing VMM on VMM Node 1

Right Click on the Setup and Run As Administrator

4

Click on Install

56

02

03

9101112

After you click Next from the Above Picture, it will check for the Prerequisite for the VMM like Minimum Memory,ADK and Etc.

It the Prerequisite Passed then it will give you option to configre Database for VMM Server’s.

13

Enter the database information for the MSSQL database you want VMM to use. As stated earlier, this should be a highly available SQL installation installed on a separate failover cluster from the cluster we are installing VMM on.

Use Domain Admin Credentials it should automatically Detect MSSQLSERVER in Instance Name and Click on Next.

15

Enter the service name for the VMM installation. Click Next

16

Click Select and search for your Service Account and enter the Password.  In the Distributed Key Management section enter the location of the DKM container in AD created earlier.

Add the Service Account to the Local Administrator Group.

1718192021

Done with the Installation on VMM Node 1 Click Close to Finish.

22

Start VMM Installation on Node 2.

Finally you need to install VMM on the second node in the cluster. To do this, log on to the second node and run the VMM installer.

You’ll be prompted to add this server as a node to the highly available VMM installation (you’ll obviously say you do).

You won’t have to enter the DKM information again (you’ll still have to enter the VMM service account password but not the username.

You won’t have to enter database information.

Below Snapshot is from the Database Configuration fron Node 2.

2324

Below Snapshot Either you can Create a Library or you can use the Existing one.

252627

To Connect to VMM Server you can either enter the Clsuter Role name for VMM server or the Active Node Name and Click Connect.

28

Below snapshot you can confirm both the VMM server’s.

29

That’s it!  You now have a highly available VMM environment to manage your Server 2012 R2 /Server 2016 Hyper-V Hosts.

Adding SCVMM 2016 Hosting to Studio

  • First Step is to Install SCVMM console on DDC.
  • This will allow me to add any machine I create through PVS via SCVMM to Machine Catalogs, and allow me to power manage those machines.
  • Open Citrix Studio, navigate to Configuration -> Hosting and then click Add Connection and Resources.

123

  • Fill in your connection details as per the below image.

4

  • Browse the Cluster you can use the Storage as per the availabilty.

5

  • Select Cluster

6789

  • Verify all your connection Details from the Summary

10

  • Verify the Connection.

11

  • Check if you are able to get the MCS option in the Machine Catalouge.

12

Setting up DKIM Keys for Highly-Available VMM 2016

Creating the Container in AD

  • Open the Active Directory Service Interfaces Editor(adsiedit.msc)
  • Right-click the ADSI Edit object in the left tree and select Connect To.
  • In most environments it should be sufficient to connect to the Default Naming Context, so the defaults are ok. Click Ok
  • Once connected, expand the connection object and then right click the domain’s container and select New > Object…

1

 

  • Provide a value for the name of the container

2

  • Select container as the class. Click Next

3

  •  Click Finish

4

  • Now the container is created but you will still need to take note of the distinguishedName property of the container and provide it to VMM during installation.

5

  • Right-Click the container and select Properties

6

  • Now provide this text string (“CN=SCVMM,DC=MSCLOUD07,DC=com”) to the VMM installer during VMM installation.

7

 

 

 

The configuration registry database is corrupt (0x800703F1).Error 2912 while VM template creation failed.

If you trying to Create A template and get’s the following error Message.

template deployment

Initially start the troubleshooting from the WinRm run the below command on the Host.

winrm set winrm/config @{MaxTimeoutms = “1800000”}

winrm set winrm/config/Service @{MaxConcurrentOperationsPerUser=”1500″}

net stop winrm

net start winrm

net start scvmmagent

Below also Could be the following reason’s.

Do not turn off the VM from the Hyper-V or SCVMM Console.

Gracefully Shutdown the VM from inside the VM and then Retry the Process.

Either the VM that you have deployed is the Syspred VM.

If you have configured Hyper-V Replica to use certificate based authentication over port 443.  SCVMM had also configured BITS to use certificate based authentication over port 443.  The result was that whenever SCVMM tried to use BITS to transfer a file – it would fail.

Fortunately – both BITS and Hyper-V Replica allow you to change the port that they use.  In my case I decided to change the port used by Hyper-V Replica from 443 to 444.  You can do this under the Hyper-V Settings:

Template1

 

Virtual machine creation fails when you try to deploy a virtual machine in Windows Azure Pack

When you try to deploy a virtual machine in Windows Azure Pack to a cloud that has a capability profile selected, virtual machine creation may fail, and you receive the following errors:

cloud

  • Log on to the System Center Virtual Machine Manager Admin console as an account that has administrative permissions.
  • Locate VMs and Services, select Clouds, and then select the cloud to which you are deploying.
  • Right-click the cloud, and then select Properties.
  • Select Capability Profiles.
  • Click to clear the check boxes for any profiles that are selected. Disabling all profiles enables deployment to any hypervisor.
  • Restart the deployment from WAP Portal.

Virtual Machine could not be started because the hypervisor is not running

hyper-v-error.jpg

Whenever I want to turn on any machine inside of Hyper-V, the following error message appears:

“Virtual Machine could not be started because the hypervisor is not running”

Whenever this happens, I run the following command:

bcdedit /set hypervisorlaunchtype Auto and reboot the Server. After a reboot, all Virtual Machines can be started without Problems.

The Hyper-V Virtual Machine Management service is set to Automatic.

Also try to change the valuve of hvservice from Regedit

Open Regedit

HKLM\SYSTEM\Current Control Set\Services\Hvservice change start DWORD value to “2”.

If you are Using Nested Virtualization.

Deploying Hyper-V over VMware Exsi check below update :-

Turn off the VM from the Vcenter

Go to Edit Setting from the VM go to option

Go to CPU/MMU Virtualization Enable VT-x and Intel APT/AMD

vmware intel

Upgrade the Hardware Version to 11 for ESXi 6.0 and 13 for ESXi for 6.5

  1. Start the vSphere Client or vSphere Web Client and log in to the vCenter Server.
  2. Select the host or cluster that contains the virtual machines to upgrade.
  3. Click the Virtual Machines tab.
  4. Select and power off the virtual machines to upgrade.
  5. Right-click your selections.
  6. Select Upgrade Virtual Hardware and click Yes.
  7. Power on the virtual machines.