Share via


Creating a Manual Prompt Task

Note  This content applies to the Windows Logo Kit (WLK). For the latest information using the new Windows Hardware Certification Kit (HCK), see Windows HCK User's Guide on the Windows Hardware Dev Center.

Tasks perform the work of a job. A Manual Prompt task displays a message to the user on the client computer, and then waits for the user to respond. For more information about tasks, see Basic Task Concepts.

To define a Manual Prompt task

Note  This content applies to the Windows Logo Kit (WLK). For the latest information using the new Windows Hardware Certification Kit (HCK), see Windows HCK User's Guide on the Windows Hardware Dev Center.

  1. Create or edit a Manual Prompt task within a job.

  2. In the Instructions to user pane, type the message that will be displayed on the client computer when the task runs.

  3. If this task's completion status should affect the completion status of the job, select Rollup Results to Job. If you do not roll the tasks results up to the job, then if the task fails, it will not cause the job to fail.

  4. Select Provide User with "Pass" and "Fail" buttons to have buttons labeled Pass and Fail added to the message dialog box. Or, select Provide User with "Continue" button to have a button labeled Continue added to the message dialog box.

    When the task runs, if the user selects the Pass or the Continue button, the task will pass. If the user selects the Fail button, or closes the dialog box without selecting any button, the task will fail.

  5. Click Preview if you want to see preview of the message that will be displayed to the user when the task runs.

  6. If the task should fail when the user does not respond to the prompt within a certain amount of time, on the Execution Options tab, select the Set timeout to check box and enter the number of hours, days, and minutes after which the task should fail.

  7. If the task should fail when the user does respond to the prompt within a certain amount of time, on the Execution Options tab, select the Set timeout to check box and enter the number of hours, days, and minutes after which the task should fail.

  8. In the User Context section of the Execution Options tab, select one of the following user contexts and sessions that will be used to run the task on the client computer:

    • Run as the user that is logged onto the first active session to run in the context of the user who is logged on to the first active session on the client computer. If no user is logged on to the client computer, the task will fail.

    • Run as user in user's active session to run as a specific user, if that user is logged on to the client computer. If the user is not logged on, the task will fail.

    • Run as user in Console if logged in to run as a specific user if that user is logged on to the client computer. However, the task will run in session zero rather than in the user's session. If the user is not logged on, the task will fail.

    • Run as user in Console even if not logged in to run as a specific user in session zero, even if the user is logged on to the client computer.

  9. If you selected Run as user in user's active session, Run as user in Console if logged in, or Run as user in Console even if not logged in, then use the following procedure to identify the user:

    1. In the User Credentials section of the Execution Options tab, select Run as Specific User to identify the user by user name, or select Run as Local Logical User to identify the user by using a Local Logical User (LLU).

    2. If you selected Run as Specific User, enter the user name and domain of the user to run as. If the User Context is Run as user in Console even if not logged in, also enter the user's password.

      Important   The password is stored on the controller and is not secure.

    3. If you selected Run as Local Logical User, enter the LLU as the Local Name.

  10. Click OK to return to the New Job window.

 

 

Build date: 9/14/2012