When i take a look at the event log on the node i try to add, it seem that the VMM query generate a 5605 evt.

Does someone allready add 2008 R2 SP1 cluster to VMM 2012 SP1 successfully ?

Standalone host is added with no problem (just a message about MPIO that can be ignored).

Here the Msg in the cluster node

Access to the root\mscluster namespace was denied because the namespace is 
marked with RequiresEncryption but the script or application attempted to 
connect to this namespace with an authentication level below Pkt_Privacy. 
Change the authentication level to Pkt_Privacy and run the script or 
application again. 

Thanks for Help

Ced.

I have two domains/forests, with a two way Forest trust, users in domain B can authenticate in domain A and users in domain A can authenticate in domain B. I have a Hyper-V cluster setup in domain A working perfectly well, however in domain B, I have SCVMM 2008 R2 and I try to add the Hyper-V cluster in domain A, but it fails. 

When adding the cluster to SCVMM, the box is ticked for host is in a trusted domain, I enter an account with permissions on domain A, which is a domain admin account, and the SCVMM service is running as a domain B account, which is a member of the local administrators group on all the domain A cluster nodes, and has also got full cluster permissions. 

I might say that I have managed to get this to work if the SCVMM service account runs with a domain A account which is a member of the local administrators group on all the domain A cluster nodes, and has also got full cluster permissions.

Running the SCVMM service as local system doesn't work either.

I would like to know the correct way to setup the permissions, I don't want to have the SCVMM service running with another domain account.

Here are the errors I am getting. DNS is all setup and is running perfectly.

Error (2917)

Virtual Machine Manager cannot process the request because an error occurred while authenticating DC-AU-HV-01.domain.local. Possible causes are:

1) The specified user name or password are not valid.

2) The Service Principal Name (SPN) for the remote computer name and port does not exist.

3) The client and remote computers are in different domains and there is not a two-way full trust between the two domains. 

 (The network path was not found (0x80070035)) 

Recommended Action

Log in by using an account on the same domain as the VMM server, or by using an account on a domain that has a two-way full trust with the domain of the VMM server, and then try the operation again. If this does not work, purge the Kerberos tickets on the VMM server by using kerbtray.exe, available at http://go.microsoft.com/fwlink/?LinkId=93709. Then, reset the SPN for DC-AU-HV-01.domain.local by using setspn.exe available from http://go.microsoft.com/fwlink/?LinkId=93710. If this still does not fix the problem, make DC-AU-HV-01.domain.local a member of a workgroup instead of a domain, restart the computer, rejoin the domain, and then try the operation again.

When I configure a Hyper-V host system in SCVMM 2012 SP1 (add the configured logical switch, add virtual adapters on the host system for LiveMigration and Cluster network) and want to add this host to an existing Hyper-V R3 cluster with the exact same configuration regarding the logical switch that is used and the virtual network adapters, I still get the following error in SCVMM 2012 SP1:

Error (25343)
No network adapter found on host <FQDN of hyper-v host system that is trying to join the cluster> that matches cluster virtual switch vSwitch.

Recommended Action
Please add a network adapter to the host and set the Logical Networks on the adapter to match the cluster network.

This error doesn't make sense because I created the logical switch on this host with the name vSwitch.

Anybody any ideas or can this be reported as a bug?


Regards
Stijn

Having added existing cluster to VMM 2012 but shared storage wasn't recognized. Is it possible to resolve this issue?

I can't recreate cluster from scratch like  http://social.technet.microsoft.com/Forums/en-US/virtualmachinemgrclustering/thread/9492b916-0ac9-4279-8fba-7acbd0a77aef

We are finding that SCVMM 2012 SP1 has been renaming our VMs to  'SCVMM VM-NAME Resources' when we migrate through SCVMM 2012 SP1 from standalone Windows Sever 2008 R2 severs running Hyper-V. This is extremely frustrating as the VM's have been given unique names for a reason and it is impossible to find what you are looking for when they are named like this.

In addition, the new names show up like this in DPM 2012 SP1 which is terrible for finding what you are looking for. Nothing like having several hundred VMs that start and end with the same name. Also, it makes the names to long!

After renaming the VMs back through the Windows Failover Cluster Manager, it throws DPM into a frenzy and SCVMM 2012 SP1 no longer thinks they are Highly Available which is what probably causes the issues for DPM. We are able to fix this by migrating the VM to a new host but that should not be needed.

Also, after the renaming, DPM will have the old names as destination options when you are trying to restore a VM. The destinations should be queried from the available hosts not from the list created in DPM which does not seem to be the case. There is a table in DPM where you can remove these but I was warned not to touch them.

If the VM is created from the Windows Failover Cluster manager the name is correct and shows correctly in SCVMM 2012 SP1 to begin with and doesn't add 'SCVMM' as a prefix and 'Resources' as a suffix.

The VM names should be consistent regardless of where is was created. SCVMM should respect the given names and not mess with them.

This is so frustrating and we are looking for a fix.

Hopefully this is as simple as a registry change on the SCVMM 2012 SP1. We are waiting until this is addressed before using the product.

Hello Error,

Can someone please help me with this error: ?  I need to create a virtual switch for a new host (2008 R2) to the cluster from within SCVMM 2012 SP1.

(26895)
Cannot change setting AutomaticVirtualNetworkCreationEnabled (Automatic creation of virtual switches) to true as VMM no longer automatically creates virtual switches.

Recommended Action
Do not set the AutomaticVirtualNetworkCreationEnabled (Automatic creation of virtual switches) to true.

thanks

Ron

Ron Finnegan DHHS NIH NIMH LNT

I need some troubleshooting help on a Hyper-V cluster. I have 4 Dell Hyper-V Hosts running Server 2012 Datacenter and a Equal Logic SAN (Firmware 6.0.6). All the Hyper-V Hosts are clustered together and the Dell SAN is setup as a Cluster Shared Volume. The servers and SAN are networked together with Cisco 3750X switches. When I try to run a Live Migration of a guest VM from one Host to another (Node A to Node B), the Migration starts and as it gets to the final sync/cut over to the receiving Host (Node B), the first host (Node A) seems to pause all the guest VMs running on Node A, not just the one I am migrating. To control the hosts I am using System Center VMM 2012 SP1 Rollup 3. I am unsure how to troubleshoot this. Does anyone have any tips?

Hi. I have a HA file share that serves as library share for VMM 2012 SP1. It seems to be working fine, but on my management server where I have the VMM console installed and on the node that is the owner of the fileshare cluster resource (no errors on the non-owning node), eventlog is being spammed by the following events:

EventID:6, Source: SMBWitnessClient: "Witness Client failed to find a Witness Server for NetName \\havmmlib with error (Element not found.). Retrying in (60) seconds."

EventID:6, Source: SMBWitnessClient: "Witness Client failed to find a Witness Server for NetName \\havmmlib.domain.local with error (Element not found.). Retrying in (60) seconds."

havmmlib is the clustered DNN. Two node cluster with a disk as witness.

I've tried searching on the Internet for errors related to SMBWitnessClient, but there's not much out there.

Any ideas?

We are running SCVMM 2012 SP1 UR3 with Win2012 Hyper-V nodes. We have a ScaleOut 2012 SMB 3.0 file servers.

Everything has been running great.... until we tried to add two mode nodes to an existing cluster.

Basically the two added nodes report that they have no file share registered (confirmed via Hyper-V node properties and also Get-SCStorageFileShare -VMHost xxxx command). Running Repair-SCStorageFileShare against the cluster does not seem to make a difference.

Checking the permissions on the ScaleOut File server shows that the permissions for the two new nodes have been added. However SCVMM think that these two nodes have no file shares registered... which mean we will run into issues the minute we migrate VMs to these systems.

Has anyone seen this before? Removing and re-adding the cluster from SCVMM is not an option as we are using XenDesktop 7.0. Doing so would create a lot of issues.

Thanks - Didier.

Hi!

I have a bunch o logical networks and IP Pools. I need to determine and configure one network for cluster, one for live migrations and one for management. Problem is, than I don't know where in VMM I should configure each network for specific purpose. I couldn't find it in cluster configuration and even after.

Thanks for help

Hi,

Is Hyper-V Live Migration compatible with Hyper-V Replica/Hyper-V Recovery Manager?

I have 2 Hyper-V clusters in my datacenter - both using CSVs on Fibre Channel arrays. These clusters where created and are managed using the same "System Center 2012 R2 VMM" installation. My goal it to eventually move one of these clusters to a remote DR site. Both sites are connected/will be connected to each other through dark fibre.

I manually configured Hyper-V Replica in the Fail Over Cluster Manager on both clusters and started replicating some VMs using Hyper-V Replica.

Now every time I attempt to use SCVMM to do a Live Migration of a VM that is protected using Hyper-V Replica to another host within the same cluster, the Migration VM Wizard gives me the following "Rating Explanation" error:

"The virtual machine virtual machine name which requires Hyper-V Recovery Manager protection is going to be moved using the type "Live". This could break the recovery protection status of the virtual machine.



When I ignore the error and do the Live Migration anyway, the Live migration completes successfully with the info above. There doesn't seem to be any impact on the VM or it's replication.

When a Host Shuts-down or is put into maintenance, the VM Migrates successfully, again, with no noticeable impact on users or replication.

When I stop replication of the VM, the error goes away.

Initially, I thought this error was because I attempted to manually configure the replication between both clusters using Hyper-V Replica in Failover Cluster Manager (instead of using Hyper-V Recovery Manager).

However, even after configuring and using Hyper-V Recovery Manager, I still get the same error. This error does not seem to have any impact on the high-availability of my VM or on Replication of this VM. Live migrations still occur successfully and replication seems to carry on without any issues.

However, it now has me concern that Live Migration may one day occur and break replication of my VMs between both clusters.

I have searched, and searched and searched, and I cannot find any mention in official or un-official Microsoft channels, on the compatibility of these two features. 

I know vMware vSphere replication and vMotion are compatible with each otherhttp://pubs.vmware.com/vsphere-55/index.jsp?topic=%2Fcom.vmware.vsphere.replication_admin.doc%2FGUID-8006BF58-6FA8-4F02-AFB9-A6AC5CD73021.html.

Please confirm to me: Are Hyper-V Live Migration and Hyper-V Replica compatible with each other?

If they are, any link to further documentation on configuring these services so that they work in a fully supported manner will be highly appreciated.

D

I realize that this is a repeated question. I write because I am surprised that VMM 2012 SP1 would call my situation "over-committed".

I have two blades, each with 16 cores and 256GB RAM. They run Server 2012 Core. I haven't changed any settings as far as reserves go, so the reserve nodes = 1.

On this failover cluster, I have four VMs. VM1 has 4 procs, 4GB RAM. VM2 has 4 procs, 2GB. VM3 and VM4 have 4 procs, 8GB.

How would this be overcommitted? Using the slot method, it should be three slots of 8GB, which is 10% of the total RAM on either blade. Is there anything else besides RAM that the over-commit checks for?

Looking for the "definitive" answer here about CSV volumes in 2012 and 2012 R2 and the ability to manually create/delete directories and copy VHD/VHDX files into and out of them. In 2008 R2, there was a big message about not touching these volumes unless you are using some sort of Hyper-V management tool. The problem is that is just not practical. Yes, we can take the CSV off in maintenance mode, but in a large shop, with many admins, that is not feasible not to say the production implications.

So ... Microsoft, can we delete/create directories and copy VHD/VHDX files on 2012 and 2012 R2 CSV volumes? If not, what are the implications of accidentally having created a directory here and there on CSV? If we did accidentally do such an act, is there a way to validate whether the CSV is still in-tact (is chkdsk enough)? I wouldn't want to experience latent data corruption simply because an admin accidentally created a directory on a CSV volume through explorer.

DPR

hi folks...............i need ur urgent help..........

i have 2 windows 2012 HyperV fail over server cluster.............

now i need to create 40 VM's on my cluster............

so my problem is what is Microsoft Best practice to do so.........

should i create only one CSV volume to create all my VM's??????????

or i should make separate CSV volumes for group of VM's??????????

i have also SAN where i will create the CSV Volumes in Dell Equallogic box.......

also can u plzzzzzzzzz give me any web link to know how to migrate physical server to vm's ????????

i have 4 windows server 2008R2 which i need to migrate to VM's in my 2012 windows server HyperV cluster........

thnx ............

istiaq

Hi all,

I am running a fail over cluster of

Host:
2 x WS2008 R2 Data Centre

managed by VMM:
VMM 2008 R2

Virtual Host:
1x windows 2003 64bit guest host/virtual machine

I have attempted a live migration through VMM 2008 R2 and im presented withe the following error:

Error (10698)
Virtual machine XXXXX could not be live migrated to virtual machine host xxx-Host01 using this cluster configuration.
 (Unspecified error (0x80004005))

What i have found when running the cluster validation:

1 out of the 2 hosts have an error with RPC related to network configuration:

An error occurred while executing the test.
Failed to connect to the service manager on 'xxx-Host02'.
The RPC server is unavailable

However there are no errors or events on host02 that are showing any probelms at all.
In fact the validation report goes on to showing the rest of the configuration information of both cluster hosts as ok.

See below:

 
--------------------------------------------------------------------------------

List BIOS Information
List BIOS information from each node.

xxx-Host01
Gathering BIOS Information for xxx-Host01
Item  Value 
Name  Phoenix ROM BIOS PLUS Version 1.10 1.1.6 
Manufacturer  Dell Inc. 
SMBios Present  True 
SMBios Version  1.1.6 
SMBios Major Version  2 
SMBios Minor Version  5 
Current Language  en|US|iso8859-1 
Release Date  3/23/2008 9:00:00 AM 
Primary BIOS  True 

xxx-Host02
Gathering BIOS Information for xxx-Host02
Item  Value 
Name  Phoenix ROM BIOS PLUS Version 1.10 1.1.6 
Manufacturer  Dell Inc. 
SMBios Present  True 
SMBios Version  1.1.6 
SMBios Major Version  2 
SMBios Minor Version  5 
Current Language  en|US|iso8859-1 
Release Date  3/23/2008 9:00:00 AM 
Primary BIOS  True 

Back to Summary
Back to Top

--------------------------------------------------------------------------------

List Cluster Core Groups
List information about the available storage group and the core group in the cluster.
Summary 
Cluster Name: xxx-Cluster01 
Total Groups: 2 
Group  Status  Type 
Cluster Group  Online  Core Cluster 
Available Storage  Offline  Available Storage 

 Cluster Group
Description:
Status: Online
Current Owner: xxx-Host01
Preferred Owners: None
Failback Policy: No failback policy defined.
Resource  Type  Status  Possible Owners 
Cluster Disk 1  Physical Disk  Online  All Nodes 
IP Address: 10.10.0.60  IP Address  Online  All Nodes 
Name: xxx-Cluster01  Network Name  Online  All Nodes 

 
 Available Storage
Description:
Status: Offline
Current Owner: Per-Host02
Preferred Owners: None
Failback Policy: No failback policy defined.
 Cluster Shared Volumes
Resource  Type  Status  Possible Owners 
Data  Cluster Shared Volume  Online  All Nodes 
Snapshots  Cluster Shared Volume  Online  All Nodes 
System  Cluster Shared Volume  Online  All Nodes 

Back to Summary
Back to Top

--------------------------------------------------------------------------------

List Cluster Network Information
List cluster-specific network settings that are stored in the cluster configuration.
Network: Cluster Network 1 
DHCP Enabled: False 
Network Role: Internal and client use 
Metric: 10000 

Prefix  Prefix Length 
10.10.0.0  20 

Network: Cluster Network 2 
DHCP Enabled: False 
Network Role: Internal use 
Metric: 1000 

Prefix  Prefix Length 
10.13.0.0  24 

Subnet Delay  
CrossSubnetDelay  1000 
CrossSubnetThreshold  5 
SameSubnetDelay  1000 
SameSubnetThreshold  5 

Validating that Network Load Balancing is not configured on node xxx-Host01.
Validating that Network Load Balancing is not configured on node xxx-Host02.
An error occurred while executing the test.
Failed to connect to the service manager on 'xxx-Host02'.
The RPC server is unavailable

Back to Summary
Back to Top

If it was an RPC connection issue, then i shouldnt be able to mstsc, explorer shares to host02. Well i can access them, which makes the report above is a bit misleading.

I have also checked the rpc service and it has started.

If there is anyone that can shed some light or advice me oany other option for trouble shooting this, that would be greatley appreciated.

Kind regards,

Chucky

Dan Gleason

Hi,

I am trying to install SCVMM 2012 with R2. I have installed fail over cluster feature on windows server 2012 R2.

During the installation of SCVMM , i have received following error;

'Creation of the VMM resource group vmm2012cluster failed.Ensure that the group name is valid, and cluster resource or group with the same name does not exist, and the group name is not used in the network;.

please guide how to resolve this.

i installed the SCVMM 2012 version 3.0.6019.0.

When i use the Create Hyper-V Cluster under Fabric page to create a Cluster.

the Create Cluster Wizard doesn't have the IP Address page to let me input the IP for the Cluster.

after i answer all the wizard, the Install Cluster job shown Error 25325

The cluster creation failed because of error At least one IP address needs to be configured..

so, how to solve it?

thanks alot.

Im trying to configure connections for windows server gateway network service in VMM. WSG is HA hosted on HA Hyper-V cluster. All Network Service tests passed successfully. Im able to configure the Front End Connection but for the Back End interface im receiving the following error:

Error (21426)
Execution of Microsoft.SystemCenter.NetworkService::InstallDeviceConnection on the configuration provider 4ee559f1-f479-480c-9458-d14b8b1c1779 failed. Detailed exception: Microsoft.VirtualManager.Utils.CarmineException: Unable to set up Remote Access server to support multi-tenancy mode. (The WS-Management service cannot process the request. The WMI service or the WMI provider returned an unknown error: HRESULT 0x800713be ).
Fix the issue in Remote Access server and retry the operation.

Recommended Action
Check the documentation for the configuration provider or contact the publisher support.