Microsoft released Update Rollup 2 for System Center 2012 Service Pack 1 which includes updates for the System Center Suite. Get more information about the Update Rollup 2 for System Center 2012 Service Pack 1 on support.microsoft.com.
If you are running Windows Server 2012 Hyper-V hosts and you are managing them with System Center Virtual Machine Manager 2012 SP1 and you are running VM Networks with Network Virtualization you can get the following error when you try to deploy a new Virtual Machine to the Hyper-V host.
“Windows network virtualization is not enabled on a host NIC available for placement”
This happens if:
You create a Logical Network with Network Virtualization enabled
You add the Logical Network to a Host Adapter or a Logical Switch on the Hyper-V host
You create a Isolated VM Network
Deploy a new Virtual Machine with the VM Network.
Enable the Windows Network Virtualization Filter driver on the Hyper-V host
Windows Network Virtualization Filter driver
If you are running this on a Team you have to enable the Windows Network Virtualization Filter driver on the Network Adapter Team.
In System Center 2012 Virtual Machine Manager was a cool new feature which allowed you to show the installed version of the Hyper-V Integration Services. In the normal Hyper-V Manager or Cluster Manager it was not possible to show the installed version. In Windows Server 2012 Hyper-V this has not changed, there is no GUI option to show the installed version, but there is Windows PowerShell. With the simple Get-VM cmdlet you can show the version of the Hyper-V Integration Services.
To use the Logical Networks in System Center Virtual Machine Manager 2012 on a specific Hyper-V Host or Hyper-V Cluster you have to add the Logical Network to the network interface which the logical network is available. In the GUI you can do this in the properties of the Hyper-V host under Hardware.
if you have a lot of Hyper-V hosts this can take some time. This Windows PowerShell script will help you. It will add the logical network on each Hyper-V host. It chooses the network adapter based on the network adapter name which is given on the Hyper-V host.
One week after the release of the Windows Server 2012, Microsoft released the Beta of System Center 2012 SP1 which brings support for the new features in Windows Server 2012 and Windows 8. The Beta includes System Center Virtual Machine Manager 2012 SP1 and System Center Data Protection Manager 2012 SP1.
System Center Virtual Machine Manager brings a cool new feature called Bare Metal Deployment. This feature allows deploying new Hyper-V hosts via Out-of-Band Management (IPMI or SMASH) with the Virtual Machine Manager. In my lab environment I use Cisco UCS C200 M2 servers as my Hyper-V servers but this guide will also work with servers from other vendors such as HP, IBM or Dell.
SCVMM boots up Bare-Metal Server via OBM
Send PXE Boot requests
WDS asks SCVMM for authorize PXE boot
Boot Windows PE
Run pre GCE scripts to configure Raid and other settings
Copy the VHD from VMM Library
Run post GCE scripts to do additional configurations