70-247 Series: Part 24
Configure and Deploy Virtual Machines and Services (17%)
Configure Profiles
Host Profiles
Host Profiles are used to standardise the deployment of Hyper-V hosts. The deployment of an operating system to a computer that does not have an operating system installed is typically referred to as "Bare-Metal Deployment" Host Profiles contain settings such as:
- The location of the Operating System image
- Hardware settings
- Operating System configuration settings
Before creating a host profile, the following prerequisites should exist in the library:
- A generalised virtual had disk must exist in a library share
- All drivers required for the physical hardware
The GUIRunOnce Commands can be used to configure the host operating system. Remote Desktop can be enabled and additional static IP addresses can be configured. Scripts can also be run after install by right-clicking the host in the fabric and selecting Run Script Command.
Guest Operating System Profiles
A Guest Operating System Profile specifies the operating system settings that you want the virtual machine to use when the virtual machine is created and deployed. A Guest Operating System Profile contains the following settings:
- Profile Name
- Computer Name - Use @Name@ to prompt for a name or Server### to use an auto-incrementing name
- Local Administrator Password
- Product Key
- Operating System
Create a Guest OS Profile
I'm going to create a Guest OS Profile for App Controller Servers. These servers have some specific requirements that I'll need to configure including:
- A specific Computer Name
- Software Prerequisites
In the Library workspace, click Create and select Guest OS Profile
You can complete each tab in the Profile. In the example below, I have configured an auto-incrementing name with the prefix APPCTR
In the example below, I am configuring the Operating System prerequisites for App Controller. These Roles and Features will only apply if the Virtual Machine Template is deployed as part of a service.
Capability Profiles
A Capability profile specifies limits and constraints of Hypervisors so that a hardware profile cannot have settings that are not able to be used on a given Hypervisor.
Create a Hardware Profile
I'm going to create 3 hardware profiles. They will be:
- Bronze - 1vCPU 1GB RAM
- Silver - 2vCPU 2GB RAM
- Gold - 4vCPU 4GB RAM
Hardware Profiles
A Hardware Profile specifies the hardware specifications for a Virtual Machine. Hardware profiles include the following settings:
- Number of processors
- Amount of static or dynamic memory
- Logical Network settings
- Highly-Available (HA) configuration
In the Library workspace, click create and then select Hardware Profile
Enter a Name and then select the Hardware Profile tab
Select the relevant tabs to configure the hardware profile
In the example below, I have removed the Legacy Network Adapter and added a Network Adapter. I've also connected it to a logical network and selected that it will receive a static IP Address from a Pool I have previously configured.
In the example below, I am configuring the Silver Hardware Profile
In the example below, I am configuring the Gold Hardware Profile
SQL Server Profiles
SQL Server Profiles provide instructions for customising an instance of SQL Server for a SQL Server DAC when deploying a virtual machine as part of a service.
How to install SQL Server using SYSPREP - Preparation
Shutdown the virtual machine
Create a template from the virtual machine
Create SQL Server Profile
Enter a name, then click SQL Server Configuration
Fill in the required information on each tab, see below
And click OK when you're done
Application Profiles
An Application Profile provides instructions for installing the following types of applications:
- Server App-V applications
- Microsoft Web Deploy Applications
- Microsoft SQL Server data-tier applications (DACs)
- Scripted application installations
Application Profiles have the following limitations:
- Application Profiles can only be used when deploying a virtual machine as part of a service
- Application Profiles are not supported for Linux Virtual Machines