Adding content

windows/manage/appv-automatic-sequence-a-new-app.md

@@ -14,7 +14,7 @@ ms.prod: w10
 **Applies to**
 -   Windows 10, version 1703
 
->[NOTE]
+>[!NOTE]
 >In Windows 10, version 1703, the App-V Sequencer is included with the Windows ADK. For more info on how to install the App-V Sequencer, see [Install the App-V Sequencer](appv-install-the-sequencer.md).
 
 Previous versions of the App-V Sequencer have required you to manually sequence your app packages. This was time-consuming and required extensive interaction, causing many companies to deploy brand-new packages rather than update an existing one. Windows 10, version 1703 introduces an updated App-V Sequencer that automatically sequences your app packages, improving your overall experience by streamlining the provisioning of the prerequisite environment, automating app installation, and expediting the package updating setup.
@@ -46,10 +46,10 @@ For this process to work, you must have a base operating system available as a V
     ```ps1
     Convert-WindowsImage -SourcePath "<path_to_iso_image>" -VHDFormat "VHD" -VHDPartitionStyle "MBR"
     ```
-    Where `SourcePath` is the full file path to your ISO image, `VHDFormat` is *VHD*, and `VHDPartitionStyle` is *MBR*. 
+    Where _SourcePath_ is the full file path to your ISO image, _VHDFormat_ is *VHD*, and _VHDPartitionStyle_ is *MBR*. 
     
     >[!IMPORTANT]
-    >You must specify the `VHDPartitionStyle` as **MBR**. Using the default value, **GPT**, will cause a boot failure in your VHD image.
+    >You must specify the _VHDPartitionStyle_ as **MBR**. Using the default value, **GPT**, will cause a boot failure in your VHD image.
 
 ### Provision your VM using your VHD file
 After you have a VHD file, you must provision your VM for auto-sequencing.
@@ -65,7 +65,7 @@ After you have a VHD file, you must provision your VM for auto-sequencing.
     New-AppVSequencerVM -VMName "<name_of_new_vm>" -ADKPath "<path_to_adk_install_folder>" -VHDPath "<path_to_vhd_file>" -VMMemory <vm_memory_size> -VMSwitch "<name_of_network_switch>"
     ```
     
-    Where you create a unique name for your VM, ensure that the VHD file and matching ADK tools are located on the Host device and referenced in the 'ADKPath' and the 'VHDPath' parameters, determine the amount of memory to be allocated for use by your VM, and provide the name of your network switch.
+    Where you create a unique name for your VM, ensure that the VHD file and matching ADK tools are located on the Host device and referenced in the _ADKPath_ and the _VHDPath_ parameters, determine the amount of memory to be allocated for use by your VM, and provide the name of your network switch.
 
 A new Hyper-V VM file is created out of the provisioned VHD, creating a "clean" checkpoint, from where all of the sequencing and updating will start.
 
@@ -76,17 +76,24 @@ If your apps require custom prerequesites, such as Microsoft SQL Server, we reco
 **To connect to your existing VM**
 - Open PowerShell as an admin and run the following commands on your existing VM:
 
-    - **Set the network category of your connection profile on the VM to `Private`:** 
+    - **Set the network category of your connection profile on the VM to _Private_:** 
     
-        `Get-netconnectionprofile | set-netconnectionprofile -NetworkCategory Private`
+        ```ps1
+        Get-netconnectionprofile | set-netconnectionprofile -NetworkCategory Private
+        ```
         
-    - **Set the Windows Firewall rules for the display groups, `Remote Desktop` and `Windows Remote Management`:** 
+    - **Set the Windows Firewall rules for the display groups, _Remote Desktop_ and _Windows Remote Management_:** 
     
-        `Enable-NetFirewallRule -DisplayGroup “Remote Desktop”` and `Enable-NetFirewallRule -DisplayGroup “Windows Remote Management”`
+        ```ps1
+        Enable-NetFirewallRule -DisplayGroup “Remote Desktop” 
+        Enable-NetFirewallRule -DisplayGroup “Windows Remote Management”
+        ```
 
     - **Set the VM to receive remote commands without a confirmation prompt:**
     
-        `Enable-PSRemoting –Force`
+        ```ps1
+        Enable-PSRemoting –Force
+        ```
 
     These commands turn on [PowerShell Remoting](https://msdn.microsoft.com/powershell/reference/5.1/Microsoft.PowerShell.Core/about/about_Remote) and turn on the necessary Windows Firewall rules so you can connect to your VM.
 
@@ -99,12 +106,12 @@ If your apps require custom prerequesites, such as Microsoft SQL Server, we reco
     New-AppVSequencerVM -VMName "<name_of_vm>" -VMComputerName "<computer_name_for_vm>" -ADKPath "<path_to_adk_install_folder>"
     ```
     
-    Where `VMName` is the name of the VM granted during its creation and shown in the Hyper-V Manager tool, and the `VMComputerName` is the name of the VM, assigned after its creation and shown on the **Computer name** field of the **System Properties** screen.
+    Where _VMName_ is the name of the VM granted during its creation and shown in the Hyper-V Manager tool, and the _VMComputerName_ is the name of the VM, assigned after its creation and shown on the **Computer name** field of the **System Properties** screen.
 
 A new Hyper-V VM file is created from the existing VM, creating a "clean" checkpoint, from where all of the sequencing and updating will start.
 
 ## Reviewing the provisioning log files
-The 2 types of provisioning log files, located at `“%temp%\AutoSequencer\Logs”`, are:
+The 2 types of provisioning log files, located at “%temp%\AutoSequencer\Logs”, are:
 
 - **New-AppVSequencerVM-<time_stamp>.txt**: Includes info about the provisioning activities, such as "Waiting for VM session", "Copying installer for Sequencer", and so on.