Metadata update deployment/deploy-windows-mdt

windows/deployment/deploy-windows-mdt/use-orchestrator-runbooks-with-mdt.md

@@ -2,35 +2,35 @@
 title: Use Orchestrator runbooks with MDT (Windows 10)
 description: Learn how to integrate Microsoft System Center 2012 R2 Orchestrator with MDT to replace the existing web services that are used in deployment solutions.
 ms.reviewer: 
-manager: dougeby
-ms.author: aaroncz
+manager: aaroncz
+ms.author: frankroj
 ms.prod: windows-client
 ms.localizationpriority: medium
-author: aczechowski
+author: frankroj
 ms.topic: article
 ms.technology: itpro-deploy
 ---
 
 # Use Orchestrator runbooks with MDT
 
-This topic will show you how to integrate Microsoft System Center 2012 R2 Orchestrator with MDT to replace the existing web services that are used in deployment solutions.
+This article will show you how to integrate Microsoft System Center 2012 R2 Orchestrator with MDT to replace the existing web services that are used in deployment solutions.
 MDT can integrate with System Center 2012 R2 Orchestrator, which is a component that ties the Microsoft System Center products together, as well as other products from both Microsoft and third-party vendors. The difference between using Orchestrator and "normal" web services, is that with Orchestrator you have a rich drag-and-drop style interface when building the solution, and little or no coding is required.
 
-**Note**  
-If you are licensed to use Orchestrator, we highly recommend that you start using it. To find out more about licensing options for System Center 2012 R2 and Orchestrator, visit the [System Center 2012 R2](https://go.microsoft.com/fwlink/p/?LinkId=619553) website.
+>[!Note]
+>If you are licensed to use Orchestrator, we highly recommend that you start using it. To find out more about licensing options for System Center 2012 R2 and Orchestrator, visit the [System Center 2012 R2](https://go.microsoft.com/fwlink/p/?LinkId=619553) website.
  
 ## <a href="" id="sec01"></a>Orchestrator terminology
 
-Before diving into the core details, here is a quick course in Orchestrator terminology:
+Before diving into the core details, here's a quick course in Orchestrator terminology:
 -   **Orchestrator Server.** This is a server that executes runbooks.
--   **Runbooks.** A runbook is similar to a task sequence; it is a series of instructions based on conditions. Runbooks consist of workflow activities; an activity could be Copy File, Get User from Active Directory, or even Write to Database.
+-   **Runbooks.** A runbook is similar to a task sequence; it's a series of instructions based on conditions. Runbooks consist of workflow activities; an activity could be Copy File, Get User from Active Directory, or even Write to Database.
 -   **Orchestrator Designer.** This is where you build the runbooks. In brief, you do that by creating an empty runbook, dragging in the activities you need, and then connecting them in a workflow with conditions and subscriptions.
 -   **Subscriptions.** These are variables that come from an earlier activity in the runbook. So if you first execute an activity in which you type in a computer name, you can then subscribe to that value in the next activity. All these variables are accumulated during the execution of the runbook.
 -   **Orchestrator Console.** This is the Microsoft Silverlight-based web page you can use interactively to execute runbooks. The console listens to TCP port 81 by default.
 -   **Orchestrator web services.** These are the web services you use in the Microsoft Deployment Toolkit to execute runbooks during deployment. The web services listen to TCP port 82 by default.
 -   **Integration packs.** These provide additional workflow activities you can import to integrate with other products or solutions, like the rest of Active Directory, other System Center 2012 R2 products, or Microsoft Exchange Server, to name a few.
 
-**Note**  
+**Note**  
 To find and download additional integration packs, see [Integration Packs for System Center 2012 - Orchestrator](/previous-versions/system-center/packs/hh295851(v=technet.10)).
  
 ## <a href="" id="sec02"></a>Create a sample runbook
@@ -40,7 +40,7 @@ This section assumes you have Orchestrator 2012 R2 installed on a server named O
 1. On OR01, using File Explorer, create the **E:\\Logfile** folder, and grant Users modify permissions (NTFS).
 2. In the **E:\\Logfile** folder, create the DeployLog.txt file.
    **Note**  
-   Make sure File Explorer is configured to show known file extensions so the file is not named DeployLog.txt.txt.
+   Make sure File Explorer is configured to show known file extensions so the file isn't named DeployLog.txt.txt.
      
    ![figure 23.](../images/mdt-09-fig23.png)
 
@@ -53,7 +53,7 @@ This section assumes you have Orchestrator 2012 R2 installed on a server named O
    Figure 24. Folder created in the Runbooks node.
 
 4. In the **Runbooks** node, right-click the **1.0 MDT** folder, and select **New / Runbook**.
-5. On the ribbon bar, click **Check Out**.
+5. On the ribbon bar, select **Check Out**.
 6. Right-click the **New Runbook** label, select **Rename**, and assign the name **MDT Sample**.
 7. Add (using a drag-and-drop operation) the following items from the **Activities** list to the middle pane:
    1.  Runbook Control / Initialize Data
@@ -65,7 +65,7 @@ This section assumes you have Orchestrator 2012 R2 installed on a server named O
    Figure 25. Activities added and connected.
 
 9. Right-click the **Initialize Data** activity, and select **Properties**
-10. On **the Initialize Data Properties** page, click **Add**, change **Parameter 1** to **OSDComputerName**, and then click **Finish**.
+10. On **the Initialize Data Properties** page, select **Add**, change **Parameter 1** to **OSDComputerName**, and then select **Finish**.
 
     ![figure 26.](../images/mdt-09-fig26.png)
 
@@ -86,23 +86,23 @@ This section assumes you have Orchestrator 2012 R2 installed on a server named O
 
     Figure 28. Subscribing to data.
 
-16. In the **Published Data** window, select the **OSDComputerName** item, and click **OK**.
+16. In the **Published Data** window, select the **OSDComputerName** item, and select **OK**.
 17. After the **{OSDComputerName from "Initialize Data"}** text, type in **has been deployed at** and, once again, right-click and select **Subscribe / Published Data**.
-18. In the **Published Data** window, select the **Show common Published Data** check box, select the **Activity end time** item, and click **OK**.
+18. In the **Published Data** window, select the **Show common Published Data** check box, select the **Activity end time** item, and select **OK**.
 
     ![figure 29.](../images/mdt-09-fig29.png)
 
     Figure 29. The expanded text box after all subscriptions have been added.
 
-19. On the **Append Line Properties** page, click **Finish**.
+19. On the **Append Line Properties** page, select **Finish**.
     ## <a href="" id="sec03"></a>Test the demo MDT runbook
-    After the runbook is created, you are ready to test it.
-20. On the ribbon bar, click **Runbook Tester**.
-21. Click **Run**, and in the **Initialize Data Parameters** dialog box, use the following setting and then click **OK**:
+    After the runbook is created, you're ready to test it.
+20. On the ribbon bar, select **Runbook Tester**.
+21. Select **Run**, and in the **Initialize Data Parameters** dialog box, use the following setting and then select **OK**:
     -   OSDComputerName: PC0010
-22. Verify that all activities are green (for additional information, see each target).
+22. Verify that all activities are green (for more information, see each target).
 23. Close the **Runbook Tester**.
-24. On the ribbon bar, click **Check In**.
+24. On the ribbon bar, select **Check In**.
 
 ![figure 30.](../images/mdt-09-fig30.png)
 
@@ -126,7 +126,7 @@ Figure 30. All tests completed.
 7.  After the **Set Task Sequence Variable** action, add a new **Execute Orchestrator Runbook** action with the following settings:
     1.  Orchestrator Server: OR01.contoso.com
     2.  Use Browse to select **1.0 MDT / MDT Sample**.
-8.  Click **OK**.
+8.  Select **OK**.
 
 ![figure 31.](../images/mdt-09-fig31.png)
 
@@ -134,9 +134,9 @@ Figure 31. The ready-made task sequence.
 
 ## Run the orchestrator sample task sequence
 
-Since this task sequence just starts a runbook, you can test this on the PC0001 client that you used for the MDT simulation environment.
-**Note**  
-Make sure the account you are using has permissions to run runbooks on the Orchestrator server. For more information about runbook permissions, see [Runbook Permissions](/previous-versions/system-center/system-center-2012-R2/hh403774(v=sc.12)).
+Since this task sequence just starts a runbook, you can test the task sequence on the PC0001 client that you used for the MDT simulation environment.
+**Note**  
+Make sure the account you're using has permissions to run runbooks on the Orchestrator server. For more information about runbook permissions, see [Runbook Permissions](/previous-versions/system-center/system-center-2012-R2/hh403774(v=sc.12)).
  
 1.  On PC0001, log on as **CONTOSO\\MDT\_BA**.
 2.  Using an elevated command prompt (run as Administrator), type the following command:
@@ -156,7 +156,7 @@ Make sure the account you are using has permissions to run runbooks on the Orche
 
 Figure 32. The ready-made task sequence.
 
-## Related topics
+## Related articles
 
 [Set up MDT for BitLocker](set-up-mdt-for-bitlocker.md)