Skip to content

Commit

Permalink
Merge pull request #30208 from cynthn/hero_edit
Browse files Browse the repository at this point in the history 
Incorping edit pass from #29869
  • Loading branch information
@jomolnar
jomolnar authored Sep 7, 2016
2 parents 719018a + b2f873d commit ba9a8e7
Show file tree
Hide file tree
Showing 2 changed files with 55 additions and 55 deletions.
58 changes: 29 additions & 29 deletions articles/virtual-machines/virtual-machines-windows-hero-role.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -19,35 +19,35 @@

# Experiment with installing a role on your Windows VM

Once you have your first VM up and running, you can move on to installing software and services. For this tutorial, we are going to use Server Manager on the Windows Server VM to install IIS. Then, we will create a Network Security Group (NSG) using the Azure portal to open port 80 to IIS traffic. If you haven't already created your first VM, you should go back to [Create your first Windows virtual machine in the Azure portal](virtual-machines-windows-hero-tutorial.md) before continuing with this tutorial.
Once you have your first virtual machine (VM) up and running, you can move on to installing software and services. For this tutorial, we are going to use Server Manager on the Windows Server VM to install IIS. Then, we will create a Network Security Group (NSG) using the Azure portal to open port 80 to IIS traffic.

If you haven't already created your first VM, you should go back to [Create your first Windows virtual machine in the Azure portal](virtual-machines-windows-hero-tutorial.md) before continuing with this tutorial.

## Make sure the VM is running

1. Open the [Azure portal](https://portal.azure.com).
2. In **Virtual machines** select the VM that you created.
3. If the status is **Stopped (Deallocated), click on the **Start** button on the **Essentials** blade of the VM. If the status is **Running*, you can move on to the next step.
2. On the hub menu, click **Virtual Machines**. Select the virtual machine from the list.
3. If the status is **Stopped (Deallocated), click the **Start** button on the **Essentials** blade of the VM. If the status is **Running*, you can move on to the next step.

## Connect to the virtual machine and log on
## Connect to the virtual machine and sign in

1. On the Hub menu, click **Virtual Machines**.

2. Select the virtual machine from the list.
1. On the hub menu, click **Virtual Machines**. Select the virtual machine from the list.

3. On the blade for the virtual machine, click **Connect**. This creates and downloads a Remote Desktop Protocol file (.rdp file) that is like a shortcut to connect to your machine. You might want to save the file to your desktop for easy access. **Open** this file to connect to your VM.

![Screenshot of the Azure portal showing how to connect to your VM.](./media/virtual-machines-windows-hero-tutorial/connect.png)
![Screenshot of the Azure portal showing how to connect to your VM](./media/virtual-machines-windows-hero-tutorial/connect.png)

4. You get a warning that the .rdp is from an unknown publisher. This is normal. In the Remote Desktop window, click **Connect** to continue.

![Screenshot of a warning about an unknown publisher.](./media/virtual-machines-windows-hero-tutorial/rdp-warn.png)
![Screenshot of a warning about an unknown publisher](./media/virtual-machines-windows-hero-tutorial/rdp-warn.png)

5. In the Windows Security window, type the username and password for the local account that you created when you created the VM. The username is entered as *vmname*\*username*, then click **OK**.

![Screenshot of entering the VM name, user name and password.](./media/virtual-machines-windows-hero-tutorial/credentials.png)
![Screenshot of entering the VM name, user name, and password](./media/virtual-machines-windows-hero-tutorial/credentials.png)

6. You will get a warning that the certificate cannot be verified. This is normal. Click **Yes** to verify the identity of the virtual machine and finish logging on.
6. You get a warning that the certificate cannot be verified. This is normal. Click **Yes** to verify the identity of the virtual machine and finish logging on.

![Screenshot showing a message abut verifying the identity of the VM.](./media/virtual-machines-windows-hero-tutorial/cert-warning.png)
![Screenshot showing a message abut verifying the identity of the VM](./media/virtual-machines-windows-hero-tutorial/cert-warning.png)


If you run in to trouble when you try to connect, see [Troubleshoot Remote Desktop connections to a Windows-based Azure Virtual Machine](virtual-machines-windows-troubleshoot-rdp-connection.md).
Expand All @@ -57,21 +57,21 @@ If you run in to trouble when you try to connect, see [Troubleshoot Remote Deskt

Now that you are logged in to the VM, we will install a server role so that you can experiment more.

1. Open **Server Manager** if it isn't already open. Click the **Start** menu and then click **Server Manager**.
1. Open **Server Manager** if it isn't already open. Click the **Start** menu, and then click **Server Manager**.
2. In **Server Manager**, select **Local Server** from the left pane.
3. In the menu, select **Manage** > **Add Roles and Features**.
4. In the Add Roles and Features Wizard, on the **Installation Type** page, choose **Role-based or feature-based installation** and then click **Next**.
4. In the Add Roles and Features Wizard, on the **Installation Type** page, choose **Role-based or feature-based installation**, and then click **Next**.

![Screenshot showing the Add Roles and Features Wizard tab for Installation Type.](./media/virtual-machines-windows-hero-tutorial/role-wizard.png)
![Screenshot showing the Add Roles and Features Wizard tab for Installation Type](./media/virtual-machines-windows-hero-tutorial/role-wizard.png)

5. Select the VM from the server pool and click **Next**.
6. On the **Server Roles** page, select **Web Server (IIS)**.

![Screenshot showing the Add Roles and Features Wizard tab for Server Roles.](./media/virtual-machines-windows-hero-tutorial/add-iis.png)
![Screenshot showing the Add Roles and Features Wizard tab for Server Roles](./media/virtual-machines-windows-hero-tutorial/add-iis.png)

7. In the pop-up about adding features needed for IIS, make sure that **Include management tools** is selected and then click **Add Features**. When the pop-up closes, click **Next** in the wizard.

![Screenshot showing pop-up to confirm adding the IIS role.](./media/virtual-machines-windows-hero-tutorial/confirm-add-feature.png)
![Screenshot showing pop-up to confirm adding the IIS role](./media/virtual-machines-windows-hero-tutorial/confirm-add-feature.png)

8. On the features page, click **Next**.
9. On the **Web Server Role (IIS)** page, click **Next**.
Expand All @@ -86,26 +86,26 @@ Now that you are logged in to the VM, we will install a server role so that you
In order for your VM to accept inbound traffic over port 80, you need to add an inbound rule to the network security group.

1. Open the [Azure portal](https://portal.azure.com).
2. Under **Virtual machines** select the VM that you created.
3. Under the virtual machines settings, select **Network interfaces** and then select the existing network interface.
2. In **Virtual machines** select the VM that you created.
3. In the virtual machines settings, select **Network interfaces** and then select the existing network interface.

![Screenshot showing the virtual machine setting for the network interfaces.](./media/virtual-machines-windows-hero-tutorial/network-interface.png)
![Screenshot showing the virtual machine setting for the network interfaces](./media/virtual-machines-windows-hero-tutorial/network-interface.png)

4. In **Essentials** for the network interface, click on the **Network security group**.
4. In **Essentials** for the network interface, click the **Network security group**.

![Screenshot showing the Essentials section for the network interface.](./media/virtual-machines-windows-hero-tutorial/select-nsg.png)
![Screenshot showing the Essentials section for the network interface](./media/virtual-machines-windows-hero-tutorial/select-nsg.png)

5. In the **Essentials** blade for the NSG, you should have one existing default inbound rule for **default-allow-rdp** which allows you to log in to the VM. You will add another inbound rule to allow IIS traffic. Click **Inbound security rule**.

![Screenshot showing the Essentials section for the NSG.](./media/virtual-machines-windows-hero-tutorial/inbound.png)
![Screenshot showing the Essentials section for the NSG](./media/virtual-machines-windows-hero-tutorial/inbound.png)

6. In **Inbound security rules**, click **Add**.

![Screenshot showing the button to add a security rule.](./media/virtual-machines-windows-hero-tutorial/add-rule.png)
![Screenshot showing the button to add a security rule](./media/virtual-machines-windows-hero-tutorial/add-rule.png)

7. In **Inbound security rules**, click **Add**. Type **80** in the port range and make sure **Allow** is selected. When you are done, click **OK**.

![Screenshot showing the button to add a security rule.](./media/virtual-machines-windows-hero-tutorial/port-80.png)
![Screenshot showing the button to add a security rule](./media/virtual-machines-windows-hero-tutorial/port-80.png)

For more information about NSGs, inbound and outbound rules, see [Allow external access to your VM using the Azure portal](virtual-machines-windows-nsg-quickstart-portal.md)

Expand All @@ -114,14 +114,14 @@ For more information about NSGs, inbound and outbound rules, see [Allow external
1. In the Azure portal, click **Virtual machines** and then select your VM.
2. In the **Essentials** blade, copy your **Public IP address**.

![Screenshot showing where to find the public IP address of your VM.](./media/virtual-machines-windows-hero-tutorial/ipaddress.png)
![Screenshot showing where to find the public IP address of your VM](./media/virtual-machines-windows-hero-tutorial/ipaddress.png)

2. Open a browser and in the address bar, type in your public IP address like this: http://<publicIPaddress> and click **Enter** to go to that address.
3. Your browser should land on the default IIS web page and the page will look something like this:
3. Your browser should open the default IIS web page. It looks something like this:

![Screenshot showing what the default IIS page looks like in a browser.](./media/virtual-machines-windows-hero-tutorial/iis-default.png)
![Screenshot showing what the default IIS page looks like in a browser](./media/virtual-machines-windows-hero-tutorial/iis-default.png)


## Next steps

* You can also experiment with [attaching a data disk](virtual-machines-windows-attach-disk-portal.md) to your virtual machine. Data disks provide more storage for your virtual machine.
- You can also experiment with [attaching a data disk](virtual-machines-windows-attach-disk-portal.md) to your virtual machine. Data disks provide more storage for your virtual machine.
Loading

0 comments on commit ba9a8e7

Please sign in to comment.