text stringlengths 0 4.23k |
|---|
pushprinterconnections <-log> <-?> |
Parameters |
Parameter |
Description |
<-log> |
Writes a per user debug log file to %temp, or writes a per machine debug log to %windir%\temp. |
<-?> |
Displays Help at the command prompt. |
pwlauncher |
Enables or disables the Windows To Go Startup Options (pwlauncher). The pwlauncher command-line tool allows you to configure the computer to boot into a Windows To Go workspace automatically (assuming one is present), without requiring you to enter your firmware or change your startup options. |
Windows To Go Startup Options allow a user to configure their computer to boot from USB from within Windows-without ever entering their firmware, as long as their firmware supports booting from USB. Enabling a system to always boot from USB first has implications that you should consider. For example, a USB device that includes malware could be booted inadvertently to compromise the system, or multiple USB drives could be plugged in to cause a boot conflict. For this reason, the default configuration has the Windows To Go Startup Options disabled by default. In addition, administrator privileges are required to configure Windows To Go Startup Options. If you enable the Windows To Go startup options using the pwlauncher command-line tool or the Change Windows To Go Startup Options app the computer will attempt to boot from any USB device that is inserted into the computer before it is started. |
Syntax |
pwlauncher {/enable | /disable} |
Parameters |
Parameter |
Description |
/enable |
Enables Windows To Go startup options, so the computer will automatically boot from a USB device when present. |
/disable |
Disables Windows To Go startup options, so the computer can't be booted from a USB device unless configured manually in the firmware. |
/? |
Displays help at the command prompt. |
Examples |
To enable boot from USB: |
pwlauncher /enable |
qappsrv |
Applies to: Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012 |
Displays a list of all Remote Desktop Session Host servers on the network. To find out what's new in the latest version, see What's New in Remote Desktop Services in Windows Server. |
Note |
This command is the same as the query termserver command. |
qprocess |
Applies to: Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012 |
Displays information about processes that are running on a Remote Desktop Session Host server. To find out what's new in the latest version, see What's New in Remote Desktop Services in Windows Server. |
Note |
This command is the same as the query process command. |
query process |
Applies to: Windows Server 2022, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2012 |
Displays information about processes that are running on a Remote Desktop Session Host server. You can use this command to find out which programs a specific user is running, and also which users are running a specific program. This command returns the following information: |
User who owns the process |
Session that owns the process |
ID of the session |
Name of the process |
ID of the process |
Note |
To find out what's new in the latest version, see What's New in Remote Desktop Services in Windows Server. |
Syntax |
query process [*|<processID>|<username>|<sessionname>|/id:<nn>|<programname>] [/server:<servername>] |
Parameters |
Parameter |
Description |
* |
Lists the processes for all sessions. |
<processID> |
Specifies the numeric ID identifying the process that you want to query. |
<username> |
Specifies the name of the user whose processes you want to list. |
<sessionname> |
Specifies the name of the active session whose processes you want to list. |
/id:<nn> |
Specifies the ID of the session whose processes you want to list. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.