In the previous blogs I have explained how to create Run As Accounts & Profiles. I also discussed Out of Band Management and specifically how to Add the HP iLO2 OOB provider to SCVMM 2012. In this blog I focus on another preparatory step before we can start our Bare Metal Deployment and Cluster Creation: Preparing the Host Profile.
The Host Profile is like a combination of the Hardware Profile and OS Profile in SCVMM 2008 R2 but intended for defining the physical server rather than the virtual machine. Again a wizard is available to define such a Host Profile which is relatively straightforward:
- General: Host Profile Name & Description plus location of the VHD file to be used as the base image for the operating system
- Hardware Configuration: Selection of the Management NIC with a choice of DHCP or static IP address; Partition and Disk Configuration and Driver Options (for injection of a specific set of (filter) drivers
- OS Configuration: similar to the OS Profile in SCVMM 2008 R2 describing OS name, Run As Profile, Admin Password, Identity Information, Product Key, Time Zone and Scripts
- Host Settings: for adding the virtual machine placement paths
The preparation of the Host Profile starts off by clicking on the Library wunderbar, expanding Profiles and right-clicking Host Profiles: Create Host Profile.
Supply a clear and standardized name to the Host Profile. I’d suggest defining these kind of names in your design because naming can become quite a mess if you don’t. Anything goes as long as it is standardized and the name is meaningful if you look at it a couple of months later. Of course a clear description will help you too.
Please also note that the VHD file must contain a version of Windows Server 2008 R2 because the OS must support boot from VHD. This VHD can be created by running the System Preparation Tool (Sysprep.exe) on a Windows Server 2008 R2 or later virtual machine.
The next step in the wizard defines how the bare metal server will be configured. The easiest way is to obtain an IP address through the DHCP service. However in this example I wanted to find out how the new logical network concept in SCVMM 2012 worked. Under Fabric | Networks we can now define one or more logical networks with pre-defined subnets, VLANs and IP-pools that allow for checking out and checking IP address. Much like a DHCP server for static IP addresses. I have expressed this wish for a centralized and flexible network configuration for Hyper-V hosts to the responsible developer teams in the past two years and …. Yes, they’ve listened! What I still don’t know of course is how this will interact with Hyper-V vNext. I still sincerely hope that configuration of high available/teamed networks will be part of the new product and that we can configure them easily from SCVMM 2012.
As you can see in the following screenshot, I have prepared a few logical networks. In the Host Profile I will use the Backend network configuration for the primary connection of the Hyper-V hosts to the network. The idea is that the bare metal server will boot from a Windows Deployment Server (WDS/PXE), get a DPCP address, configures the profile and finally receive a static IP address from the IP pool. Manual intervention should no longer be necessary.
You might well ask yourself: “What if I have a server with eight NIC’s? Which one will it take?” The SCVMM team thought of that too as we will see in the next blog.
The following sub-step in the Hardware configuration part of the New Host Profile Wizard is the definition of partitions and disks. Be aware that Microsoft has chosen to use the Boot from VHD method for deploying bare metal servers. But before a VHD can be deployed, at least one disk and partition must be configured. The disk type can be selected (MBR/GPT), the volume can be labeled, the partition type can be selected and either all remaining free disk space or a set amount of disk space can be configured. Of course Make this the boot partition must be checked for the first disk that is defined.
The last step in the hardware configuration depends on your server hardware or specific storage requirements. By default, Virtual Machine Manager injects all drivers that match the Plug and Play (PnP) IDs discovered on the target physical computer. If on the other hand you want only desired drivers to be applied to the operating system, you can add a list of tags.
Next we define the OS configuration. If you have worked with SCVMM 2008 R2 this will be mostly familiar. Only the RunAs profile is new and saves you an extra authentication step.
The Host settings completes the preparation of the Host Profile. In this list you can add one or more default locations for virtual machine placement to be used by the Hyper-V hosts.
In the next blog we will arrive at our real goal for all these blogs: the Bare Metal Configuration of one or more physical servers. Please join me later for the next blog in the sequel.