Musings of a PC

Thoughts about Windows, TV and technology in general

SCVMM 2012: Preparing for Bare Metal Deployment, part 2

In part 1, I went through the steps required to quickly add a copy of Windows Server 2008 R2 SP1 as a deploying image.

In this part, I’m going to look at the Add Resource Wizard, which finds bare metal servers on the network and allows you to specify provisioning information. Some sections of this wizard require other information to have been created beforehand (e.g. Run As accounts, Host Profile) so I’ll go through those steps first.

Creating a Bare Metal Run As account

This is done by going to the Settings section of the console and clicking on Create Run As Account.

image

Specify a name for the account – one that is meaningful to you – along with an optional description. Set the category to BMC Account (for bare metal) and then enter the user name and password. Turn off Validate credentials. Click Next twice and then click Finish.

Creating a Host Profile

To create a host profile, go to Library and then click Add > Host Profile:

image

In the New Host Profile Wizard, enter a name and optional description for this host profile and click Next:

image

On the next page, select the OS image. This can be, for example, the Windows Server VHD that was created in the previous blog posting.

image

On the next screen, you need to make some hardware configuration decisions:

image

For the network adapter, you can choose either to obtain an IP address through the DHCP service or allocate a static IP from one of the logical networks you might have defined. I don’t want this blog posting to get too “nested” in setting things up, so I’ll cover network definitions another time.

For the drives, you can choose the partitioning scheme (MBR or GPT) and how much of the drive will be used for the OS.

Finally, you can exercise some control over driver injections but I’m going to leave it on the default.

On the OS configuration screen, more decisions need to be made:

image

You need to specify a domain for the server to join and a Run As account to be used to establish that domain join.

You need to specify a local administrator password for the server.

You need to specify identity information – the full name and organisation name that is required by Windows upon installation.

You need to specify the product key. I’m going to leave this blank as I use volume licensing media and the server should gets its key from the key management service we run.

You need to set the time zone.

Finally, you can run commands the first time a user logs on, but I’ve left that blank.

On the Host Settings page, you can specify placement paths for the virtual machines:

image

Phew! That’s it. Click Finish and the host profile is created.

Adding a Physical Host to SCVMM

From the main console, in Fabric view, choose Add Resources > Hyper-V Hosts and Clusters:

image

In the Add Resource Wizard, select Physical computer to be provisioned into Hyper-V hosts and click Next:

image

On the Credentials and protocol page, you have a couple of things to specify:

image

For the Run As account, you need to browse and pick an account that you have previously defined. When you click Browse in the Credentials and protocol page, you should see all of the BMC accounts you have created. Pick the one that is relevant to the server(s) that you want to add.

For protocol, you’ve got a choice of IPMI, DCMI and SMASH. Dell supports IPMI for their DRAC cards but note that you may need to reconfigure the DRAC card to allow IPMI over LAN.

On the next window, either specify an IP subnet for SCVMM to scan, or an IP range:

image

If everything works properly, when you click Next, you should see some servers:

image

Select the server(s) that you want to add and click Next.

image

On the Provisioning options screen, you will need to have already defined a host profile (see earlier in this post for details). In my scenario, my host profile uses DHCP to get its IP address. If the host profile uses static IP addresses from one of the logical networks, it will be necessary to provide additional information about the NIC hardware on the server so that the correct NIC is configured for management purposes.

On the final screen, Deployment customization, you may initially be thrown by the warning of missing settings:

image

Not to worry, though. All that is missing is the host name. Simply highlight the server and type in the computer name. When you click Next, you’ll get one final warning:

image

Click OK and then Finish to close the Add Resource Wizard. The jobs window will then appear and you can select the Create a new host from physical machine job to get more detail on the progress being made:

image

In my scenario, I’ve just realised that I need to build out some more infrastructure. Step 1.2.4 isn’t going to get very far because it says “Waiting for physical machine to PXE boot” and I don’t have a PXE boot server.

Time to do some more infrastructure building …

Advertisements

2 responses to “SCVMM 2012: Preparing for Bare Metal Deployment, part 2

  1. Pingback: SCVMM 2012: Bare Metal Deployment « Musings of a PC

  2. Pingback: SCVMM 2012: Preparing for Bare Metal Deployment, part 3 « Musings of a PC

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: