Merge pull request #3944 from KBDAzure/7-16

Fixes for AUX471

articles/virtual-machines-create-custom.md

@@ -1,4 +1,4 @@
-<properties linkid="manage-linux-howto-custom-create-vm" urlDisplayName="Custom create a VM" pageTitle="Custom create a virtual machine running Linux in Azure" metaKeywords="Azure custom vm, creating custom vm" description="Learn how to create a custom virtual machine in Azure." metaCanonical="http://www.windowsazure.com/en-us/manage/windows/how-to-guides/custom-create-a-vm/" services="virtual-machines" documentationCenter="" title="" authors="kathydav" solutions="" manager="dongill" editor="tysonn" />
+<properties linkid="manage-linux-howto-custom-create-vm" urlDisplayName="Create a custom VM" pageTitle=" Create a custom virtual machine running Linux in Azure" metaKeywords="Azure custom vm, creating custom vm" description="Learn how to create a custom virtual machine in Azure." metaCanonical="http://www.windowsazure.com/en-us/manage/windows/how-to-guides/custom-create-a-vm/" services="virtual-machines" documentationCenter="" title="" authors="kathydav" solutions="" manager="dongill" editor="tysonn" />
 
 #How to Create a Custom Virtual Machine
 
@@ -10,7 +10,7 @@ A *custom* virtual machine refers to a virtual machine you create using the **Fr
 - Adding the VM to an existing cloud service 
 - Adding the VM to an availability set
 
-**Important**: If you want your virtual machine to use a virtual network so you can connect to it directly by hostname or set up cross-premises connections, make sure you specify the virtual network when you create the virtual machine. A virtual machine can be configured to join a virtual network only when you create the virtual machine. For more information about virtual networks, see [Azure Virtual Network Overview](http://go.microsoft.com/fwlink/p/?LinkID=294063).
+**Important**: If you want your virtual machine to use a virtual network so you can connect to it directly by hostname or set up cross-premises connections, make sure you specify the virtual network when you create the virtual machine. A virtual machine can be configured to join a virtual network only when you create the virtual machine. For details on virtual networks, see [Azure Virtual Network Overview](http://go.microsoft.com/fwlink/p/?LinkID=294063).
 
 [WACOM.INCLUDE [virtual-machines-create-WindowsVM](../includes/virtual-machines-create-WindowsVM.md)]
 

articles/virtual-machines-install-symantec.md

@@ -40,12 +40,12 @@ Open an Azure PowerShell session and run the following commands. Be sure to subs
 <p>`$name = MyVmName`
 <p>`$vm = Get-AzureVM -ServiceName $servicename -Name $name`
 
- > [WACOM.NOTE] If you don't know the cloud service and VM name, run Get-AzureVM to display that information for all VMs in the current subscription.
+	> [WACOM.NOTE] If you don't know the cloud service and VM name, run Get-AzureVM to display that information for all VMs in the current subscription.
 
 2.	Add Symantec Endpoint Protection Agent to the virtual machine. To install the latest version, run:
 	<p>`Set-AzureVMExtension -Publisher Symantec -ExtensionName SymantecEndpointProtection -VM $vm.VM`
 
- > [WACOM.NOTE] If you want to install a specific version, run the following command to get a list of available versions: `Get-AzureVMAvailableExtension –Publisher Symantec –ExtensionName SymantecEndpointProtection`. 
+	> [WACOM.NOTE] If you want to install a specific version, run the following command to get a list of available versions: `Get-AzureVMAvailableExtension -Publisher Symantec -ExtensionName SymantecEndpointProtection`. 
 Then, include the Version parameter when you run Set-AzureVMExtension.
 
 3.	Update the VM, which installs the Symantec Endpoint Protection Agent:

articles/virtual-machines-install-trend.md

@@ -37,12 +37,12 @@ Open an Azure PowerShell session and run the following commands. Be sure to subs
 	<p>`$name = MyVmName`
 	<p>`$vm = Get-AzureVM -ServiceName $servicename -Name $name`
 
- > [WACOM.NOTE] If you don't know the cloud service and VM name, run Get-AzureVM to display that information for all VMs in the current subscription.
+	> [WACOM.NOTE] If you don't know the cloud service and VM name, run Get-AzureVM to display that information for all VMs in the current subscription.
 
 2.	Add the Deep Security Agent to the virtual machine:
 <p> `Set-AzureVMExtension -Publisher TrendMicro.DeepSecurity -ExtensionName TrendMicroDSA -VM $vm.VM`
 
- > [WACOM.NOTE] If you want to install a specific version, run the following command to get a list of available versions: `Get-AzureVMAvailableExtension TrendMicro.DeepSecurity -ExtensionName TrendMicroDSA`. Then, include the Version parameter when you run Set-AzureVMExtension.
+	> [WACOM.NOTE] If you want to install a specific version, run the following command to get a list of available versions: `Get-AzureVMAvailableExtension TrendMicro.DeepSecurity -ExtensionName TrendMicroDSA`. Then, include the Version parameter when you run Set-AzureVMExtension.
 
 3.	Update the VM, which installs the Deep Security Agent:
 <p> `Update-AzureVM -ServiceName $servicename -Name $name -VM $vm.VM`

includes/CreateVirtualMachineWindowsTutorial.md

@@ -1,3 +1,5 @@
+<properties title="Create a Virtual Machine Running Windows Server" pageTitle="How to create a Virtual Machine Running Windows Server" description="Describes how to create a Windows virtual machine, add a data disk, and log on remotely" metaKeywords="" services="virtual machines" solutions="" documentationCenter="" authors="kathydav" videoId="" scriptId="" />
+
 # Create a Virtual Machine Running Windows Server #
 
 This tutorial shows you how easy it is to create an Azure virtual machine running Windows Server, using the Image Gallery in the Windows Azure Management Portal. The Image Gallery offers a variety of images, including Windows operating systems, Linux-based operating systems, and application images. 

includes/virtual-machines-create-WindowsVM.md

@@ -1,8 +1,6 @@
 1. Sign in to the Windows Azure [Management Portal](http://manage.windowsazure.com). Check out the [Free Trial](http://www.windowsazure.com/en-us/pricing/free-trial/) offer if you do not have a subscription yet.
 
-2. On the command bar at the bottom of the screen, click **New**.
-
-	![Select New from the Command Bar](./media/virtual-machines-create-WindowsVM/commandbarnew.png)
+2. On the command bar at the bottom of the window, click **New**.
 
 3. Under **Compute**, click **Virtual Machine**, and then click **From Gallery**.
 
@@ -12,19 +10,20 @@
 
 	![Choose an image](./media/virtual-machines-create-WindowsVM/chooseimage.png)
 
-5. The second screen lets you pick a computer name, size, and administrative user name and password. For this tutorial, fill in the fields as shown in the image below. Then, click the arrow to continue.
+5. The second screen lets you pick a computer name, size, and administrative user name and password. For this tutorial, fill in the fields as shown in the image below. Then, click the arrow to continue. Here are some details to help you fill this out: 
+
+	- **New User Name** refers to the administrative account that you use to manage the server. Create a unique password for this account and make sure to remember it. **You'll need the user name and password to log on to the virtual machine**. 
 
-	>[WACOM.NOTE] **New User Name** refers to the administrative account that you use to manage the server. Create a unique password for this account and make sure to remember it. **You'll need the user name and password to log on to the virtual machine**.
+	- A virtual machine's size affects the cost of using it, as well as configuration options such as the number of data disks you can attach. For details, see [Virtual Machine and Cloud Service Sizes for Azure](http://go.microsoft.com/fwlink/p/?LinkId=466520).
 
 	![Configure the properties of the virtual machine](./media/virtual-machines-create-WindowsVM/vmconfiguration.png)
 
-
 
-6. The third screen lets you configure resources such as the cloud service and the storage account. When this screen is complete, click the arrow to continue. Some tips to help you fill this out are: 
 
+6. The third screen lets you configure resources such as the cloud service and the storage account. When this screen is complete, click the arrow to continue. Here are some details to help you fill this out: 
 
 
-	- The **Cloud Service DNS Name** is the global DNS name that becomes part of the URI that is used to contact the virtual machine. You'll need to come up with your own cloud service name since cloud service names must be unique in Azure. Cloud services are important for more complex scenarios using [multiple virtual machines](http://www.windowsazure.com/en-us/documentation/articles/cloud-services-connect-virtual-machine/).
+	- The **Cloud Service DNS Name** is the global DNS name that becomes part of the URI that's used to contact the virtual machine. You'll need to come up with your own cloud service name because it must be unique in Azure. Cloud services are important for scenarios using [multiple virtual machines](http://www.windowsazure.com/en-us/documentation/articles/cloud-services-connect-virtual-machine/).
 
 	- For **Region/Affinity Group/Virtual Network**, use a region that is appropriate to your location. You can also choose to specify a virtual network instead.
 
@@ -34,12 +33,12 @@
 
 	![Configure the connected resources of the virtual machine](./media/virtual-machines-create-WindowsVM/resourceconfiguration.png)
 
-7. The fourth configuration screen lets you configure the VM Agent and some of the available extensions. For this tutorial, do not make any changes to this screen. Click the check mark to create the virtual machine.
+7. The fourth configuration screen lets you configure the VM Agent and some of the available extensions. Click the check mark to create the virtual machine.
 
 
 	![Configure VM Agent and extensions for the virtual machine](./media/virtual-machines-create-WindowsVM/agent-and-extensions.png)
 
-	>[WACOM.NOTE] The VM agent provides the environment for you to install extensions that can help you interact with the virtual machine. For details, see [Using Extensions](http://go.microsoft.com/FWLink/p/?LinkID=390493).  
+	>[WACOM.NOTE] The VM agent provides the environment for you to install extensions that can help you interact with or manage the virtual machine. For details, see [Using Extensions](http://go.microsoft.com/FWLink/p/?LinkID=390493).  
 
 8. After the virtual machine is created, the Management Portal lists the new virtual machine under **Virtual Machines**. The corresponding cloud service and storage account are also created under their respective sections. Both the virtual machine and cloud service are started automatically and the Management Portal shows their status as **Running**.