RequiresUserInput

Applies To: Windows 7, Windows 8, Windows 8.1, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2

The RequiresUserInput setting is not used.

Note

Unlike synchronous commands, asynchronous commands may start and finish in any order. They cannot delay the appearance of the Windows® desktop, even if the asynchronous command requires user input. If an asynchronous command requires user input, the end user will see the input window after the desktop appears. For information about synchronous commands, see SynchronousCommand.

Values

true

This setting is not used.

false

This setting is not used.

Valid Configuration Passes

oobeSystem

Parent Hierarchy

Microsoft-Windows-Shell-Setup | LogonCommands | AsynchronousCommand | RequiresUserInput

Applies To

For a list of the supported Windows® editions and architectures that this component supports, see Microsoft-Windows-Shell-Setup.

XML Example

The following XML output shows examples of how to set two logon commands. The RequiresUserInput setting has no effect for either of the commands.

<LogonCommands>
  <AsynchronousCommand wcm:action="add">
    <CommandLine>c:asynccommands\command1.exe</CommandLine>
    <Description>Description_of_command1</Description>
    <Order>1</Order>
    <RequiresUserInput>true</RequiresUserInput>
  </AsynchronousCommand>
  <AsynchronousCommand wcm:action="add">
    <CommandLine>c:asynccommands\command2.exe</CommandLine>
    <Description>Description_of_command2</Description>
    <Order>2</Order>
    <RequiresUserInput>false</RequiresUserInput>
  </AsynchronousCommand>
</LogonCommands>

See Also

Concepts

AsynchronousCommand
RequiresUserInput