Datasets:
IAmSomeone
/
Windows_command

Dataset card Data Studio Files
xet
 Community
text
stringlengths
0
4.23k
Parameters
Parameter
Description
/b
Specifies backup operation.
/r
Specifies restore operation.
<folder path_to_storage_device>
Specifies the path where the MSMQ message files and registry settings are stored.
/?
Displays help at the command prompt.
<folder path_to_storage_device>
Remarks
If a specified folder doesn't exist while performing either the backup or restore operation, the folder is automatically created by the utility.
If you choose to specify an existing folder, it must be empty. If you specify a non-empty folder, the utility deletes every file and subfolder contained within it. In this case, you'll be prompted to give permission to delete existing files and subfolders. You can use the /y parameter to indicate that you agree beforehand to the deletion of all existing files and subfolders in the specified folder.
The locations of folders used to store MSMQ message files are stored in the registry. Therefore, the utility restores MSMQ message files to the folders specified in the registry and not to the storage folders used before the restore operation.
Examples
To backup all MSMQ message files and registry settings, and to store them in the msmqbkup folder on your C: drive, type:
mqbkup /b c:\msmqbkup
To delete all existing files and subfolders in the oldbkup folder on your C: drive, and then to store MSMQ message files and registry settings in the folder, type:
mqbkup /b /y c:\oldbkup
To restore MSMQ messages and registry settings, type:
mqbkup /r c:\msmqbkup
mqsvc
Message Queuing technology enables apps running at different times to communicate across heterogeneous networks and systems that may be temporarily offline. Message Queuing provides guaranteed message delivery, efficient routing, security, and priority-based messaging. It can be used to implement solutions for both asynchronous and synchronous messaging scenarios. For more information about Message Queuing, see Message Queuing (MSMQ).
Syntax
mqsvc.exe
mqtgsvc
Monitors a queue for incoming messages and performs an action, in the form of an executable file or COM component, when the rules of a trigger are evaluated as true. For examples of how the Message Queuing Triggers service can be used, see Message Queuing Triggers.
Syntax
mqtgsvc.exe
msdt
Invokes a troubleshooting pack at the command line or as part of an automated script, and enables additional options without user input.
Note
The Microsoft Support Diagnostic Tool (MSDT) is deprecated. For more information, see Deprecated Windows features.
Syntax
msdt </id <name> | /path <name> | /cab < name>> <</parameter> [options] … <parameter> [options]>>
Parameters
Parameter
Description
/id <packagename>
Specifies which diagnostic package to run. For a list of available packages, see Available Troubleshooting packs.
/path <directory|.diagpkg file|.diagcfg file>
Specifies the full path to a diagnostic package. If you specify a directory, the directory must contain a diagnostic package. You cannot use the /path parameter in conjunction with the** /id**, /dci, or /cab parameters.
/dci <passkey>
Prepopulates the passkey field. This parameter is only used when a support provider has supplied a passkey.
/dt <directory>
Displays the troubleshooting history in the specified directory. Diagnostic results are stored in the user’s %LOCALAPPDATA%\Diagnostics or %LOCALAPPDATA%\ElevatedDiagnostics directories.
/af <answerfile>
Specifies an answer file in XML format that contains responses to one or more diagnostic interactions.
/modal <ownerHWND>
Makes the troubleshooting pack modal to a window designated by the parent Console Window Handle (HWND), in decimal. This parameter is typically used by applications that launch a troubleshooting pack. For more information about obtaining Console Window Handles, see How to Obtain a Console Window Handle (HWND).
/moreoptions <true|false>
Enables (true) or suppresses (false) the final troubleshooting screen that asks if the user wants to explore additional options. This parameter is typically used when the troubleshooting pack is launched by a troubleshooter that isn't part of the operating system.
/param <parameters>
Specifies a set of interaction responses at the command line, similar to an answer file. This parameter isn't typically used within the context of troubleshooting packs created with TSP Designer. For more information about developing custom parameters, see Windows Troubleshooting Platform.