PERFGURU : Windows server 2008

Remote Assistance in Windows 2008

pawansharma — Mon, 07 Jul 2008 11:03:00 GMT

Remote Assistance provides a way for users to get the help they need and makes it easier and less costly for corporate helpdesks to assist their users.

The Remote Assistance application in Windows Server 2008 is implemented in MSRA.exe.

It can be started from the command line by running msra.exe.

%systemroot%\system32\msra.exe

From the Start > All Programs > Maintenance > Windows Remote Assistance

Remote Assistance Registry Keys

User-specific Remote Assistance registry keys will not exist unless Remote Assistance is installed and the current user has run Remote Assistance at least once.

The per-user Remote Assistance registry values are located in the following key: HKCU\Software\Microsoft\Remote Assistance\

The location of the per-machine registry key for Remote Assistance has changed from previous versions of Windows. The new location is:

HKLM\SYSTEM\CurrentControlSet\Control\Remote Assistance

In previous versions of Windows location is:

HKLM\SYSTEM\CurrentControlSet\Control\Terminal Service

Remote Assistance Group Policies

Remote Assistance may be configured using the group policies located in the following container: Computer Configuration/Administrative Templates/System/Remote Assistance

The policies write registry values to the following area of the registry: HKLM\Software\Policies\Microsoft\Windows NT\Terminal Services

A Remote Assistance connection may be initiated by the following ways:

++Offer Remote Assistance (unsolicited) mode

++Solicited mode

Offer Remote Assistance (or Unsolicited Remote Assistance)

Unsolicited remote assistance is initiated by an Expert user and is used to offer Remote Assistance to a Novice user. The Expert should know the Novice’s machine name or IP address to view the novice’s desktop. If the Expert needs to share control of the Novice’s machine, the Expert can request control and the Novice can accept or deny the request.

Solicited Remote Assistance

The Invite someone you trust to help you option, also referred to as solicited, Remote Assistance, is initiated by a Novice user that looks for assistance from an Expert user. This mode is started by using one of the following methods:

++Send an invitation by email via Simple MAPI The Novice can email the RA invitation to the Expert as an attachment.

To use this method, the Novice’s email application must support Simple MAPI protocol. e.g. Microsoft Outlook, Outlook Express and Lotus Notes support Simple MAPI protocol.

++Manually save an invitation file and send it to the Expert Novice has to create the ticket as a file (save it to a file) and manually send the file to an Expert.

The invitation file is a text file that is XML formatted and contains information that the Expert's machine will be able to start remote assistance.

Session logs are XML-formatted documents.

Log Path: %SystemDrive%\Users\user_name\Documents\Remote Assistance Logs

A unique session log file is created for each RA Session on the computer. Log files stored within this folder are formatted using XML and are named using the convention YYYYMMDDHHMMSS.xml, where the time format is 24-hour.

How to change RDP Port on TS

pawansharma — Tue, 01 Jul 2008 11:16:00 GMT

Terminal services used port 3389 by default. It is well known port TS uses so there can be a chance that it can be a target for attack by network intruders.

Even though network attackers can find the port that is in use, changing TS port from 3389 can make it more difficult to attack a TS server.

TS port can be changed from the registry

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp

Value: Port Number

Type: REG_DWORD

Data: 3389 in decimal or d3d in hex

We can use any ephemeral port ranging from 1024-4999 by default. After making the registry changes restart the terminal services

To check the port on which terminal server is listening run nestat –aon from command prompt.

++ Remote Desktop Client

Launch mstsc.exe. In the computer field specify the <TS name>:<port number> e.g. If server name is termserver1 and port is 3900 then we need to put termserver1:3900

++Remote Desktop We Connection

Make connection to web server which host the remote desktop web connection using http://<server name>/ts

Click on the Remote Desktop icon. In Connect to: field specify the <TS name>:<port number>

++Remote Applications:

To configure Remote Applications, accessible through TS Web Access or a custom .rdp file, to use custom Terminal Server port, you must configure custom RDP Settings in TS Remote App Manager MMC snap-in.

RemoteApp Deployment Settings à Terminal Server à RDP Port

Specify the custom port in RDP port field.

How to install application on Windows 2008 Terminal Server

pawansharma — Mon, 30 Jun 2008 09:56:00 GMT

It’s recommended to install Terminal services role before installing any application which will be available to terminal server users. If TS role installed after the applications are installed, some the application may not work correctly in a multiple user environment.

In that scenario uninstalling and reinstalling the affected programs can resolve the issue.

To ensure that an application is installed correctly to work in a multiple user environment, the Terminal Server must be switched into Install mode before applications are installed on the server.

A Terminal Server canbe placed into Install mode using one of the following methods:

++Using the Install Application on Terminal Server tool in Control Panel\Programs.

This tool is available only when we install terminal server. It will automatically put terminal server into execute mode when application installation is complete.

++ Run Change user /install from command promptto place the server into Install mode and install the application. After installing the application, use the Change user /execute command (or restart the server) to place the server back into Execute mode before using the application.

Change user /query command can be used to find the current mode.

When an application is installed in Install mode, HKEY_CURRENT_USER information is primarily written to the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install

This information is then circulated to HKEY_CURRENT_USER for each user when they log on to the Terminal Server.

Terminal Server Easy Print

pawansharma — Wed, 25 Jun 2008 12:04:00 GMT

Terminal Server Easy print

Terminal service easy printing is a new feature introduced in windows 2008 server.It enables users to print from a Terminal Services session to the local or network printers configured on the client computer without the need to install drivers on the Terminal Server.

User will see the full printer properties of the local printer in the session and have access to all printer functionality. The Easy Print universal driver acts as a proxy and redirects all UI

To use the Terminal Services Easy Print feature in Terminal Services on Windows Server 2008, clients must be running Remote Desktop Connection (RDC) 6.1 client and have the .NET Framework 3.0 Service Pack 1 installed. Both included with Windows Server 2008 and will be available for download for Windows Vista.

New features in Windows Server 2008 Terminal Services:

++Terminal Services Easy Print.

++Client-redirected printers are now scoped per session.

++Printers now have the Session SID set in the list of ACLs that prevents printers from appearing in another session, even for the same user.

++Ability to view and manage session printers. By default, users, including administrators, can only see the printers that they have redirected in their session.

++Users can change access to the printers by editing the permissions in the printer properties to be made accessible to other users.

The Terminal Services Easy Print feature works seamlessly in mixed platform environments:

· x86 clients > x64 Windows Server 2008 Terminal Servers

· x64 clients > x86 Windows Server 2008 Terminal Servers

Things we need to check if TS easy printing is not working:

++clients are running Remote Desktop Connection (RDC) 6.1 client and have the .NET Framework 3.0 Service Pack 1.

a) XP SP3 includes RDC 6.1 client. But we need to install .NET Framework

Microsoft .NET Framework 3.5 (which includes .NET Framework 3.0 SP1) can be downloaded from the Microsoft Download Center

http://go.microsoft.com/fwlink/?LinkId=109422

b) On a Windows Server 2008-based server (that is acting as the client), you must add .NET Framework 3.0 SP1 by using either Server Manager or by adding the feature from the command line.

To add .NET Framework 3.0 SP1 by using the Server Manager user interface

1. Start Server Manager. To open Server Manager, click Start, point to Administrative Tools, and then click Server Manager.

2. In the left pane of Server Manager, right-click Features, and then click Add Features.

3. On the Select Features page, expand .NET Framework 3.0.

4. Select the .NET Framework 3.0 Features and the XPS Viewer check boxes, and then click Next.

5. Click Install.

To add .NET Framework 3.0 SP1 by using the command line

1. Start the command prompt with elevated privileges. To do this, click Start, right-click Command Prompt, and then click Run as administrator.

2. At the command prompt, type the following, and then press ENTER:

pkgmgr.exe /iu:NetFx3

The installation occurs silently, and may take several minutes.

c) Windows Vista® with SP1 includes both of the required components. By default, Windows Vista with SP1 supports the Terminal Services Easy Print driver with no additional configuration

++ Check if tsprint.dll in the following location:

%systemroot%\System32\Spool\Drivers\w32x86\3\tsprint.dll (Terminal Services Easy Print is implemented in tsprint.dll)

++Check the Terminal Services Easy Print and compare with the working machine.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\ <architecture>\Drivers\Version-3\Terminal Services Easy Print

Terminal Service Printing Group Policies

Group Policies for Terminal Services printing are located in the following container:

Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server

Table: Terminal Services Print Group Policies

Group Policy	Function Explanation
Do not set default client printer to be default printer in a session	This policy setting allows you to specify whether the client default printer is automatically set as the default printer in a Terminal Services session.
Do not allow client printer redirection	This policy setting allows you to specify whether to prevent the mapping of client printers in Terminal Services sessions. Enabling this policy will disable printer redirection.
Specify terminal server fallback printer driver behavior	This policy setting allows you to specify the Terminal Server fallback printer driver behavior. You must enable this policy to use the fallback driver.
Use Terminal Services Easy Print driver first	This policy setting allows you to specify whether the Terminal Services Easy Print printer driver is used first to install all client printers. Enabling this policy will cause all redirected printers to use the Easy Print driver.
Redirect only the default client printer	This policy setting allows you to specify whether the default client printer is the only printer redirected in Terminal Services sessions. Enabling this policy causes the server to only redirect the client default printer, not all

Terminal Server Command Line tools in Windows Server 2008

Roop — Mon, 10 Mar 2008 13:02:00 GMT

Command	Description
Change	Changes Terminal Server settings for logons, COM port mappings, and install mode.
Change logon	Enables or disables logons from client sessions on a Terminal Server, or displays current logon status.
Change port	Lists or changes the COM port mappings to be compatible with MS-DOS applications.
Change user	Changes the install mode for the Terminal Server.
Chglogon	Enables or disables logons from client sessions on a Terminal Server, or displays current logon status.
Chgport	Lists or changes the COM port mappings to be compatible with MS-DOS applications.
Chguser	Changes the install mode for the Terminal Server.
Flattemp	Enables or disables flat temporary folders.
Logoff	Logs off a user from a session on a Terminal Server and deletes the session from the server.
Msg	Sends a message to a user on a Terminal Server.
Mstsc	Creates connections to Terminal Servers or other remote computers.
Qappsrv	Displays a list of all Terminal Servers on the network.
Qprocess	Displays information about processes that are running on a Terminal Server.
Query	Displays information about processes, sessions, and Terminal Servers.
Query process	Displays information about processes that are running on a Terminal Server.
Query session	Displays information about sessions on a Terminal Server.
Query termserver	Displays a list of all Terminal Servers on the network.
Query user	Displays information about user sessions on a Terminal Server.
Quser	Displays information about user sessions on a Terminal Server.
Qwinsta	Displays information about sessions on a Terminal Server.
Reset session	Enables you to reset (delete) a session on a Terminal Server.
Rwinsta	Enables you to reset (delete) a session on a Terminal Server.
Shadow	Enables you to remotely control an active session of another user on a Terminal Server.
Tscon	Connects to another session on a Terminal Server.
Tsdiscon	Disconnects a session from a Terminal Server.
Tskill	Ends a process running in a session on a Terminal Server.
Tsprof	Copies the Terminal Services user configuration information from one user to another.

The command line tools in the following table are not used for Terminal Services in Windows Server 2008.

Table 5 - Deprecated Command Line Utilities

Command	Function
tsshutdn	Shuts down a Terminal Services server.
register	Registers a program so that it has special execution characteristics.
cprofile	Removes user-specific file associations from a user's profile.

Since tsshutdn.exe is not included with Windows Server 2008, the recommended method for shutting down or restarting a Windows Server 2008 Terminal Server is by using Shutdown.exe.

Terminal Server Group Policy Guide in Server 2008

Roop — Mon, 10 Mar 2008 12:39:00 GMT

Terminal Server Computer Configuration Group Policies

Computer Group Policy Settings for Terminal Server Connections

Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Connections

Computer Group Policies for Terminal Server Connections
Allow reconnection from original client only
Allow remote start of unlisted programs
Allow users to connect remotely using Terminal Services
Automatic reconnection
Configure keep-alive connection interval
Deny logof of an administrator to the console session
Limit number of connections
Restrict Terminal Services users to a single remote session
Set rules for remote control of Terminal Services user sessions

Computer Group Policy Settings for Terminal Server Device and Resource Redirection

Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Device and Resource Redirection

Computer Group Policies for Terminal Server Device and Resource Redirection
Allow audio redirection
Allow time zone redirection
Do not allow clipboard redirection
Do not allow COM port redirection
Do not allow drive redirection
Do not allow LPT port redirection
Do not allow supported Plug and Play device redirection

Computer Group Policy Settings for Terminal Server Licensing

Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Licensing

Computer Group Policies for Terminal Server Licensing
Hide notifications about TS Licensing problems that affect the terminal server
Set the Terminal Services licensing mode
Use the specified Terminal Services licensing servers

Computer Group Policy Settings for Terminal Server Printer Redirection

Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Printer Redirection

Computer Group Policies for Terminal Server Printer Redirection
Do not allow client printer redirection
Do not set default client printer to be default printer in a session
Redirect only the default client printer
Specify terminal server fallback printer driver behavior
User Terminal Services Easy Print driver first

Computer Group Policy Settings for Terminal Server Profiles

Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Profiles

Computer Group Policies for Terminal Server Profiles
Set path for TS Roaming Profiles
Set TS User Home Directory
Use mandatory profiles on the terminal server

Computer Group Policy Settings for Terminal Server Remote Session Environment

Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Remote Session Environment

Computer Group Policies for Terminal Server Remote Session Environment
Always show desktop on connection
Enforce Removal of Remote Desktop Wallpaper
Limit maximum color depth
Remove “Disconnect” option from Shut Down dialog
Remove Windows Security item from Start menu
Start a program on connection

Computer Group Policy Settings for Terminal Server Security

Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Security

Computer Group Policies for Terminal Server Security
Always prompt for password upon connection
Do not allow local administrators to customize permissions
Require secure RPC communication
Require use of specific security layer for remote (RDP) connections
Require user authentication using RDP 6.0 for remote connections
Server Authentication Certificate Template
Set client connection encryption level

Computer Group Policy Settings for Terminal Server Session Time Limits

Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Session Time Limits

Computer Group Policies for Terminal Server Session Time Limits
Set time limit for active but idle Terminal Services sessions
Set time limit for active Terminal Services sessions
Set time limit for disconnected sessions
Terminate session when time limits are reached

Computer Group Policy Settings for Terminal Server Temporary folders

Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Temporary folders

Computer Group Policies for Terminal Server Temporary Folders
Do no delete temp folder upon exit
Do not use temporary folder per session

Computer Group Policy Settings for Terminal Server TS Session Broker

Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\TS Session Broker

Computer Group Policies for Terminal Server TS Session Broker
Join TS Session Broker
TS Session Broker Farm Name
TS Session Broker Load Balancing
TS Session Broker Server
Use IP Address Redirection

Terminal Server User Configuration Group Policies

User Group Policy Settings for Remote Desktop Connection Client

User Configuration\Administrative Templates\Windows Components\Terminal Services\Remote Desktop Connection Client

User Group Policies for Remote Desktop Connection Client
Allow .rdp files from valid publishers and user’s default .rdp settings
Allow .rdp files from unknown publishers
Do not allow passwords to be saved
Specify SHA1 thumbprints of certificates representing trusted .rdp publishers

User Group Policy Settings for Terminal Server Connections

User Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Connections

User Group Policies for Terminal Server Connections
Set rules for remote control of Terminal Services user sessions
Allow reconnection from original client only

User Group Policy Settings for Terminal Server Device and Resource Redirection

User Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Device and Resource Redirection

User Group Policies for Terminal Server Device and Resource Redirection
Do not allow clipboard redirection
Allow time zone redirection

User Group Policy Settings for Terminal Server Printer Redirection

User Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Printer Redirection

User Group Policies for Terminal Server Printer Redirection
Use Terminal Services Easy Print driver first
Redirect only the default client printer

User Group Policy Settings for Terminal Server Remote Session Environment

User Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Remote Session Environment

User Group Policies for Terminal Server Remote Session Environment
Start a program on connection
Enforce Removal of Remote Desktop Wallpaper
Always show desktop on connection

User Group Policy Settings for Terminal Server Session Time limits

User Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Session Time Limits

User Group Policies for Terminal Server Session Time limits
Set time limit for disconnected sessions
Set time limit for active but idle Terminal Services sessions
Set time limit for active Terminal Services sessions
Terminate session when time limits are reached

User Group Policy Settings for TS Gateway

User Configuration\Administrative Templates\Windows Components\Terminal Services\TS Gateway

User Group Policies for Terminal Server Session Time limits
Set TS Gateway authentication method
Enable connection through TS Gateway
Set TS Gateway server address

How to Obtain a Kernel Memory Dump file in Server Core of Windows Server 2008

Roop — Mon, 10 Mar 2008 12:34:00 GMT

If a Kernel memory dump is needed for troubleshooting purposes, the following methods may be used:

■ Crash.exe (available with Microsoft Support)– both the command line and GUI versions of Crash.exe may be used to create a memory dump file on Server Core.

■ CrashOnCTRLScroll – the “CTRL+Scroll Lock+Scroll Lock” keyboard sequence may be used to “crash” a server to create a memory dump file after editing the registry to add the CrashOnCTRLScroll DWORD value, set to 1, in the following key and restarting the server:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\
Parameters

Note

The CrashOnCTRLScroll process is described in the following Knowledge Base article:

244139 Windows feature lets you generate a memory dump file by using the keyboard
http://support.microsoft.com/default.aspx?scid=kb;EN-US;244139

As with previous versions of Windows, prior to creating a memory dump, the paging file and memory dump type must be configured and the server must be restarted. To create a Complete memory dump, the paging file must be located on the System drive and sized to at least (installed memory + 50MB). The paging file may be configured using the steps discussed in the “Configure the Paging File” topic in the Initial Configuration of Server Core section of this module.

By default, Windows Server 2008 is configured to create a Kernel memory dump when a Kernel exception occurs. The memory dump type is defined by the CrashDumpEnabled DWORD value in the following registry key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl

Valid CrashDumpEnabled registry values are as follows:

■ 0x0 = None

■ 0x1 = Complete memory dump

■ 0x2 = Kernel memory dump

■ 0x3 = Small memory dump (64KB)

Other settings that are available in the Startup and Recovery options on a full installation of Windows Server 2008 are also located in the CrashControl registry key as shown in the following table.

Table 16: Full Windows Server 2008 Startup and Recovery Option Registry Values

Startup and Recovery UI Option	Registry value (value range)
Write an event to the System log	Logevent (0, 1)
Automatically restart	AutoReboot (0,1)
Write debugging information	CrashDumpEnabled (see above)
Dump file	DumpFile (path\<dump file name>.dmp)
Overwrite any existing file	Overwrite (0,1)

Performance Monitoring in Server Core in Windows Server 2008

Roop — Mon, 10 Mar 2008 12:27:00 GMT

Performance Monitoring

The Reliability and Performance Monitor (RPM) console is not available on Server Core, however, the Performance Logs and Alerts service and the underlying performance subsystem is the same as a full installation of Windows Server 2008. Performance Monitoring of a Server Core server can be accomplished using the following methods:

■ Remotely using Performance Monitor on a full installation of Windows Server 2008 or Windows Vista

■ Locally on Server Core using the following command line performance monitoring tools:

Logman.exe

Logman.exe can be used to perform the following tasks:

■ Locally and remotely manage performance counter and event trace log collections.

■ Configure a data collector set on one computer and then copy that configuration to multiple computers from a central location.

■ Query currently-running logs and event traces.

Command Syntax

The following table describes logman.exe command line parameters:

Table 13: LOGMAN Command Parameters

Parameter	Description
Verbs
create	Create a new data collector.
query	Query data collector properties by name.
start	Start an existing data collector and set the begin time to manual.
stop	Stop an existing data collector and set the end time to manual.
delete	Delete an existing data collector.
update	Update an existing data collector's properties.
import	Import a data collector set from an XML file.
export	Export a data collector set to an XML file.
Options
-?	Displays context sensitive help.
-s <computer>	Perform the command on specified remote system.
-config <value>	Settings file containing command options.
-ets	Send commands to Event Trace Sessions without saving or scheduling.

A common scenario for using logman.exe on Server Core is to create a Data Collector Set using Performance Monitor on a full installation of Windows Server 2008, or Windows Vista, and export the Data Collector Set configuration as an XML template. Then, use logman.exe to import and start the Data Collector Set on a Server Core server. After exporting the Data Collector Set XML template file, the following command can be used to import the XML template using logman.exe:

logman import –n <name> -xml <filename>

where:
<name> = desired name for target Data Collector Set
<filename> = name of XML template to import

To start the Performance Monitor Data Collector Set after inporting the XML template, type the following command at the command prompt:

logman start <name>

where:
<name> = name of Data Collector Set to start

Tip

All of the configured Data Collector Sets may be listed using logman query.

The Performance Monitor log file will be created in the following folder, by default:

%systemdrive%\PerfLogs

Relog.exe

Relog can be used to create new performance logs from data in existing performance logs by changing the sampling rate and/or converting the file format. Supports all performance log formats, including Windows NT 4.0 compressed logs.

Command Syntax

relog <filename [filename ...] [options]

The following table describes Relog command line parameters.

Table 14: RELOG Command Parameters

Parameter	Description
<filename [filename ...]	Required: Performance file to relog.
Options
-?	Displays context sensitive help.
-a	Append output to the existing binary file.
-c <path [path ...]>	Counters to filter from the input log.
-cf <filename>	File listing performance counters to filter from the input log. Default is all counters in the original log file.
-f <CSV\|TSV\|BIN\|SQL>	Output file format.
-t <value>	Only write every nth record into the output file. Default is to write every record.
-o	Output file path or SQL database.
-b <M/d/yyyy h:mm:ss[AM\|PM]	Begin time for the first record to write into the output file.
-e <M/d/yyyy h:mm:ss[AM\|PM]	End time for the last record to write into the output file.
-config <filename>	Settings file containing command options.
-q	List performance counters in the input file.
-y	Answer yes to all questions without prompting.

Typeperf.exe

Typeperf.exe can be used to perform the following tasks:

■ Write performance data to the command window or to a supported log file format (csv | tsv | bin | sql).

■ Display all of the counters that are currently available on a particular local or remote computer.

Command Syntax

typeperf { <counter [counter ...]>

| -cf <filename>

| -q [object]

| -qx [object]

} [options]

The following table describes typeperf command line parameters

Typeperf.exe supports the following commands:

Table 15: Typeperf Command Parameters

Parameter

Description

<counter [counter ...]>

Required: Performance counters to monitor.

Note

The counter parameter(s) specify the full name of a performance counter in \\<Computer>\<object>(<instance>)\<counter> format.

Example: \\Server1\Processor(0)\% User Time

Options

-f <CSV|TSV|BIN|SQL>

Output file format. Default is CSV.

-cf <filename>

File containing performance counters to monitor, one per line.

-si <[[hh:]mm:]ss>

Time between samples. Default is 1 second.

-o <filename>

Path of output file or SQL database. Default is STDOUT.

-q [object]

List installed counters (no instances). To list counters for one object, include the object name, such as Processor.

-qx [object]

List installed counters with instances. To list counters for one object, include the object name, such as Processor.

-sc <samples>

Number of samples to collect. Default is to sample until CTRL+C.

-config <filename>

Settings file containing command options.

-s <computer_name>

Server to monitor if no server is specified in the counter path.

-y

Answer yes to all questions without prompting.

Displays context sensitive help.