I believe in Hyper-V!

SCVMMCategory Archives

Delete obsolete virtual networks with dependency in VMM 2012 SP1

Few days ago I modified network settings on one of Hyper-V hosts and also migrated two of VMs to another Hyper-V host. After VMs migration and changed network settings on the Hyper-V everything has been working like a charm! After I do that, on the Virtual Machine Manager I noticed that two network adapters are still there regardless of what no longer exist in Hyper-V host. That isn’t a problem, right click on VM Network and Logical Networks, and that’s it, but…!? When I tried to delete obsolete virtual network got error that have dependent resources on that VM Network like in the picture below.


In other words; when I migrate VMs from one Hyper-V host to another VMM didn’t “release” VMs from VM Networks. I’m sure that everything what I done, I did in the right way!
When opened View Dependent Resources I saw two migrated VMs and connected checkpoints.


The same dependencies are on the Logical Networks


In the next couple of hours I tried to figure out how to solve the problem! In the pictures below is few examples what I tried to do.

Tried to delete through PowerShell.


Tried to change all .xml configuration file related to VMs


At the end, what did I do? It’s simple but it’s manual work!

Step 1

Export VMs


Step 2

Delete exported VMs through Virtual Machine Manager


Step 3

Remove Virtual Network from the VM Networks and from the Logical Networks


Step 4

Import VMs



We are done!

Enjoy in day ;)


Issue with Migration of Virtual Machines |System Center 2012 SP1 Virtual Machine Manager|

Today I tried migrate virtual machine from one stand alone Hyper-V host to another through System Center 2012 SP1 Virtual Machine Manager and got errors like in the picture below.
The first error was: The credentials supplied to the package were not recognized…
and the second was: Live Migrating Hyper-V virtual machines may fail with error 0x80070569


After a little of investigation I found resolution on Ben Armstrong blog and on Microsoft support site. So, what we have to do?

1. Step
– Open Properties on the Hyper-V host
– Go to the Host Access
– Add Run As account created earlier


2. Step
– On the Domain Controller create new GPO with the parameters like in the picture below and Link in OU where your Hyper-V hosts are.


– Update group policy on every Hyper-V host | gpupdate /force |. (You may need to wait several minutes for Active Directory replication to occur).


We are done! Open VMM Console and migrate VMs as you wish.



Voila, VM is migrated. Of course, migration time depends on the virtual machine size.

Enjoy in day!


Microsoft Hyper-V Server 2012–installation and configuration

I this blog post I’ll describe how to install and configure Microsoft Hyper-V Server 2012 from the scratch.
Why I chose to use Hyper-V Server 2012 in my production environment?
1. It’s free!
2. Less maintenance!
3. We don’t need to restart the host so often for the updates!
4. Performance and security reasons!

In this scenario I have HP ML 350G6 with 2 CPUs 32GB of RAM and 3TB disk.
HP have a great tool called HP SmartStart CD with integrated drivers and other tools required for server management, but in this case doesn’t work because WS 2012 and Hyper-V 2012 is not covered. I used this tool to create RAID array.


How do I integrate the drivers, (network, storage, etc…)? I used Windows Assessment and Deployment Kit software.




After a very short time, my Hyper-V Server 2012 is up and running.

When Hyper-V Server 2012 console appears you can to configure Domain, Computer Name, Remote Management, Network Settings and so on….
If you don’t like command line you can use Hyper-V management console or even better Virtual Machine Manager console to connect to your Hyper-V Server 2012.
Of course, there are third-party tools, like 5nine, vtUtilities… that can maintain Hyper-V Server remotely.

Few words about Hyper-V Server 2012.
Hyper-V Server is a dedicated stand-alone product that contains the hypervisor, Windows Server driver model, virtualization capabilities, and supporting components such as failover clustering, bud doesn’t contain the robust set of features and roles as the Windows Server operating system.
Differences between Microsoft Windows Server 2012 with Hyper-V role installed and Hyper-V Server 2012:
– There is no GUI. You use PowerShell, SConfig, or remote administration to manage the machine.
– There are no free virtualization rights to install Windows Server in guest OS’s on this machine. This means it is good for labs, VDI, Linux hosting and upgrading older hosts without SA.
– It is stripped down so it is just a Hyper-V host and nothing else.

I hope that you will enjoy in Windows Hyper-V Server 2012 Winking smile