At customer location we're using multiple Hyper-V hosts, managed by a System Center Virtual Machine Manager (SCVMM) server. On multiple Virtual Machines (VM's) we like to deploy a server operating system with ConfigMgr. Trick is, when booting Hyper-V VM's from a PXE server, nothing seems to happen. Within Hyper-V Manager > BIOS config, the "Legacy Network adapter" is on top. Just have a look at the comment: "Use a legacy network adapter to perform a network-based installation of the guest operating system."
Because "Legacy Network adapter" is displayed here, we're thinking that the right network adapter is installed in the VM. Unfortunately this is not the case. Within VM properties in SCVMM there's a choice to use a network adapter or legacy network adapter. By default the network adapter is installed. With this network adapter no PXE boot can be done. Just delete this network adapter or choose "not connected" and add a new legacy network adapter.
After that PXE boot is working immediately. Just remember the following: Hyper-V supports booting a VM from the network using the F12 option. Trick is that you must use the legacy network adapter. The regular network adapter is synthetic and therefore not available at boot time. You have to remove the existing network adapter and add a new legacy network adapter. With that you're done!
Today I want to install the System Center 2012 suite again with RTM version. Before I started the Virtual Machine Manager (SCVMM) must be upgraded from the RC to RTM version. This because my RC installation is expired (180 days evaluation) and cannot be used anymore. The following error message is displayed:
A default upgrade from SCVMM RC to RTM is not possible because it's not supported. The following error message is displayed then:
Microsoft has a SCVMM upgrade tool available for doing this. It can be requested HERE Best thing is to open a support incident via the web for free usage. In my case the upgrade tool was available within one (1) hour!
Just follow the steps described in the e-mail message which is send by Microsoft. The most important ones are in this blog post also.
First make sure no open connections are available to SCVMM. Also have a look at which service account is used for the VMM service. Then click uninstall, choose remove features and select the necessary modules. In my case I selected VMM Management Server, VMM Console and VMM Self-Service Portal. On the Database options page make sure to choose Retain Data.
After uninstalling, which takes a few minutes, the database must be upgraded from RC to RTM version. This can be done with the UpgradeVMM2012RC.exe tool, send by Microsoft. With UpgradeVMM2012RC.exe /? you can see what different parameters you can use. The command I used here is showed in the picture. Good news: The upgrade successfully completed!
Now it's time to install SCVMM again. Just start the RTM setup and specify the VMM database retained from the RC installation. Also the Service account used for the VMM service must be filled in again. Select all the components to install the SCVMM RTM version.
When an error message is displayed that the upgrade cannot be done, make sure that all VMM RC components are uninstalled before. It's also possible that an error message is displayed that the VMM Library share already exists. Just remove the share before starting setup again.
After that the Setup completed successfully! Now it's time to look at new functionality and update the existing VMM Agents.
