Exercise - Analyze a scenario and map it to a technology option - Training

10 minutes

Your organization grows, and demand rises in Europe and Asia. Your organization is based in the United States. Most of your infrastructure is cloud based. Your European users are reporting a slow website. To provide better service to the customers in Europe, your company has asked you to create a new and improved web server for Europe. The machine must be configured as an IIS web server when it's provisioned.

You've been asked to choose appropriate provisioning tools. Your tools should also be easy to use and easily customizable.

In this exercise, you provision a web server to meet the requirements.

Provision a web server

You need to use several tools to provision a web server. Using an Azure Resource Manager template, you can define the environment for your web server. The Resource Manager template can also help you define a desired state configuration (DSC) for your web server. When you link to a DSC extension handler in the Resource Manager template, both the environment and the desired state are applied when you provision the web server. The DSC extension handler helps enforce the DSC state that you defined.

In the following exercise, you use a Resource Manager template to provision a virtual machine. The DSC extension handler that's included in the template enforces your state on the virtual machine. You use an Azure storage account to host your DSC configuration file.

Clone the configuration and template

Let's start by obtaining a configuration file and an Azure Resource Manager template from GitHub.

In Azure Cloud Shell instance on the right, run the following command to clone the GitHub repository.
```
git clone https://github.com/MicrosoftDocs/mslearn-choose-compute-provisioning.git
```

Examine and compress the State Configuration file

The State Configuration is defined in the Webserver.ps1 file, which includes the IIS web server on your virtual machine. Let's examine that file.

To open the file, run these commands:

cd mslearn-choose-compute-provisioning
code Webserver.ps1

The configuration file includes the following code. Notice that it installs IIS, ASP.NET, and the IIS Management Console.

Configuration Webserver
{
    param ($MachineName)

    Node $MachineName
    {
        #Install the IIS Role
        WindowsFeature IIS
        {
            Ensure = "Present"
            Name = "Web-Server"
        }

        #Install ASP.NET 4.5
        WindowsFeature ASP
        {
            Ensure = "Present"
            Name = "Web-Asp-Net45"
        }

        WindowsFeature WebServerManagementConsole
        {
            Name = "Web-Mgmt-Console"
            Ensure = "Present"
        }
    }
}

To close the code editor, press Ctrl+Q.
To see the contents of the cloned repository, run this command:
```
ls -al
```
Notice that the repository contains both the Webserver.ps1 file, and the Webserver.zip compressed file. You use the zipped file later in this exercise.

Configure the template

The GitHub repository that you cloned, also contains a Resource Manager template. Let's edit the template to add the location of the zipped configuration file to it.

In Cloud Shell, run this command to open the template:
```
code template.json
```
In the template.json file, look for the <parameters> element. Notice that some members, such as vmName, don't have default values. When you use the template, you're prompted to enter values for those properties.

You can also provide a default value for the configuration file URL. In the template.json code file, locate this code:

"modulesUrl": {
    "type": "string",
    "metadata": {
        "description": "URL for the DSC configuration module."
    }
},

Add the default value as follows so that it looks like this code:

"modulesUrl": {
    "type": "string",
    "defaultValue": "https://github.com/MicrosoftDocs/mslearn-choose-compute-provisioning/raw/master/Webserver.zip",
    "metadata": {
        "description": "URL for the DSC configuration module."
    }
},

Save the template by pressing Ctrl+S.

In the <variables> section of the template.json file, notice that values are stored to configure networking for a virtual machine.

In the <resources> section, notice that the template defines an IP address, a virtual network, a virtual machine, and other related resources.
Close the code editor by pressing Ctrl+Q.

Validate your template

Now that you have a completed template and a zipped configuration file, you can use the Azure CLI to deploy them. Before you deploy, validate your files to see if the deployment can succeed.

In Cloud Shell, run this command to validate your deployment. When prompted for a password, enter a complex password of your choice.

az deployment group validate \
    --resource-group <rgn>[sandbox resource group name]</rgn> \
    --template-file template.json \
    --parameters vmName=hostVM1 adminUsername=serveradmin

If your deployment is validated, the output shows information about your deployment. Pay special attention to the error property, which is near the beginning of the output and can be found by scrolling back through the output text. It should be null.

If there are no errors, your template was validated and can be deployed.

Deploy your template

Now that you know the template is valid, you can deploy it.

To deploy the template, run the following command. When prompted for a password, enter the password you defined in the previous task.

az deployment group create \
    --resource-group <rgn>[sandbox resource group name]</rgn> \
    --template-file template.json \
    --parameters vmName=hostVM1 adminUsername=serveradmin

It may take several minutes for deployment to complete.

When the deployment is completed, you should have a virtual machine configured as an IIS web server. To confirm it has been set up, run the following command to list all of the resources in the resource group.
```
az resource list \
    --resource-group <rgn>[sandbox resource group name]</rgn> \
    --output table \
    --query "[*].{Name:name, Type:type}"
```
The output should show your host, extension, network interface, public address, virtual network, and storage account. If you see all of these resources listed, your deployment was successful.

Run the following command to generate the URL for your web server. The output IP address confirms that IIS was successfully installed.

echo http://$(az vm show \
    --show-details \
    --resource-group <rgn>[sandbox resource group name]</rgn> \
    --name hostVM1 \
    --query publicIps \
    --output tsv)

Select the URL, or copy and paste it into a new browser window. You should see the default IIS page.

Congratulations! You successfully provisioned a web server using a Resource Manager template, and enforced a Desired State Configuration (DSC) on your virtual machine using a DSC extension handler.

Continue

Exercise - Analyze a scenario and map it to a technology option