From 155700d0bff06ef5090e89c5b267078ec6c8c576 Mon Sep 17 00:00:00 2001
From: Andres Mariano Gorzelany <36666927+get-itips@users.noreply.github.com>
Date: Mon, 29 Apr 2019 12:06:05 -0300
Subject: [PATCH] Removed ADKPath param from Connect-AppvSequencerVM

Connect-AppvSequencerVM cmdlet does not have ADKPath parameter. Also, changed the command's description.
https://github.com/MicrosoftDocs/windows-itpro-docs/issues/3366
---
 .../application-management/app-v/appv-auto-provision-a-vm.md  | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/windows/application-management/app-v/appv-auto-provision-a-vm.md b/windows/application-management/app-v/appv-auto-provision-a-vm.md
index 53a38b3f05..9cb9b8fade 100644
--- a/windows/application-management/app-v/appv-auto-provision-a-vm.md
+++ b/windows/application-management/app-v/appv-auto-provision-a-vm.md
@@ -95,12 +95,12 @@ If your apps require custom prerequisites, such as Microsoft SQL Server, we reco
 2. Open PowerShell as an admin and run the **Connect-AppvSequencerVM** cmdlet, using the following parameters:
 
     ```ps1
-    Connect-AppvSequencerVM -VMName "<name_of_vm>" -ADKPath "<path_to_adk_install_folder>"
+    Connect-AppvSequencerVM -VMName "<name_of_vm>"
     ```
     
     Where ```<name_of_vm>``` is the name of the VM as shown in the Hyper-V Manager tool.
 
-This command creates a new Hyper-V VM file using the provided VHD file and also creates a "clean" checkpoint, from where all sequencing and updating will start.
+This command connects to an existing Hyper-V VM using the provided VM name for auto-sequencing.
 
 ### Review the provisioning log files