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.