Copyright: Overview of Windows NT Resource Kit Tools version 4.00.01 © Microsoft Corporation 1993 - 1996


Three-Dimensional Paint: 3DPAINT.EXE
Desktop Tools

3DPAINT.EXE: Three-Dimensional Paint

Run Three-Dimensional Paint now.

3DPAINT is an OpenGL paint utility that enables you to create three-dimensional bitmap graphics.

Platform	3DPAINT runs only on x86-based computers.

For more information

Open 3DPAINT.HLP now.

Files required


Files required for 3DPAINT

3DPAINT.EXE

3DPAINT.HLP


ADDUSERS.EXE: Add Users
User Account Administration Tools

ADDUSERS.EXE: AddUsers

AddUsers for Windows NT is a 32-bit administrative tool that uses a comma-delimited file to create, write, and delete user accounts. AddUsers is most beneficial when the file is maintained in a spreadsheet, such as Microsoft Excel, that will work with comma-delimited files.

The format for the comma-delimited file requires headings for Users, Global Groups, and Local Groups. It is recommended that you first execute AddUsers with the /d switch, the dump accounts option, to write the headings, user accounts, local groups, and global groups to a file. Viewing this file should give you a clearer picture of the structure and headings of the comma-delimited file before you use the /c option to create user accounts. For more information on the format for the comma-delimited file, see Additional Notes.

You must be a member of the Administrators group on the target computer to add accounts and a member of the Users group to write accounts.

AddUsers topics

AddUsers syntax

Additional notes

Example: AddUsers file

Files required


File required for AddUsers

ADDUSERS.EXE


ADDUSERS.EXE: AddUsers

AddUsers syntax

Additional notes

Example: AddUsers file


AddUsers syntax
ADDUSERS.EXE: AddUsers

AddUsers syntax	  Open Command Prompt now.

addusers [ \\computername ] [{ /c | /d | /e } filename] [/s:x] [/?]

Where

\\computername

is the computer on which you want to create user accounts or from which you want to write user accounts. If you do not specify a computer name, AddUsers will use the local computer by default.

/c

creates user accounts, local groups, and global groups as specified by filename.

/d

dumps user accounts, local groups, and global groups to filename.

Note	Choosing to dump current user accounts does not save the account's passwords or any security information for the accounts. To back up security information for accounts, a Tape Backup should be used.

Note	Since password information is not saved in a user account dump, using the same file to create accounts will cause all passwords of newly created accounts to be empty. All created users will be required to change their password at logon by default.

/e

deletes user accounts as specified by filename.

Caution	Be careful when erasing user accounts, as it is not possible to recreate the user account with the same SID. This option, however, cannot erase built-in default accounts.

filename

is the comma-delimited input/output file that AddUsers will use for data.

/s:x

changes the character used for separating fields in the file. The x should be replaced with the new character to be used for separating fields. For example, /s:~ would make the field-separation character the "~" (tilde).

If this option is not specified, the default separator, a comma, will be used.

/?

displays a usage screen


Additional notes
ADDUSERS.EXE: AddUsers

Additional notes

AddUsers requires that each section in the file have a heading to denote what type of information follows. These headings are [Users], [Global], and [Local]. Use the dump users (/d) option to create a file that will demonstrate the use of these headings.

Syntax is section-specific for each entry (line) in the different sections, as follows:

[Users]

<User Name>,<Full Name>,<Password>,<Home Drive>,<Home Path>,<Profile>,<Script>

[Global]

<Global Group Name>,<Comment>,<UserName>, ...

[Local]

<Local Group Name>,<Comment>,<UserName>, ...

The entries (lines) in the [Local] and [Global] group sections can have 0 or more <UserName> entries after the comment field. Each user name will be added to that group. Lines must end with a comma (or the appropriate separator character).

Note	To change the separator character from the default comma, use the /s:x command-line switch.

Note	Global Groups will appear to be added to computers running Windows NT Workstation. However, since Windows NT Workstation does not support Global Groups, they are not actually added.


Example: AddUsers file
ADDUSERS.EXE: AddUsers

Example: AddUsers file

Please note that the blank lines between the sections are not required. If blank lines are used, they must be completely empty (no spaces or tabs, only the return character).

[User]

jimmy,James Edward Phillip II,,,,,,

alex,Alex Denuur,,,E:\,E:\users\alex,,

ron,Ron Jarook,,hello,E:\,E:\users\ron,,

sarah,Sarah Selly,,,,,,

mike,Mike Olarte,,,,,,

[Global]

TestTeam,Regression,ron,alex,

DevTeam,Conversion to Sources,mike,sarah,jimmy,

[Local]

UsersAM,Users A through M,alex,jimmy,mike,

UsersNZ,Users N through Z,ron,sarah,


ANIEDIT.EXE: Animated Cursor Creator
Desktop Tools

ANIEDIT.EXE: Animated Cursor Creator

Run Animated Cursor Creator now.

Animated Cursor Creator enables you to create and edit animated cursors and icons in color or monochrome, including small Windows 95-style icons (16 colors, 16x16 pels). It can arrange and animate frames produced with Image Editor.

Animated Cursor Creator topics

To use Animated Cursor Creator

Tips for using Animated Cursor Creator

Related topics

Files required


Files required for Animated Cursor Creator

ANIEDIT.EXE

IMAGEDIT.EXE

IMAGEDIT.HLP


ANIEDIT.EXE: Animated Cursor Creator

To use Animated Cursor Creator

Tips for using Animated Cursor Creator


ANIEDIT.EXE: To use Animate Cursor Creator
ANIEDIT.EXE: Animated Cursor Creator

To use Animated Cursor Creator

Run Animated Cursor Creator now.

1	Click the Start button.

2	Point to Programs.

3	Point to Resource Kit 4.0.

4	Point to Desktop Tools.

5	Click Animated Cursor Creator.

6	On the File menu, click New to create a new animated cursor sequence, or click Open to edit an existing animated cursor.

7	In the Show for: box, select the number of jiffies (1/60th seconds) that the current frame will appear during the animation sequence.

8	Use the toolbar or menu commands to edit frames:

File New	Edit Cut
File Open	Edit Copy
File Save	Edit Paste
	Edit Delete
	New Frame
	Edit Frame
Other menu command: Import Frame

For online Help,on the Help menu, click Contents.


Import Frame

Imports a .CUR or .ICO image to serve as a frame in the sequence for the current file.


Edit Cut

Cuts a selected frame and places it on the Clipboard, so that it can be pasted in another position in the sequence or in another animated cursor file.


Edit Copy

Copies a selected frame and places it on the Clipboard, so that it can be pasted in another position in the sequence or in another animated cursor file.


Edit Paste

Pastes a frame from the Clipboard into the indicated position in the sequence.


File New

Displays an empty Frame sequence so that you can create a new animated cursor file.


File Open

Displays the Open dialog box so that you can select an animated cursor (.ANI) file to edit.


File Save and File Save As

Saves the sequence under the current filename (Save) or under a filename that you supply (Save As).


Edit Delete

Deletes a selected frame from the animation sequence.


Edit Frame

Runs Image Editor so that you can alter the currently selected frame.


New Frame

Runs Image Editor so that you can create a new frame for the animation.


ANIEDIT.EXE: Tips for using Animated Cursor Creator
ANIEDIT.EXE: Animated Cursor Creator

Tips for using Animated Cursor Creator

To select multiple frames, hold down SHIFT or CTRL and click the desired frames. Then you can change the speed for several frames at once.

If you select multiple frames that have different frame speeds, clicking the Up arrow or Down arrow in the Jiffies edit box will change their speed proportionally. That is, they will all increase or decrease x%, but an actual number will not appear in the Jiffies box.

To enable easy viewing of .ANI files by double-clicking the filename in Explorer, associate the .ANI file extension with ANIEDIT.EXE. On the View menu of Explorer, click Options, then click the File Types tab.


APIMON.EXE: API Monitor
Tools for Developers

APIMON.EXE: API Monitor

Run API Monitor now.

This command-line tool enables you to monitor the API calls a process is making.

APIMON reports the number of calls made to and total time spent in each API, and optionally generates a trace file listing the individual calls with the calling parameters.

APIMON incorporates the functionality of Windows API Profiler (WAP), which it replaces in the Windows NT 4.0 Resource Kit.

For more information

Open API Monitor Help now.

Files required


Files required for API Monitor

APIMON.EXE

APIMON.HLP

APIDLL.DLL


ASSOCIATE.EXE
Batch Tools

ASSOCIATE.EXE

This command-line utility enables you to register or unregister a filename extension with the Registry. "File extension, executable program" associations enable the Windows NT 4.0 shell to launch the correct executable program when a file with the associated extension is opened from the command line, from Explorer, or from File Manager.

For example, if you use a lot of files with the extension ".ABC" and have an application ABCRUN.EXE that operates on them, you could associate the extension and application by running:

associate .abc abcrun.exe

Then, whenever a file with the .ABC extension is started from the command line or from Explorer, ABCRUN.EXE would be run.

ASSOCIATE topics

ASSOCIATE syntax

ASSOCIATE examples

Files required


File required for ASSOCIATE

ASSOCIATE.EXE


ASSOCIATE.EXE

ASSOCIATE syntax

ASSOCIATE examples


ASSOCIATE syntax
ASSOCIATE.EXE

ASSOCIATE syntax	  Open Command Prompt now.

associate .ext filename [/q] [/d] [/f] [/?]

Where

.ext

indicates the extension to be associated.

filename

indicates the executable program to associate .ext with.

/q

(quiet) suppresses all interactive prompts.

/d

deletes the association if it exists.

/f

forces an overwrite or delete of the existing entry without questions.

/?

displays a usage screen.


ASSOCIATE examples
ASSOCIATE.EXE

ASSOCIATE examples

Example 1

associate .lst notepad.exe

adds the association of .LST with NOTEPAD.EXE.

Example 2

associate .lst notepad.exe /d

removes the association of .LST with NOTEPAD.EXE.

Example 3

associate .lst

returns the name of the associated executable for .LST, if it exists

Return Value

A return value of zero indicates success. Any other value indicates failure.


ATANLYZR.EXE
Network Diagnostic Tools

ATANLYZR.EXE: AppleTalk network device ANaLYZeR

Run ATANLYZR now.

This GUI utility performs an AppleTalk lookup for registered AppleTalk devices on an AppleTalk network. The user can perform a lookup of all Appletalk devices, specific Net, Name, Type, or partial Name, and Types in the selected zone(s).

You can use this utility to find information on the AppleTalk Network, such as what systems are routing, what system has a printer captured, or a list of printers or computers running Windows NT. Each Device returns values for their Net, Node, Socket, Name, Type, and Zone. The combinations of Net/Node/Socket or Name/Type/Zone are unique values.

The computer that will be executing ATANLYZR must have the AppleTalk stack installed. The stack is part of Services for Macintosh and Appletalk Protocol.

Files required


Files required for ATANLYZR

ATANLYZR.EXE

the AppleTalk stack and related components


AUDITCAT.HLP: Audit Categories Help
Computer Diagnostic Tools

AUDITCAT.HLP: Audit Categories Help

Open Audit Categories Help now.

This Windows Help file displays information on seven categories of audit events.

Audit event records displayed by Event Viewer (part of the  Administrative Tools for the Windows NT operating system) are divided into auditing categories. These categories allow a user to visually distinguish or automatically filter audit events of interest.

For more information

Open Event Viewer now.

Related topics

Files required


File required for Audit Categories Help

AUDITCAT.HLP


AUTOEXNT.EXE: AutoExNT Service
Batch Tools

AUTOEXNT.EXE: AutoExNT Service

The AutoExNT service allows you to start a batch file, AUTOEXNT.BAT, at boot time without having to log onto the computer on which it will run.

AutoExNT includes an /interactive option (analogous to the /interactive option of the AT command) that allows you to see the processes started. To use AutoExNT, you must be running Windows NT 3.5 or later.

For more information

For instructions on installation and usage:

Open AUTOEXNT.TXT now.

Files required


Files required for AutoExNT

AUTOEXNT.EXE

AUTOEXNT.TXT

SERVMESS.DLL

INSTEXNT.EXE


AutoLogon: Windows NT Auto Logon Setter
User Account Administration Tools

AUTOLOG.EXE: Windows NT Auto Logon Setter

Run Auto Logon Setter now.

Windows NT Auto Logon Setter is a simple GUI utility that configures a Windows NT Workstation to automatically log on a particular user at bootup. This enables you to bypass the CTRL+ALT+DEL logon dialog box.

AUTOLOG displays a dialog box that prompts you for your password and allows you to enable or disable auto logon. When you click the OK button, AUTOLOG changes the appropriate configuration settings, which are maintained in the Windows NT Registry.

The Registry database is also the repository for every application's configuration settings. Windows NT ships with a tool, REGEDT32.EXE, that allows a user to examine and edit the contents of the Registry. Extreme caution is required when modifying Registry entries, a task usually reserved for system administrators.

AUTOLOG permits a regular user to update auto-logon settings without having to manually edit the Registry itself. It opens the Registry, changes the appropriate values, and closes the Registry.

Note	AUTOLOG does not allow the specified user to log off and a different user to log on: at logoff, it will automatically log the specified user back on.  To enable another user to log on, you must disable AUTOLOG.

Related topics

Files required


File required for Windows NT Auto Logon Setter

AUTOLOG.EXE


BREAKFTM.EXE: Automated Mirror Break/Restore Utility
Disk/Fault Tolerance Tools

BREAKFTM.EXE: Automated Mirror Break/Restore Utility

Server only	Included in the Windows NT Server, but not Workstation, Resource Kit.

This command-line utility was designed to be used with Windows NT Server 4.0 Unattended Upgrade.

Computers running Windows NT that have the system drive mirrored cannot be upgraded, as a mirrored system drive will cause the Unattended Upgrade to fail. The mirror must therefore be broken before upgrading.

BREAKFTM breaks the system mirror before the Windows NT Server 4.0 upgrade, and then recreates the mirror once the upgrade is finished. The tool has no effect on computers that do not have a system mirror.

Use BREAKFTM only with Windows NT Server 4.0 Unattended Upgrade. To break or create a mirror manually, use Disk Administrator in Administration Tools (Windows NT Server version only).

Note	BREAKFTM can only be used to recover mirrors that were broken by the utility. This tool cannot recover mirrors that were broken manually.

BREAKFTM can be run either through SMS or directly from the command prompt.

For more information

Open BREAKFTM.TXT now.

For command-line syntax, type breakftm /? at the command prompt.

Related topics

Files required


Files required for Automated Mirror Break/Restore Utility

BREAKFTM.EXE

BREAKFTM.PDF

BREAKFTM.TXT


BROWMON.EXE: Browser Monitor
Network Diagnostic Tools

BROWMON.EXE: Browser Monitor

Run Browser Monitor now.

Server only	Included in the Windows NT Server, but not Workstation, Resource Kit.

The Browser Monitor utility monitors the status of browsers on selected domains. Browsers are shown on a per-domain and per-transport basis.

To use Browser Monitor

1	Click the Start button.

2	Point to Programs.

3	Point to Resource Kit 4.0.

4	Point to Diagnostics.

5	Click Browser Monitor.

To get online Help while working in Browser Monitor, press F1.

For more information

Open Browser Monitor Help now.

Files required


Files required for Browser Monitor

BROWMON.EXE

BROWMON.HLP


BROWSTAT.EXE: Browser Status
Network Diagnostic Tools

BROWSTAT.EXE: Browser Status

Server only	Included in the Windows NT Server, but not Workstation, Resource Kit.

BrowStat is a general purpose, character-based browser diagnostic tool. Use BrowStat to find out whether a browser is running and to find active Microsoft Windows for Workgroups (WFW) browsers in Windows NT domains. This utility also provides information about the state of the browser in a workgroup, including the name of the master browser.

You can find out which transports are on a computer by using the net config rdr command and examining the result. In this discussion, "transport" refers to the Windows NT device name (case-insensitive) for the specified transport, in one of the following formats:

\device\transport (For example: \device\Nbf_elnk1601)

\transport

transport

BrowStat topics

BrowStat syntax

Flags in BrowStat listings

BROWSTAT STATS example

BROWSTAT STATUS example

Files required


File required for BrowStat

BROWSTAT.EXE


BROWSTAT.EXE: Browser Status

BrowStat syntax

Flags in BrowStat listings

BROWSTAT STATS example

BROWSTAT STATUS example


To use BrowStat
BROWSTAT.EXE: Browser Status

BrowStat syntax	  Open Command Prompt now.

browstat options

Where

options

is the whole word or abbreviation from the following list:

ELECT (EL)	Force election on remote domain.

GETBLIST (GB)	Get backup list for domain.

GETMASTER (GM)	Get remote master name (using NetBIOS).

GETPDC (GP)	Get primary domain controller name (using NetBIOS).

LISTWFW (WFW)	List active Windows for Workgroups servers.

STATS (STS)	Dump browser statistics. STATS example

STATUS (STA)	Display status about a domain. STATUS example

TICKLE (TIC)	Force remote master browser to stop.

VIEW (VW)	Retrieve list of servers on a transport or workgroup.


Flags in Browstat Listings
BROWSTAT.EXE: Browser Status

Flags in BrowStat listings

AFP = AFP Server BBR = Backup Browser BDC = Backup Domain Controller DFS = Distributed File System DL = Dial-in Server DMB = Domain Master Browser MBR = Master Browser MDC = Member Domain Controller MFPN = Microsoft File and Print for Netware NT = Windows NT NV = Novell OSF = OSF Server	PBR = Potential Browser PDC = Primary Domain Controller PQ = Print Server S = Server SQL = SQL Server SS = Windows NT Member Server TS = Time Source VMS = Vax VMS Server W = Workstation W95 = Windows 95 WFW = Windows for Workgroups XN = Xenix


BROWSTAT ELECT  (EL)

This command forces a master browser election on the domain that uses the transport specified.

Usage:

browstat elect transport domain


BROWSTAT GETBLIST  (GB)

This command retrieves a list of the backup browsers on the domain with the specified transport.

Usage:

browstat getblist transport [[domain] refresh]


BROWSTAT GETMASTER  (GM)

This command uses NetBIOS to retrieve the name of the browser master for a transport for a workgroup.

Usage:

browstat getmaster transport domain


BROWSTAT GETPDC  (GP)

This command uses NetBIOS to retrieve the name of the primary domain controller for a transport for a workgroup.

Usage:

browstat getpdc transport domain


BROWSTAT LISTWFW  (WFW)

This command finds WFW computers that are currently running the browser. If you have a mixed workgroup-and-domain network, you can disable the browser in Windows for Workgroups.

Usage:

browstat listwfw domain


BROWSTAT STATS  (STS)

This command dumps various useful browser statistics. The \\server switch allows it to be pointed to a specific server.

Usage:

browstat stats [\\server] [clear]


BROWSTAT STATUS  (STA)

This command dumps browser status for the specified workgroup on all local transports. It also includes the build number of the browser master and how many servers are in the workgroup.

Usage:

browstat status [-v] workgroup


BROWSTAT TICKLE  (TIC)

This command stops the browse master for the specified workgroup on the specified transport. It can be used to reset a computer that has been determined to be "bad."

Usage:

browstat tickle transport domain


BROWSTAT VIEW  (VW)

This command retrieves the list of servers or domains for a specified server for a specified transport or workgroup.

Usage:

browstat view transport

browstat view transport domain | server [/DOMAIN]

browstat view transport server /DOMAIN domain


BROWSTAT STATISTICS example
BROWSTAT.EXE: Browser Status

BROWSTAT STATS example

C>BROWSTAT STATS

Browser statistics since 20:40:54.705 on 6/9/1993	Time statistics were last cleared

NumberOfServerEnumerations:	237

NumberOfDomainEnumerations:	235

NumberOfOtherEnumerations:	6

NumberOfMailslotWrites:	1974

NumberOfServerAnnouncements:	0

NumberOfDomainAnnouncements:	0

NumberOfElectionPackets:	27425

NumberOfGetBrowserServerListRequests:	0

NumberOfMissedGetBrowserServerListRequests:	0

NumberOfDroppedServerAnnouncements:	0

NumberOfDroppedMailslotDatagrams:	0

NumberOfFailedMailslotReceives:	0

NumberOfMasterAnnouncements:	0

NumberOfIllegalDatagrams:	0

Meaning:

NumberOfServerEnumerations: = Number of browse requests for servers

NumberOfDomainEnumerations: = Number of browse requests for domains

NumberOfOtherEnumerations: = Number of "other" browse requests

NumberOfMailslotWrites: = Number of mailslot writes received

NumberOfServerAnnouncements: = Number of server announcements received

NumberOfDomainAnnouncements: = Number of domain (workgroup) announcements received

NumberOfElectionPackets: = Number of browser election packets received

NumberOfGetBrowserServerListRequests: = Number of GetBrowserServerList requests received

NumberOfMissedGetBrowserServerListRequests: = Number of GetBrowserServerList requests missed

NumberOfDroppedServerAnnouncements: = Number of server announcements dropped

NumberOfDroppedMailslotDatagrams: = Number of mailslot writes dropped due to memory

NumberOfFailedMailslotReceives: = Number of mailslot writes dropped due to transport

NumberOfMasterAnnouncements: = Number of WAN master browser announcements

NumberOfIllegalDatagrams: = Number of illegal datagrams received


BROWSTAT STATUS Example
BROWSTAT.EXE: Browser Status

BROWSTAT STATUS example

C>BROWSTAT STATUS NTLAN

Status for domain ntlan on transport \Device\Nbf_Lance01

    Master browser name is: MSTRBROWSER1

        Master browser is running build 1.511.1

    3 backup servers retrieved from master MSTRBROWSER1

        \\MYPC

        \\MSTRBROWSER1

        \\BACKUPSVR1

    There are 20 servers in domain ntlan on transport \Device\Nbf_Lance01

    There are 1074 domains in domain ntlan on transport \Device\Nbf_Lance01

Status for domain ntlan on transport \Device\Streams\NWNBLINK

    Master browser name is: MSTRBROWSER1

        Master browser is running build 1.511.1

    3 backup servers retrieved from master MSTRBROWSER1

        \\BACKUPSVR1

        \\MSTRBROWSER1

        \\MYPC DEBUG

    There are 8 servers in domain ntlan on transport \Device\Streams\NWNBLINK

    There are 36 domains in domain ntlan on transport \Device\Streams\NWNBLINK

Status for domain ntlan on transport \Device\Streams\NBT

    Master browser name is: MSTRBROWSER1

        Master browser is running build 1.511.1

    3 backup servers retrieved from master MSTRBROWSER1

        \\MSTRBROWSER1

        \\BACKUPSVR1

        \\MYPC

    There are 11 servers in domain ntlan on transport \Device\Streams\NBT

    There are 101 domains in domain ntlan on transport \Device\Streams\NBT


C2CONFIG.EXE: Windows NT C2 Configuration Manager
Computer Administration/Configuration Tools

C2CONFIG.EXE: Windows NT C2 Configuration Manager

Run C2CONFIG.EXE now.

C2CONFIG.EXE, the Windows NT C2 Configuration Manager, can be used to compare the current security configuration on your Windows NT Workstation with C2-level security requirements of the United States government's National Computer Security Center. You can then configure the workstation to conform up to the C2 level.

C2 Configuration Manager displays the Windows NT parameters that the C2 evaluators felt were critical, along with their current configuration. Selecting one of these items displays more information on the configuration of that item and allows you to change the configuration.

C2CONFIG.EXE comes with a .H file that lets users write their own extensions to the application by calling DLLs. C2DLL.TXT is the text file that explains how this is done.

For information on setting up a C2-certifiable system, see "Microsoft Report on C2 Evaluation of Windows NT, " or contact Microsoft's Federal Office.

For more information

For help on a specific item while running C2 Configuration Manager, select that item in the list box and press the F1 key.

Open C2CONFIG.HLP now.

Open C2DLL.TXT now.

For a conceptual overview, see the chapter on the Windows NT security model in Windows NT Workstation Resource Guide.

If you have installed the Online Books, click to:

Open Windows NT Workstation Resource Guide in Online Books

Files required


Files required for C2 Configuration Manager

C2ACLS.DLL

C2CONFIG.EXE

C2CONFIG.HLP

C2CONFIG.INF

C2DLL.H

C2DLL.TXT

C2FUNCS.DLL

C2NTFACL.INF

C2REGACL.INF


CHOICE.EXE: User Input for Batch Files
Batch Tools

CHOICE.EXE: User Input for Batch Files

CHOICE prompts the user to make a choice in a batch program by displaying a prompt and pausing for the user to choose from among a set of keys. You can use this command only in batch programs.

CHOICE topics

CHOICE syntax

CHOICE examples: What the user sees when you use CHOICE in a batch file

CHOICE examples: What the user sees if you leave out a prompt

CHOICE examples: What the user sees if you use the /T switch

CHOICE ERRORLEVEL note

Files required


File required for CHOICE

CHOICE.EXE


CHOICE.EXE: User Input for Batch Files

CHOICE syntax

CHOICE examples: What the user sees when you use CHOICE in a batch file

CHOICE examples: What the user sees if you leave out a prompt

CHOICE examples: What the user sees if you use the /T switch

CHOICE ErrorLevel Note


To use Choice
CHOICE.EXE: User Input for Batch Files

CHOICE syntax	  Open Command Prompt now.

choice [/c[:]choices] [/n] [/s] [/t[:]c,nn] [text]

Where:

/c[:]choices

specifies allowable keys in the prompt. When displayed, the keys will be separated by commas, will appear in brackets ([]), and will be followed by a question mark. If you don't specify the /c switch, CHOICE uses YN as the default (which displays as [Y, N]). The colon (:) is optional.

/n

causes CHOICE not to display the prompt. The text before the prompt is still displayed, however. If you specify the /n switch, the specified keys are still valid.

/s

causes CHOICE to be case-sensitive. If the /s switch is not specified, CHOICE will accept either uppercase or lowercase for any of the keys that the user specifies.

/t[:]c,nn

causes CHOICE to pause for a specified number of seconds before defaulting to a specified key. The values for the /t switch are as follows:

c = the character to default to after nn seconds. The character must be in the set of choices specified in the /c switch.

nn = the number of seconds to pause. Acceptable values are from 0 to 99. If 0 is specified, there will be no pause before defaulting.

text

specifies text you want to be displayed before the prompt. Quotation marks are necessary only if you include a switch character (/) as part of the text before the prompt. If you don't specify text, CHOICE displays only a prompt.


Choice examples: What the user sees when you use Choice in a batch file
CHOICE.EXE: User Input for Batch Files

CHOICE examples: What the user sees when you use CHOICE in a batch file

If you use the following syntax in a batch file:

  choice /c:ync

then the user sees the following when CHOICE is started:

    [Y,N,C]?

If you add text to the syntax:

  choice /c:ync Yes, No, or Continue

then the user sees the following when CHOICE is started:

    Yes, No, or Continue [Y,N,C]?


Choice Examples: What the user sees if you leave out a prompt
CHOICE.EXE: User Input for Batch Files

CHOICE examples: What the user sees if you leave out a prompt

If, as in the following example, you use the /N switch to leave out the prompt in a batch program:

  choice /n Yes, No, or Continue?

then the user sees only the text you specified when CHOICE is started:

    Yes, No, or Continue?


Choice examples: What the user sees if you use the /T switch
CHOICE.EXE: User Input for Batch Files

CHOICE examples: What the user sees if you use the /T switch

If you use the following syntax in a batch program:

  choice /c:ync /t:n,5

then the user sees the following when CHOICE is started:

    [Y,N,C]?

If, after 5 seconds, the user hasn't pressed a key, CHOICE chooses N and returns an ERRORLEVEL value of 2. If the user presses a key before 5 seconds, CHOICE returns the value corresponding to the user's choice.


Choice ERRORLEVEL note
CHOICE.EXE: User Input for Batch Files

CHOICE ERRORLEVEL note

ERRORLEVEL is set to the offset of the key that the user presses in choices.

The first key you assign returns a value of 1, the second a value of 2, the third a value of 3, and so on. If the user presses a key that is not among the keys you assigned, CHOICE sounds a warning beep (that is, it sends a BEL, or 07h, character to the console).

If CHOICE detects an error condition, it returns an ERRORLEVEL value of 255.

If the user presses CTRL+BREAK or CTRL+C, CHOICE returns an ERRORLEVEL value of 0.

When you use ERRORLEVEL parameters in a batch program, list them in decreasing order.


CLIP.EXE: Clip
Batch Tools

CLIP.EXE: Clip

This command-line utility dumps STDIN to the Windows NT Clipboard.

To use Clip

Open Command Prompt now.

1	Run any program that prints text to STDOUT and pipe the results through Clip. Clip will read from its STDIN and copy the text to the Clipboard.

2	Use the Paste command from any application that can handle text in the Clipboard.

Example

dir | clip

copies a folder listing onto the Clipboard. Next run Notepad (or any other text editor) and choose Edit | Paste from the menu. The folder listing will be pasted into Notepad.

Files required


File required for Clip

CLIP.EXE


COMPREG.EXE
Registry Tools

COMPREG.EXE

A Win32 character-based/command-line "Registry DIFF" that enables you to compare any two local and/or remote Registry keys in both Windows NT and Windows 95.

For more information

Open COMPREG.TXT now.

Files required


File required for COMPREG

COMPREG.EXE

COMPREG.TXT


COMPRESS.EXE: File Compress
File Tools

COMPRESS.EXE: File Compress

This command-line utility can compress one or more files.

Compress syntax

  Open Command Prompt now.

compress [-r] [-d] source [destination] [-?]

Where

-r

renames compressed files.

-d

updates compressed files only if out of date.

source

specifies the source file. The "*" and "?" wildcards can be used.

destination

specifies the destination file or path. The destination can be a folder. If source specifies multiple files and -r is not specified, then destination must be a folder.

-?

shows command-line help.

Related topics

Files required


File required for Compress

COMPRESS.EXE


Crystal Reports
Computer Diagnostic Tools

Crystal Reports Event Log Viewer

Server only	Included in the Windows NT Server, but not Workstation, Resource Kit.

Crystal Reports Event Log Viewer is a full-featured report writer that provides an easy way to extract, view, save, and publish information from the Windows NT system, application and security event logs in a variety of formats.

Crystal Reports offers direct access to the event logs of multiplecomputers. It can open and manipulate existing log files (in read-only mode) and Access database files. Enhancements in this version allow more flexibility in filtering and analyzing data contained in the security event log.

Crystal Reports allows you to format and group information, then export it to a printer, word processor, or spreadsheet. It includes 12 useable reports that quickly provide information from one or multiple computers in a single report.

The main components of Crystal Reports are CRW.EXE, the report designer-viewer, and CRPE.DLL, the print engine that generates reports.

For more information

See README.HLP in the \CRYSTAL\DISK1 folder on the Resource Kit CD.

Related topics

Files required


Files required for Crystal Reports

The files required for Crystal Reports are in the \APPS\CRYSTAL folder on the Resource Kit CD. Crystal Reports must be installed separately from the Resource Kit.


dbWeb
Internet and TCP/IP Services/Tools

dbWeb

Run dbWeb Administrator now.

Server only	Included in the Windows NT Server, but not Workstation, Resource Kit.

dbWeb is a gateway between Microsoft Open Database Connectivity (ODBC) data sources and the Internet Information Server (IIS). You can use dbWeb to publish data from an ODBC data source and provide familiar World Wide Web (WWW) hypertext navigation. While allowing users to create queries, dbWeb enables you to filter the data and sources users can access and display.

dbWeb works with any client/server or desktop database that supports 32-bit ODBC, including:

Microsoft SQL Server

Microsoft Access

Microsoft Visual FoxPro

Oracle

dbWeb topics

dbWeb components

Installing dbWeb

For more information

DBWEB.HLP contains detailed information on setting up, configuring, and using dbWeb.

Open DBWEB.HLP now.

The dbWeb Tutorial shows how to quickly publish your database by using the built-in wizard. It also shows how to customize the default display pages generated by dbWeb.

Open the dbWeb Tutorial (DBTUTOR.DOC) now.

Files required


Files required for dbWeb

The files for dbWeb are in the \APPLICATIONS\DBWEB folder of the Windows NT Resource Kit CD


dbWeb

dbWeb components

Installing dbWeb


dbWeb components
dbWeb

dbWeb components

dbWeb Administrator
offers an easy graphical user interface that helps you create Hyper-Text Markup Language (HTML) pages that present information to Internet clients. You do not need to program in HTML or Internet Server Application Programming Interface (ISAPI) to use dbWeb Administrator.

With a question-and-answer wizard, dbWeb Administrator guides you through creating a Web site, determining how the information in a database is published, and controlling what information is displayed.

dbWeb Service
a Windows NT Server service, communicates between IIS and the ODBC data source, processing queries from a user using a Web browser, then formatting and displaying the results.


Installing dbWeb
dbWeb

Installing dbWeb

Open DBWEB.HLP now.

dbWeb requires 10MB of hard disk space on a personal computer with an Intel Pentium or higher microprocessor.

The following must be installed on yourcomputer:

Internet Information Server (IIS)

Typically, IIS resides in the INETSRV directory.

ODBC

While installing dbWeb, you can choose to add ODBC as well if you do not currently have it.

Internet Explorer or another web browser

Before installing dbWeb, you must install the IIS and the ODBC drivers.

To install dbWeb

In the \APPLICATIONS\DBWEB folder of the Windows NT Resource Kit CD, run SETUP.EXE.

If you accept the default setup options, Microsoft dbWeb creates the following directories.

Directory	Description
\dbWeb	dbWeb root directory
\dbWeb\admin	dbWeb Administrator executable
\dbWeb\ODBC32	Microsoft ODBC 2.5
\dbWeb\server	dbWeb NT service executable
\inetsrv\scripts\dbWeb	dbWeb Server executable
\dbWeb\samples\NWind	Sample database
\dbWeb\samples\Pubs	Sample database
If you chose to add the ODBC files when you installed dbWeb, you need to run the ODBC setup program to install ODBC.

To install ODBC

On the Start menu for ODBC, click the ODBC Setup icon.

After installing ODBC, you can use the ODBC Administrator see the two system data sources called dbpubs and dbWebSchema that the dbWeb setup program automatically adds. You can use these two dsn's to practice using dbWeb.

After installing, you can run a test Web page in your Web browser to make sure that all of the components are working together.


DELPROF.EXE: User Profile Deletion Utility
User Account Administration Tools

DELPROF.EXE: User Profile Deletion Utility

Run DELPROF now.

This utility deletes user profiles on computers running Windows NT.

It can be run on a local or remote computer running any version of Windows NT through 4.0 (but not Windows 95—the tool is Unicode-based).

On Windows NT 4.0, user profiles can grow quite large (easily over a megabyte each), which takes up considerable disk space when several people are using onecomputer. With this tool, administrators can free up disk space on a computer when some users are no longer working on it.

Caution	This tool will delete everything in a user's profile, including settings, colors, and documents.

DelProf topic

DelProf syntax

Related topics

Files required


File required for DelProf

DELPROF.EXE


DelProf syntax
DelProf

DelProf syntax	  Open Command Prompt now.

delprof [/q] [/i] [/p] [/c:\\computername] [/d:days] [/?]

Where:

/q

runs DelProf in quiet mode, with no confirmation for each profile to be deleted.

/i

indicates that DelProf should ignore errors and continue deleting.

/p

prompts for confirmation before deleting each profile.

/c:\\computername

specifies a remote computer name on which to run DelProf.

/d:days

specifies the number of days of inactivity (days is an integer). Profiles with longer inactivity will be deleted.

/?

displays command-line syntax


DELSRV.EXE
Registry Tools

DELSRV.EXE

This command-line utility unregisters a service with the service control manager.

Files required


File required for DELSRV

DELSRV.EXE


Desktop Themes for Windows NT 4.0
Desktop Tools

Desktop Themes for Windows NT 4.0

Run Desktop Themes now.

Desktop Themes include a variety of visual, sound, and symbolic components that can enhance the look and feel of your Windows NT 4.0 desktop. Each desktop theme includes a background wallpaper, a screen saver, a color scheme, and a set of sounds, cursors, icons, and fonts.

You can use a theme as it is, or you can modify it by changing one or more of its desktop elements.

To select a desktop theme, double-click Desktop Themes in Control Panel.

Note	Some desktop themes require a video card and monitor that support at least 256 colors. Other desktop themes require a video card and monitor that support high color (16-bit or greater). To see which themes are high color, double-click the Desktop Themes icon in Control Panel, and then scroll through the Theme list.

For more information

For Help on an item, use the right mouse button to click an item, and then click the What's This? command.

For information on using Desktop Themes:

Open Desktop Themes Help now.

Files required


Files required for Desktop Themes

THEMES.CPL

THEMES.EXE

THEMES.HLP

THEMES.CNT

Desktop Themes media files


Desktop Themes is not installed on your computer. To install it:

1	Have your Windows NT Workstation or Server Resource Kit installation CD handy.

2	Click here  [image]  to open the Add/Remove Programs properties.

3	Click Windows NT Workstation or Server Resource Kit, and then click Add/Remove to start setup.

4	Click Add/Remove, and then follow the instructions on your screen.


DESKTOPS.EXE: DeskTops
Desktop Tools

DESKTOPS.EXE: DeskTops

Run DeskTops now.

This desktop-switching application for Windows NT 4.0 enables you to customize desktop wallpaper and colors and separate executing programs into new deskspaces.

DeskTops was formerly knows as MultiDesk.

For more information

Open the DeskTops documentation (DESKTOPS.WRI) now.

Related topics

Files required


Files required for DeskTops

DESKTOPS.EXE

DESKTOPS.WRI


DFLYDIST.EXE: Compound File Layout User Tool
File Tools

DFLYDIST.EXE: Compound File Layout User Tool

This layout tool for document files enables you to optimize compound files for improved performance over low-bandwidth networks, such as the Internet. The utility is particularly useful for Web masters interested in publishing compound files on the World Wide Web.

Compound File Layout User Tool provides a graphical interface for quickly selecting and optimizing compound files. The tool launches the application associated with a selected compound file, monitors its usage pattern, and then reorganizes the file according to the usage pattern necessary to load and view the file. The application used to create the files to be optimized must be installed on the computer.

For example, Compound File Layout User Tool could be used to optimize Microsoft Word .DOC files. All the data and control structures necessary for downloading and displaying the selected file will be relocated at the beginning of the file.

Once a file has been optimized, the end user can use an asynchronous storage-enabled browser to access and read the file without having to wait until the entire file has finished downloading. An optimized file also loads faster when accessed over a network or on the local hard disk. It also may be smaller than the original file, since unused/reserved space inside the file is removed.

To install Compound File Layout User Tool

Run DFLYDIST.EXE.

DFLYDIST.EXE is a self-extracting setup program that installs DFLAYOUT.DLL and DFLAYOUT.EXE into the system directory.

Files required


Files required for Compound File Layout User Tool

DFLYDIST.EXE


DH.EXE
Network/Server Administration Tools

DH.EXE

This command-line utility enables your to lock heaps, tags, stacks, and objects.

Files required


Files required for DH

DH.EXE


DHCPCMD.EXE: DHCP Administrator's Tool
Internet and TCP/IP Services/Tools

DHCPCMD.EXE: DHCP Administrator's Tool

Server only	Included in the Windows NT Server, but not Workstation, Resource Kit.

The command-line DHCP Administrator's Tool provides an auxiliary method of administering DHCP servers.

DHCP Administrator's Tool topics

DHCP Administrator's Tool syntax

AddIpRange

AddReservedIp

EnumClients

MibCounts

ServerConfig

For more information

Open DHCPCMD.TXT now.

Files required


Files required for DHCP Administrator's Tool

DHCPCMD.EXE

DHCPCMD.TXT


DHCPCMD.EXE: DHCP Administrator's Tool

DHCP Administrator's syntax

AddIpRange

AddReservedIp

EnumClients

MibCounts

ServerConfig


To use DHCP Administrator's Tool
DHCPCMD.EXE: DHCP Administrator's Tool

DHCP Administrator's Tool syntax	Open Command Prompt now.

dhcpcmd ServerIpAddress command [command parameters]

Where:

ServerIpAddress

specifies the IP address of the DHCP server on which you are running the command.

command

is one of the commands in the following list:

AddIpRange

AddReservedIp

EnumClients

MibCounts

ServerConfig

command parameters

are parameters you may have to specify, depending on the value of command. For information on these parameters, choose the topic for the appropriate command from the preceding list.

Note	The command-line usage listing for DHCP Administrator's Tool, displayed by running dhcpcmd /?, shows a sixth command, GetVersion. The command-line usage is incorrect: GetVersion is not supported.


DHCPCMD ADDIPRANGE
DHCPCMD.EXE: DHCP Administrator's Tool

DHCPCMD ADDIPRANGE

Adds another IP range to an already existing scope.

Usage:

dhcpcmd ServerIpAddress addiprange ScopeAddress StartIpRange EndIpRange

Example:

dhcpcmd 127.0.0.1 addiprange 11.101.0.0 11.101.4.1 11.101.4.254


DHCPCMD ADDRESERVEDIP
DHCPCMD.EXE: DHCP Administrator's Tool

DHCPCMD ADDRESERVEDIP

Adds a reserved IP to an already existing scope.

Usage:

dhcpcmd ServerIpAddress addreservedip ScopeAddress ReserveIp HardwareString

Example:

dhcpcmd 127.0.0.1 addreservedip 11.101.0.0 11.101.13.53 08002B30369B


DHCPCMD ENUMCLIENTS
DHCPCMD.EXE: DHCP Administrator's Tool

DHCPCMD ENUMCLIENTS

Lists the lease information in a different format.

Usage:

dhcpcmd ServerIpAddress enumclients ScopeAddress [-v | -h]

Where -v displays detailed lease information, and -h displays lease information including hardware information.

Example:

dhcpcmd 127.0.0.1 enumclients 11.101.0.0 -h


DHCPCMD MIBCOUNTS
DHCPCMD.EXE: DHCP Administrator's Tool

DHCPCMD MIBCOUNTS

Displays the current DHCP server statistic information.

Usage:

dhcpcmd ServerIpAddress mibcounts

Example:

dhcpcmd 127.0.0.1 mibcounts


DHCPCMD SERVERCONFIG
DHCPCMD.EXE: DHCP Administrator's Tool

DHCP SERVERCONFIG

Displays and sets server parameters.

Usage:

dhcpcmd ServerIpAddress serverconfig [ConfigParameter] [Value]

Where:

ConfigParameter

can be any of the DHCP server parameters.

Value

is the value to which you want to set that parameter.

Typing dhcpcmd ServerIpAddress serverconfig with no further options displays the DHCP server parameters.

Example:

dhcpcmd 127.0.0.1 serverconfig

dhcpcmd 127.0.0.1 serverconfig backupinterval 15

The first example displays DHCP Server parameters, and the second example sets the backupinterval parameter to 15.


DHCPLOC.EXE: DHCP Server Locator Utility
Internet and TCP/IP Services/Tools

DHCPLOC.EXE: DHCP Server Locator Utility

Server only	Included in the Windows NT Server, but not Workstation, Resource Kit.

Use this command-line utility to detect unauthorized DHCP servers on a subnet.

DHCPLOC.EXE displays the DHCP servers active on the subnet. It beeps and sends out alert messages if it detects any unauthorized DHCP servers. It also displays packets it detects from DHCP servers; you can specify whether it displays packets from all DHCP servers, or only from unauthorized servers.

DHCP Server Locator Utility topics

DHCP Server Locator Utility syntax

DHCP Server Locator Utility output

For more information

Open DHCPLOC.TXT now.

Files required


Files required for DHCP Server Locator Utility

DHCPLOC.EXE

DHCPLOC.TXT


DHCPLOC.EXE: DHCP Server Locator Utility

DHCP Server Locator Utility syntax

DHCP Server Locator Utility output


To use DHCP Server Locator Utility
DHCPLOC.EXE: DHCP Server Locator Utility

DHCP Server Locator Utility syntax	  Open Command Prompt now.

dhcploc [-p] [-a:alertname_list] [-i:alertinterval] computer_ip_address [valid_dhcp_server_list]

Where:

-p:

specifies not to display detected packets from any of the authorized DHCP servers specified in valid_dhcp_server_list.

-a:alertname_list

specifies to send alert messages to the names in alertname_list if any unauthorized DHCP servers are found.

-i:alertinterval

specifies the alert frequency in seconds.

computer_ip_address

specifies the IP address of the computer from which you are running DHCPLOC. If the computer has multiple adapters, you must specify the IP address of the adapter that is connected to the subnet you want to test.

valid_dhcp_server_list

specifies the IP addresses of any number of authorized DHCP servers. The utility will not send alerts when it detects packets from the servers in this list. However it will display those packets unless you specify the -p option.


DHCP Server Locator Utility output
DHCPLOC.EXE: DHCP Server Locator Utility

DHCP Server Locator Utility output

The output of DHCP Server Locator Utility will be formatted as follows:

time (IP) ipaddress OfferedPacketType (S) ServerIPAddress [***]

where "***" indicates a packet from an unauthorized server.

Sample output:

17:34:58 (IP)0.0.0.0        NACK      (S)11.11.31.84         ***

17:36:38 (IP)11.101.190.130 OFFER     (S)11.101.12.226       ***

17:36:38 (IP)11.101.196.231 ACK       (S)11.101.13.53

17:36:53 (IP)11.101.196.231 ACK       (S)11.101.13.53

17:37:05 (IP)11.101.196.234 OFFER     (S)11.101.13.53

17:37:05 (IP)11.101.193.232 OFFER     (S)11.101.12.198

17:37:06 (IP)11.101.190.132 OFFER     (S)11.101.12.226       ***


DIRUSE.EXE: Directory Disk Usage
File Tools

DIRUSE.EXE: Directory Disk Usage

DirUse shows disk space used per folder. You can use this utility to check how disk space is being used in users' home folders. If you run DirUse while logged on as a member of the Administrators group, you can check the use of disk space in folders on an NTFS partition, even if you don't have access rights to those folders.

You can also specify a maximim folder size, and DirUse will mark any folders that exceed it and, if you choose, alert you to the problem.

DirUse topic

DirUse syntax

Files required


File required for DirUse

DIRUSE.EXE


To use DirUse
DIRUSE.EXE: Directory Disk Usage

DirUse syntax	  Open Command Prompt now.

diruse {/s | /v} {/m | /k | /b} [/c] [/,] [/q:# [/l] [/a] [/d] [/o]] [/*] dirs

Where:

/s

includes sub-folders of the specified folders in the output.

/v

outputs progress reports while scanning sub-folders. Ignored if /s is specified.

/m

displays disk usage in megabytes.

/k

displays disk usage in kilobytes.

/b

displays disk usage in bytes (default).

/c

uses compressed file size instead of apparent file size.

/,

displays the thousands separator (comma or period) in file sizes.

/q:#

marks folders that exceed the specified size (#) with a "!". If /m (megabytes) or /k (kilobytes) is not specified, then the size is assumed to be in bytes.

If /q is specified, then the return code is ONE if any folders are found that exceed the specified sizes. Otherwise the return code is ZERO.

/l

outputs overflows to logfile DIRUSE.LOG in the current folder.

/a

specifies that an alert is generated if sizes specified by /q:# are exceeded. The Alerter service must be running, and the alert appears only when you are using DirUse.

/d

displays only folders that exceed specified sizes.

/o

specifies that sub-folders are not checked to see if they exceed the specified size.

/*

uses the top-level folders residing in the specified dirs.

dirs

specifies a list of paths to check. dirs is required.

diruse with no parameters or with any unrecognized parameter displays command-line help.

Parameters can be typed in any order. You can use the "-" (dash) symbol rather than the "/" symbol. For example:

diruse -s -m -q:1.5 -l -* c:\users


DiskMap
Disk/Fault Tolerance Tools

DISKMAP.EXE

This command-line utility produces a detailed report on the configuration of the hard disk that you specify. It provides information from the Registry about disk characteristics and geometry, and reads and displays data about all of the partitions and logical drives defined on the disk.

A good use for this utility is to run it for each disk in your computer, print out the configuration report for each disk, and save the hardcopy with the other configuration information that you maintain for your computer. This information can then be used to reconstruct the hard disk structure in case of some kinds of disk problems.

For more information

For detailed background on DiskMap and related Resource Kit utilities, see the "Disk, File System and Backup Utilities" chapter in the Windows NT Server Resource Guide.

If you have installed the Online Books, click to:

Open Windows NT Server Resource Guide in Online Books

DISKMAP syntax

Open Command Prompt now.

diskmap /d<drive#> [/h]

Where:

/d<drive#>

specifies the number <drive#> of the physical disk for which you want a map.

/h

specifies hexadecimal output. The default is decimal output. Some fields (described in Disk Utilities," Windows NT Workstation Resource Guide) are always decimal or always hexadecimal regardless of the value of this parameter.

Related topics

Files required


Files required for DISKMAP

DISKMAP.EXE


DISKSAVE.EXE
Disk/Fault Tolerance Tools

DISKSAVE.EXE

DISKSAVE allows you to save the Master Boot Record and Partition Boot Sector as binary image files. Once these critical disk structures have been saved, they can be easily restored if they become corrupted later on.

This tool also enables you to disable fault tolerance on the Boot Drive, which can be useful when Windows NT will not boot from a mirrored system drive.

The Master Boot Record (MBR) contains code that the BIOS on x86-based computers uses to read the partition table and jump to the operating-system partition. This sector also contains the partition tables. If this sector becomes damaged, the computer will not boot. DISKSAVE saves the MBR of the boot drive only.

The Partition Boot Sector contains code that loads the operating system kernel or a multi-boot loader. A corrupt Boot Sector can also cause boot failures. DISKSAVE saves the Partition Boot Sector of the system partition only (the partition that contains the files used to load Windows NT).

To run this utility, you must first boot MS-DOS.

Platform	DISKSAVE runs only on x86-based computers.

For more information

For information on how to use DiskSave:

Open DISKSAVE.TXT now.

For detailed background on DiskSave and related Resource Kit utilities, see the "Disk, File System and Backup Utilities" chapter in the Windows NT Server Resource Guide.

If you have installed the Online Books, click to:

Open Windows NT Server Resource Guide in Online Books

Related topics

Files required


Files required for DISKSAVE

DISKSAVE.EXE

DISKSAVE.TXT


DNSSTAT.EXE
Internet and TCP/IP Services/Tools

DNSSTAT.EXE

This command-line utility provides a dump of DNS server statistics (queries and responses, database size, caching, memory consumption) on a computer running Microsoft DNS Server.

You can also use DNSSTAT to clear these statistics without stopping the DNS server. By default, these statistics are cumulative and are not normally cleared until the computer running Microsoft DNS Server is stopped.

DNSSTAT syntax

Open Command Prompt now.

dnsstat {servername | IP address} [{-c | /c | -clear | /clear}]

Where

servername

gives a dump of all DNS server statistics on the server named servername.

IP address

gives a dump of all DNS server statistics on the server with the IP address indicated.

-c or /c or -clear or /clear

clears clearable DNS statistics on the server indicated.

For more information

Run dnsstat at the command prompt without parameters for a usage screen.

Files required


File required for DNSSTAT

DNSSTAT.EXE


DOMMON.EXE: Domain Monitor
Network Diagnostic Tools

DOMMON.EXE: Domain Monitor

Run Domain Monitor now.

Server only	Included in the Windows NT Server, but not Workstation, Resource Kit.

Domain Monitor monitors the status of servers in a domain and the secure channel status to the domain controller and to domain controllers in trusted domains. Domain Monitor displays the domain controller name and a list of trusted domains, plus various status errors.

To use Domain Monitor

Double-click the Domain Monitor icon in the Resource Kit program group.

To get online Help while working in Domain Monitor, press F1.

For more information

Open Domain Monitor Help now.

Files required


Files required for the Domain Monitor

DOMMON.EXE

DOMMON.HLP


DRIVERS.EXE: List Loaded Drivers
Computer Diagnostic Tools

DRIVERS.EXE: List Loaded Drivers

List Loaded Drivers displays character-based information about the installed device drivers. There are no command-line arguments.

List Loaded Drivers syntax

Open Command Prompt now.

drivers | more

Format for Drivers data

ModuleName   Code   Data   Bss   Paged   Init   LinkDate

ModuleName	The driver’s filename.

Code	The executable code in the image.

Data	The non-.BSS data in the image.

Bss	The .BSS section from the image.
This is data that is initialized to 0.

Paged	The size of the data that is paged.

Init	The size of the file on disk.

LinkDate	The date that the driver was linked.

Related topics

Files required


File required for Drivers

DRIVERS.EXE


DSKPROBE.EXE: DiskProbe
Disk/Fault Tolerance Tools

DSKPROBE.EXE: DiskProbe

Run DiskProbe now.

DiskProbe is a sector editor for Windows NT Workstation and Server. It allows a user with local Administrator rights to directly edit, save and copy data on the physical hard drive that is not accessible in any other way.

You can use DiskProbe to replace the Master Boot Record, repair damaged partition table information and to repair or replace damaged Partition Boot Sectors or other file system data. The program can also save Master Boot Records and Partition Boot Sectors as files. They can then be replaced if the sectors become damaged at a later time. These on-disk data structures are not accessible through the file system, and so are not saved by any backup programs currently available.

Restrictions

Only users with local Administrator rights can use DiskProbe to access the physical disk. Other users can run DiskProbe, but in the “Open Physical Drive” dialog box, no physical drives will be listed.

DiskProbe will run under Windows 95, but no physical drives will be available. Windows 95 still uses BIOS Interrupt 13 calls for disk access, and does not support the kernel mode calls necessary to access large physical drives. But under Windows 95 you can still open, edit, and save files as raw hex data.

Command-line usage

Although it is a GUI utility, DiskProbe can also be run from the command prompt. Only the path and filename are supported as arguments, for example:

dskprobe c:\mydir\sector00.dsk

This example runs DiskProbe and opens SECTOR00.DSK in the C:\MYDIR folder.

After the program has been run, double-clicking a file with the .DSK extension will start DiskProbe and load the file.

Caution	Because any sector editor allows direct access to a physical drive, it is possible to damage or permanently overwrite critical on-disk data structures. Backup all critical data before using any low-level utility such as DiskProbe. Misuse of low-level tools such as DiskProbe may make all data on a drive or volume permanently inaccessible.

For more information

For information on how to use DiskProbe:

Open DSKPROBE.HLP now.

For detailed background on DiskProbe and related Resource Kit utilities, see the "Disk, File System and Backup Utilities" chapter in the Windows NT Server Resource Guide.

If you have installed the Online Books, click to:

Open Windows NT Server Resource Guide in Online Books

Related topics

Files required


Files required for DiskProbe

DSKPROBE.EXE

DSKPROBE.HLP

MFC40.DLL

MSVCRT40.DLL

Note These DLLs may be used by other Resource Kit utilities

DiskProbe uses no configuration files. The only change it makes to the Registry is to register the shell type and default file extension (.DSK).


DUMPEL.EXE: Dump Event Log
Computer Diagnostic Tools

DUMPEL.EXE: Dump Event Log

Dump Event Log is a command-line utility that dumps an event log for a local or remote system into a tab-separated text file. This utility can also be used to filter for or filter out certain event types.

Dump Event Log topics

Dump Event Log syntax

Dump Event Log Examples

For more information

Open DUMPEL.TXT now.

Related topics

Files required


Files required for DUMPEL

DUMPEL.EXE

DUMPEL.TXT


DUMPEL.EXE: Dump Event Log

Dump Event Log syntax

Dump Event Log Examples


To use Dump Event Log
Dump Event Log

Dump Event Log syntax	  Open Command Prompt now.

dumpel -f file [-s \\server] [-l log [-m source] [-e n1 n2 n3...] [-r] [-t]

Where:

-f file

specifies the filename for the output file. There is no default for -f, so you must specify the file.

-s server

specifies the server for which you want to dump the event log. Leading backslashes on the server name are optional.

-l log

specifies which log (system, application, security) to dump. If an invalid logname is specified, the application log will be dumped.

-m source

specifies in which source (such as Rdr, Serial, ...) to dump records. Only one source can be supplied. If this switch is not used, all events are dumped. If a source is used that is not registered in the Registry, the application log will be searched for records of this type.

-e n1 n2 n3 ...

filters for event ID nn (up to 10 can be specified). If the -r switch is not used, only records of these types are dumped; if -r is used, all records except records of these types are dumped. If this switch is not used, all events from the specified sourcename are selected. You cannot use this switch without the -m switch.

-r

specifies whether to filter for specific sources or records, or to filter them out.

-t

specifies that individual strings are separated by tabs. If -t is not used, strings are separated by spaces.


Dump Event Log examples
Dump Event Log

Dump Event Log examples

To dump the system event log on server \\EVENTSVR to a file named EVENT.OUT, use:

dumpel -f event.out -s eventsvr -l system

To dump the local system event log to a file named EVENT.OUT, but only get Rdr events 2013, use:

dumpel -f event.out -l system -m rdr -e 2013

To dump the local application log to a file named EVENT.OUT, and get all events except ones from the Garbase source, use:

dumpel -f event.out -l application -m garbase -r


EM2MS.EXE
Internet and TCP/IP Services/Tools

EM2MS.EXE

This command-line utility converts verbose descriptions of files stored on NT-based EMWAC (European Microsoft Windows NT Academic Centre) Gopher Servers to the Microsoft Internet Information Gopher Server content format. EM2MS.EXE is useful for EMWAC Gopher Server administrators who want to begin using the Microsoft Internet Information Gopher Server. It allows them to easily convert their EMWAC-based content descriptions to the Microsoft Gopher tag-file format.

The EMWAC Gopher server has a feature that allows it to cache descriptive tag information for each file stored in a directory. This cached information is kept in a single CACHE.GFR file found within each content subdirectory. EM2MS parses these CACHE.GFR files and creates individual hidden "gopher tag" files. During the conversion process, no files are damaged, deleted, or modified.

These hidden tag files (named FOO.GTG on FAT volumes or FOO:GTG on NTFS volumes) can then be used by the Microsoft Internet Information Gopher Server to display descriptive information about each file stored in the local subdirectory. The GDSSET.EXE utility, provided with Microsoft Internet Information Server, can then be used to view and edit the individual hidden tag files.

In the current version, the recursive subdirectory feature is not yet available, but administrators can still use the tool on a single directory-by-directory basis.

For more information

To display descriptive command-line usage, run em2ms.exe -? at the command line.

Files required


File required for EM2MS

EM2MS.EXE


EMWAC Server CGI Scripts
Internet and TCP/IP Services/Tools

EMWAC Server CGI Gateway Scripts

Server only	Included in the Windows NT Server, but not Workstation, Resource Kit.

A gateway script is an executable program that uses the CGI protocol, Common Gateway Interface, to communicate with a server on the World Wide Web. Gateway scripts add custom features to a Web server, increasing the diversity of services that a Web server can provide to the Web browser.

The example gateway script provided in the Resource Kit demonstrates how to provide access to the Microsoft SQL Server. The script accepts a single SQL statement, which it passes on to SQL Server. The results, including any error messages, are returned to the browser for display to the user.

To compile and use this script requires some familiarity with the C programming language, the DB-Library routines, and HTML.

The EMWAC Server CGI Gateway Scripts are provided by European Microsoft Windows NT Academic Centre.

EMWAC Server CGI Gateway Scripts topics

To compile the example

To install EMWAC Server CGI Gateway Scripts

For more information

Open SQL_CGI.DOC now.

Open SQL_CGI.HTM now.

Files required


Files required for EMWAC Server CGI Gateway Scripts

These files are installed by the Resource Kit in the %NTRESKIT%\EMWAC folder.

SQL_CGI.C

SQL_CGI.DOC

SQL_CGI.HTM

SQL_CGI.MAK


EMWAC Server CGI Gateway Scripts

To compile the example

To install EMWAC Server CGI Gateway Scripts


EMWAC Server CGI Scripts: To compile the example
EMWAC Server CGI Gateway Scripts

To compile the example

To compile the example requires the following software:

Microsoft Visual C++ 2.0 or another compiler capable of producing a Win32 console application.

SQL Server Programmer’s Toolkit

The example program file is named SQL_CGI.C; the make file is named SQL_CGI.MAK. To compile and link the program also requires the following files from the Microsoft SQL Server Programmer’s Toolkit:

SQLDB.H

SQLFRONT.H

NTWDBLIB.LIB


EMWAC Server CGI Scripts: To install EMWAC Server CGI Gateway Scripts
EMWAC Server CGI Gateway Scripts

To install EMWAC Server CGI Gateway Scripts

Place the SQL_CGI.EXE program (after compiling it) and the SQL_CGI.HTM files on the data folder of the Web Server.

To use this gateway script also requires the following software:

Window NT 3.5 or later

SQL Server 4.21

Web Server software

Any Web browser


ENUMPRN.EXE
Computer Diagnostic Tools

ENUMPRN.EXE

Run ENUMPRN now.

This GUI utility enumerates installed printer drivers.

Files required


Files required for ENUMPRN

ENUMPRN.EXE


EXCTRLST.EXE: Extensible Performance Counter List
Computer Diagnostic Tools

EXCTRLST.EXE: Extensible Performance Counter List

Run Extensible Performance Counter List now.

This utility provides information on the Extensible Performance Counter DLLs that have been installed on a computer running Windows NT, listing the services and applications that provide performance information via the Windows NT Registry. You can use these performance counters for optimizing and troubleshooting.

Windows NT Server and Windows NT Workstation are thoroughly instrumented to measure many aspects of performance and status. These measurements are collected in the Performance Registry and can be conveniently displayed using Performance Monitor (PERFMON.EXE), a tool provided with the Windows NT operating system.

To enable device drivers, system services and applications to display performance data in Performance Monitor along with the standard system measurements, an interface is published to enable the developers of these programs to provide these data to the Performance Registry. Once the information can be read by the Performance Registry, it can be viewed in Performance Monitor. Extensible Performance Counter List reads the Registry to find the programs and devices that have registered an Extensible Performance Counter library.

For more information

For details on how to use Extensible Performance Counter List:

Open EXCTRLST.DOC now.

Files required


Files required for Extensible Performance Counter List

EXCTRLST.EXE


EXETYPE.EXE: Finding the Executable Type
File Tools

EXETYPE.EXE: Finding the Executable Type

ExeType is a command-line application that identifies the operating system environment and processor required to run a particular executable file.

You can use ExeType to determine:

Why an application will not run (perhaps because a subsystem is failing).

Whether to force MS-DOS mode if it is a bound OS/2 application.

ExeType topics

ExeType syntax

Example of ExeType output

EXETYPE.INI file

Files required


Files required for ExeType

EXETYPE.EXE

EXETYPE.INI


EXETYPE.EXE: Finding the Executable Type

ExeType syntax

Example of ExeType output

EXETYPE.INI file


To use ExeType
EXETYPE.EXE: Finding the Executable Type

ExeType syntax	  Open Command Prompt now.

exetype filename

Where

filename

is the name of the executable file you want information about.
ExeType does not support wildcards for filenames.

The EXETYPE.INI file must be somewhere in your PATH (if unsure, type path at the command prompt).


Example of ExeType output
EXETYPE.EXE: Finding the Executable Type

Example of ExeType output

The file MYFILE.EXE is of the following type:

        Windows NT

        32 bit machine

        Executable File

        Built for the Intel 386 processor

        Runs under the Windows GUI subsystem


EXETYPE.INI file
EXETYPE.EXE: Finding the Executable Type

EXETYPE.INI file

The format of EXETYPE.INI is as follows:

[entry1]

TYPE    string

ADDRESS hex value or **

OFFSET  hex value

MASK    hex value

VALUE   hex value or !<hex value>

ADDRESS hex value or **

OFFSET  hex value

MASK    hex value

VALUE   hex value

[entry2]

TYPE    string

HEADER  hex value or **

OFFSET  hex value

MASK    hex value

VALUE   hex value

Each Entry has one TYPE field and from one to five groups of ADDRESS, OFFSET, MASK, and VALUE fields.

Note:	All hexadecimal values must have an even number of characters (in bytes). If an odd number of nibbles is needed, please pad with zeros.


[entry] in EXETYPE.INI

This denotes the start of a new entry (80 characters maximum).


TYPE in EXETYPE.INI

A description of the file type (80 characters maximum).


ADDRESS in EXETYPE.INI

Microsoft .EXE files have the address of the header at a certain location. This value is kept at offset 3c from the beginning of the file. If your entry does not keep the address of the header in an offset, use ** and the offset parameter will be ignored.


OFFSET in EXETYPE.INI

This hexadecimal value denotes the offset from the beginning of the header.


MASK in EXETYPE.INI

This bitmask lets you screen which bits of the bytes you want to look at.


VALUE in EXETYPE.INI

This is the actual value you are comparing to the value of the bits at OFFSET strained through MASK.

The "!" denotes a logical NOT; in other words, this file fits the criteria only if the value in the file does not match this value.


EXPNDW32.EXE: File Expansion Utility
File Tools

EXPNDW32.EXE: File Expansion Utility

Run File Expansion Utility now.

You can use File Expansion Utility to expand one or more compressed files from the Windows NT CD. EXPNDW32.EXE is a 32-bit utility that provides a graphical interface for easy use.

To use File Expansion Utility

1	Click the Start button.

2	Point to Programs.

3	Point to Resource Kit 4.0.

4	Point to Desktop Tools.

5	Click File Expansion Utility.

For online Help while you are using File Expansion Utility, click the Help button or press F1.

For more information

Open File Expansion Utility Help now.

Related topics

Files required


Files required for File Expansion Utility

EXPNDW32.EXE

EXPNDW32.HLP

CTL3D32.DLL


FINDGRP.EXE: Find Group
Computer Diagnostic Tools

FINDGRP.EXE: Find Group

Server only	Included in the Windows NT Server, but not Workstation, Resource Kit.

The Find Group utility finds all direct and indirect group memberships for a specified user in a domain. This helps determine a particular user’s access to Windows NT Domain Controllers in a domain by listing the groups in which the user is a member.

Note	FINDGRP was created especially for use in a trusted domain model. Administrative access to either your domain or user’s domain is not required.

Find Group topics

FindGrp syntax

Find Group example

Files required


File required for the Find Group utility

FINDGRP.EXE


FINDGRP.EXE: Find Group

FindGrp syntax

Find Group example


FINDGRP.EXE - Example
FINDGRP.EXE: Find Group

FindGrp syntax	  Open Command Prompt now.

findgrp [your domain] [user's domain\username]

Where:

your domain

is the domain from which the group information is retrieved. Type localmachine to list groups on your local Windows NT Workstation computer.

user's domain

is the domain that contains the user account.

username

is the name of the user.

Note	your domain and user's domain can be the same. If they are not the same, your domain must trust the user’s domain.


Find Group example
FINDGRP.EXE: Find Group

Find Group example

In the following example, JohnDoe has a user account in the APPLE domain. The PEACH domain trusts the APPLE domain.

C:\reskit> findgrp peach apple\johndoe

The user is in the following APPLE Global Groups:

Domain Users

Department 10

Global Project

The user is in the following PEACH Local Groups:

Project

Test

Plans


FLOPLOCK.EXE: Lock Floppy Disk Drives
Computer Administration/Configuration Tools

FLOPLOCK.EXE: Lock Floppy Disk Drives

FloppyLock is a service that controls access to the floppy drives of a computer.

When the service is started on Windows NT Workstation, only members of the Administrators and Power Users groups can access the floppy drives. When the service is started on Windows NT Server, only members of the Administrators group can access the floppy drives.

If the FloppyLock service is configured to start automatically, the lock stays in place even after the computer is restarted. This service can be used to prevent the unauthorized installation of software or the introduction of viruses via the floppy disks.

To use the FloppyLock service, you must first install FLOPLOCK.EXE as a service on every computer where you want to lock the floppy drives. Then use Control Panel to configure this service to start automatically.

Installing the FloppyLock service is a separate task after you install the Resource Kit tools.

FloppyLock topics

To install the FloppyLock service

To configure the FloppyLock service

To remotely turn on or off the FloppyLock service

To remove the FloppyLock service

For more information

Open FLOPLOCK.TXT now.

Files required


Files required for FloppyLock

FLOPLOCK.EXE

FLOPLOCK.TXT

INSTSRV.EXE


FLOPLOCK.EXE: Lock Floppy Disk Drives

To install the FloppyLock service

To configure the FloppyLock service

To remotely turn on or off the FloppyLock service

To remove the FloppyLock service


To install the FloppyLock service
FLOPLOCK.EXE: Lock Floppy Disk Drives

To install the FloppyLock service	  Open Command Prompt now.

instsrv FloppyLocker exe-location

Where:

exe-location

Is the fully qualified path, including a drive letter that specifies a fixed, local drive, of FLOPLOCK.EXE.

For example:

instsrv FloppyLocker c:\reskit\floplock.exe


To configure the FloppyLock service
FLOPLOCK.EXE: Lock Floppy Disk Drives

To configure the FloppyLock service

Open Control Panel now.

1	In Control Panel, double-click the Services icon, and select the FloppyLock service name.

2	Click the Startup button, and select System Account (to ensure that the FloppyLock service starts properly).

3	If you want the service to start automatically, select Automatic, to ensure that the service will work across restarts and logoffs.

4	Restart the computer, log on as Guest, and try to access the floppy drives as a test.


To remotely turn on or off the FloppyLock service
FLOPLOCK.EXE: Lock Floppy Disk Drives

To remotely turn on or off the FloppyLock service

Run Server Manager now.

Use Server Manager to remotely stop and start the FloppyLock service when you are logged on as an Administrator. Stopping the FloppyLock service unlocks the floppy drives; restarting the service locks them again.


To remove the FloppyLock service
FLOPLOCK.EXE: Lock Floppy Disk Drives

To remove the FloppyLock service

Open Control Panel now.

1	Stop the service by using the Services icon in Control Panel.

Open Command Prompt now.

2	At the command prompt, type instsrv remove


FORFILES.EXE
Batch Tools

FORFILES.EXE

This command-line utility can be used in a batch file to select files in a folder or tree for batch processing.

FORFILES enable you to run a command on or pass arguments to multiple files. For example, you could run the TYPE command on all files in a tree with the *.TXT extension. Or you could execute every batch file (*.BAT) on the C:\ drive with the filename "MYINPUT.TXT" as the first argument.

FORFILES works by implementing the "recurse subdirectories" flag on tools designed to process only a single file

FORFILES topic

FORFILES syntax

Files required


File required for FORFILES

FORFILES.EXE


FORFILES syntax
FORFILES.EXE

FORFILES syntax	  Open Command Prompt now.

forfiles [-ppath] [-msearchmask] [-ccommand] [-dddmmyy] [-s] [-v] [-?]

Where:

-ppath

indicates a path on which to start searching.

The default folder is the current one from which forfiles is run.

-msearchmask

searches files according to searchmask.

The default searchmask is *.*

-ccommand

indicates a command to execute on each file.

The default command is "cmd /c echo @FILE"

The following variables can be used in command : @FILE, @PATH, @RELPATH

-dddmmyy

selects files with a date greater than or equal to ddmmyy.

-s

instructs forfiles to recurse into subdirectories.

-v

runs forfiles in verbose mode.

-?

displays this usage screen

Example

forfiles -pc:\ -s -m*.BAT -c"cmd /c echo @FILE is a batch file"


FREEDISK.EXE
File Tools

FREEDISK.EXE

This command-line utility checks for free disk space, returning a 0 If there is enough space and a 1 if there isn't.

The return value makes FREEDISK useful in batch files.

Files required


File required for FREEDISK

FREEDISK.EXE


FTEDIT.EXE: FT Registry Information Editor
Disk/Fault Tolerance Tools

FTEDIT.EXE: FT Registry Information Editor

Run FT Registry Information Editor now.

FTEDIT.EXE is a new GUI utility that allows you to create, edit, and delete fault tolerance sets for disk drives and partitions of local and remote computers. It improves on the functionality of the command-line utility SHOWDISK.EXE.

Information on disks and fault tolerance is stored as disk keys in the Registry. To read it, you only need guest access (by default), but to change it, you must have the permissions necessary to write to the SYSTEM hive of the Registry.

For more information

Open FT Registry Information Editor Help now.

Related topics

Files required


Files required for FTEDIT

FTEDIT.EXE

FTEDIT.HLP


FTP Configure
Internet and TCP/IP Services/Tools

FTPCONF.EXE: FTP Configure

Run FTP Configure now.

FTP Configure helps you configure your Microsoft FTP Server. To run this utility, the Microsoft FTP Server service (supplied with Windows NT Workstation and Windows NT Server) must be installed, and you must have administrative privileges.

With FTP Configure, you can control:

the maximum number of clients who can use the service simultaneously

whether users can access the FTP Server anonymously

how user logons are logged to the event log

the form of folder listings on the server

the messages the server displays to users

the starting, stopping, and pausing of the service

For more information

For details on how to use FTP Configure:

Open FTP Configure Help now.

See Windows NT documentation for instructions on installing the Microsoft FTP Server service.

Files required


Files required for FTP Configure

FTPCONF.EXE

FTPCONF.HLP

CTL3D32.DLL (to display the 3D controls properly)


GETMAC.EXE: GetMAC
Computer Diagnostic Tools

GETMAC.EXE: GetMAC

GetMAC provides a quick method for obtaining the MAC (Ethernet) layer address and binding order for a computer running Windows NT Workstation or Windows NT Server (locally or across a network). This can be useful when you want to enter the address into a sniffer, or if you need to know what protocols are currently in use on acomputer.

GetMAC topics

GetMAC syntax

GetMAC example

Related topics

Files required


File required for GetMAC

GETMAC.EXE


GETMAC.EXE: GetMAC

GetMAC syntax

GetMAC example


GetMAC syntax
GetMAC

GetMAC syntax	  Open Command Prompt now.

getmac [\\computername]

Where:

\\computername

is the name of a computer accessible across a network (including via RAS).


GetMAC example
GetMAC

GetMAC example

getmac \\a_pauldo

returns the following information:

Information for machine \\a_pauldo

Transport Address  Transport Name

-----------------  --------------

00-00-1B-16-78-76  \Device\NetBT_NE32007

00-00-1B-16-78-76  \Device\NwlnkNb

00-00-00-00-00-00  \Device\NetBT_NdisWan5

52-41-53-48-00-01  \Device\Nbf_NdisWan4

52-41-53-48-00-04  \Device\Nbf_NdisWan8

00-00-1B-16-78-76  \Device\Nbf_NE32007

In this example:

00-00-1b-16-78-76 is the address of an NE3200 Ethernet card.

00-00-00-00-00-00, 52-41-53-48-00-01, and 52-41-53-48-00-04 are RAS addresses.

When attempting a connection to a remote computer over the network, the workstation service will use the following order:

NetBT (TCP/IP) over the NE3200

NwlinkNb (IPX) over the NE3200

NetBT over one of the RAS links

Nbf (NetBIOS) over two other RAS links

Nbf over the NE3200

To change the order in which Windows NT attempts connections for the workstation service:

1	In Control Panel, double click Network.

2	Click Bindings.

3	In "Show Bindings For," select "Workstation."

4	Adjust the binding order with the arrows on the right.


GETSID.EXE
User Account Administration Tools

GETSID.EXE

Server only	Included in the Windows NT Server, but not Workstation, Resource Kit.

GetSID compares the user security IDs (SIDs) of two accounts.

You can use it to compare account SIDs between a Primary Domain Controller and Backup Domain Controller when you suspect user database corruption.

GetSID topic

GetSID syntax

Files required


File required for GetSID

GETSID.EXE


GetSID syntax
GetSID

GetSID syntax	  Open Command Prompt now.

getsid \\server1 account \\server2 account

Where:

\\server1 and \\server2

Are the names of the servers on which the accounts are found.

account

Is the account SID.


GLOBAL.EXE
User Account Administration Tools

GLOBAL.EXE

This command-line utility displays members of global groups on remote servers or domains.

GLOBAL syntax

Open Command Prompt now.

global groupname [domainname | \\server ]

Where

groupname

is the name of the global group for which to display members.

If groupname is multi-word (containing spaces), it must be enclosed in double quotation marks, for example, "domain users".

domainname

is the name of a network domain.

\\server

is the name of a network server.

global

run without parameters, displays this usage screen.

Example

global "domain users" nt_domain

Related Topics

Files required


File required for GLOBAL

GLOBAL.EXE


GRPCPY.EXE: Group Copy
User Account Administration Tools

GRPCPY.EXE: Group Copy

Run Group Copy now.

Server only	Included in the Windows NT Server, but not Workstation, Resource Kit.

This GUI utility enables users to copy the usernames in an existing group to another group in the same or another domain or on a computer running Windows NT.

Users of this program must have at least account operator privileges in the domains within which they want to work.

For more information

For details on how to use Group Copy:

Open GRPCPY.DOC now.

Related Topics

Files required


Files required for Group Copy

GRPCPY.EXE

GRPCPY.DOC


HCLFEB96.HLP: Hardware Compatibility List
Computer and Network Setup Tools

HCL40.HLP: Hardware Compatibility List

Open Hardware Compatibility List now.

The Hardware Compatibility List is a help file that describes the computers and peripherals that are compatible with Windows NT 4.0.

Updates to this list will be available:

On CompuServe Information Services in:
Library 1 of the WINNT (GO WINNT) forum or Library 17 of the MSWIN32 forum (GO MSWIN32).

On the World Wide Web on Microsoft's home page (if you have an Internet connection, you can click this link to go there now):

http://www.microsoft.com/backoffice/ntserver/hcl/hclintro.htm

Through FTP from Microsoft's site (if you have an Internet connection, you can click this link to go there now):

ftp://ftp.microsoft.com/bussys/winnt/winnt-docs/hcl/hcl40/

To use the Hardware Compatibility List

1	Click the Start button.

2	Point to Programs.

3	Point to Resource Kit 4.0.

4	Point to Online Help.

5	Click Hardware Compatibility List.

6	Select a category of hardware, and in some cases a subcategory, to see a list of models that have passed compatibility testing.

Files required


File required for the Hardware Compatibility List

HCL40.HLP


HEAPMON.EXE
Tools for Developers

HEAPMON.EXE

This command-line tool enables the user to view system heap information.

Files required


File required for HEAPMON

HEAPMON.EXE


IFMEMBER.EXE
User Account Administration Tools

IFMEMBER.EXE

IfMember is a command-line utility that checks whether the current user is a member of a specified group. It is typically used in Windows NT Workstation and Windows NT Server logon scripts and other batch files.

IfMember accepts a list of groups as parameters on the command line, and checks to see to how many of those groups the current user belongs. It then exits with the number of matches as its exit value, which can be used by the IF ERRORLEVEL command in the logon script.

IfMember uses it's own process token to discover group membership, rather than querying the relevant Domain Controller each time it runs. Whilst this has a significant performance benefit, it does mean that IfMember will only be aware of groups on the local computer, on the computer’s domain, and on trusted domains.

IfMember topics

IfMember syntax

IfMember example

Files required


File required for IfMember

IFMEMBER.EXE


IFMEMBER.EXE

IfMember syntax

IfMember example


IfMember syntax
IFMEMBER.EXE

IfMember syntax	  Open Command Prompt now.

ifmember [groupname1] [groupname2] ... [groupnameN]

Where:

groupname

Specifies the name of a group.


IfMember example
IFMEMBER.EXE

IfMember example

These lines of code illustrate the use of IfMember with IF ERRORLEVEL in a batch file:

ifmember Administrators

if not errorlevel 1 exit

REM the rest of this batch file will only be run if the user is a member of the Administrators group.


IMAGEDIT.EXE: Image Editor
Desktop Tools

IMAGEDIT.EXE: Image Editor

Run Image Editor now.

Image Editor enables you to create and edit custom cursors and icons in color or monochrome, including small Windows 95-style icons (16 colors, 16x16 pels). Working with Animated Cursor Creator, Image Editor can also help create animated cursors by drawing and editing frames.

To use Image Editor

1	Click the Start button.

2	Point to Programs.

3	Point to Resource Kit 4.0.

4	Point to Desktop Tools.

5	Click Image Editor.

Or in Animated Cursor Editor, click New Frame or Edit Frame.

When you create, open, or edit a .CUR or .ICO file, Image Editor allows you to select an image type or an existing image in a file.

To get online Help while working in Image Editor, press F1.

For more information

Open Image Editor Help now.

Related Topics

Files required


Files required for Image Editor

IMAGEDIT.EXE

IMAGEDIT.HLP


Index Server
Internet and TCP/IP Services/Tools

Index Server

Server only	Included in the Windows NT Server, but not Workstation, Resource Kit.

Index Server is the Microsoft content-indexing and searching solution for Microsoft Internet Information Server (IIS), which is included with Windows NT Server 4.0, and Peer Web Services (PWS), which is included with Windows NT Workstation 4.0. An add-on module for IIS and PWS, Index Server is designed to index the full text and properties of documents on an IIS or PWS-based server. Index Server can index documents for both corporate intranets and for any drive accessible through an uniform naming convention (UNC) path on the Internet.

Clients can formulate queries by using any World Wide Web (WWW) browser to fill in the fields of a simple Web query form. The Web server forwards the query form to the query engine, which finds the pertinent documents and returns the results to the client formatted as a Web page.

Unlike many content indexing systems, Index Server can index the text and properties of formatted documents, such as those created by Microsoft® Word or Microsoft® Excel. This feature lets you publish existing documents on your intranet Web without converting them to HyperText Markup Language (HTML).

For more information

INDEX.TXT, located in the \APPS\INDEX folder on the Resource Kit CD, contains details on installing Index Server. This information is also provided in Files required below.

Related topics

Files required


Files required for Index Server

The files for Index server are located in the \APPS\INDEX folder on the Resource Kit CD. They are divided into four sub-folders corresponding to the platforms supported: i386, Alpha, MIPS, and PPC.

In each sub-folder are three self-extracting .EXE files:

IDXSVALL.EXE	Indexes documents in all supported languages.
IDXSVENG.EXE	Indexes documents in International English.
IDXSVENU.EXE	Indexes documents in U.S. English.


INET.EXE
Internet and TCP/IP Services/Tools

INET.EXE

INET is a network command that works like the Windows NT NET command, except that UNC names are assumed to be Internet Domain Name System (DNS) names and are translated accordingly. INET works on TCP/IP services rather than on SMB.

INET cannot be used with any system commands other than those used with NET, nor with GUI utilities such as WINFILE.

INET topics

INET syntax

INET examples

Related topics

See Windows NT Help for more information on the NET command

Files required


File required for INET

INET.EXE


INET.EXE

Inet syntax

Inet examples


INET syntax
INET.EXE

INET syntax	  Open Command Prompt now.

inet [/v] [netcommand] [x:] [DNSname]

Where:

/v

specifies verbose (explanatory) output.

netcommand

is a command that can be used with NET.

x:

is the name of a drive on the current computer (for an ftp connection).

DNSname

is a Domain Name Server name.


INET examples
INET.EXE

INET examples

You could specify

inet view \\ftp.microsoft.com

or

inet use x: \\ftp.microsoft.com\data

Adding a /v switch as the first parameter produces verbose (explanatory) output, for example:

inet /v view \\ftp.microsoft.com


INSTSRV.EXE
Computer Administration/Configuration Tools

INSTSRV.EXE: Service Installer

Service Installer is a command-line utility that installs and uninstalls executable (.EXE) services and assigns names to them.

To run INSTSRV.EXE, you must have administrative privileges.

A GUI application, Service Installation Wizard (SRVINSTW.EXE), is also available in the Windows NT Resource Kit. This wizard provides increased functionality and enables you to connect to and configure services on remote as well as local computers.

Service Installer topics

Service Installer syntax

To uninstall services

Related topics

Files required


File required for Service Installer

INSTSRV.EXE


INSTSRV.EXE: Service Installer

Service Installer syntax

To uninstall services


Service Installer syntax
INSTSRV.EXE: Service Installer

Service Installer syntax	  Open Command Prompt now.

instsrv service-name exe-location

Where:

service-name

is the name you want to assign to the service. This name will appear in listings such as those in the Services option of Control Panel or in NetSvc/WinNetSvc.

exe-location

is the fully qualified path, including a drive letter, of the executable file for the service. The drive must be fixed and local.

For example, to install SRVANY.EXE as MyService, you would type:

instsrv MyService c:\tools\srvany.exe


To uninstall services
INSTSRV.EXE: Service Installer

To uninstall services	  Open Command Prompt now.

instsrv service-name remove

Where:

service-name

is the name of the service you want to remove.

For example, if you've installed FlopLock like this:

instsrv FloppyLocker c:\reskit.351\floplock.exe

you can uninstall it like this:

instsrv FloppyLocker remove


KERNPROF.EXE: Kernel Profiler
Network/Server Administration Tools

KERNPROF.EXE: Kernel Profiler

This command-line utility provides counters for and profiles of various functions of the Windows NT operating system Kernel.

With Kernel Profiler, you can monitor details and frequency for each function the Kernel calls, how often a process switches from User mode to Kernel mode, and, on a multi-processor computer, display information for each processor.

Kernel Profiler topics

Kernel Profiler syntax

Kernel Profiler examples

Files required


File required for KERNPROF

KERNPROF.EXE


KERNPROF.EXE: Kernel Profiler

Kernel Profiler syntax

Kernel Profiler examples


KERNPROF syntax
KERNPROF.EXE: Kernel Profiler

KERNPROF syntax	  Open Command Prompt now.

kernprof [-a] [-d] [-c] [-w waittime] [-x] [-p] [-v] [-s source] [sampletime] [lowthreshold]

Where:

-a

displays function address and length and bucket size of the actual functions being called by the Kernel.

-d

computes hit density for each function. This tells you how many times each function is being called, which can be helpful in determining what the majority of the Kernel calls are.

-c

displays individual counters per call.

-w waittime

sets a wait time of waittime before starting sampling (collection). This is helpful if time is needed to start an application or process before taking a sample.

-x

displays context switch counters. Context switch counters track how many times a process switches from User mode to Kernel mode.

-p

displays per-processor profile objects. This gives you a display for each processor as opposed to combining data for all processors into the same counters.

-v

displays verbose symbol information.

-s source

specifies a source to use instead of the clock as profile source.

sampletime

specifies, in seconds, how long to collect profile information. The default is to sample until CTRL + C is pressed.

lowthreshold

specifies a minimum number of counts to report. The default is 100.

Setting a count for the minimum number of hits for a particular sample can help to limit the amount of data you collect. If you set low threshold to 200, you will get all counters that are above 200, while any counters below 200 will not be reported in the output data.


KERNPROF examples
KERNPROF.EXE: Kernel Profiler

KERNPROF examples

The following example takes a sample for 500 seconds and pipes the information to the path specified after ">" (in this case, C:\PATHTO\OUTPUTFILE\TEST.TXT).

kernprof -a -d -c -x -p -v 500 >c:\pathto\outputfile\test.txt

The following example takes a sample of any counter over 200 and pipes the information to the path specified after the ">" (in this case, the directory from which KERNPROF was run to TEST1.TXT).

kernprof -a -d -c -x -p -v 500 200 >test1.txt

The following example takes a sample after waiting for 60 seconds and pipes the information to the path specified after ">" (in this case, C:\USERS\DEFAULT\TEST3.TXT).

kernprof -a -d -c -w 60 -x -p -v 500 >c:\users\default\test3.txt


KILL.EXE: Task Killing Utility
Computer Diagnostic Tools

KILL.EXE: Task Killing Utility

KILL.EXE is a command-line utility you can use to end one or more tasks or processes.

When using KILL, you can specify a process by its process ID number, any part of its process name, or its window title, if it has a window. You can use PULIST or TLIST, two utilities included with this Resource Kit, to find the process names and process IDs of currently running processes.

With KILL, you can also specify how the process is to be stopped: you can have KILL send it a command telling it to halt itself, or have KILL force the process to end.

KILL topic

KILL syntax

Related topics

Files required


File required for the Task Killing utility

KILL.EXE


KILL syntax
KILL.EXE: Task Killing Utility

KILL syntax	  Open Command Prompt now.

kill [/f] {process_id | pattern}

Where:

/f

forces the process to terminate, rather than allowing it to halt itself.

process_id

specifies the ID number of the process to be ended.

pattern

can be either a complete process name, or an expression using wildcards that will be compared to the process names and window titles of all current processes. For example, typing kill *help* will end all processes with process names or window titles that contain "help".


KIX32.EXE: KiXtart 95
Batch Tools

KIX32.EXE: KiXtart 95

Server only	Included in the Windows NT Server, but not Workstation, Resource Kit.

KiXtart 95 is a logon script processor and/or enhanced batch language for Windows NT and Windows 95 workstations in a Windows Networking environment.

Version 3.21, the latest release of the 32-bit version of KiXtart, offers new features including Program Group Control and .INI-file Management.

With KiXtart 95's free-format scripting language, you can conditionally display information, set environment variables, start programs, connect to network drives, read or edit the Registry, and change the current drive and directory.

For more information

For documentation on KiXtart 95:

Open KIX32.DOC now.

For release notes on KiXtart 95:

Open KIX32REL.TXT now.

Related topics

Files required


Files required for KiXtart 95

The files for KiXtart 95 are installed by the Resource Kit in the %NTRESKIT%\KIX95 folder.


LAYOUT.DLL
Desktop Tools

LAYOUT.DLL

This utility is a shell extension that saves and restores the icon positions on a desktop.

To install LAYOUT

1	Copy LAYOUT.DLL from the Resource Kit directory to the \%SYSTEMROOT%\SYSTEM32 sub-directory.

2	In Explorer, double-click LAYOUT.REG in the Resource Kit directory.

Open LAYOUT.REG now.

Installation creates two new items on the context menu of the My Computer icon: "Save Desktop Icon Layout" and "Restore Desktop Icon Layout." To open the context menu, click the right mouse button on the icon.

Files required


Files required for LAYOUT

LAYOUT.DLL

LAYOUT.REG


LOCAL.EXE
User Account Administration Tools

LOCAL.EXE

This command-line utility displays members of local groups on remote servers or domains.

LOCAL syntax

Open Command Prompt now.

local groupname [domainname | \\server ]

Where

groupname

is the name of the local group for which to display members.

If groupname is multi-word (containing spaces), it must be enclosed in double quotation marks, for example, "server operators".

domainname

is the name of a network domain.

\\server

is the name of a network server.

local

run without parameters, displays this usage screen.

Example

local "server operators" nt_domain

Related Topics

Files required


File required for LOCAL

LOCAL.EXE


LOGEVENT.EXE: Event Logging Utility
Computer Diagnostic Tools

LOGEVENT.EXE: Event Logging Utility

This tool enables you to make entries to the Windows NT Event Log on either a local or remote computer from the command prompt or a batch file.

The program is particularly useful for storing historical information from the execution of batch programs run from Login Scripts or the AT command. Its ability to store entries into the event log of other computers allows these data to be collected centrally, if required.

In order to allow the Event Log Viewer to properly display the entry, the application should be installed onto the computer being used to view the event log. Installation is automatically performed when the LogEvent program is used for the first time.

Event Logging Utility topic

Event Logging Utility examples

For more information

To display the program's syntax, enter the command without parameters:

logevent

Open Command Prompt now.

Related topics

Files required


File required for Event Logging Utility

LOGEVENT.EXE


Event Logging Utility examples
LOGEVENT.EXE: Event Logging Utility

Event Logging Utility examples	  Open Command Prompt now.

logevent "Batch program failed"

puts an Information entry into the event log with the text "Batch program failed".

logevent -m \\Master -s W -c 999 "Fatal Error !"

puts a Warning entry into the event log with the text "Fatal Error".


LOGTIME.EXE
Batch Tools

LOGTIME.EXE

A command-line tool that logs the start or finish of command-line programs from a batch file. This can be useful for timing and tracking batch jobs such as mail-address imports.

LOGTIME creates a log file, LOGTIME.LOG, with a date-and-time stamp next to the specified parameter (text_string in LOGTIME syntax). When called from within a batch file, the date-and-time stamp records when LOGTIME (with the given parameter) was run by the batch file. If, for example, LOGTIME is run before and after a command-line program in a batch file, LOGTIME.LOG will record the start and stop time of that program (see GO.BAT in LOGTIME syntax).

New information is appended to LOGTIME.LOG; the file is not overwritten.

LOGTIME topic

LOGTIME syntax

Files required


Files required for LOGTIME

LOGTIME.EXE

LOGTIME.TXT


LOGTIME syntax
LOGTIME.EXE

LOGTIME syntax	  Open Command Prompt now.

logtime [text_string] [/?]

Where:

text_string

specifies the message you wish to display.

/?

displays usage instructions.

Sample batch file: GO.BAT

logtime "begin import program"

import.exe

logtime "end import program"

LOGTIME.LOG output for GO.BAT

05/27/96 13:14:19  begin import program

05/27/96 13:15:07  end import program


Mail Server
Internet and TCP/IP Services/Tools

Mail Server

Server only	Included in the Windows NT Server, but not Workstation, Resource Kit.

This utility allows you to configure a computer running Windows NT Server as an electronic mail (e-mail) provider for intranet or Internet users. With Mail Server installed, the computer can connect directly to the Internet to send and receive e-mail and provide user postoffice services.

Mail Server is a basic SMTP and POP3 server, an implementation of the SendMail daemon for Windows NT Server. It supports Internet-based mail clients including the Windows NT Inbox, Microsoft Exchange, and Microsoft Mail, among others. The Mail Server e-mail service, however, is completely separate from the electronic messaging and groupware services of Microsoft Exchange and Microsoft Mail.

Intermediate files required by Mail Server and mailboxes are all spooled on the Windows NT server that is running the service. They can be accessed through a public-domain or commercial POP3 client. Mail Server automatically creates a mail folder with secured permissions the first time the user's account receives mail or the first time the user checks his or her mail via a POP client.

Caution	Windows NT security provides a high level of security both for individual users and Windows NT-based networks. However, Mail Server supports only the clear text password authentication of POP3 and does not support the APOP command. In other words, clear text passwords are sent over the network in readable (clear) format and are not encrypted. If network security is a concern, administrators should use caution when using the Microsoft Mail Server utility. The potential for malicious tampering with Internet communications should be considered before using Microsoft Mail Server.

For more information

For details on how to use Mail Server:

Open Mail Server version 1.1 Release Notes (MAILSRV.HTM) now.

For background on Mail Server, see the section on Mail Server in Windows NT Server Internet Guide.

If you have installed the Online Books, click to:

Open Windows NT Server Internet Guide in Online Books

Related topics

Files required


Files required for Mail Server

These files are installed by the Resource Kit in the %NTRESKIT%\MAILSRV folder.

MAILSRV.EXE

INSTALL.EXE

MAILSRV.HTM


MIBCC.EXE: SNMP MIB Compiler
Network Diagnostic Tools

MIBCC.EXE: SNMP MIB Compiler

MIBCC compiles SNMP MIB files.

The SNMP service for Windows NT supports multiple MIBs using an extension-agent API interface. Two extension-agent DLLs come with Windows NT to support the Internet MIB II and a subset of the LAN Manager MIB II objects. Other extension-agent DLLs can be added.

MIBCC topic

MIBCC syntax

Related topics

Files required


Files required for MIBCC

MIBCC.EXE

Source files (LMMIB2.MIB, MIB_II.MIB, and SMI.MIB are included in the Resource Kit)


MIBCC syntax
MIBCC.EXE: SNMP MIB Compiler

MIBCC syntax	  Open Command Prompt now.

mibcc [-ex] [-l] [-n] [-ofilename] [-t] [-w] [files...] [-?]

Where:

-ex

stops after x errors. (Default = 10)

-l

does not print logo.

-n

prints each node as it is added.

-ofilename

outputs filename. (Default = MIB.BIN)

-t

prints the MIB tree when finished.

-wx

sets warning level of x, where 1=errors and 2=warnings.

files

specifies the source filenames.

-?

displays help.


MONITOR.EXE: Performance Data Logging Service and Configuration Tool
Computer Diagnostic Tools

MONITOR.EXE: Performance Data Logging Service and Configuration Tool

Monitor is the configuration tool for installing and controlling the Data Logging Service (DATALOG.EXE).

The Data Logging Service is a Windows NT Service that performs the same function as the Performance Monitor Alert and Logging facility. The Data Logging Service is useful in remotely administering log files for large numbers of computers.

Monitor and Data Logging Service topics

To set up the Data Logging Service

Monitor syntax

Monitor example: remotely logging activities

Monitor example: automatically starting and stopping the service

Files required


Files required for Monitor and Data Logging Service

DATALOG.EXE

MONITOR.EXE

The system counter names and explanatory text have been removed from the Registry and moved to two data files shipped with Windows NT:

PERFC009.DAT - Counter IDs and names

PERFHOO9.DAT - Counter explanatory text


MONITOR.EXE: Performance Data Logging Service and Configuration Tool

To set up the Data Logging Service

Monitor syntax

Monitor example: remotely logging activities

Monitor example: automatically starting and stopping the service


To set up the Data Logging Service
MONITOR.EXE: Performance Data Logging Service and Configuration Tool

To set up the Data Logging Service

1	Create a settings file by using the Windows NT Performance Monitor (PERFMON.EXE).

Specify all objects you want to log and the alerts you want. Specify a logfile name (*.LOG) and the logging interval, but do not start logging. Save the settings file (*.PMW) into your %SYSTEMROOT%\SYSTEM32 folder by using the Save Workspace command on the File menu.

2	Copy DATALOG.EXE into your %SYSTEMROOT%\SYSTEM32 folder. If you want to use the Data Logging Service on a remote computer, copy the DATALOG executable and your settings file to that computer's %SYSTEMROOT%\SYSTEM32 folder.

3	To install the Data Logging Service, in a command prompt window in the %SYSTEMROOT%\SYSTEM32 folder, type:

monitor setup

This command registers the service with the Service Manager. You only need to run this command once for every computer.

4	To use your settings file, type:

monitor filename

5	To start logging events and alerts, immediately type:

monitor start

6	To stop logging, type:

monitor stop

7	You can then view the log file in Performance Monitor.

Note:	You must stop the Monitor service before you can use the log file in Performance Monitor.


Monitor syntax
MONITOR.EXE: Performance Data Logging Service and Configuration Tool

Monitor syntax	  Open Command Prompt now.

monitor [\\server] [filename] [setup] [start] [stop] [pause] [continue] [automatic] [manual] [disable]

Where:

monitor

with no switch, displays the current setup and status of the service.

\\server

specifies the name of a remote computer. If not specified, the local computers is used.

filename

sets the service to use the named configuration (*.PMW) file.

setup

sets up the datalog service Registry variables and installs them in the Service Controller.

start

starts the service.

stop

stops the service.

pause

pauses the service.

continue

continues the service.

automatic

sets the service to start automatically when Windows NT starts.

manual

sets the service to require a manual start using the Service Control icon in Control Panel or this utility's START command.

disable

disables the service.


Monitor example: remotely logging activities
MONITOR.EXE: Performance Data Logging Service and Configuration Tool

Monitor example: remotely logging activities

You can log events and alerts on a remote computer with the Data Logging Service. To install the Data Logging Service on a remote computer, copy DATALOG.EXE and your settings file (WHATSUP.PMW, for this example) to that computer's %SYSTEMROOT%\SYSTEM32 folder. For these examples, assume you are installing on a computer named FOREIGN.

To register the service with the Service Manager, type

monitor \\FOREIGN setup

This command changes information in the Registry and only needs to be run once per computer.

To use your settings file, type

monitor \\FOREIGN whatsup.pmw

To start logging events and alerts, type

monitor \\FOREIGN start


Monitor example: automatically starting and stopping the service
MONITOR.EXE: Performance Data Logging Service and Configuration Tool

Monitor example: automatically starting and stopping the service

You can use the Schedule service and the AT command to schedule monitoring at a set time. For example, you have a server that is slowing down severely between 2:40 AM and 2:50 AM every work night. You want to log the activity on the computer, but you do not want to get out of that nice warm bed. Instead, you can log for that period by entering the following AT commands:

at \\FOREIGN 2:30 /every:m,t,w,th,f monitor start

at \\FOREIGN 3:00 /every:m,t,w,th,f monitor stop

Optionally, as a reminder, you can enter the following:

at \\FOREIGN 2:30 /every:f net send <YourUserName> "The Monitor is stopped. The log contains data for this week!"


MUNGE.EXE
Batch Tools

MUNGE.EXE

This utility provides a convenient way to search for and replace strings in a file.

MUNGE topics

MUNGE syntax

Files required


File required for MUNGE

MUNGE.EXE


MUNGE syntax
MUNGE.EXE

MUNGE syntax	  Open Command Prompt now.

munge scriptFile [-q [-e] [-o]] [-r] [-c] [-i] [-m] [-z] [-@] [-n] [{-l | -L}] [-s] [-a] [-f] [-t] [-k] [-u undoFileName] [-v] filesToMunge

Where:

scriptFile

takes any of the following forms:

oldName newName

These must follow C Identifier rules.

"oldString" "newString"

These are arbitrary text strings.

-F {.EXT | NAME. | NAME.EXT}

-F limits the munge to files that match:

.EXT -  a particular extension

NAME. - a particular name

NAME.EXT - a particular name and extension

If no -F line is seen in the scriptFile, the following is the default:

-F .ASM .C .CLI .CPP .CXX .DEF .H .HXX .IDL .INC .MAK .RC .S .SRC .SRV .TK

-q

query only - does not actually make changes.

-e

query only - displays the entire line for each match.

-o

query only - displays filename only once on first match.

-r

recurses.

-c

if file is not munged, checks for cleanlyness.

-i

just outputs a summary of files changed at the end of the run.

-m

collapses multiple carriage returns into one.

-z

Ctrl-Z truncates file.

-@

removes null characters.

-n

neuter - surrounds all strings with TEXT().

-l

literals - does not process any quoted text (including comments).

-L

literals - does not process any quoted text (excluding comments).

-s

uses OUT command for files that are read-only.

-a

uses ATTRIB -r command for files that are read-only.

-f

uses -z flag for SLM OUT command.

-t

trusts MUNGE and does not create .BAK files.

-k

case - treats scriptFile as case-sensitive.

-u undoFileName

generates an undo script file (undoFileName) for the changes made.

-v

verbose - shows files being scanned

filesToMunge

are the names of a file or files to which to apply this command.

-?

displays this usage screen.

Note	Some of these switches are case-sensitive.


NETCLIP.EXE: Remote Clipboard Viewer
Network/Server Administration Tools

NETCLIP.EXE: Remote Clipboard Viewer

Run Remote Clipboard Viewer now.

NETCLIP is a GUI utility that enables you to view the contents of another computer's clipboard, and to Drag & Drop (or Cut & Paste) any data, in any format, to and from the other computer.

To share the clipboard between the two computers, NETCLIP uses the Microsoft Component Object Model (COM). It fully supports Rich Text Format (RTF) as well as any custom data format supported by your applications.

NETCLIP requires Windows NT 4.0 to view and modify the clipboard on another computer. It also works on Windows 95 as a local clipboard viewer only.

For more information

For details on how to use Remote Clipboard Viewer:

Open NETCLIP.HTM now.

Files required


Files required for Remote Clipboard Viewer

NETCLIP.EXE

NETCLIP.HTM

NCLIPPS.DLL


NETSVC.EXE: Command-Line Service Controller
Network/Server Administration Tools

NETSVC.EXE: Command-Line Service Controller

Server only	Included in the Windows NT Server, but not Workstation, Resource Kit.

You can use NETSVC to remotely start, stop, and query the status of services from the command line.

To use NETSVC, you need no special rights unless the owner of a computer has blocked out all users. To use the /stop or /start options, you must have an account on the target computer with privileges that allow starting or stopping services.

Because NETSVC uses the service names as listed under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services in the Registry, the service names displayed with NETSVC can be slightly different from those displayed with NET START.

NETSVC topics

NETSVC syntax

NETSVC notes

Files required


File required for Command-Line Service Controller

NETSVC.EXE


NETSVC.EXE: Command-Line Service Controller

NETSVC syntax

NETSVC notes


NETSVC syntax
NETSVC.EXE: Command-Line Service Controller

NETSVC syntax	  Open Command Prompt now.

netsvc servicename \\computername switch

Where:

servicename

is the name of the service you want to control. You can enter either the service names, as defined in the Registry, or the display names, as shown when you double-click the Services icon in Control Panel. If the service name has embedded spaces, place quotes around the service name.

\\computername

is the name of the computer whose services you want to control.

switch

/query, /start, /stop, /continue, /list, or /pause. No servicename is required when you use the /list switch. All switches are case-insensitive.

For example:

netsvc /query \\anniep "Network DDE"

You can type netsvc with /? or /help to get help at the command prompt.


NETSVC notes
NETSVC.EXE: Command-Line Service Controller

NETSVC notes

Not all services can be stopped directly (such as the Workstation service), although you can query it. If the user has a lot of active connections, you cannot force the service to shut down remotely, although you can pause or query it. Other services have services that are dependent on them; trying to shut down such services will fail unless the dependent services are shut down first.

For example, the ClipBook Server requires the Network DDE Service; so you cannot shut down NetDDE without first shutting down ClipBook Server. This is true even with net stop.

Therefore, you must be familiar with the services you are shutting down.

If you try to stop an unstoppable service, netsvc simply reports that the service is running. For example:

netsvc /stop \\machine TargetService

Reply:

Service is running

This indicates that the service rejected the request to stop. It is impossible for netsvc to know why the service refuses to be stopped, since the reason varies from service to service.

Likewise, some services cannot be PAUSED or CONTINUED, because PAUSE or CONTINUE logic is not included in the service program. If you try to pause a nonpausable service, netsvc reports the "Service is running" immediately afterwards.


NetTime
Network/Server Administration Tools

NetTime for Macintosh

This Macintosh program synchronizes the local Macintosh clock to a given AppleShare server on the network. It requires ResEdit or another resource editor to change the zone and server name for the tool to synchronize to.

It is provided in a self-extracting archive file in BinHex 4.0 format, NETTIME.HQX.

NetTime for Macintosh topics

To expand and install NetTime for Macintosh

For more information

Open the User's Guide for NetTime in Word for Windows (NETTIME.DOC) now.

Open the User's Guide for NetTime in WinHelp (NETTIME.HLP) now.

Files required


Files required for NetTime for Macintosh

NETTIME.DOC

NETTIME.HLP

NETTIME.HQX


To expand and install NetTime for Macintosh
NetTime for Macintosh

To expand and install NetTime for Macintosh

NETTIME.HQX is a self-extracting archive file in BinHex 4.0 format that contains the single application NetTime. It and the NetTime documentation (NETTIME.DOC and NETTIME.HLP) are found in the the NetTime.Mac directory on the CD.

1	Transfer NETTIME.HQX from the CD to your Macintosh. You can do this in a variety of ways, including:

Copy the file to MS-DOS formatted floppy and place it in a Macintosh that has PC Exchange and/or can read MS-DOS formatted floppies, then copy it to your Macintosh.

If you have Windows NT Server with Services for Macintosh installed, share the Resource Kit CD out as a Macintosh volume, then mount the volume from your Macintosh, find the directory where NetTime.hqx is, and copy it down from the volume.

Place the Resource Kit CD-ROM into a Macintosh CD-ROM player (assuming you have a CD-ROM player and the proper CD extensions to mount the CD-ROM), and copy the file from the CD to your Macintosh.

2	Once the file has been transferred, decode it with a program such as BinHex 4.0, or Stuffit Expander™.

If you are using Stuffit Expander™, simply drop the file onto it and it will decode and expand the self-extracting archive.

If you are using BinHex 4.0, it will only decode the file. Once it's decoded, you will be able to launch the self-extracting archive, and it will finish decompressing.

Stuffit Expander™ can be found in BinHex 4.0 format on:

http://www.aladdinsys.com/obstufex.htm

If you have an Internet connection, you can click this link to go there now.

It is a freeware utility courtesy of Aladdin Systems.

BinHex 4.0 is probably harder to obtain if you don't already have it. The best bet is to check at a local Mac software store for share/freeware programs. If you have access to an online service, do a search on "BinHex" to see it if is available.


NETWATCH.EXE: Net Watcher
Network Diagnostic Tools

NETWATCH.EXE: Net Watcher

Run Net Watcher now.

NETWATCH:EXE: Net Watcher shows which users are connected to shared folders. It also enables you to disconnect users and un-share folders. It can now simultaneously monitor multiple computers.

Note:	To use Net Watcher, the Server service must be started and you must be logged on as a member of the Administrators group for any computer you are trying to watch.

Net Watcher topics

To use Net Watcher

Net Watcher tips

Files required


File required for Net Watcher

NETWATCH.EXE


NETWATCH.EXE: Net Watcher

To use Net Watcher

Net Watcher tips


To use Net Watcher
NETWATCH.EXE: Net Watcher

To use Net Watcher

Run Net Watcher now.

1	Click the Start button.

2	Point to Programs.

3	Point to Resource Kit 4.0.

4	Point to Diagnostics.

5	Click Net Watcher.

or

At the command prompt, type:

netwatch \\computername1 [\\computername2 ... \\computernameN]

Where:

computername1 to N

are the names of the computers whose users you want to monitor.

To indicate the network connections you want to watch:

On the Options menu, click Show Open Files, Show Hidden Shares, or Show In Use Shares Only.


Tips for using Net Watcher
NETWATCH.EXE: Net Watcher

Tips for using Net Watcher

You can keep Net Watcher open on the desktop with no menu bar or title bar, by choosing No Menu Bar and Title from the Options menu.

Net Watcher updates the list of connected users every 30 seconds or whenever you press F5.

You can view more details on a resource by double-clicking it or by selecting it and pressing ALT+ENTER.

The Manage Shared Folders dialog box (CTRL+S) lists and shows the paths of the shared folders of the computer.


NLMON.EXE: Replication Monitor
Network/Server Administration Tools

NLMON.EXE

This command-line utility can be used to list and test many aspects of Trust relationships.

NLMON uses the Browser Service to enumerate Domain Controllers. Therefore if browsing is not working correctly, NLMON may produce inconsistent results. Also, the computer where NLMON is run, and also those providing the Browsing services, must share the same protocols that are used by the Domain Controllers to carry out their Domain activity.

For more information

For details on how to use NLMON:

Open the NLMON.TXT now.

Files required


Filesrequired for NLMON

NLMON.EXE

NLMON.TXT


NLTEST.EXE
Network/Server Administration Tools

NLTEST.EXE

This command-line tool helps perform administrative tasks such as forcing a user-account database into sync, getting a list of primary domain controllers (PDCs), forcing a shutdown, and querying and checking on the status of trust.

Files required


File required for NLTEST

NLTEST.EXE


NOW.EXE: Now
Batch Tools

NOW.EXE: Now

Now displays the current date and time on STDOUT, followed by any command-line arguments you add.

Now is similar to the MS-DOS ECHO command, but with a timestamp. The utility is useful for logging times from .BAT or .CMD files in order to track progress.

The output from the NOW command can be redirected via > or |, if required.

Now topic

Now syntax

Files required


File required for Now

NOW.EXE


Now syntax
NOW.EXE: Now

Now syntax	  Open Command Prompt now.

now [message] [/?]

Where:

message

specifies the message you wish to display.

/?

displays usage instructions.

For example, typing:

now Download Completed.

elicits this reply:

Tue Aug 01 00:57:26 1995 Download Completed.


NTCARD40.HLP: Windows NT Adapter Card Help
Computer and Network Setup Tools

NTCARD40.HLP: Windows NT Adapter Card Help

Open Windows NT Adapter Card Help now.

Windows NT Adapter Card Help was created by Microsoft Product Support to assist you in the setup of network adapters, SCSI adapters, and sound cards for Windows NT 4.0. This file provides IRQ, I/O base, RAM base address, and other settings, along with illustrations that show the location for jumper settings on the cards.

Note	This Help file is not intended as a replacement for the documentation provided with your adapter. It is provided as a convenience to help you configure your adapter more quickly. For information not covered in NTCARD40.HLP, consult your adapter's documentation.

The products described in NTCARD40.HLP are manufactured by vendors independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding these products' performance or reliability.

Windows NT Adapter Card Help topic

To use Windows NT Adapter Card Help

Files required


File required for Windows NT Adapter Card Help

NTCARD40.HLP


To use Windows NT Adapter Card Help
NTCARD40.HLP: Windows NT Adapter Card Help

To use Windows NT Adapter Card Help

Open Windows NT Adapter Card Help now.

1	Click the Start button.

2	Point to Programs.

3	Point to Resource Kit 4.0.

4	Point to Online Help.

5	Click Windows NT Adapter Card Help.

To find information within Windows NT Adapter Card Help:

1	Double-click a category of adapter card from the Help Topics dialog box, then double-click a manufacturer.

2	Click a specific adapter card name for details.

If you need to use Control Panel, Setup, Notepad, or RegEdit to set up the adapter card, click the button for one of these applications at the top of the Help window.


NTDETECT.COM: Startup Hardware Detector
Computer and Network Setup Tools

NTDETECT.COM (INSTALLD.CMD): Startup Hardware Detector

INSTALLD.CMD installs NTDETECT.CHK, the debug or checked version of NTDETECT.COM, from the Windows NT CD.

On x86-based computers, NTDetect detects installed hardware components at startup time and displays the hardware information structures passed to the Kernel. If NTDETECT.COM fails to detect all of the hardware that you think it should find, you can use the debug version, NTDETECT.CHK, to help isolate the problem. A mouse or a disk controller is the component that typically causes problems.

Installing NTDETECT is a separate task after you install the Resource Kit utilities.

Caution	Under no circumstances should you delete NTDETECT.COM. NTDETECT.COM is a required program for a Windows NT system. The version that is installed by INSTALLD.CMD is a special version that displays diagnostic information. If you have removed it and your system doesn't start correctly, use the Emergency Repair Disk to restore files. You can use INSTALLD.CMD to remove the special version of NTDetect (see To remove the special version of NTDetect).

Platform	NTDETECT runs only on x86-based computers.

NTDetect topics

To install NTDetect

To remove the special version of NTDetect

Example of NTDetect Information for the system component

Files required


Files required for NTDetect

INSTALLD.CMD

NTDETECT.COM


NTDETECT.COM: Startup Hardware Detector

To install NTDetect

To remove the special version of NTDetect

Example of NTDetect Information for the system component


To install NTDetect
NTDETECT.COM: Startup Hardware Detector

To install NTDetect	  Open Command Prompt now.

1	At the command prompt, switch to the folder where the Resource Kit utilities are installed, and type installd

INSTALLD performs these functions:

a	Renames NTDETECT.COM in the root directory of your system partition.

b	Copies NTDETECT.CHK from SUPPORT\DEBUG\I386 on the Windows NT CD to the root directory.

c	Renames NTDETECT.CHK to NTDETECT.COM.

2	Shut down and restart the computer to see the results.

NTDetect displays information about the system component, bus/adapter component, disk geometry, ROM blocks, keyboard and COM port and parallel port components, mouse component, and floppy disk drive component. When detection is complete, you are asked to press any key to display hardware information.

3	Keep pressing any key to view more information. This information is similar to what is stored under HKEY_LOCAL_MACHINE\HARDWARE\Controllerx in the Registry.

Example of NTDetect information for the system component

4	After all information for detected hardware is displayed, you can press the spacebar if you want to use the LastKnownGood control set instead of the current control set to start the system.


To remove the special version of NTDetect
NTDETECT.COM: Startup Hardware Detector

To remove the special version of NTDetect	  Open Command Prompt now.

At the command prompt, type installd /not.


Example of NTDetect Information for the System Component
NTDETECT.COM: Startup Hardware Detector

Example of NTDetect Information for the system component

Current Node: 00050000

Type: MaximumType

Child: 00050045

Parent = 00000000

Sibling: 00000000

ConfigurationData = 00000000

IdentifierLength = 0000011

Identifier= AT/AT COMPATIBLE

ConfigdataLength = 00000044

Version = 0000, Revision = 0000

Count = 0002

Type = Device Data

Size = 0000000C

0080 0000 00DB 000 0000 0000 002 0000 000B 0000 0001 0000


NTUUCODE.EXE: 32-Bit UUDecode/UUEncode Utility
Internet and TCP/IP Services/Tools

NTUUCODE.EXE: 32-Bit UUDecode and UUEncode Utility

Run UUEncode/Decode now.

NTUUCODE is a 32-bit GUI program that you can use to encode or decode files according to the UUEncoding standard.

NTUUCODE topics

To use NTUUCODE

To decode a file

To encode a file

To have the window cleared automatically after decoding a file

Files required


File required for NTUUCODE

NTUUCODE.EXE


NTUUCODE.EXE: 32-Bit UUDecode and UUEncode Utility

To use NTUUCODE

To decode a file

To encode a file

To have the window cleared automatically after decoding a file


To use NTUUCODE
NTUUCODE.EXE: 32-Bit UUDecode and UUEncode Utility

To use NTUUCODE

Run UUEncode/Decode now.

1	Click the Start button.

2	Point to Programs.

3	Point to Resource Kit 4.0.

4	Point to Internet Utls.

5	Click UUEncode/Decode.


To decode a file
NTUUCODE.EXE: 32-Bit UUDecode and UUEncode Utility

To decode a file

1	Paste the file to be decoded into the NTUUCODE window. If the file is on disk, you can click Open on the File menu to bring the file into the window.

If the file has multiple parts, every part must be pasted into the window, and the parts must be in correct order. You do not need to delete headers from the files to be decoded.

2	Click the Decode button, or click the Decode! menu command.

You are prompted for a location to store the decoded file.

3	Type the location to store the file.

4	To have the file automatically load after decoding, check the option "Load after decode" on the Options menu.

After decoding, the file will be loaded according to the Explorer file type, and minimized on the desktop.


To encode a file
NTUUCODE.EXE: 32-Bit UUDecode and UUEncode Utility

To encode a file

1	Click the Encode button on the toolbar, or click the Encode! menu command.

2	In the Open File to Encode dialog box, type the filename of the file to be decoded in the File Name box, and then click OK.

The encoded file is displayed in the NTUUCODE window. You can save the file to disk, or copy and paste it to another program.


To have the window cleared automatically after decoding a file
NTUUCODE.EXE: 32-Bit UUDecode and UUEncode Utility

To have the window cleared automatically after decoding a file

On the Options menu, click Clear After Decode.

This command is useful if you are decoding multiple files, and you do not want to manually clear the window after each file.


OLEVIEW.EXE: OLEViewer
Tools for Developers

OLEVIEW.EXE: OLE/COM Object Viewer

Run OLE/COM Object Viewer now.

This administration and testing tool for Microsoft Component Object Model (COM) classes is oriented towards developers and power users. The user interface, however, offers both "Expert" and "Novice" modes.

OLE/COM Object Viewer enables you to browse, configure, activate, and test all of the COM classes installed on your computer. You can also configure system-wide COM settings, including enabling or disabling Distributed COM, and activate COM classes remotely. The new Component Categories specification is fully supported.

With OLE/COM Object Viewer, you can figure out what methods, properties, and events an ActiveX Control supports, and copy a properly formatted OBJECT tag to the clipboard for inserting into an HTML document.

OLE/COM Object Viewer requires Windows NT 4.0 or Windows 95. You must also have installed either Internet Explorer 3.0 or the ActiveX Software Development Kit.

Windows NT 3.5 and Windows NT 3.51 versions of this tool, then called OLE2View, are available in the Win32 SDK and Visual C++.

The CCDIST.EXE utility must be run to correctly set up OLE/COM Object Viewer components.

Launch CCDIST.EXE now.

For more information

For details on how to use OLE/COM Object Viewer:

Open OLEVIEW.HTM now.

Files required


Files required for OLE/COM Object Viewer

OLEVIEW.EXE

OLEVIEW.HTM

IVIEWERS.DLL

COMCAT.DLL

CCDIST.EXE


OS2API.TXT: API Information
Tools for Developers

OS2API.TXT: API Information

Open OS2API.TXT now.

The OS2API.TXT file contains information for developers describing which APIs for the OS/2 operating system are supported by Windows NT 4.0 and which are not supported.

To use OS2API

Open the OS2API.TXT file in a text editor.

Files required


File required for OS2API

OS2API.TXT


PATHMAN.EXE: PathMan
Computer Administration/Configuration Tools

PATHMAN.EXE: Pathman

This command-line tool enables you to add or remove components of both the system and user paths. It can modify any number of paths in a single call and includes error checking that can handle path abnormalities such as repeated entries, adjacent semicolons, and missing entries.

Windows NT manages two different types of paths; the current user's path and the system path. Windows NT keeps a separate user path for every user on a system, but there is only one global system path. When a user logs on to a computer running Windows NT, these two paths are combined to create the user's full path. For backward compatibility, Windows NT also loads path information from old AUTOEXEC.BAT files left in the root directory.

A non-administrative user can modify his or her own user path. But in order to modify the system path, the user of pathman must have Administrator privileges. Pathman does not manage information contained in old AUTOEXEC.BAT files.

For more information

For details on how to use Pathman:

Open PATHMAN.WRI now.

Files required


Files required for PathMan

PATHMAN.EXE

PATHMAN.WRI


PASSPROP.EXE
Network/Server Administration Tools

PASSPROP.EXE

This command-line tool can be used to set two domain policy flags: whether passwords have to be complex and whether the administrator account can be locked out. These domain password and security properties cannot be set by any other tool, including the NET command and User Manager.

The first property is password complexity. If password complexity is enabled, the password must be mixed-case (including a combination of upper and lower-case letters) or contain numbers or symbols. If it is not enabled, passwords are still case-sensitive, but they are not required to be mixed case or contain numbers or symbols.

The second property is whether the Administrator user account can be locked out. If locking out the Administrator user account is enabled, then once it is locked out it can only be used to log on interactively on domain controllers: network logons or logons to non-domain controllers will fail.

For more information

For details on PASSPROP syntax and usage:

at the command prompt, run

passprop

with no parameters.

Related topics

Files required


File required for PASSPROP

PASSPROP.EXE


PERF2MIB.EXE: Performance Monitor MIB Builder Tool
Network Diagnostic Tools

PERF2MIB.EXE: Performance Monitor MIB Builder Tool

Using PERF2MIB.EXE: Performance Monitor MIB Builder Tool, developers can create new ASN.1 syntax MIBs for their applications, services, or devices that use Performance Monitor counters. Administrators can then track performance of these components by using any system-management program that supports SNMP.

This tool also creates a .MIB file that can be used by an SNMP-based management console to perform SNMP requests for the performance data in question, and thus to monitor performance remotely. This allows all performance data available through the HKEY_PERFORMANCE_DATA Registry key to be exposed through SNMP.

PERF2MIB topics

PERF2MIB syntax

How to create and set up a MIB with existing performance counters

To create and compile a MIB for a new component

MIB content example

Related topics

Files required


File required for PERF2MIB

PERF2MIB.EXE

PERFMIB.DLL

PERFM.BAT

PERFMIB.REG


PERF2MIB.EXE: Performance Monitor MIB Builder Tool

PERF2MIB syntax

To create and set up a MIB with existing performance counters

To create and compile a MIB for a new component

MIB content example


PERF2MIB syntax
PERF2MIB.EXE: Performance Monitor MIB Builder Tool

PERF2MIB syntax	  Open Command Prompt now.

perf2mib MIBfilename INIfilename [ObjectName MIBIndex MIBPrefix [...]]

Where:

MIBfilename

Is the name of the MIB file to be created.

INIfilename

Is the name of the generated configuration file. This file is used by the MITV Windows NT SNMP extension agent to map performance counters to MIB variables.

ObjectName

Is the name of the performance counter object whose counters you want to expose (such as "Processor," "Memory," and so on).

Note  ObjectName is case sensitive. If it contains imbedded spaces, as in “MSExchangeMTA Connections,” it must be enclosed in quotation marks ( “ ).

MIBIndex

Is the numeric ID of the MIB branch where this particular object’s data should be placed.

MIBPrefix

Is the abbreviation that should be placed before counter names belonging to this object (such as "mem" for Memory counters, "proc" for Processor counters, and so on).

Note:	The last three parameters can be repeated to map multiple object types with one call.


PERF2MIB.EXE: To create and set up a MIB with existing performance counters
PERF2MIB.EXE: Performance Monitor MIB Builder Tool

To create and set up a MIB with existing performance counters

To get the Memory, Processor, Network Segment, and PhysicalDisk Performance Monitor counters via SNMP, you can follow the following steps or run PERFM.BAT, provided in the Windows NT Resource Kit. In case  you do not wish to create it, PERFMIB.REG has been provided on the Resource Kit CD.

1	Run PERF2MIB.EXE as follows:

perf2mib perfmib.mib perfmib.ini memory 1 memory processor 2 CPU "Network Segment" 3 net PhysicalDisk 4 disk

2	Run the Windows NT 4.0 Resource Kit utility MIBCC.EXE to compile the MIB as follows:

mibcc -o%ntreskit%\mib.bin -n -t -w2 %ntreskit%\smi.mib %ntreskit%\LMMIB2.MIB %ntreskit%\mib_II.mib perfmib.mib

3	Stop the SNMP agent (for example, "net stop snmp").

4	Rename %SYSTEMROOT%\SYSTEM32\MIB.BIN to MIB.OLD.

5	Copy the following files to the %SYSTEMROOT%\SYSTEM32 folder:

PERFMIB.DLL (from the Resource Kit)

PERFMIB.INI (created when you ran PERF2MIB.EXE)

MIB.BIN (created when you ran MIBCC.EXE)

6	Register PERFMIB.REG in the Registry (in case  you do not wish to create it, PERFMIB.REG has been provided on the Resource Kit CD). This can be performed by creating the following keys with Registry Editor or by copying the following Registry information into a file called PERFMIB.REG and running regini perfmib.reg (REGINI.EXE is a utility in the Resource Kit).

The PERFMIB.REG file should contain the following:

\Registry\Machine

        Software

            Microsoft

                PerformanceAgent

                    CurrentVersion

                        Pathname = REG_EXPAND_SZ %SystemRoot%\System32\perfmib.dll

        System

            CurrentControlSet

                Services

                    SNMP

                        Parameters

                            ExtensionAgents

                                MicrosoftPerformanceAgent = SOFTWARE\Microsoft\PerformanceAgent\CurrentVersion

7	Restart the SNMP agent (for example, "net start snmp").

8	Add "PERFMIB.MIB" to the management station by using the appropriate method.

Now you can query the MIB with Windows NT utilities such as SNMPUTIL.EXE from the Resource Kit, or with other network management software.

Note
To monitor multiple computers on a network, you can create one Perf2MIB MIB and compile it on the SNMP manager station. Then propagate the .INI file to all the computers on which you want to monitor the counters.

Examples

For %Network Utilization:

snmputil get localhost public .iso.org.dod.internet.private.enterprises.microsoft.software.systems.O .WinNT.Performance.2.1.2.0

For %Processor Time:

snmputil walk localhost public .iso.org.dod.internet.private.enterprises.microsoft.software.systems.O .WinNT.Performance.3.1.6

For %Disk Time:

snmputil get localhost public .iso.org.dod.internet.private.enterprises.microsoft.software.systems.O .WinNT.Performance.4.1.3.0

For Memory Available Bytes:

snmputil get localhost public .iso.org.dod.internet.private.enterprises.microsoft.software.systems.O .WinNT.Performance.1.1


PERF2MIB.EXE: To create and compile an MIB for a new component
PERF2MIB.EXE: Performance Monitor MIB Builder Tool

To create and compile a MIB for a new component

1	Run PERF2MIB, specifying the object for which you want to create a MIB (see the preceding syntax information). A configuration (.INI) file will also be generated.

2	Copy the .MIB file to the console device.

3	Run the MIB compiler to compile the management station with the .MIB file.

For example, if you are using HP OpenView to populate the map with a new object, you would run the HP OpenView MIB compiler with the .MIB file and then associate the resulting icon with an object and place it on the map.

This step enables the management station to read the component’s MIB via SNMP.

Note	To monitor multiple computers on a network, you can create one Perf2MIB MIB and compile it on the SNMP manager station. Then propagate the .INI file to all the computers on which you want to monitor the counters.


PERF2MIB.EXE: MIB content example
PERF2MIB.EXE: Performance Monitor MIB Builder Tool

MIB content example

This command line:

perf2mib test.mib test.ini Memory 1 mem Processor 2 proc System 3 sys

generates this ASN.1 syntax MIB file for the "memory" object and its associated performance counters (partial listing):

WINDOWS-NT-PERFORMANCE DEFINITIONS ::= BEGIN

  IMPORTS

    enterprises

      FROM RFC1155-SMI

    OBJECT-TYPE

      FROM RFC-1212

    DisplayString

      FROM RFC-1213;

  microsoft  OBJECT IDENTIFIER ::= { enterprises 311 }

  software  OBJECT IDENTIFIER ::= { microsoft 1 }

  systems   OBJECT IDENTIFIER ::= { software 1 }

  OS     OBJECT IDENTIFIER ::= { systems 3 }

  WinNT    OBJECT IDENTIFIER ::= { OS 1 }

  Performance OBJECT IDENTIFIER ::= {WinNT 1 }

-- Memory MIB

  Memory OBJECT IDENTIFIER ::= { Performance 6 }

  memAvailableBytes OBJECT-TYPE

    SYNTAX INTEGER

    ACCESS read-only

    STATUS mandatory

    DESCRIPTION

      "Available Bytes displays the size of the virtual memory currently on..."

    ::= { Memory 1 }

  memCommittedBytes OBJECT-TYPE

    SYNTAX INTEGER

    ACCESS read-only

    STATUS mandatory

    DESCRIPTION

      "Committed Bytes displays the size of virtual memory (in bytes) that..."

    ::= { Memory 2 }

  memCommitLimit OBJECT-TYPE

    SYNTAX INTEGER

    ACCESS read-only

    STATUS mandatory

    DESCRIPTION

      "Commit Limit is the size (in bytes) of virtual memory that can be..."

    ::= { Memory 3 }

The following listing is the portion of the SNMP extension agent configuration file that corresponds to the preceding MIB fragment:

6.1 Memory\Available Bytes

6.2 Memory\Committed Bytes

6.3 Memory\Commit Limit


PERFMTR.EXE: Performance Meter
Computer Diagnostic Tools

PERFMTR.EXE: Performance Meter

The Performance Meter displays text-based information on the performance of a computer running Windows NT.

To use Performance Meter

1	At the command prompt, type perfmtr

2	Type a command (without pressing ENTER) for any of the following:

c	CPU usage

f	file cache usage

h	header

i	I/O usage

p	POOL usage

r	Cache Manager reads and writes

s	server statistics

v	virtual memory usage

x	x86 VDM (Virtual DOS Machine) usage

3	Type q to quit.

Files required


File required for Performance Meter

PERFMTR.EXE


Performance Data Log Service (PerfLog)
Computer Diagnostic Tools

PerfLog: Performance Data Log Service

This tool logs data from performance counters to tab or comma-separated variable files. It lets you choose which performance counters you want to log, and starts new log files automatically at intervals you select.

The text files to which PerfLog logs data can be used as input to spreadsheets, databases, and other applications, as well as to Performance Monitor. Unlike Performance Monitor logs, which store data in a compact, multi-dimensional C-language data format, PerfLog logs can be used as direct input without reformatting.

PerfLog uses the same objects and counters as Performance Monitor (included with the Windows NT operating system), but it lets you select which counters you want to log for each instance of an object. You can also select the level of detail you need on an instance and let PerfLog select a set of counters for you.

For more information

Open PerfLog Help (PDLCNFIG.HLP) now.

Files required


Files required for PerfLog

PDLCNFIG.EXE

PDLSVC.EXE

PDLCNFIG.HLP

PDLCNFIG.CNT


Performance Tools
Computer Diagnostic Tools

Performance Tools

The \PERFTOOL folder of the installed Resource Kit contains tools for monitoring and optimizing the performance of a computer running Windows NT or a Windows NT application. Several of these tools are also covered in separate topics in this Help file.

The Performance Tools are grouped into folders by function. A few of these tools are listed in more than one sub-folder. The \EXAMPLES folder is not installed by default because it contains over 20 MB of files.

Click the name of a folder for information about its contents:

Performance Monitor Counter Utilities

\CNTRTOOL
Performance Monitor Counter Utilities

\EXAMPLES
Performance Tools Examples

\LOGTOOLS
PerfLog: Performance Data Log Service

\MEASTOOL
Measurement Tools

\P5CTRS
Performance Monitor Extension for Pentium Counters (Pperf)

\PROBE
Response Probe

\TOTLPROC
Performance Monitor Extension for Total Processor Usage

For more information

Many of the Performance Tools are also described in the chapter on "Performance Monitoring Tools" in the "Optimizing Windows NT Workstation" section of Windows NT Workstation Resource Guide.

If you have installed Online Books, click to:

Open Windows NT Workstation Resource Guide in Online Books

Files required


Files required for Performance Tools

The files for Performance Tools are installed by the the Resource Kit in the %NTRESKIT%\PERFTOOL folder. On the Resource Kit CD, they are located in the \COMMON\PERFTOOL folder.

See the sub-topics on each folder for a list of files in that folder.


Performance Tools

\CNTRTOOL
Performance Monitor Counter Utilities

\EXAMPLES
Performance Tools Examples

\LOGTOOLS
PerfLog: Performance Data Log Service

\MEASTOOL
Measurement Tools

\P5CTRS
Performance Monitor Extension for Pentium Counters (Pperf)

\PROBE
Response Probe

\TOTLPROC
Performance Monitor Extension for Total Processor Usage


\CNTRTOOL
Performance Tools

\CNTRTOOL

The tools in this folder, the Performance Monitor Counter Utilities, are useful for listing and finding detailed information about standard and extensible performance counters, for debugging, and for developing and troubleshooting Windows NT performance-counter DLLs.

For more information on the tools:

Open CNTRTOOL.TXT now.

For more detailed information on performance counters:

Open COUNTERS.HLP now.

EXCTRLST.EXE also has its own topic in this Help file. Click the underlined green filename below to see the topic.

Files in the \CNTRTOOL folder

CNTRTOOL.TXT

COUNTERS.HLP

CTRLIST.EXE

EXCTRLST.EXE

SHOWPERF.EXE


\EXAMPLES
Performance Tools

\EXAMPLES

Because the \EXAMPLES folder contains over 20 MB of files, it is not installed by default. To install the examples, run the Resource Kit SETUP, choose Custom Setup, and select the option of installing the Performance Tools \EXAMPLES folder.

Files in the \EXAMPLES folder

STRIPE-RAND.LOG

STRIPE-READ.LOG

STRIPE-WRITE.LOG


\LOGTOOLS
Performance Tools

\LOGTOOLS

This folder contains the files for PerfLog: Performance Data Log Service. For a brief overview, see the topic on PerfLog in this Help file.

For more information on the tools in this folder:

Open CNTRTOOL.TXT now.

For assistance in using PerfLog:

Open PerfLog Help (PDLCNFIG.HLP) now.

Files in the \LOGTOOLS folder

LOGTOOL.TXT

PDLCNFIG.CNT

PDLCNFIG.EXE

PDLCNFIG.HLP

PDLSVC.EXE


\MEASTOOL
Performance Tools

\MEASTOOL

This collection of performance tools, the Measurement Tools, can help you measure and analyze computers running Windows NT. These are documented briefly in MEASTOOL.TXT.

Open MEASTOOL.TXT now.

For conceptual background and more detailed information on many of these tools, see the chapter on "Performance Monitoring Tools" in the "Optimizing Windows NT Workstation" section of the Windows NT Workstation Resource Guide.

If you have installed Online Books, click to:

Open Windows NT Workstation Resource Guide in Online Books

Some of the following utilities are also covered in their own topics in this Help file. Click the underlined green filenames below to see the topics.

Files in the \MEASTOOL folder

CLEARMEM.EXE

CPUSTRES.EXE

DATALOG.EXE

DRIVERS.EXE

EMPTY.EXE

EXCTRLST.EXE

FASTIMER.DLL

HEAPMON.EXE

KILL.EXE

MEASTOOL.TXT

MONITOR.EXE

NTIMER.EXE

PERFMTR.EXE

PFMON.EXE

PMON.EXE

PROFILE.EXE

PSAPI.DLL

PSTAT.EXE

PVIEW.EXE

PVIEWER.EXE

SETEDIT.EXE

TLIST.EXE

TOP.EXE

VADUMP.EXE

WPERF.EXE


\P5CTRS
Performance Tools

\P5CTRS

Performance Monitor Extension for Pentium Counters (Pperf) is a performance driver that installs and reads the Intel Pentium (P5) and Pentium Pro (P6) processor internal performance counter registers for display in Pperf and in Performance Monitor.

For information on installing and using this  tool:

Open P5PERF.TXT.

Files in the \P5CTRS folder

P5CTRNAM.H

P5CTRS.DLL

P5CTRS.INI

PDUMP.EXE

P5PERF.REG

P5PERF.TXT

PSTAT.SYS

PPERF.EXE


\PROBE
Performance Tools

\PROBE

Response Probe is a script-based utility that measures the response of the computer and operating system to a predefined, fixed workload. It can be used to optimize the performance of Windows NT Workstation and Server. This folder includes the tools needed to run Response Probe and a sub-folder with ready-to-use Response Probe tests.

For more information on CREATEFIL.EXE:

Open CREATFIL.TXT.

Files in the \PROBE folder

CREATFIL.EXE

CREATFIL.TXT

PROBE.EXE

PROBEPRC.EXE

STATW32.DLL

TIMERW32.DLL

WAIT.EXE

\EXAMPLES

1024.SCP

1024.SCR

1024.SCT

1MSU.SCP

1MSU.SCR

1MSU.SCT

2048.SCP

2048.SCR

2048.SCT

256KSU.SCP

256KSU.SCR

256KSU.SCT

2KSU.SCP

2KSU.SCR

2KSU.SCT

4096.SCP

4096.SCR

4096.SCT

4MSU.SCP

4MSU.SCR

4MSU.SCT

512.SCP

512.SCR

512.SCT

8KSU.SCP

8KSU.SCR

8KSU.SCT

DISKMAX.SCP

DISKMAX.SCR

DISKMAX.SCT

DISKMAX.TXT

DOPROBE.BAT

MINREAD.SCP

MINREAD.SCR

MINREAD.SCT

MINREAD.TXT

SIZEREAD.BAT

SIZEREAD.TXT


\TOTLPROC
Performance Tools

\TOTLPROC

Performance Monitor Extension for Total Processor Usage is a performance-counter driver that displays the total processor load of a multi-processorcomputer.

For more information:

Open TOTLPROC.TXT.

Files in the \TOTLPROC folder

PERFTP.DLL

PERFTP.H

PERFTP.INI

TOTLPROC.EXE

TOTLPROC.TXT

TP.REG


Perl 5 scripting language
Batch Tools

Perl 5 Scripting Language

Run Perl 5 Scripting Language now.

Perl 5 version 5.001 is a scripting language ported from UNIX to Windows NT Workstation and Windows NT Server. Perl 5 combines some of the features of C, sed, awk, and Bourne shell. This version of Perl 5 also enables you to work with the Registry and event logs, and can act as an OLE automation controller.

Not all of the functions from the UNIX version of Perl 5 have analogs in the Windows NT realm, so some are not implemented in this version. STATUS.TXT and STATUS.HTM both contain a list of all functions NOT implemented in this release.

Perl 5 has been developed with Microsoft Visual C++ version 2.0. The source release of Perl 5 includes the source files and test scripts, as well as a makefile for building Perl 5 from the SDK. INSTALL.TXT includes instructions for building Perl 5.

Perl 5 topics

To install Perl 5

System and platform requirements for Perl 5

Perl 5 technical notes

For more information

README.TXT gives an overview of Perl 5.

INSTALL.TXT describes how to install Perl 5. The information in this file is not accurate for the Resource Kit installation. For current information, see To install Perl 5.

LICENSE.TXT contains the GNU "General Public License" and "Artistic License."

RELEASE.TXT contains Perl 5's revision history, changes since last release, and plans for future releases.

STATUS.TXT lists unsupported functions and features.

The entire Perl 5 manual can be viewed with any World Wide Web browser by opening the file NTPERL5.HTM, which is the first HTML page of the documentation. This manual includes the original Perl 5 manual pages and the Windows NT extensions to Perl 5.

Copyright Notice:
The files for the Perl 5 scripting language, POSIX Utilities, and Regina REXX scripting language are the only files covered by the GNU Library General Public License. All other files are copyrighted by Microsoft Corporation or the respective owners, and are subject to the terms of a separate license agreement.

Related topics

Files required


Files required for Perl 5

MANIFEST.TXT lists the files included in this release of Perl 5, which are are installed by the Resource Kit in the %NTRESKIT%\PERL folder.


Perl 5 Scripting Language

To install Perl 5

System and platform requirements for Perl 5

Perl 5 technical notes


To install Perl 5
Perl 5 Scripting Language

To install Perl 5

The Resource Kit SETUP:

copies the following files for Perl 5 to %NTRESKIT%\PERL:

PERL.EXE

PERLGLOB.EXE

PERL100.DLL

CMD32.EXE

PL2BAT.BAT

README.TXT

INSTALL.TXT

LICENSE.TXT

RELEASE.TXT

STATUS.TXT

MANIFEST.TXT

updates the system path to include this folder.

creates or updates the following Registry values.

LOCAL\SOFTWARE\Microsoft\Resource Kit\PERL5

BIN	= %NTRESKIT%\PERL

HTML-DOCS	= CD_drive:\Source\GNU\Perl\docs

PRIVLIB	= CD_drive:\Source\GNU\Perl\lib

After installation, you can copy any of your own scripts or library files into the %NTRESKIT%\PERL folder.


System and platform requirements for Perl 5
Perl 5 Scripting Language

System and platform requirements for Perl 5

To run Perl 5, you will need a computer running Windows NT Workstation or Server 3.5 or later, or Windows 95, with at least 2 MB of disk space free.

If you plan on building from the source, the amount of disk space required increases to at least 10 MB.

Perl 5's source code will compile on any platform supported by Windows NT Workstation or Server 3.5 or later, or Windows 95.


Perl 5 technical notes
Perl 5 Scripting Language

Perl 5 technical notes

If you are moving Perl scripts from UNIX to Windows NT, you may have to reformat them. Perl scripts written under UNIX terminate lines with a linefeed, while Windows NT scripts terminate text lines with two characters: a carriage return AND a linefeed.

Several file test features, most notably stat() and the -s test, are not implemented in this version of Perl 5.

Perl 5's functionality on Windows NT is not exactly the same as described in documentation for some other versions of Perl.


PERMCOPY.EXE
File Tools

PERMCOPY.EXE

This command-line utility copies share-level permissions (ACLs) from one share to another.

Note	Copying the shares from an administrative share (for example, \C$) to a target share will NOT change the permissions of the target share. Also, copying permissions to an administrative share located on an x86 machine causes SERVICES.EXE to crash.

Files required


File required for PERMCOPY

PERMCOPY.EXE


PERMS.EXE: File Access Permissions per User
Computer Administration/Configuration Tools

PERMS.EXE: File Access Permissions per User

The PERMS tool is used to display users' access permissions for a specified file or set of files.

To use PERMS, you need "Backup files and folders" privileges on the computer where the files are stored, and you must be logged on as a member of the Administrators group for the domain or computer where the user account is defined. Otherwise, "Access denied" errors may occur.

PERMS topics

PERMS syntax

Characters in PERMS listings

File required for PERMS

PERMS.EXE

Files required


File required for PERMS

PERMS.EXE


PERMS.EXE: File Access Permissions per User

PERMS syntax

Characters in PERMS listings


PERMS syntax
PERMS.EXE: File Access Permissions per User

PERMS syntax	  Open Command Prompt now.

perms [account] [path] [/i] [/s] [/?]

Where:

account

is the name of the user whose permissions are to be checked, in the format domain\username or computer\username or local username.

path

is the name of a file or folder in any legal format, including UNC (\\). You can use the * or ? wildcards.

/i

indicates that Perms is to assume that account is interactively logged on to the computer where path resides. Without this parameter, Perms assumes the user is logged on over the network and is a member of the Network security group.

/s

checks permissions on files in sub-folders.

/?

displays help for the PERMS command.


Characters in PERMS listings
PERMS.EXE: File Access Permissions per User

Characters in PERMS listings

The information returned by PERMS uses these characters:

R	Generic Read

W	Generic Write

X	Generic Execute

D	Standard Delete

P	Change Permissions

O	Take Ownership

A	General All

None	No Access

*	The specified account is the owner of the file or folder.

#	A group of which the user is a member owns the file or folder.

?	The user's access permissions cannot be determined.


PFMON.EXE: Page Fault Monitor
Computer Diagnostic Tools

PFMON.EXE: Page Fault Monitor

This utility enables you to monitor the page faults that occur as you run an application. Page Fault Monitor produces a running list of hard and soft page faults generated by each function call by the application.

The best indicator of a memory bottleneck is a sustained high rate of hard page faults—over 5 per second.

You can use this tool to trace the source and number of page faults in a process. Page Fault Monitor can display the data, write it to a log file, or both.

You must run Page Fault Monitor from the command prompt window.

Page Fault Monitor topic

Page Fault Monitor syntax

For more information

Type pfmon /? at the command prompt to see a usage screen.

See the "Performance Monitoring Tools" chapter in the Windows NT Workstation Resource Guide.

If you have installed Online Books, click to:

Open Windows NT Workstation Resource Guide in Online Books

Files required


Files required for Page Fault Monitor

PFMON.EXE

PSAPI.DLL

On the Windows NT 4.0 Workstation Resource Kit CD, these files are located in the Performance Monitoring group (\PERFTOOL\MEASTOOL)


Page Fault Monitor syntax
PFMON.EXE: Page Fault Monitor

Page Fault Monitor syntax	  Open Command Prompt now.

pfmon [-n] [-l] [-c] [-h] [-p pid] [-d] [-k] [-K] application-command-line [-?]

Where:

-n

does not display running faults, just logs to PFMON.LOG.

-l

logs faults to PFMON.LOG.

-c

shows only code faults.

-h

shows only hard faults.

-p pid

attaches to existing process ID (pid).

-d

specifies this tab-delimited database format:

page fault number

page fault type (hard or soft)

program counter's module

symbol for PC

decimal value of PC

decimal value of PC

module of the virtual address accessed

symbol for VA

value of VA

-k

shows kernel-mode page faults and user-mode page faults.

-K

shows kernel-mode page faults instead of user-mode page faults.

application-command-line

is the command line that runs the application to be monitored.

-?

displays a usage screen.


PMON.EXE: Process Resource Monitor
Computer Diagnostic Tools

PMON.EXE: Process Resource Monitor

PMon is a command-line tool that monitors process resource usage, tracking CPU and memory usage.

To run Process Resource Monitor

At the command prompt, type pmon.

To quit Process Resource Monitor

Press CTRL+C or click Close on the window menu of the command-prompt window.

Process Resource Monitor topic

Process Resource Monitor output format

Related topics

Files required


File required for Process Resource Monitor

PMON.EXE


Process Resource Monitor output format
PMON.EXE: Process Resource Monitor

Process Resource Monitor output format

CPU	CpuTime	Mem Usage	Mem Diff	Page Faults	Flts Diff	Commit Charge	Usage NonP	Usage Page	Pri	Hnd Cnt	Thd Cnt	Image Name


CPU (%CPU)

Identifies the percentage of total CPU usage associated with a particular process.


CpuTime (CPU Time)

Expressed as a percentage of the elapsed time that a processor is busy executing a non-Idle thread. It can be viewed as the fraction of the time spent doing useful work. Each processor is assigned an Idle thread in the Idle process that consumes those unproductive processor cycles not used by any other threads.


Mem Usage (Memory Usage)

Identifies the total memory used.


Page Faults

Page faults/second is a count of the page faults in the processor. A page fault occurs when a process refers to a virtual memory page that is not in its working set in main memory. A page fault will not cause the page to be fetched from disk if that page is on the standby list, and hence already in main memory, or if it is in use by another process with which the page is shared.


Commit Charge

Displays the size of virtual memory (in bytes) that has been Committed (as opposed to simply reserved). Committed memory must have backing (that is, disk) storage available, or must be assured never to need disk storage (because main memory is large enough to hold it).


Usage NonP (NonPaged Usage)

The size of the Nonpaged Pool, which is a system memory area where space is acquired by operating system components as they accomplish their appointed tasks. Nonpaged Pool pages cannot be paged out to the paging file, but instead remain in main memory as long as they are allocated.


Usage Page (Paged Usage)

The amount of the Page File instance in use.


Thd Cnt (Thread Count)

Identifies the number of threads for the particular process.


Image Name

Identifies the executable filename or process associated with a particular item.


POLEDIT.EXE: Windows NT System Policy Editor
Computer Administration/Configuration Tools

POLEDIT.EXE: Windows NT System Policy Editor

This utility sets administrative policies to override user behavior.

For more information

For details on how to use Windows NT System Policy Editor:

Open Windows NT System Policy Editor Help now.

For background on Windows NT System Policy Editor, See the Windows NT Workstation Resource Guide.

If you have installed Online Books, click to:

Open Windows NT Workstation Resource Guide in Online Books

Files required


Files required for Windows NT System Policy Editor

POLEDIT.EXE

POLEDIT.CNT

POLEDIT.HLP

COMMON.ADM

WINDOWS.ADM

WINNT.ADM


Posix Utilities
Tools for Developers

POSIX Utilities

The POSIX Utilities have been recompiled to operate on Windows NT Workstation and Windows NT Server version 4.0.

The POSIX Utilities are not placed in your system's PATH automatically. If you choose to install these utilities, they will be installed in the \ResourceKit\POSIX folder (where \ResourceKit is the folder where you choose to install the Resource Kit utilities). To run the POSIX Utilities easily, add the \ResourceKit\POSIX folder to your PATH.

For the first time, this Resource Kit also ships Win32 clones of seven of the POSIX Utilities.

Caution	Different versions of FIND, MKDIR, and RMDIR (POSIX utilities) are shipped with Windows NT. You should rename the POSIX versions of these so there is no confusion.

To use the POSIX utilities

Open Command Prompt now.

At the command prompt, type the name of the command you want to run.

POSIX topics

POSIX Utility Descriptions

POSIX Utility Notes

Win32 POSIX clones

For more information

Open the POSIX Utilities Write file (POSIX.WRI) now.

Copyright Notice:

The files for the Perl 5 scripting language, POSIX Utilities, and Regina REXX scripting language are the only files covered by the GNU Library General Public License. All other files are copyrighted by Microsoft Corporation or the respective owners, and are subject to the terms of a separate license agreement.

Related topics

Files required


Files required for the POSIX utilities

CAT.EXE

CC.EXE

CHMOD.EXE

CHOWN.EXE

CP.EXE

FIND.EXE

GREP.EXE

LN.EXE

LS.EXE

MKDIR.EXE

MV.EXE

POSIX.WRI

RM.EXE

RMDIR.EXE

SH.EXE

TOUCH.EXE

VI.EXE

WC.EXE


POSIX Utilities

POSIX Utility Descriptions

POSIX Utility Notes

CC Command Information

SH Command Information

VI Command Information

Win32 POSIX clones


POSIX Utility Descriptions
POSIX Utilities

Utility	MS-DOS Equivalent	Description

cat	TYPE	"conCATenator"

cc	none	"C Compiler" - CL front-end. More CC info

chmod	ATTRIB	"CHange MODe"

chown	none	"CHange OWNer".

cp	COPY	"CoPy"

find	none	file finder

grep	none	"Global Regular Expression Print" - FIND sub.

ln	none	"LiNker".

ls	DIR	"LiSt"

mkdir	MD	"MaKe DIRectory"

mv	REN	"MoVe"

rm	DEL	"ReMove"

rmdir	RD	"ReMove DIRectory"

sh	COMMAND	"SHell". More SH Info

touch	none	Change dates.

vi	EDIT	vi ("VIsual") clone. More VI Info

wc	none	"Word Count".


POSIX Utility Notes
POSIX Utilities

POSIX Utility Notes

When you run the POSIX utilities, any parameters consisting of filenames should be in the POSIX format; for example, if you want to display the file D:\TEMP\MESSAGE.TXT, in the COMMAND program, you might enter:

type d:\temp\message.txt

whereas in the sh program, you would enter:

cat //D/temp/message.txt

Drive letters (which must be capitalized) are preceded by two forward slashes, and folders are preceded by one forward slash. Case sensitivity is also important for POSIX filenames; if you want to search all the C files in a FAT folder for the string "main", you need to enter the following:

grep main *.C

If "*.c" is entered instead, nothing would match in the FAT folder, due to the automatic uppercasing of filenames on FAT file systems.


chown

Changes owner of files.


find

Searches folder tree for files matching given criteria.


ln

Gives multiple names to the same file.


sh

Large subset of Korn shell (no variable arrays).


touch

Changes modification date of files.


wc

Gives bytes, words, and lines for files.


CCCommand Information
POSIX Utilities

CC Command Information

Before using cc, you need to:

Go to your system's MSTOOLS folder and copy LINK32.EXE to LINK.EXE.

Customize your environment. Some of the variables that you will need to set are:

MAKEPATH=location of default make rules

PATH=location of cc executables

POSIX_INC=location(s) of default include files

POSIX_LIB=location of default libraries

SHELL=full path of Korn shell

Note:	These variables need to contain POSIX-style paths, not NTFS-style paths; yet the only paths that need to be added by using the System icon in Control Panel are POSIX_INC and POSIX_LIB. The best place to enter the other variables is in your profile file (the file pointed to by the ENV environment variable). Also:

The MAKEPATH variable needs to contain the folder where the default make rules files (that is, the contents of the MK-RULES.ZIP archive) are installed.

The PATH variable needs to include the folder where the cc executables reside, in order to be able to run them from anywhere.

 	The POSIX_INC variable needs to have the location(s) of the default include files. If more than one folder is required in POSIX_INC, then separate the folders with colons.

Note:	Order is significant; folders listed first will be searched first.

The POSIX_LIB variable needs to be set to the location of the default libraries. The SHELL variable needs to point to the full path of the Korn shell executable (including any .EXE suffix).


SH Command Information
POSIX Utilities

SH Command Information

Before using the shell, you may need to customize your environment. Some of the environment variables that you may want to set are:

ENV=location of .profile equivalent

PATH=location of sh executable

TZ=appropriate timezone

The ENV variable contains the full path of a file that contains shell commands that you want to run initially, for example, creating aliases, customizing prompts, and so on.

The PATH variable needs to include the folder where the sh resides, in order to be able to run it from anywhere.

The TZ variable should be set according to your location on the planet; for example, for residents of Oregon it should be set to "PST8PDT", translated as "normally Pacific Standard Time, eight hours behind Coordinated Universal Time, during the summer Pacific Daylight Time".

A sample .profile file may look something like this:

alias a=alias

alias md=mkdir

alias rd=rmdir

alias ua=unalias

set -o vi

PS1='[!] '

These commands set four aliases, make available vi-style command-line editing, and set the prompt to display the current command number inside of brackets. For a more complete view of what the shell can do, see a good book on the subject, such as Bolsky & Korn's The KornShell Command and Programming Language, published by Prentice Hall (ISBN 0-13-516972-0).

There is an extension to the typeset built-in command, a "-p" parameter, representing POSIX customization of an environment variable.

For example, if there were a variable named GLOP that contained "C:\users\default\telnet.trm", applying typeset -p GLOP to it would result in GLOP having the value "//C/users/default/telnet.trm".

The converse command, typeset +p GLOP, would "de-POSIX-ize" the variable, leaving the original value in GLOP.

Note that Windows NT environment variables that reference other Windows NT environment variables, for example, SET LOGNAME=%USERNAME%, will not be expanded inside of the shell; such variables will have the unexpanded value—for example, LOGNAME would contain "%USERNAME%", not "Administrator".


VI Command Information
POSIX Utilities

VI Command Information

Before using vi, you need to customize your environment. Some of the environment variables that you need to set are:

PATH=location of the vi executable

TERM=ansi

TERMCAP=location of termcap equivalent

_POSIX_TERM=on

The PATH variable needs to include the folder where the vi executable resides, to be able to run it from anywhere.

The TERM variable needs to have a value that matches an entry in the TERMCAP file; by default, this entry is named "ansi".

The TERMCAP variable contains the full path of the termcap file. You should customize the entry in the termcap file according to your typical Command Prompt window size; if you usually use a window that's not 80 columns by 25 lines, change the co entry to match the number of columns, and change the li entry to match the number of lines. For example, if you normally use a 100 column by 60 line window, the co entry would be "co#100" and the li entry would be "li#60".

The _POSIX_TERM variable must be set to "on" to use the terminal emulation portion of the POSIX server.


Win32 POSIX clones
POSIX Utilities

Win32 POSIX clones

For the first time, Win32 work-alikes of seven of the POSIX Utilities are included in this Resource Kit. These clones don't use the POSIX subsystem at all, but duplicate the functionality of the corresponding POSIX tools.

These seven Win32 clones can be found in the File/Batch sub-directory of the Resource Kit.

cat.exe

cp.exe

ls.exe

mv.exe

touch.exe

wc.exe

vi.exe


PSTAT.EXE: Process and Thread Status
Computer Diagnostic Tools

PSTAT.EXE: Process and Thread Status

PSTAT is a character-based tool that lists all running processes and threads and displays their status. This tool is similar to QSLICE.EXE, but uses a command-line rather than a GUI interface.

The current version of PSTAT takes a system snapshot and shows PMON.EXE and old PSTAT-style data, along with DRIVERS.EXE output, in a single output stream. This output can be useful for trouble shooting.

PSTAT syntax

Open Command Prompt now.

Type pstat | more at the command prompt.

PSTAT output format

pid: ##  pri:  executablename

    tid: ##  pri: ##  cs: ##  [wait: Info | running]

Related topics

Files required


File required for PSTAT

PSTAT.EXE


Process ID

The process ID number in hexadecimal format.


PULIST.EXE
Tools for Developers

PULIST.EXE

This command-line tool tracks what processes are running on local or remote computers. It can list the names and process IDs of all processes running on one or more remote systems. If run against the local computer (with no arguments specified), PULIST will also try to list the user name associated with each process.

This utility can be used by network administrators to determine what processes are running on servers and workstations on a network. Furthermore, batch-file developers can redirect the output of the utility to a file and leverage this information in useful ways.

PULIST works much like TLIST, but can also enumerate an owner for processes on a local computer, in addition to enumerating processes on remote computers.

For more information

Open PULIST.TXT now.

Related topics

Files required


Files required for PULIST

PULIST.EXE

PULIST.TXT


PVIEWER.EXE: Process Viewer
Computer Diagnostic Tools

PVIEWER.EXE: Process Viewer

Run Process Viewer now.

Process Viewer is a Windows-based tool that displays information about a running process and allows you to stop (kill) processes.

Click an item to view information about that element of Process Viewer:

Memory Detail

Kill Process

Computer

Process

Processor Time

Privileged Time

User Time

Process Memory Used

Process Priority

Thread Priority

Thread Information

To use Process Viewer

1	Click the Start button.

2	Point to Programs.

3	Point to Resource Kit 4.0.

4	Point to Diagnostics.

5	Click Process Viewer.

Files required


File required for Process Viewer

PVIEWER.EXE


Memory Detail

Click this button to see details about memory use for the selected process.


Kill Process

Click this button to stop the selected process.

Caution	Do not attempt to kill processes required for running Windows NT. Make sure you understand which program owns a process before attempting to kill it.


Computer

Shows the name of the computer whose processes are currently displayed. Click the Connect button and complete the dialog box to view processes for a remote computer.


Process

The name of the process followed by the process ID number (in hexadecimal format) in parentheses.


Processor Time

Processor Time is expressed as a percentage of the elapsed time that a processor is busy executing a non-Idle thread. It can be viewed as the fraction of the time spent doing useful work. Each processor is assigned an Idle thread in the Idle process that consumes those unproductive processor cycles not used by any other threads.


Privileged Time

Privileged Time is the percentage of processor time spent in Privileged Mode in non-Idle threads. The Windows NT service layer, the Executive routines, and the Windows NT Kernel execute in Privileged Mode. Device drivers for most devices other than graphics adapters and printers also execute in Privileged Mode. Unlike some early operating systems, Windows NT uses process boundaries for subsystem protection in addition to the traditional protection of User and Privileged modes. These subsystem processes provide additional protection. Therefore, some work done by Windows NT on behalf of your application may appear in other subsystem processes in addition to the Privileged Time in your process.


User Time

User Time is the percentage of processor time spent in User Mode in non-Idle threads. All application code and subsystem code execute in User Mode. The graphics engine, graphics device drivers, printer device drivers, and the window manager also execute in User Mode. Code executing in User Mode cannot damage the integrity of the Windows NT Executive, Kernel, and device drivers. Unlike some early operating systems, Windows NT uses process boundaries for subsystem protection in addition to the traditional protection of User and Privileged modes. These subsystem processes provide additional protection. Therefore, some work done by Windows NT on behalf of your application may appear in other subsystem processes in addition to the Privileged Time in your process.


Process Memory Used

The current number of bytes in the Working Set of this process. The Working Set is the set of memory pages touched recently by the threads in the process. If free memory in the computer is above a threshold, pages are left in the Working Set of a process even if they are not in use. When free memory falls below a threshold, pages are trimmed from Working Sets. If they are needed, they will then be soft-faulted back into the Working Set before they leave main memory.


Process Priority

The current base priority of this process. Threads within a process can raise and lower their own base priority relative to the process's base priority.


Threads

Thread State is the current state of the thread. It is 0 for Initialized, 1 for Ready, 2 for Running, 3 for Standby, 4 for Terminated, 5 for Wait, 6 for Transition, 7 for Unknown. A Running thread is using a processor; a Standby thread is about to use one. A Ready thread wants to use a processor but is waiting for a processor because none are free. A thread in Transition is waiting for a resource in order to execute, such as waiting for its execution stack to be paged in from disk. A Waiting thread has no use for the processor because it is waiting for a peripheral operation to complete or a resource to become free.


Thread Priority

The current base priority of this thread. The system may raise the thread's dynamic priority above the base priority if the thread is handling user input, or lower it towards the base priority if the thread becomes compute bound.


Thread Information

Context Switches/sec is the rate of switches from one thread to another. Thread switches can occur either inside of a single process or across processes. A thread switch may be caused either by one thread asking another for information, or by a thread being preempted by another, higher-priority thread becoming ready to run.

Dynamic Priority is the current dynamic priority of this thread. The system may raise the thread's dynamic priority above the base priority if the thread is handling user input, or lower it towards the base priority if the thread becomes compute bound.


QSLICE.EXE: CPU Usage by Processes
Computer Diagnostic Tools

QSLICE.EXE: CPU Usage by Processes

Run Quick Slice now.

Quick Slice shows the percentage of total CPU usage for each process in the system. This tool is similar to PSTAT.EXE, but it presents the information in a graphical format.

Quick Slice topics

To use Quick Slice

The Quick Slice window

To specify the sampling interval for Quick Slice

Related topics

Files required


File required for Quick Slice

QSLICE.EXE


QSLICE.EXE: CPU Usage by Processes

To use Quick Slice

The Quick Slice window

To specify the sampling interval for Quick Slice


To use Quick Slice
QSLICE.EXE: CPU Usage by Processes

To use Quick Slice

Run Quick Slice now.

1	Click the Start button.

2	Point to Programs.

3	Point to Resource Kit 4.0.

4	Point to Diagnostics.

5	Click Quick Slice.

6	Double-click an image name in the Quick Slice window to see details about the threads of that process.


The Quick Slice window
QSLICE.EXE: CPU Usage by Processes

The Quick Slice window

Quick Slice displays, for active processes:

PID (Process ID)

The process ID number in hexadecimal format.

Image Name

Identifies the executable filename or process associated with a particular item.

% Process CPU Usage

Identifies the percentage of total CPU usage associated with a particular process.

In the Quick Slice window:

Red bar = Kernel time

Blue bar = user time

For the main window, the length of the bar represents (CPU usage for a single process) / (CPU usage for all processes currently running in the system) * 100.

For the secondary windows, the length of the bar represents (CPU usage for an individual thread) / (CPU usage for all the threads in this process) * 100.


To specify the sampling interval for Quick Slice
QSLICE.EXE: CPU Usage by Processes

To specify the sampling interval for Quick Slice

Open Command Prompt now.

At the command prompt, type

start qslice -tnnn

Where:

-tnnn

Specifies the display interval in milliseconds. (The default is 500 milliseconds.)


QUICKRES.EXE: Quick Resolution Changer
Desktop Tools

QUICKRES.EXE: Quick Resolution Changer

Run Quick Resolution Changer now.

This tool enables you to change the visible screen area, resolution (DPI), bit depth, and color palette settings from the taskbar, without restarting Windows NT.

QUICKRES resides in the notification area at the right end of the taskbar. Single-click (left) the icon to dynamically select new display settings for your desktop. Double-click (left) to bring up the Display properties applet.

Note	If you select a mode that is incompatible with your video card, simply wait 15 seconds and then hit the ESC key. This will return you to the previous resolution.

Files required


File required for Quick Resolution Changer

QUICKRES.EXE


RASLIST.EXE
Network/Server Administration Tools

RASLIST.EXE

Server only	Included in the Windows NT Server, but not Workstation, Resource Kit.

This command-line utility displays RAS server announces from a network.

RASLIST gets RAS server announces from all LANAs, with 1 listening thread per LANA.

RASLIST topics

RASLIST syntax

RASLIST example

Related topics

Files required


File required for RASLIST

RASLIST.EXE


RASLIST.EXE

RASLIST syntax

RASLIST example


RASLIST syntax
RASLIST.EXE

RASLIST syntax	  Open Command Prompt now.

raslist [-?]

Where

raslist

run without parameters, displays RAS server announces.

-?

displays this usage screen

To terminate raslist, type CTRL + C.


RASLIST example
RASLIST.EXE

RASLIST example

c:\raslist

Initializing...

Ready to receive RAS announces...

RAS announce received from host TODDW3

RAS announce received from host JAWADKMIPS

RAS announce received from host PAULFI_P5

RAS announce received from host ZUBAIRA3

RAS announce received from host ERICCH-ALPHA

RAS announce received from host COLINW0

RAS announce received from host ARDEN_D

RAS announce received from host VADIME4

RAS announce received from host KIMST_NT

RAS announce received from host PCHIU1

RAS announce received from host PRADEEPB_PTM

RAS announce received from host SAMRACHT6


RASUSERS.EXE: Enumerating Remote Access Users
Network/Server Administration Tools

RASUSERS.EXE: Enumerating Remote Access Users

Server only	Included in the Windows NT Server, but not Workstation, Resource Kit.

RasUsers lets you list all user accounts that have been granted permission to dial in to the network via Remote Access Service (RAS).

RasUsers syntax

Open Command Prompt now.

rasusers {domainName | \\serverName}

For example:

rasusers MYDOMAIN

rasusers \\rasserver1

Type rasusers /? or rasusers /help to get help.

Related topics

Files required


File required for RasUsers

RASUSERS.EXE

RASSAPI.DLL


RCMD.EXE: Remote Command Service
Network/Server Administration Tools

RCMD.EXE: Remote Command Service

Run the Remote Command client (RCMD.EXE) now.

Server only	Included in the Windows NT Server, but not Workstation, Resource Kit.

The Remote Command Service (RCMD.EXE) provides a secure, robust way to remotely administer and run command-line programs.

RCMD consists of client and server components. The client is a command-line program, RCMD.EXE. The server end, RCMDSVC.EXE, is installed and run as a service. That is, it can be stopped and started locally or remotely via the Control Panel Network application, or locally with the NET START and NET STOP commands. As a service, if configured for autostart, it will run whenever the system is running, independently of whether a user is locally logged on.

A command session, or "virtual console," is created when a client connects to the server. It is not visible on the desktop, and does not in any way interfere with it. Up to 10 clients may be simultaneously connected to the remote command server on a computer, all operating securely and independently of each other.

Remote Command Service topics

Remote Command Installation

Remote Command Operation

Interactive Session

Interactive Multi-Session

Single-Command Session

Remote Command Security

Remote Command Limitations

Related topics

Files required


Files required for Remote Command Service

RCMD.EXE

RCMDSVC.EXE

OEMNSVRC.INF


RCMD.EXE: Remote Command Service

Remote Command Installation

Remote Command Operation

Interactive Session

Interactive Multi-Session

Single-Command Session

Remote Command Security

Remote Command Limitations


Remote Command Installation
RCMD.EXE: Remote Command Service

Remote Command Installation

The Resource Kit setup program installs the Remote Command Service files into your Resource Kit folder. No further installation is necessary for the Remote Command client.

To install the Remote Command server

1	Copy the following files from your Resource Kit folder to your %SYSTEMROOT%\SYSTEM32 folder:

RCMDSVC.EXE

OEMNSVRC.INF

2	Click Start, point to Settings, and click Control Panel.

3	Double-click the Network icon.

4	Click the Services tab.

5	Click Add.

6	On the Network Service list, select Remote Command Server and click OK.

You do not have to restart the system for the installation to take effect. There are no configuration options.

Before using Remote Command Server, however, you must start the service:

To start the service

1	Double-click the Services icon in Control Panel.

2	Select Remote Command Server and click Start.


Remote Command Operation
RCMD.EXE: Remote Command Service

Remote Command Operation

To start the client side, type rcmd at the command prompt.

Or click to:

Run the Remote Command client (RCMD.EXE) now.

For syntax information, type rcmd /?

There are three modes of operation:

Interactive Session

Interactive Multi-Session

Single-Command Session


Interactive Session
RCMD.EXE: Remote Command Service

Interactive Session

To run an interactive session

1	At the command prompt, type rcmd \\server_name.

This establishes a command session with the computer specified in server_name.

2	Enter multiple commands, if necessary.

3	Type CTRL+BREAK to terminate the session and exit RCMD.

If a program is executing on the target at the time the session is terminated, the program will be terminated, except for spawned, detached processes (see Remote Command Limitations).

4	Type exit to terminate the remote command shell and break the session.


Interactive Multi-Session
RCMD.EXE: Remote Command Service

Interactive Multi-Session

To run an interactive multi-session

1	At the command prompt, type rcmd.

2	Type the server name without the \\.

When a server name is entered, if the session is successfully established, multiple commands can be entered, as in Interactive Session mode. However, typing CTRL+BREAK or CTRL+C will break only the session and not exit the program. Instead, the program will prompt for another server with which to establish a new session.

3	Type CTRL+BREAK again to terminate the session and exit RCMD.


Single Command
RCMD.EXE: Remote Command Service

Single-Command Session

To run a single-command session

At the command prompt, type rcmd \\server_name command

The specified command on the specified server executes. Upon completion of the command, RCMD terminates. This is particularly useful for executing a series of commands to multiple servers from a batch command script.


Remote Command Security
RCMD.EXE: Remote Command Service

Remote Command Security

Security is provided in two ways:

The logged-on user must have interactive logon privileges on the target computer in order to connect to it.

Note:	All Windows NT Workstation users have this privilege by default. Anyone who can locally log on to your system can transparently access it over the network, unless you configure it otherwise. For Windows NT Server, however, only system administrators have this privilege.

Any programs executed on the target computer are executed impersonating the logged-on user. Any access validation (such as opening files) is performed as if the user were logged on to the local computer.


Remote Command Limitations
RCMD.EXE: Remote Command Service

Remote Command Limitations

Only non–MS-DOS programs using STDIN/STDOUT/STDERR for input/output will function redirected across the network. Programs that use the WIN32 Console API will not work correctly. MS-DOS programs will not work. Generally, any programs that use on-screen character mode windows or cursor manipulation (such as screen-mode editors) will not work.

It is not possible to connect with the user’s credentials, from the remote shell, to file resources remote to the target computer. The only way to connect is to specify a username and password with the NET USE command (see NET USE help). Due to the way the NET USE command works, it is not possible to be prompted for the password; it must be entered on the command line, and, in any case, is then sent in clear text across the network.

Executing START on the remote computer will result in spawning detached processes. These processes are not "connected" (that is, no input or output is possible), and will not be killed when you exit the remote command shell. This wastes resources on the remotecomputer.

The standard users environment is not set up in the remote command shell. Any environment must be set up explicitly during the command session.


REGBACK.EXE: Registry Backup
Registry Tools

REGBACK.EXE: Registry Backup

REGBACK is a backup batch tool that backs up the Windows NT Registry to files without use of a tape drive, providing a complete snapshot of the Registry. REGBACK allows you to back up Registry hives while the system is running and has the hive files open.

To use REGBACK, you must be logged on as a member of a group that has "Backup files and folders" privileges.

Caution	By default, the RDISK utility in Windows NT Server and Windows NT Workstation does not back up all of the Registry. RDISK is intended as a last resort for making a system bootable, but not necessarily as it was. If you want RDISK to back up the entire Registry, including the DEFAULT, SAM and SECURITY files, you must use the /s switch, running rdisk /s. For more information, see "Preparing for and Performing Recovery" in the Windows NT Server Resource Guide.

REGBACK topics

REGBACK syntax

To back up all Registry files in the \CONFIG folder

To manually back up a hive to a named file

Regular Registry backup on multiple computers

Notes on REGBACK

REGBACK ErrorLevel

REGBACK example

Related topics

Files required


File required for REGBACK

REGBACK.EXE


REGBACK.EXE: Registry Backup

REGBACK syntax

To back up all Registry files in the \CONFIG folder

To manually back up a hive to a named file

Regular Registry backup on multiple computers

Notes on REGBACK

REGBACK ErrorLevel

REGBACK example


REGBACK syntax
REGBACK.EXE: Registry Backup

REGBACK syntax	  Open Command Prompt now.

regback switches (described in command-line help)

To see command-line help, type:

regback

or

regback /?

To see one screen of help at a time, type:

regback | more

REGBACK will display the command line syntax to edit and use. You can use the cut-and-paste feature of the console to set up a manual backup quickly.

After using REGBACK, examine the output to make sure that the backup did what you wanted.

Note	The change takes effect only after the system is restarted.


To back up all Registry files in the \CONFIG directory
REGBACK.EXE: Registry Backup

To back up all Registry files in the \CONFIG folder

Open Command Prompt now.

regback DestinationFolder

For example: regback c:\monday.bku saves all hives in the MONDAY.BKU folder. A warning appears if there are hives that must be backed up manually or if there are errors.


To manually back up a hive to a named file
REGBACK.EXE: Registry Backup

To manually back up a hive to a named file

Open Command Prompt now.

regback filename hivetype hivename

Where:

hivetype

is either machine or users. Will fail if the hivetype isn't machine or users.

hivename

is the name of an immediate subtree of HKEY_LOCAL_MACHINE or HKEY_LOCAL_USERS. Will fail if hivename isn't a hive root.

For example:

regback c:\special.sav\system machine system

regback c:\savedir\prof users s-1-0000-0000-1234


Regular Registry backup on multiple computers
REGBACK.EXE: Registry Backup

Regular Registry backup on multiple computers

You can create a batch file that uses REGBACK to regularly back up the Registry hives on multiple computers. You can schedule this batch file to run with the AT service or WinAT (the Schedule service must be running in an account that can access the network, and not in the System account).

Here's an example of such a batch file:

echo on

rem doback

rem Back up Registry from \CONFIG to network

rem

net use z: \\backupserv\registry

<error text>

cd z:\MyComputerName

md z:\MyComputerName\backreg

copy C:\winnt\system32\config z:\MyComputerName\backreg

regback z:\MyComputerName

Note	REGBACK cannot back up files onto a target folder that already contains files with the same names. So be sure to delete all files in the target folder before you attempt a backup.

Also, remember that REGBACK does not back up hives that aren't in active use. You must use the Copy, XCopy, or SCopy command to back up unused hive files, such as unused user profiles.


Notes on REGBACK
REGBACK.EXE: Registry Backup

Notes on REGBACK

REGBACK and REGREST save and reload the entire hive, including access control lists. So it's possible to restore a hive and find that you have different access control lists than before.

REGBACK does not back up hives that aren't loaded. You can just copy these files, since they are not loaded in the Registry.

REGBACK does not automatically back up hives that don't reside in the CONFIG folder (specifically, some user profiles), but it will do so manually. This avoids name conflicts.

REGBACK will stop at the first bug, except for manual hives.

REGBACK will not overwrite existing files; instead, it reports an error.

REGBACK fails if the hive files don't all fit on the target, so often it's best to use REGBACK to back up hives to a hard disk folder and then use BACKUP.EXE, or use XCOPY.EXE or SCOPY.EXE to save the backed up hives on floppy disks.

REGBACK does not copy the files in the CONFIG folder that are not currently kept open by the Registry. Use XCOPY.EXE or SCOPY.EXE to save inactive hives.

If you have a tape drive, use the Windows NT Backup program instead. Start Backup by double-clicking its icon in the Administrative Tools program group.


REGBACK ErrorLevel
REGBACK.EXE: Registry Backup

REGBACK ErrorLevel

The error on exit will be:

0 if the procedure was successful

1 if a hive that requires manual backup or restoration was encountered

2 for all other errors


REGBACK example
REGBACK.EXE: Registry Backup

REGBACK example

d:\>regback d:\test

saving SECURITY to d:\test\SECURITY

saving SOFTWARE to d:\test\SOFTWARE

saving SYSTEM to d:\test\SYSTEM

saving .DEFAULT to d:\test\DEFAULT

saving SAM to d:\test\SAM

saving S-1-0-17-12-4-56-64744-46-1363 to d:\test\USER000

d:\>regback d:\test\USER000 users S-1-0-17-12-4-56-64744-46-1363

saving S-1-0-17-12-4-56-64744-46-1363 to d:\test\USER000

d:\>regback d:\test

saving SECURITY to d:\test\SECURITY

Save failed

hivebranch='machine', hive='SECURITY', result='0x000000b7'

file='d:\test\SECURITY'


REGCHG.EXE
Registry Tools

REGCHG.EXE

This command-line utility enables you to add or change Registry values on the local or a remote computer.

REGCHG operates on keys in the HKEY_LOCAL_MACHINE hive only. It allows Key names with spaces in them, which REGINI.EXE does not, because the Registry path must be enclosed in quotation marks.

For more information

Run regchg without switches at the command prompt.

Related topics

Files required


File required for REGCHG

REGCHG.EXE


REGDEL.EXE
Registry Tools

REGDEL.EXE

This command-line and batch utility removes Registry keys remotely or on the local computer. It can be used in batch files to delete Registry settings on multiple servers.

REGDEL syntax

Open Command Prompt now.

regdel [-r \\ServerName] "RegistryPathToDelete"

Where:

-r \\ServerName

indicates the name of a remote computer on which to delete a Registry path.

"RegistryPathToDelete"

is the name, enclosed in quotation marks, of a Registry path to delete.

Related topics

Files required


File required for REGDEL

REGDEL.EXE


REGENTRY.HLP: Windows NT Registry Entries
Registry Tools

REGENTRY.HLP: Windows NT Registry Entries

Open Windows NT Registry Entries now.

This tool provides a database of Windows NT Registry entries in the form of a Help file. You can use this Help file while working in Registry Editor to find ranges, minimum-maximum values, and instructions for setting specific values in the Registry.

Files required


File required for REGENTRY

REGENTRY.HLP


Regina REXX scripting language
Batch Tools

Regina REXX Scripting Language

Regina REXX is a full scripting language with Registry access, event log functions, and OLE automation support.

Because it can be used as a batch language for any application that also supports OLE automation, it is fully integrated into the Win32 environment. For example, you can use an OLE-compatible spreadsheet to generate and save formatted reports or perform advanced filtering.

Regina REXX topics

To use Regina REXX

Regina REXX example

For more information

Open REXX.WRI now.

Copyright Notice:
The files for the Perl 5 scripting language, POSIX Utilities, and Regina REXX scripting language are the only files covered by the GNU Library General Public License. All other files are copyrighted by Microsoft Corporation or the respective owners, and are subject to the terms of a separate license agreement.

Related topics

Files required


Files required for Regina REXX

REXX.EXE

REXX.WRI

The source files for Regina REXX are located in the \SOURCE\REXX folder on the Resource Kit CD.


Regina REXX Scripting Language

To use Regina REXX

Regina REXX example


To use Regina REXX
Regina REXX Scripting Language

To use Regina REXX

Open Command Prompt now.

Prepare a script file with NOTEPAD.EXE or other text file editor. To execute the script, run REXX.EXE with the name of the script file. At the command line, type:

rexx scriptfile

Where:

scriptfile

is the filename of the script file to use.


Regina REXX example
Regina REXX Scripting Language

Regina REXX example

rexx myscript.rexx

A new feature in CMD.EXE under Windows NT 4.0 allows this script to be started simply as:

myscript.rexx

For information on how to do this, see the documentation under the /x switch when you type cmd /?


REGINI.EXE: Registry Change by Script
Registry Tools

REGINI.EXE: Registry Change by Script

This utility uses character-based batch files to add keys to the Windows NT Registry by specifying a Registry script. Similar functionality is available as an interactive process in the Registry Editor. But REGINI supports a wider range of data types and provides a quick way to add or modify drivers in the Registry.

Registry Change by Script topics

REGINI syntax

Using an .INI file

To modify a REG_BINARY Registry entry

For more information

Open REGINI.DOC now.

Related topics

Files required


Files required for Registry Change by Script

REGINI.EXE

REGINI.DOC

User-defined script file


REGINI.EXE: Registry Change by Script

REGINI syntax

Using an .INI file

To modify a REG_BINARY Registry entry


RegIni syntax
REGINI.EXE: Registry Change by Script

REGINI syntax	  Open Command Prompt now.

regini InputTextFile ...

Where:

InputTextFile

is the filename of one or more files to be processed into the Windows NT Registry. InputTextFiles must be in ANSI format and are converted to Unicode when read from the disk.

For details on how to create InputTextFiles:

Open REGINI.TXT now.


Using an .INI file
REGINI.EXE: Registry Change by Script

Using an .INI file

To save a file named SRV.INI on a shared folder, you would use this command line:

regini \\popcorn\public\scottsu\srv.ini

If you use an .INI file to specify the Registry change, the format must locate the key on the first line, followed by the Registry entry value in this format:

\registry\key
valuename = datatype value

For example, the following would place the DiskSpaceThreshold parameter in the Registry or change the value that is already there:

\registry\machine\system\currentcontrolset\services\lanmanserver\parameters
DiskSpaceThreshold = REG_DWORD 0x00000000


To modify a REG_BINARY Registry entry
REGINI.EXE: Registry Change by Script

To modify a REG_BINARY Registry entry

To allow REGINI.EXE to modify a REG_BINARY Registry entry, the .INI file must use the following syntax:

first argument: the number of bytes

subsequent arguments: the actual data


REGKEY.EXE: Logon and FAT File System Settings
Registry Tools

REGKEY.EXE: Logon and FAT File System Settings

Run Logon and FAT File System Settings now.

REGKEY is a GUI utility that can be used to set several Registry settings without actually editing the Registry.

Use REGKEY to set the options for the following:

Display Shutdown button in Logon dialog.

Display last user in Logon dialog.

Parse AUTOEXEC.BAT for SET and PATH commands.

Number of user profiles to cache.

Default background wallpaper.

Allow long filenames in FAT.

Files required


File required for REGKEY

REGKEY.EXE


REGREAD.EXE
Registry Tools

REGREAD.EXE

This command-line utlity reads the Registry, parses out values, and outputs them to the screen.

REGREAD operates on keys in the HKEY_LOCAL_MACHINE hive only.

Files required


File required for REGREAD

REGREAD.EXE


REGREST.EXE: Registry Restoration
Registry Tools

REGREST.EXE: Registry Restoration

REGREST restores Registry hive files from backup copies by using the Win32 ReplaceKey function.

You must be logged on as a member of a group that has "Backup Files and Folders" privileges to use REGREST.

Caution	By default, the RDISK utility in Windows NT Server and Windows NT Workstation does not back up all of the Registry. RDISK is intended as a last resort for making a system bootable, but not necessarily as it was. If you want RDISK to back up the entire Registry, including the DEFAULT, SAM and SECURITY files, you must use the /s switch, running rdisk /s. For more information, see "Preparing for and Performing Recovery" in the Windows NT Server Resource Guide.

REGREST topics

REGREST syntax

To restore all active Registry hive files in the \CONFIG folder

To manually restore a hive

Notes on REGREST

REGREST ErrorLevel

Related topics

Files required


File required for REGREST

REGREST.EXE


REGREST.EXE: Registry Restoration

REGREST syntax

To restore all active Registry hive files in the \CONFIG folder

To manually restore a hive

Notes on REGREST

REGREST ErrorLevel


REGREST syntax
REGREST.EXE: Registry Restoration

REGREST syntax	  Open Command Prompt now.

regrest switches

To see command-line help one screen at a time, type:

regrest | more

REGREST will display the command line to edit and use. You can use the cut-and-paste feature of the console to set up a manual restoration quickly.

After using REGREST, examine the output to make sure that the restoration did what you wanted.

Note:	The change takes effect only after the system is restarted.


To restore all active Registry hive files in the \CONFIG directory
REGREST.EXE: Registry Restoration

To restore all active Registry hive files in the \CONFIG folder

Open Command Prompt now.

regrest newFolder saveFolder

Where:

newFolder

Specifies the folder for the source of the backed up hive file that will replace a hive file in the CONFIG folder. For each active Registry hive whose file is in CONFIG, RegRest attempts to replace the current file with a like-named file from the newFolder.

saveFolder

Specifies the folder where the old hive files in CONFIG are moved to.

For example: regrest c:\monday.bku c:\install.sav. A warning appears if there are hives that must be backed up manually or if there are errors.


To manually restore a hive
REGREST.EXE: Registry Restoration

To manually restore a hive

Open Command Prompt now.

regrest newFilename saveFilename hivetype hivename

Where:

newFilename

Specifies the backup source filename. RegRest will rename this file and use it to replace the old hivename file.

saveFilename

Specifies the filename for saving the old hivename that is being replaced. The old hive file will be renamed and moved to this location.

hivetype

Either machine or users. Will fail if the hivetype isn't machine or users.

hivename

The name of an immediate subtree of HKEY_LOCAL_MACHINE or HKEY_LOCAL_USERS. Will fail if hivename isn't a hive root.

For example:

regrest c:\special.sav\system c:\oldsys.sav machine system


Notes on REGREST
REGREST.EXE: Registry Restoration

Notes on REGREST

REGBACK and REGREST save and reload the entire hive, including access control lists. So it's possible to restore a hive and find that you have different access control lists than before.

REGREST does not automatically restore hives that don't reside in the CONFIG folder (such as some user profiles), but RegRest will do so manually. This avoids name conflicts.

REGREST does not restore hives that aren't loaded. You can copy those files to restore them.

All files must be on the same volume. REGREST renames rather than copies files.

The old hive will be stored in a .SAV file, so there must be space for this file.

REGREST will stop at the first bug, except for manually saved hives.

If you have a tape drive, use the Windows NT Backup program instead. Start Backup by double-clicking its icon in the Administrative Tools program group.


REGREST ErrorLevel
REGREST.EXE: Registry Restoration

REGREST ErrorLevel

The error on exit will be:

0 if the procedure was successful

1 if a hive that requires manual backup or restoration was encountered

2 for all other errors


REGSEC.EXE
Registry Tools

REGSEC.EXE

This command-line utility removes the Everyone group from a Registry key.

Removing the Everyone group can enable you to implement stricter and more specific security.

Related topics

Files required


File required for REGSEC

REGSEC.EXE


Remote Access Manager
Network/Server Administration Tools

Remote Access Manager

Remote Access Manager, by virtual motion, enables network managers to manage Remote Access Service (RAS) on a per-user, RAS server, or port basis. You can control RAS resources via LAN or dial-up access.

With Remote Access Manager, you can:

display RAS server and port status.

disconnect RAS sessions from any port.

enable or disable RAS privileges for any user.

Enhanced security and access control enable you to restrict RAS access based on group membership, control RAS access based on time of day, limit the number of connections per day, and define maximum connect time and idle time.

To monitor RAS activity, Remote Access Manager offers enhanced RAS event logging, server and port resource utilization bar graphs, user accounting, and billing reports.

Related topics

Files required


Files required for Remote Access Manager

The files and installation program (SETUP.EXE) for Remote Access Manager are in the \APPS\RASMGR folder on the Resource Kit CD. Remote Access Manager must be installed separately from the Resource Kit.


Remote Console
Network/Server Administration Tools

Remote Console

Server only	Included in the Windows NT Server, but not Workstation, Resource Kit.

Remote Console is a client/server application that enables you to run a command-line session remotely, within which you may launch any other application.

The Remote Console Server service launches a CMD.EXE process per client connection (CMD is the command-line interpreter executable). It then takes full control of the console in which CMD is running and notifies the client of any video memory change of the console. As Remote Console does not redirect standard output, but directly takes control of the video memory, you may remotely run any console program that uses video memory, such as EDIT.

The client sends all keyboard events to the Remote Console Server, so that these events are 'simulated' in the CMD console on the server side.

Few tools besides Remote Console run applications remotely. REMOTE is not a service, but simply redirects standard input and output, so console programs that take control of the video memory and the keyboard do not work with REMOTE. Along with RCMD and RSH, Remote Console Server offers users a new way to run consoles remotely and to take control of a CMD session.

The Remote Console client may be run under any version of Windows NT Workstation or Server.

Remote Console topics

Remote Console installation

Monitoring Remote Console Clients

Security notes

Client/server notes

Related topics

Files required


Files required for Remote Console

The files for Remote Console are installed by the Resource Kit in the %NTRESKIT%\RCONSOLE folder.

RCLIENT.EXE

RCONGRP.EXE

RCONSTAT.EXE

RCONSVC.EXE

RCRUNCMD.EXE

RCONMSG.DLL

OEMSETUP.INF


Remote Console

Remote Console installation

Monitoring Remote Console Clients

Security notes

Client/server notes


Remote Console Installation
Remote Console

Remote Console installation

Server setup

The Remote Console Server service installs in less than a minute by using Network in Control Panel.

1	Open the Network properties dialog box (through Control Panel or by right-clicking the Network Neighborhood icon and clicking Properties).

Open Control Panel now.

2	Click Services.

3	Click Add and Have Disk.

4	Enter the path to the Remote Console Server service distribution files on the Resource Kit CD.

5	Click Remote Console Server.

6	Click OK.

7	Reboot.

The Remote Console Server service is started automatically at bootup.

Client setup

No special installation is required to run the client. Just copy RCLIENT.EXE to a directory in your path on the client side.

To run the Remote Console client, use the following command-line syntax:

RCLIENT [\\]servercomputername

The client runs ONLY under Windows NT.


Monitoring Remote Console Clients
Remote Console

Monitoring Remote Console Clients

You can monitor Remote Console connections in two ways:

1	All Remote Console clients connections are logged in the system event logs. A Success Audit event is logged on the server when a client connects to Remote Console Server and another Success Audit event is logged when the same user is disconnected. Each user is given a unique ID so that the administrator can find, for example, the disconnection event matching a given connection event.

2	The administrator may also run RCONSTAT.EXE on the server or remotely when connected to the server with the Remote Console client. RCONSTAT.EXE doesn't take any parameter and lists all the current connections. The output looks like:

Current number of clients                         = 1

Total number of clients since service has started = 1

  Id  Client User Name               Start Time                In      Out

-------------------------------------------------------------------------------

   1  DOMAIN\User                    Wed Aug 21 18:48:10 1996  2KO     59KO

Use of RCONSTAT is limited to administrators: all other users will be given an access denied error message. Notice that the client user name is always "NT AUTHORITY\SYSTEM' under NT 3.51 because the displayed name matches the security context of the CMD process.

Caution	Stopping the Remote Console Server Service actually closes all current connections. Moreover when a client is disconnected, all the processes it has launched during the remote CMD session and that are still running are killed.


Security notes
Remote Console

Security notes

Caution	Permitting all users to connect to Remote Console Server can compromise server security, as Remote Console clients are given a CMD session. Any user who is given access to a CMD session can run any application as if he or she were physically logged onto the server.

Under Windows NT 4.0, clients are limited to members of the Administrators group. Under Windows NT 4.0, by default, Remote Console Server will only allow clients that belong to the Administrators group.

However, you may allow other users not in the Administrators group to connect to Remote Console Server. Remote Console Server setup creates a local group on your computer called 'RConsole Users' that includes a list of users and global groups. Use User Manager to modify the members of this group. All members of RConsole Users local group are permitted to connect to Remote Console Server (notice that Administrators members are always permitted to run remote console clients whether they are members of RConsole Users or not).

Remote Console Server setup also adds the following Registry entry:

Key = HKEY_LOCAL_MACHINE\CurrentControlSet\Services\RCONSVC\Parameters

Value = OtherAllowedUsers

This is a multi-string value and includes by default only one string: 'RConsole Users'.

"OtherAllowedUsers" is a list of all users that do not belong to the Administrators group but that are permitted to run a CMD session remotely with RCLIENT. Each element of OtherAllowedUsers may have one of the two following forms:
USERNAME or DOMAIN\USERNAME. Notice that USERNAME may also be the name of a group.

For these users, a CMD process is lauched with the security context of the client. So the CMD process runs with the same security access token as if the client were physically logged onto the server.

WINLOGON usually checks that a user who attempts to physically log onto a server has the special user right 'Log on locally' (refer to User Manager documentation for more information). Remote Console Server doesn't check this privilege before granting access to the client. Therefore, if you configure the server to accept clients that are not members of the Administrators group, you should be aware that they will have access to anything on the server, as if they were logged onto the server and running CMD.

For better security in this case, you should check all file permissions so that the client may only edit or modify files with access granted.


Client/server notes
Remote Console

Client/server notes

Remote Console Server does not only send its video memory to the client. The client is an exact copy of the console on which CMD is running. This means that the server also sends the client any change in its console size. The client may run mode x,y on the client side, for example, to see the changes.


Remote Kill
Computer Diagnostic Tools

Remote Kill

This service (RKILLSRV.EXE) with both GUI (WRKILL.EXE) and command-line (RKILL.EXE) clients allows a user to enumerate and kill processes on a remote computer. To kill a process remotely with this tool, you must be member of the Administrators group.

Remote Kill combines some of the functionality of TLIST.EXE and KILL.EXE.

The service can be installed with INSTSRV.EXE or SRVINSTW.EXE.

Related topics

Files required


Files required for Remote Kill

RKILL.EXE (command-line version)

RKILLSRV.EXE (service)

WRKILL.EXE (GUI version)


REMOTE.EXE: Remote Command Line
Network/Server Administration Tools

REMOTE.EXE: Remote Command Line

The REMOTE utility allows you to run command-line programs on remote computers.

For example, when you are developing software, you can compile code with the processor and resources of a remote computer while you perform other tasks on your computer. You can also use REMOTE to distribute the processing requirements for a particular task across several computers.

To use REMOTE, you must first start the Server end (by running remote /s) on the computer where you want to run the selected program. Then, you connect to the Server end from another computer (by running remote /c).

Please note that REMOTE does NO security authorization, and will permit anyone with a REMOTE client (remote /c) to connect to your REMOTE server (remote /s). This leaves the account under which the REMOTE server was run open to anyone who connects. By contrast, RCMD.EXE: Remote Command Service authenticates all users with standard Windows NT user authentication procedures.

Note:	REMOTE cannot be used to control graphical Windows-based applications.

REMOTE topics

To start the Server end of REMOTE

To start the Client end of REMOTE

To exit REMOTE on the Server computer

To exit REMOTE on the Client computer

REMOTE Server example

REMOTE Client example

REMOTE Limitations

Related topics

Files required


File required for REMOTE

REMOTE.EXE


REMOTE.EXE: Remote Command Line

To start the Server end of REMOTE

To start the Client end of REMOTE

To exit REMOTE on the Server computer

To exit REMOTE on the Client computer

REMOTE Server example

REMOTE Client example

REMOTE Limitations


To start the Server end of REMOTE
REMOTE.EXE: Remote Command Line

To start the Server end of REMOTE

Open Command Prompt now.

At the command prompt on the Server computer, type:
remote /s "cmd" uniqueID [/u [domainname\]username] [/f] [/b]

Where:

"cmd"

Specifies the text-mode executable name for the program that you want to control from another computer, enclosed in quotes with any optional parameters required.

uniqueID

For the /s switch, specifies a string to uniquely identify this session of Remote Server from other possible sessions on this computer.

/u [domainname\]username

Specifies a group or user that can connect. For example, remote /s cmd Rana /u administrators allows only members of the Administrators group to connect, and remote /s cmd Rana /u anniep allows only a user logged on as "anniep" to connect. If this is not specified, anyone can connect to the session.

/f param

Specifies a foreground color for the remote command prompt such as yellow, black, and so on.

/b param

Specifies a background color for the remote command prompt such as lblue, white, and so on, where "lblue" means light blue.


To start the Client end of REMOTE
REMOTE.EXE: Remote Command Line

To start the Client end of REMOTE

Open Command Prompt now.

At the command prompt on the Client computer, type:
remote /c computername uniqueID [/f] [/b] [/l]

Where:

computername

Specifies the name of the computer on which the remote Server is running.

uniqueID

For the /c switch, specifies the uniqueID of the remote Server running on computername

/f param

Specifies a foreground color for the remote command prompt such as yellow, black, and so on.

/b param

Specifies a background color for the remote command prompt such as lblue, white, and so on, where "lblue" means light blue.

/l param

Specifies the number of lines to get for the Client.


To exit REMOTE on the Server computer
REMOTE.EXE: Remote Command Line

To exit REMOTE on the Server computer

At the command prompt, type @k.


To exit REMOTE on the Client computer
REMOTE.EXE: Remote Command Line

To exit REMOTE on the Client computer

At the command prompt, type @q.

This stops REMOTE on the Client end, but leaves the REMOTE running at the Server.


REMOTE Server example
REMOTE.EXE: Remote Command Line

REMOTE Server example

remote /s "i386kd -v" brillig /u administrators

This starts the Kernel Debugger with the -v switch, with only members of the administrators group allowed to connect.

To interact with this "cmd" from another computer, start the Client end with this command, where "apears" is the Remote Server name:

remote /c apears brillig


REMOTE Client example
REMOTE.EXE: Remote Command Line

REMOTE Client example

remote /c rajx86 brillig

This statement connects to a server session on the server named rajx86 with the ID "brillig" if there is a remote /s "cmd" brillig started on the computer rajx86.


REMOTE Limitations
REMOTE.EXE: Remote Command Line

REMOTE Limitations

Only non–MS-DOS programs using STDIN/STDOUT/STDERR for input/output will function redirected across the network. Programs that use the WIN32 Console API will not work correctly. MS-DOS programs will not work. Generally, any programs that use on-screen character mode windows or cursor manipulation (such as screen-mode editors) will not work.


RESTKEY.EXE
Registry Tools

RESTKEY.EXE

This command-line utility enables you to restore a Registry key from a file.

Files required


File required for RESTKEY

RESTKEY.EXE


RIPROUTE.WRI: Routing with Windows NT Server
Internet and TCP/IP Services/Tools

RIPROUTE.WRI: Routing with Windows NT Server

Open RIPROUTE.WRI now.

Server only	Included in the Windows NT Server, but not Workstation, Resource Kit.

This Microsoft Write document explains how you can use Windows NT Server, along with Windows NT Server Multi-Protocol Routing, to connect local area networks (LANs) together or local area networks to wide area networks (WANs) without needing to purchase a dedicated router.

After installing Windows NT Server Multi-Protocol Routing and enabling the Routing Information Protocol (RIP) routing options, your computer running Windows NT Server should be able to route network packets between two or more network adapters by using RIP on Internet Protocol (IP) or Internetwork Packet Exchange (IPX), or both, and be a BOOTP/DHCP Relay Agent (depending on your configuration), which allows a computer to relay BOOTP/DHCP messages across an IP LAN.

Windows NT Server Multi-Protocol Routing is intended for use by system administrators already familiar with routing protocols and routing services. RIPROUTE.WRI provides installation instructions and a brief overview on routing, but assumes that the reader has a basic understanding of routing and dynamic-routing protocols. For more information on routing in general and dynamic routing protocols, please consult a TCP/IP or IPX protocol related book.

Files required


File required for Routing with Windows NT Server

RIPROUTE.WRI


RMTSHARE.EXE: Remote Share
Network/Server Administration Tools

RMTSHARE.EXE: Remote Share

RMTSHARE is a command-line utility that allows you to set up or delete shares remotely.

In order to run RMTSHARE, even to just view shares, you must have share-changing permissions on the remote computer.

Remote Share topic

Remote Share syntax

Files required


File required for Remote Share

RMTSHARE.EXE


Remote Share syntax
RMTSHARE.EXE: Remote Share

Remote Share syntax	  Open Command Prompt now.

rmtshare \\server[\sharename[=path [/printer]]] [/grant [user[:perms ]]] [/remove user][/users:number] [/unlimited] [/remark:"text"] /delete]

Where:

rmtshare

without parameters, displays all command-line options.

\\server

without a sharename, lists all shares on a server. The server name is always required.

\\server\sharename

are the server and share to create, inspect, modify, or delete.

Note	If a sharename or path contains spaces, it must be enclosed in quotes. For example:

\\server\"with space" = "c:\with space"

\\server\sharename=path

are the server and share to set up and assign to the specified path on the computer. For example:

\\myserver\newshare=c:\dir\subdir

assigns the server and sharenames \\myserver\newshare to the \dir\subdir path on drive c:

\\server\sharename=path /printer

sets up a printer share:

rmtshare \\myserver\sharedprt=myprn /printer

Note that the syntax is slightly different: there is no drive letter in the resource name.

/grant (or /g)

without a user, removes the ACL, if any, from a share. Note that this grants the permission "Everyone:Full Control." For example:

rmtshare \\myserver\ashare /g

removes the ACL, if any, from share ashare on server \\myserver.

/grant user

without permissions, removes the name of a valid user or group on the server from the ACL. For example:

rmtshare \\myserver\ashare /g thisuser

removes user billev from the ACL on the share, if there is an ACL, and if there is an entry for billev.

/grant user:perms

adds the name of a valid user or group on the server with permissions, or changes the user's permissions in an ACL.

Valid permissions are r=read, c=change (write), f=full, n=none. You may type "READ", but only the first character is used.

/remove user

removes the specific entry for user, so that user then inherits permissions (in contrast to "/grant user :none", which denies any access at all to user).

/users:number

is the number of users with privileges to the server and share.

Note that:

rmtshare \\server\sharename /users

(without a colon or number) ignores the /users switch and simply shows share information.

rmtshare \\server\sharename /users:

(with a colon but no number) returns a response of "The command completed successfully," although in fact the command did nothing.

/unlimited

specifies that an unlimited number of users will have privileges on the share.

/remark:"text"

adds a comment about the share. Text must be enclosed in quotes (" "). For example:

\\myserver\myshare /remark:"This is a new share"

/delete

deletes the share specified by \\server\sharename. For example:

\\myserver\myshare /delete


ROBOCOPY.EXE: XCOPY with Retries
File Tools

ROBOCOPY.EXE: Enhanced Network File-Copying Utility

ROBOCOPY is a Win32 console-mode application designed to simplify the task of maintaining an identical copy of a folder tree in multiple locations, either on the same computer or in separate network locations. It can provide time-efficient maintenance of mirror images of large folder trees between network servers separated by slow or unreliable WAN links.

Retries for network errors make for robustness, and copying only changed files saves a lot of time. ROBOCOPY's flexibility enables you to copy a single folder or walk a folder tree, specifying multiple filenames and wildcards for source files.

By default, ROBOCOPY ignores source file attributes when selecting files to copy—any file matching other specified conditions will be copied regardless of its attribute settings.

Both the source and destination folders should reside on an NTFS partition wherever possible. Copying to downlevel file systems (HPFS or FAT) will work, but you may lose long filenames, and file times may suffer from rounding errors on the destination.

ROBOCOPY outputs a log of files and folders to its console window, listing the folders processed, files copied and why, network errors, and incompatibilities between the source and destination folder-tree structures. This output can be redirected to a disk file if required. Just before ROBOCOPY terminates, it outputs a summary of its activities during the run to its console window (or disk file if redirected).

Although ROBOCOPY doesn't run as a service, you can use the Schedule service to run ROBOCOPY as a scheduled job. The scheduled job can run a command file that (a) invokes ROBOCOPY and (b) uses SOON.EXE to reschedule the same command file some time in the future. This would have the same effect as a replication service, albeit restricted to having a single drive or sharename as both the source and destination.

ROBOCOPY topic

ROBOCOPY syntax

For more information

For brief usage instructions, run ROBOCOPY with no command-line arguments.

For detailed instructions and notes:

Open ROBOCOPY.WRI now.

Files required


Files required for ROBOCOPY

ROBOCOPY.EXE

ROBOCOPY.WRI


ROBOCOPY syntax
ROBOCOPY.EXE: Enhanced Network File-Copying Utility

ROBOCOPY syntax	  Open Command Prompt now.

robocopy source destination [filename [filename]...] [options]

Where:

robocopy

without parameters, displays all command-line options.

source

is the source folder (drive:\path or \\server\share\path).

destination

is the destination folder (drive:\path or \\server\share\path).

filename

is a file to copy (you can use wildcard characters—the default is "*.*").

options

include:

/s

Copy sub-folders, but not empty ones.

/e

Copy sub-folders, including empty ones.

/t

Timestamp all destination files, including skipped files.

/r:n

Retry n times on failed copies—default is 1 million.

/w:n

Wait n seconds between retries—default is 30 seconds.

/reg

Save /r:n and /w:n in the Registry as default settings.

/x

Report all eXtra files, not just those selected.

/v

Produce Verbose output, showing skipped files.

/l

List only—don't copy, timestamp, or delete any files.

/a+:[r][a][s][h]

Add the given Attributes to copied files.

/a-:[r][a][s][h]

Remove the given Attributes from copied files.

/xa:[r][a][s][h]

Exclude files with any of the given Attributes.

/a

Copy only files with the Archive attribute set.

/m

Like /a, but remove Archive attribute from source files.

/xf filename [filename]...

eXclude Files matching given names/paths/wildcards.

/xd dir [dir]...

Exclude Folders matching given names/paths.

/xc | /xn | /xo

Exclude Changed | Newer | Older files.

/xx | /xl

Exclude eXtra | Lonely files and folders.

/is

Include Same files.

/eta

Show Estimated Time of Arrival of copied files.

/move

Move files and folders (delete from source after copying).

/purge

Delete destination files and folders that no longer exist in source.


RREGCHG.EXE
Registry Tools

RREGCHG.EXE

This command-line and batch utility creates or changes Registry settings on a remote computer.

RREGCHG is useful for making global Registry changes over a network. It also allows Key names with spaces in them, which REGINI.EXE does not, because the Registry path must be enclosed in quotation marks.

For more information

Run rregchg without switches at the command prompt.

Related topics

Files required


File required for RREGCHG

RREGCHG.EXE


RSHSVC.EXE: TCP/IP Remote Shell Service
Internet and TCP/IP Services/Tools

RSHSVC.EXE: TCP/IP Remote Shell Service

Server only	Included in the Windows NT Server, but not Workstation, Resource Kit.

TCP/IP Remote Shell Service, the server side of the TCP/IP utility RSH.EXE, provides a command-line shell or single command execution service for remote users.

RSHSVC.EXE works like the UNIX Remote Shell Service. Any computer with an RSH client—which exists for nearly all major operating systems—can access this service.

TCP/IP Remote Shell Service topics

To install Remote Shell Service

To start and stop Remote Shell Service

For more information

For information on security, starting batch files and window applications, and limitations of the application:

Open RSHSVC.HTM now.

Related topics

Files required


Files required for TCP/IP Remote Shell Service

RSHSETUP.EXE

RSHSVC.DLL

RSHSVC.EXE

RSHSVC.HTM


RSHSVC.EXE: TCP/IP Remote Shell Service

To install Remote Shell Service

To start and stop Remote Shell Service


To install Remote Shell Service
RSHSVC.EXE: TCP/IP Remote Shell Service

To install Remote Shell Service

Open Command Prompt now.

1	Copy RSHSETUP.EXE, RSHSVC.EXE, RSHSVC.DLL to the %SYSTEMROOT%\SYSTEM32 folder.

2	At the command prompt, type the following command:

rshsetup %systemroot%\system32\rshsvc.exe %systemroot%\system32\rshsvc.dll


To start and stop Remote Shell Service
RSHSVC.EXE: TCP/IP Remote Shell Service

To start and stop Remote Shell Service

Open Command Prompt now.

To start the service, at the command prompt, type:

net start rshsvc

To stop the service, at the command prompt, type:

net stop rshsvc


SAVEKEY.EXE
Registry Tools

SAVEKEY.EXE

This command-line utility enables you to save a Registry key to a file.

Files required


Files required for SAVEKEY

SAVEKEY.EXE


SC.EXE
Computer Administration/Configuration Tools

SC.EXE

This tool provides a way to communicate with Service Controller (SERVICES.EXE) from the command prompt to retrieve information about services.

SC topics

How administrators can use SC

How developers can use SC

For more information

For a syntax listing, run sc /? or sc at the command prompt.

For information on developing services with SC:

Open "Using SC.EXE to Develop Windows NT Services" (SC-DEV.TXT) now.

Files required


File required for Service Controller

SC.EXE


SC.EXE

How administrators can use SC

How developers can use SC


How administrators can use SC
SC.EXE

How administrators can use SC

Administrators can find out the name of the binary for any service, and whether it shares a process with other services, by running:

sc qc servicename

from the command prompt.

SC can help match up services in the Services Control Panel applet with processes in Performance Monitor: if the binary name is SERVICES.EXE, the service shares the Service Controller process.

SERVICES.EXE, Service Controller (also known as Service Control Manager), starts all the services. A number of Win32 services developed within the Windows NT group have been written to share the Service Controller's process, in order to conserve system resources. These services don't show up as separate processes in Performance Monitor.

Win32 services developed outside the Windows NT group can also be configured to share processes with each other, so there may not be a process for every other service. SC can be used to get configuration information on these services. If a service doesn't share its process with other services, however, there will definitely be a process for it in Performance Monitor when the service is running.


How developers can use SC
SC.EXE

How developers can use SC

SC can be useful for developers of services, as it provides more detailed and accurate information about services than the two end-user utilities provided with the Windows NT operating system. The Services Control Panel applet and the network command-line interface, NET.EXE, can determine whether a service is running, stopped, or paused. Although these tools are fine for completely debugged applications when everything is running smoothly, the information they provide about a service being developed can be misleading.

SC implements calls to all of the Windows NT service control application programming interface (API) functions. You can set the parameters to these functions by specifying them on the command line.

With SC, you can query the service status and retrieve the values stored in the status structure fields. NET.EXE and the Services Control Panel applet cannot provide you with the complete status of a service, but SC will tell you the exact state of the service, as well as show the last checkpoint number and wait hint. The checkpoint can then be used as a debugging tool, because it provides a clear indication of how far the initialization progressed before the program froze. The utility also lets you specify the name of a remote computer so that you can call the service API functions or view the service status structures on the remote computer.


SCANREG.EXE
Registry Tools

SCANREG.EXE

A Win32 character-based/command-line "Registry GREP" that enables you to search for any string in keynames, valuenames, and/or valuedata in local or remote Registries keys in both Windows NT and Windows 95.

For more information

Open SCANREG.TXT now.

Files required


File required for SCANREG

SCANREG.EXE

SCANREG.TXT


SCOPY.EXE: File Copy with Security
File Tools

SCOPY.EXE: File Copy with Security

File Copy with Security can be used to copy files and folders from NTFS partitions with their security intact. You can use this utility to back up files and folders from NTFS partitions without using a tape drive.

Note:	If you are copying from folders that are on FAT or HPFS partitions, which contain no security information to be copied, use XCOPY instead.

SCOPY topics

SCopy syntax

SCopy and user privileges

Files required


File required for SCOPY

SCOPY.EXE


SCOPY.EXE: File Copy with Security

SCOPY syntax

SCOPY and user privileges


SCOPY syntax
SCOPY.EXE: File Copy with Security

SCOPY syntax	  Open Command Prompt now.

scopy source [destination] [/o] [/a] [/s] [/?]

Where:

source

specifies the source for files to be copied.

destination

specifies where to copy files to.

/o

copies owner security information.

/a

copies security auditing information.

/s

copies all files in sub-folders.

/?

shows all command-line options.

Note:	To copy your own files, you do not require any special user privileges. But to use the /o or /a switches, or to copy other users' files that you don't ordinarily have access to, you must be logged on as a member of the Administrators group on both the computer where you are copying the files from and on the computer you are copying the files to.


SCOPY and user privileges
SCOPY.EXE: File Copy with Security

SCOPY and user privileges

SCOPY tries to use the following user privileges in these cases:

"Backup files and folders" privilege allows you to copy files when ordinarily your access is restricted at the source.

"Restore files and folders" privilege is needed to use the /o switch to copy files that aren't your own.

"Manage auditing and the security log" privilege is needed to use the /a switch.


SCLIST.EXE
Network/Server Administration Tools

SCLIST.EXE

This command-line tool can show currently running services, stopped services, or all services on a local or remote computer.

SCLIST is particularly useful in determining what services are running on a physically remote or blind (no monitor) system. To enable SCLIST to report on the status of services on a computer, however, the Server service must be running on it.

For more information

For a syntax listing, run sclist -? or sclist /? at the command prompt.

Related topics

Files required


Files required for SCLIST

SCLIST.EXE


SECADD.EXE
Registry Tools

SECADD.EXE

This command-line utility enables you to add user permissions to a Registry key.

Files required


Files required for SECADD

SECADD.EXE


SECEDIT.EXE
Computer Administration/Configuration Tools

SECEDIT.EXE

Run SECEDIT.EXE now.

This GUI security-context editor allows you to modify security privileges of the logged-on user and running processes, and to list the security contexts that are in use.

Files required


File required for SECEDIT

SECEDIT.EXE


SETUPMGR.EXE: Setup Manager
Computer and Network Setup Tools

SETUPMGR.EXE: Windows NT Setup Manager

Run Setup Manager now.

Windows NT Setup Manager is an administrative tool that enables system administrators to install or upgrade Windows NT on several computers without having to monitor the installations or upgrades.

With Setup Manager, you can create answer files that are used by Windows NT Setup to perform unattended installations or upgrades of Windows NT. Answer files contain the information that Setup would normally prompt users for while it is installing or upgrading Windows NT.

Note that answer files do not automatically eliminate the need for user input when Setup runs. The parameters in answer files must be set so that user interaction is not required.

If you are upgrading an existing Windows NT installation, Setup will use the parameters of the existing installation and ignore parameters specified in the answer file.

Setup Manager topic

To use Setup Manager

For more information

Open Setup Manager Help (SETUPMGR.HLP) now.

Open SETUPMGR.TXT now.

Related topics

Files required


Files required for Setup Manager

SETUPMGR.EXE

SETUPMGR.INF

SETUPMGR.HLP


To use Setup Manager
SETUPMGR.EXE: Windows NT Setup Manager

To use Setup Manager

Run Setup Manager now.

1	Click Start.

2	Point to Programs.

3	Point to Resource Kit 4.0.

4	Point to Setup

5	Click Windows NT Setup Manager.

To run Setup Manager from the command prompt, type:

setupmgr

For on-screen assistance:

Open Setup Manager Help (SETUPMGR.HLP) now.


SETX.EXE
Batch Tools

SETX.EXE

A command-line utility that offers a batch method for setting environmental variables in the the user or computer environment from a variety of sources, without any programming or scripting. Besides taking both the variable and value from the command line, it can also take values from Registry keys and offsets into text files.

Without SETX, there is no method for settings values directly into the master environment for Windows NT. These are configureable only through Control Panel or through the Registry Editor. The SET command, which is internal to the command interpreter, sets variables only into the environment of the current window.

SETX allows you to set values for variables in either the user or computer environment from one of three sources: Command Line Mode, Registry Mode, and File Mode.

SETX.EXE topics

Command-Line Mode syntax

Registry Mode syntax

File Mode syntax

Known limitations

For more information

setx /? or setx (without parameters) displays command-line options for all three modes.

setx -i displays additional information and examples for all three modes.

Files required


File required for SETX.EXE

SETX.EXE


SETX.EXE

Command-Line Mode syntax

Registry Mode syntax

File Mode syntax

Known limitations


SETX.EXE Command-Line Mode syntax
SETX.EXE

Command-Line Mode syntax	  Open Command Prompt now.

setx variable value [-m]

Where:

variable

is the name of the environmental variable to set.

value

is the value to which the environmental variable will be set.

-m

sets value in the computer environment. The default is the User environment.


SETX.EXE Registry Mode syntax
SETX.EXE

Registry Mode syntax	  Open Command Prompt now.

setx variable -k hive\key\...\value [-m]

Where:

variable

is the name of the environmental variable to set.

-k

specifies that the variable will be set based upon information from a Registry key.

hive\key\...\value

is the Registry path to the value to use for the environmental variable, for example, HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TimeZoneInformation\StandardName

-m

sets value in the Machine environment. The default is the User environment.


SETX.EXE File Mode syntax
SETX.EXE

File Mode syntax	  Open Command Prompt now.

setx variable -f filename {-a x,y | -r x,y "string"} [-d d] [-x] [-m]

Where:

-f filename

specifies the name of the file to use.

-a x,y

specifies absolute coordinates and offset as search parameters.

-r x,y "string"

specifies relative coordinates and offset from string as search parameters.

-d d

specifies additional delimiters (d) such as "," or "\".

The four built-in delimiters are: space, tab, carriage return and linefeed. Additional delimiters can be any ASCII character.  The maximum number of delimiters, including the four built-in ones, is 15.

-x

displays file coordinates. Switches -a, -r, and -d are ignored.

-m

sets value in the Machine environment. The default is the User environment.


SETX.EXE known limitations
SETX.EXE

Known limitations

SETX writes variables to the master environment in the Registry. Variables set with SETX are only available in future command windows, not in the current command window. This is a limitation of Windows NT.

When accessing REG_MULTI_SZ values in the Registry, only the first item is extracted and used.

Only the HKEY_CURRENT_USER and HKEY_LOCAL_MACHINE hives are supported.

Values added to the user or machine environments cannot be removed with SetX (as a corresponding one can be removed from the local environment by using SET with a variable name and no value.)

Registry values of type REG_DWORD are extracted and used in hex mode.

File Mode supports parsing of CR-LF text files only.


ShareUI
Network/Server Administration Tools

ShareUI

This stand-alone extension of Explorer makes it easier to manage network shares.

ShareUI is a special shell folder that allows you to view, add, remove, and configure the properties of network shares for any local or remote computer that you have permission to administer. Network shares are objects that represent shared directories on a computer.

With ShareUI, you can configure all the directory sharing for a computer from a single window. Without ShareUI, you must manually find all shared directories on a computer by using Explorer, and configure them individually. In addition, without ShareUI the only way to administer shares on remote computers is to use Windows NT Server Manager, which is not integrated with the new shell.

Only users that have permission to view and configure shares on a remote computer will see the Shared Directories folder on that remote computer. On the local computer, the Shared Directories folder will still exist, but no configuration operations will be available—the user will only be allowed to view the network shares.

ShareUI topics

To install ShareUI

To uninstall ShareUI

To use ShareUI

Files required


Files required for ShareUI

SHAREUI.DLL

SHAREUI.INF


ShareUI

To install ShareUI

To uninstall ShareUI

To use ShareUI


To install ShareUI
ShareUI

To install ShareUI

The ShareUI tool consists of two files: SHAREUI.DLL and SHAREUI.INF, which must be in the same folder (as the Resource Kit installs them). In Explorer, right-click SHAREUI.INF to see a context menu. On the menu, click Install.

The setup program copies files and modifies the Registry to install ShareUI. Opening My Computer at this point (or choosing Refresh from the View menu of My Computer if it is already open) will display the new folder.


To uninstall ShareUI
ShareUI

To uninstall ShareUI

ShareUI can be uninstalled by choosing Add/Remove Programs from Control Panel, selecting Shared Directories Folder, and clicking the Add/Remove button.


To use ShareUI
ShareUI

To use ShareUI

After installing ShareUI, a new "Shared Directories" folder appears on My Computer. The folder shows a view of all shares on the computer. This is a normal Explorer view, so you can look at it in Explorer tree or folder view, use any view (Large icons, Small icons, List or Details), or use the Toolbar.

Operations on objects are available from context menus as well as from the menu bar. For instance, you can arrange the share objects by name, comment, path, or maximum number of concurrent users. In Details view, you can sort the objects by clicking the column headers. The share objects have three operations: delete, rename, and properties. In Properties, you can change the share name, directory, comment, maximum number of concurrent users, and permissions.

From the File menu, choosing New | Share brings up a dialog box that allows you to share any directory on the selected computer.This is also available on the context menu (opened by clicking the right mouse button on the window background).

Everything you can do locally, you can also do remotely on any remote computer on which you have administrative privilege. Either browse to it in the Network Neighborhood or select Start | Run from the Taskbar, type \\computername (the name of the remote computer), and click OK. In My Computer for the remote computer, you will see the "Shared Directories" folder.

To facilitate quick administration of a server's shared directories, you can create shortcuts on your desktop to the Shared Directories folders of interest.


SHOWACLS.EXE
Computer Diagnostic Tools

SHOWACLS.EXE

This command-line utility enumerates access rights for files, folders, and trees. It allows masking to enumerate only specific ACLs.

Files required


File required for SHOWACLS

SHOWACLS.EXE


SHOWDISK.EXE
Disk/Fault Tolerance Tools

SHOWDISK.EXE

This command-line utility reads and displays the Registry subkey HKEY_LOCAL_MACHINE\SYSTEM\DISK.

This subkey contains information about each of the primary partitions and logical drives defined on the computer. It also identifies which of the primary partitions and logical drives are members of volume sets, stripe sets, mirror sets, and stripe sets with parity.

SHOWDISK syntax

Open Command Prompt now.

showdisk

SHOWDISK topic

SHOWDISK sample output

For more information

For detailed background on SHOWDISK and related Resource Kit utilities, see the "Disk, File System and Backup Utilities" chapter in the Windows NT Server Resource Guide.

If you have installed the Online Books, click to:

Open Windows NT Server Resource Guide in Online Books

Related topics

Files required


File required for SHOWDISK

SHOWDISK.EXE


SHOWDISK sample output
SHOWDISK.EXE

SHOWDISK sample output

Opening \SYSTEM\DISK successful

Disk Registry Information Size........ 168

Operating System Version.............. 3

Checksum.............................. 0x140300

Dirty Shutdown?....................... 114

<reserved 1>.......................... 0x0

<reserved 2>.......................... 0x6d

<reserved 3>.......................... 0x0

Disk Info Offset...................... 0x2c

Disk Info Size........................ 124

FT Info Offset........................ 0xa8

FT Info Size.......................... 0

FT Stripe Width....................... -553123840

FT Pool Size.......................... 1311456

Name Offset <not implemented>......... 0x1402e0

Name Size <not implemented>........... 5505107

General Disk Information:

Number of Disks....................... 2

<reserved>............................ 0

Disk #0:

Number Of Partitions.......... 1

<reserved>.................... 0x0

Signature..................... 0x351d0ce2

Partition #1:

FT Type............... Not a Fault Tolerance Partition

FT State.............. Healthy

Starting Offset....... 0x4600

Length................ 212011520

FtLength.............. 0

<reserved 1>.......... 0x0

<reserved 2>.......... 0x0

Drive Letter..........

Assign Drive Letter?.. Yes

Logical Number........ 1

Ft Group.............. Not an FT Partition

Modified?............. Yes

<reserved char 0>..... 0x0

<reserved char 1>..... 0x0

<reserved char 2>..... 0x0

Disk #1:

Number Of Partitions.......... 1

<reserved>.................... 0x0

Signature..................... 0xdefa0a19

Partition #1:

FT Type............... Not a Fault Tolerance Partition

FT State.............. Healthy

Starting Offset....... 0x7e00

Length................ 527933952

FtLength.............. 0

<reserved 1>.......... 0x0

<reserved 2>.......... 0x0

Drive Letter..........

Assign Drive Letter?.. Yes

Logical Number........ 1

Ft Group.............. Not an FT Partition

Modified?............. Yes

<reserved char 0>..... 0x0

<reserved char 1>..... 0x0

<reserved char 2>..... 0x0


SHOWGRPS.EXE
User Account Administration Tools

SHOWGRPS.EXE

This command-line utility shows the groups to which a user belongs.

SHOWGRPS syntax

Open Command Prompt now.

showgrps {user | domain /user} [/?]

Where

user

is the name of the user for whom to display group membership.

domain /user

is the name of the user on a network domain for whom to display group membership.

/?

displays a usage screen

Related Topics

Files required


File required for SHOWGRPS

SHOWGRPS.EXE


SHOWMBRS.EXE
User Account Administration Tools

SHOWMBRS.EXE

This command-line utility shows the usernames of members of a group.

SHOWMBRS syntax

Open Command Prompt now.

showmbrs {group | domain /group} [/?]

Where

group

is the name of the group for which to display members.

domain /group

is the name of the network domain and group for which to display members.

/?

displays a usage screen

Related Topics

Files required


File required for SHOWMBRS

SHOWMBRS.EXE


SHUTDOWN.EXE: Remote Shutdown
Network/Server Administration Tools

SHUTDOWN.EXE: Remote Shutdown

SHUTDOWN.EXE: Remote Shutdown is a command-line utility that allows you to remotely shut down or reboot a computer running Windows NT.

Remote Shutdown topic

SHUTDOWN.EXE syntax

Related topics

Files required


Files required for Remote Shutdown

SHUTDOWN.EXE


SHUTDOWN.EXE syntax
SHUTDOWN.EXE: Remote Shutdown

SHUTDOWN.EXE syntax	  Open Command Prompt now.

shutdown [\\computername] [/l] [/a] [/r] [/t:xx] ["msg"] [/y] [/c] [/?]

Where:

\\computername

specifies a remote computer to shut down. Note that if no name is given but the utility is started with any of the other options, the local computername will be used.

/l

specifies a local shutdown.

/a

aborts a system shutdown. This is only possible during the timeout period. If this switch is used, all others are ignored.

/r

specifies that the computer should reboot after shutdown.

/t:xx

sets the timer for system shutdown in xx seconds. The default is 20 seconds.

"msg"

specifies an additional message of a maximum of 127 characters, surrounded by quotation marks.

/y

answers all following questions with yes.

/c

forces running applications to close.

Caution	If you use the /c parameter, Windows NT ignores the application's option to save data that may have changed. You will see no File Save dialog box, because Windows NT will force the application to close. This will result in a loss of all data not previously saved.

/? (or shutdown without parameters)

shows all command-line options.

Note:	To schedule Remote Shutdown for a specific time, use the AT command (see Windows NT Help for a full description) or WINAT.EXE: Command Scheduler.


SHUTGUI.EXE: Remote Shutdown GUI
Network/Server Administration Tools

SHUTGUI.EXE: Remote Shutdown GUI

Run Remote Shutdown GUI now.

SHUTGUI.EXE allows you to remotely shut down or reboot a computer running Windows NT. It can be run either with command-line parameters or without.

If no command-line parameters are given, a GUI interface is presented for parameter input. If command-line parameters are given, no GUI interface is presented and the program executes with the parameters provided. This makes it possible to use SHUTGUI.EXE to shut down computers in a batch file.

Remote Shutdown GUI topic

SHUTGUI.EXE command-line syntax

Related topics

Files required


Files required for Remote Shutdown GUI

SHUTGUI.EXE


SHUTGUI.EXE syntax
SHUTGUI.EXE : Remote Shutdown GUI

SHUTGUI.EXE syntax	  Open Command Prompt now.

shutgui [\\computername] [/l] [/a] [/r] [/t:xx] ["msg"] [/c] [/?]

Where:

\\computername

specifies a remote computer to shut down. Note that if no name is given but the utility is started with any of the other options, the local computername will be used.

/l

specifies the local computer to shut down. Note that if you use this parameter the program will ignore any other computername used.

/a

aborts a system shutdown. This is only possible during the timeout period. If this switch is used, all others are ignored.

/r

specifies that the computer should reboot after shutdown.

/t:xx

sets the timer for system shutdown in xx seconds. The default is 30 seconds.

"msg"

specifies an additional message, which must be enclosed in quotes, with a maximum of 127 characters.

/y

answers all following questions with yes.

/c

forces running applications to close.

Caution	If you use the /c parameter, Windows NT ignores the application's option to save data that may have changed. You will see no File Save dialog box, because Windows NT will force the application to close. This will result in a loss of all data not previously saved.

/? (or shutcmd without parameters)

shows all command-line options.

Note	To schedule Remote Shutdown GUI for a specific time, use the AT command (see Windows NT Help for a full description) or WINAT.EXE: Command Scheduler.


SLEEP.EXE: Batch File Wait
Batch Tools

SLEEP.EXE: Batch File Wait

SLEEP causes the computer to wait for a specified amount of time. SLEEP is useful in batch files and may be more convenient to use than the at command in certain cases.

SLEEP topics

SLEEP syntax

SLEEP batch file example

Related topics

Files required


File required for Sleep

SLEEP.EXE


SLEEP.EXE: Batch File Wait

SLEEP syntax

SLEEP batch file example


SLEEP syntax
SLEEP.EXE: Batch File Wait

SLEEP syntax	  Open Command Prompt now.

Add a line in a batch file in the format:
sleep time

Where

time

is the number of seconds to pause.

For example:

sleep 3600

will pause for an hour before running the next command in a batch file.

sleep 10

waits 10 seconds.


SLEEP batch file example
SLEEP.EXE: Batch File Wait

SLEEP batch file example

This example could be used in a logon script:

@echo off

echo * Message of the Day - 7/22/93 *

echo.

echo Don't forget the company picnic!

echo Buses leave at 4pm.

sleep 60


SNMPMON.EXE: SNMP Monitor
Network Diagnostic Tools

SNMPMON.EXE: SNMP Monitor

Run SNMP Monitor now.

Server only	Included in the Windows NT Server, but not Workstation, Resource Kit.

SNMP Monitor is a utility that can monitor any SNMP MIB variables across any number of SNMP nodes. It can then optionally log query results to any ODBC data source (such as SQL Server), automatically creating any necessary tables. Logging can be enabled for all queries or limited to particular thresholds, and thresholds can be either edge or level triggered.

Rudimentary conditionals are also possible. SNMP Monitor can execute arbitrary command lines based on whether or not the node responded to the query, whether or not the node supported the requested variable, and whether the value was greater than, less than, or equal to a specified constant.

SNMP Monitor is a stand-alone executable that accepts a configuration file as input.

SNMP Monitor topics

SNMP Monitor syntax

SNMP Monitor configuration file format

SNMP Monitor sample configuration file: M5.MON

SNMP Monitor sample configuration file: PBXFIX.MON

SNMP Monitor database table schema

SNMP Monitor caveats

Related topics

Files required


File required for SNMP Monitor

SNMPMON.EXE

ODBC32.DLL must be available if database logging is to be used.


SNMP Monitor

SNMP Monitor syntax

SNMP Monitor configuration file format

SNMP Monitor sample configuration file: M5.MON

SNMP Monitor sample configuration file: PBXFIX.MON

SNMP Monitor database table schema

SNMP Monitor caveats


SNMP Monitor syntax
SNMP Monitor

SNMP Monitor syntax	  Open Command Prompt now.

snmpmon configuration_file

Where:

configuration_file

is the fully qualified path to an SNMP Monitor configuration file.

For example:

snmpmon c:\snmp\monitor.ini


SNMP Monitor configuration file format
SNMP Monitor

SNMP Monitor configuration file format

A configuration file is an ASCII text file that consists of one or more "monitored node definitions" separated by at least one blank line or C++ style comment line.  Comments are not allowed within a monitored node definition.  A monitored node definition consists of the "scope declaration" followed by any number of "conditional statements".

Scope declaration

Conditional statements

String substitution

Example


SNMP Monitor

SNMP Monitor configuration file format

Scope declaration

Conditional statements

String substitution

Example


SNMP Monitor configuration file: scope declaration
SNMP Monitor configuration file

Scope declaration

A scope declaration has the following format:

<Node ID> <OID> <Poll interval> <Default log setting> [<ODBC data source> <ODBC table name> <ODBC user ID> [<ODBC password>]]

Where:

<Node ID>

must be one of the following:

A computer name without backslashes (for example, "MY_SEVER")

A dotted IP address (for example, "128.11.100.4")

A colon followed by the path to a text file containing a list of computer names or IP addresses. There must be one entry per line, and blank lines are ignored (for example, ":c:\snmpmon\data\machines.ip").

<OID>

is the dotted object identifier within the MIB namespace (for example, "1.3.6.1.2.1.1.3").

<Poll interval>

is the number of seconds between each poll of this monitored node.

<Default log setting>

is one of the following values:

0	Don't log any data unless specified by one of the conditionals.

1	Log all query results, ignoring the log settings in the conditionals.

<ODBC data source>

is the name of the ODBC data source to which to direct logged data.

<ODBC table name>

is the name of the table within the data source to which to direct logged data. If this table does not exist, it will be created.

<ODBC user ID>

is the user ID used to connect to the ODBC data source.

<ODBC password>

is the password used to connect to the ODBC data source. If this parameter is omitted, no password is used.


SNMP Monitor configuration file: conditional statements
SNMP Monitor configuration file

Conditional statements

The scope declaration is followed immediately by any number of conditional statements. Each conditional has the following format:

<Condition> <Log trigger> [<Command-line trigger> <Command-line timeout> <Command line>]

Where:

<Condition>

is one of the following:

NO_RESPONSE	met when the node does not respond to the query.

RESPONDED	met when the node responds to a query regardless of the value.

SUPPORTED	met when the node responds with a valid value from the query.

NOT_SUPPORTED	met when the node responds, but does not support the value in question.

<x	met when the result is less than the integer x.

>x	met when the result is greater than the integer x.

=x	met when the result is equal to the integer x.

Note:	Spaces are not allowed between the operator and the integer in the three previous conditionals.

<Log trigger>

is one of the following values:

0	Don't log anything when this conditional is met.

1	Log the result only when this conditional was not met during the last poll ("edge triggered").

2	Log the result each time this conditional is met ("level triggered").

<Command-line trigger>

is one of the following values:

0	Execute this command line every time this conditional is met.

1	Execute this command line only if this conditional was not met during the last poll ("edge triggered").

<Command-line timeout>

specifies, in milliseconds, how long to wait for the command line to finish executing. For any timeout greater than 0, if the command has not completed when the timeout expires the command will be terminated.

<Command line>

is the command line to execute when this conditional is met.

Conditionals are processed in the order in which they occur in the node definition. Only the first met conditional is actually processed.


SNMP Monitor configuration file: string substitution
SNMP Monitor configuration file

String substitution

SNMP Monitor also provides for string substitution within command lines. This feature allows an administrator to put placeholders in command lines within the configuration file that will be replaced with the appropriate values when they are executed.

Such substitution strings are specified in a command line by a single percent character ("%") followed by the letter corresponding to the desired value. A percent character can be included in a command by preceding it with another percent character, for example, "%%"). The following substitutions are available:

i	IP address of the current node

o	OID being queried

d	Name of the ODBC data source where this data is being logged

t	Name of the table within the ODBC data source where this data is being logged

r	Result of the SNMP query. This is not the value of the query, but rather a success/failure indication.

v	Value of the queried variable. If the query failed, this resolves to zero.


SNMP Monitor configuration file: example
SNMP Monitor configuration file

Example

Given that we are currently monitoring the 1.3.6.1.2.1.1.3 object ("system uptime") for the device with the IP address 128.11.109.3 and the device has been running for 30 seconds (3000 hundredths of a second), the following command line:

coolstuf %i %o %v

would resolve to:

coolstuf 128.11.109.3 1.3.6.1.2.1.1.3 3000


SNMP Monitor sample configuration file: M5.MON
SNMP Monitor

SNMP Monitor sample configuration file: M5.MON

// In all cases, we turn the icon red if the machine doesn't answer,

// green if it does, and purple if it has been rebooted within the

// last ten minutes

// Headend and operations machines

:ops.b15 1.3.6.1.2.1.1.3 120 0 SNMPMonTest SNMP_HE_Data sa

NO_RESPONSE 	1 1 20 	ovstat %i 0

<30000 	1 1 20  ovstat %i 2

RESPONDED       0 1 20  ovstat %i 3

// USRobotics hardware

:usrobot.b15 1.3.6.1.2.1.1.3 120 0 SNMPMonTest SNMP_Modem_Data sa

NO_RESPONSE 	1 1 20 	ovstat %i 0

<30000 	1 1 20  ovstat %i 2

RESPONDED       0 1 20  ovstat %i 3

// MMS controllers

:tiger.b15 1.3.6.1.2.1.1.3 120 0 SNMPMonTest SNMP_Tiger_Data sa

NO_RESPONSE 	1 1 20 	ovstat %i 0

<30000 	1 1 20  ovstat %i 2

RESPONDED       0 1 20  ovstat %i 3

// Production STBs

:stbe.b15 1.3.6.1.2.1.1.3 120 0 SNMPMonTest SNMP_STB_Data sa

NO_RESPONSE 	1 1 20 	ovstat %i 0

<30000 	1 1 20  ovstat %i 2

RESPONDED       0 1 20  ovstat %i 3

// Test STBs

:stbetest.b15 1.3.6.1.2.1.1.3 120 0 SNMPMonTest SNMP_STB_Data sa

NO_RESPONSE 	1 1 20 	ovstat %i 0

<30000 	1 1 20  ovstat %i 2

RESPONDED       0 1 20  ovstat %i 3

// The cubs don't seem to have SNMP installed so for now we won't

// poll them

//:cub.b15 1.3.6.1.2.1.1.3 1120 0 SNMPMonTest SNMP_CUB_Data sa

//NO_RESPONSE 	1 1 20 	ovstat %i 0

//<30000 	1 1 20  ovstat %i 2

//RESPONDED       0 1 20  ovstat %i 3

_


SNMP Monitor sample configuration file: PBXFIX.MON
SNMP Monitor

SNMP Monitor sample configuration file: PBXFIX.MON

// Production STBs

:stbe.b15 1.3.6.1.2.1.1.3 20 0 SNMPMonTest ModemCtlData sa

NO_RESPONSE 	1 1 20 	modemctl %i BUSY

>30000 	1 1 20  modemctl %i RESTORE

// Test STBs

:stbetest.b15 1.3.6.1.2.1.1.3 20 0 SNMPMonTest ModemCtlData sa

NO_RESPONSE 	1 1 20 	modemctl %i BUSY

>30000 	1 1 20  modemctl %i RESTORE

_


SNMP Monitor database table schema
SNMP Monitor

SNMP Monitor database table schema

The data tables that are created by SNMP Monitor and to which query results are logged contain the following fields/columns:

Column name	Datatype

----------------------------------------------------

ID	int

IPAddress	varchar(20)

ObjectIdentifier	varchar(255)

Result	int

Value	int

Time	datetime


SNMP Monitor caveats
SNMP Monitor

SNMP Monitor caveats

In the current implementation, the timeouts used for SNMP queries are not configurable.  The defaults are 750 millisecond timeout and two retries.

SNMP Monitor assumes a community string of "public" for all SNMP queries. This is not currently configurable.

If polling intervals are too small, SNMP Monitor can get behind. Everything will still get polled and evaluated correctly, but accurate timing cannot be assumed.


SNMPUTIL.EXE: SNMP Browser
Network Diagnostic Tools

SNMPUTIL.EXE: SNMP Browser

SNMP Browser is a utility that lets you get SNMP information from an SNMP host on your network.

SNMP Browser topics

SNMPUTIL syntax

SNMPUTIL example

Related topics

Files required


File required for SNMP Browser

SNMPUTIL.EXE

SNMP service must be installed.


SNMPUTIL.EXE: SNMP Browser

SNMPUTIL syntax

SNMPUTIL example


SNMPUTIL syntax
SNMPUTIL.EXE: SNMP Browser

SNMPUTIL syntax	  Open Command Prompt now.

snmputil {{get | getnext | walk} agent community oid [oid]  |  trap}

Where:

get

gets the current value of the specified oid(s).

getnext

gets the current value of the item in the MIB that follows the item whose oid is specified.

walk

steps through the MIB and retrieves the values of all items in the branch of the MIB specified by oid.

agent

specifies the computer to query. This can be either an IP address or a hostname if the computer is specified in the HOSTS file.

community

specifies a community name, which is used to group computers together into management groups. You can see a list of community names in the SNMP Service Configuration dialog box by choosing the Network icon in Control Panel or looking up the value of ValidCommunities in the SNMP\Parameters subkey in the Registry. By default, a community called "public" is created when you install SNMP under Windows NT.

oid

the ASN.1 name of the variable being queried, of the form .N.N.N.N (that is, a string of numbers separated by periods or, alternately, a string of names separated by periods). oid is an abbreviation for "Object IDentifier."

trap

tells SNMPUTIL to listen for and trap PDUs.


SNMPUTIL example
SNMPUTIL.EXE: SNMP Browser

SNMPUTIL example

snmputil get jb486 public .iso.org.dod.internet.mgmt.mib-2.system.sysDescr.0

would return a text description of the type of computer hardware and software being used on the computer named jb486.

Notice that the oid strings can get quite long. There is one built-in shortcut. For items in the .iso.org.dod.internet.mgmt.mib-2 branch of the Internet MIB, the request can be shortened to:

snmputil get jballard486 public system.sysDescr.0

In this case, the oid does not start with a period (".").

Note:	The SNMP service does not need to be running on the computer that is executing SNMPUTIL, but the proper files must be copied to that computer. In particular, MGMTAPI.DLL and MIB.BIN must be present, and TCP/IP must be installed on the computer.


SOON.EXE: Near-Future Command Scheduler
Computer Administration/Configuration Tools

SOON.EXE: Near-Future Command Scheduler

SOON schedules commands and programs to run in the near future on either the local or a remote computer, by generating and executing an appropriate AT command.

The SOON command closely resembles the AT command because SOON simply generates and executes a suitable AT command. The Schedule service must be running to use the SOON command.

SOON schedules jobs to run at a time relative to the current time (a number of seconds from "now"). Rescheduling a job with SOON therefore requires no editing of the SOON command.

SOON can also be used to schedule jobs to run cyclically at intervals of less than one day. You encapsulate the job to be scheduled in a command file, along with a suitable SOON command, then schedule the command file rather than the actual job it encapsulates.

To install SOON

Make sure SOON.EXE and AT.EXE are on your PATH and that the Windows NT Schedule service has been started on the target computer.

SOON topics

To use SOON

Scheduling syntax

Configuration syntax

Using SOON to schedule jobs repetitively

Example: Running a command every five minutes

For more information

For brief usage instructions, run soon with no arguments.

To view SOON's default settings, run soon /d.

Related topics

Files required


Files required for SOON.EXE

SOON.EXE

AT.EXE (standard Windows NT utility) must be on your PATH.

Schedule service (standard Windows NT service) must be running on the target computer.


SOON.EXE: Near-Future Command Scheduler

To use SOON

Scheduling syntax

Configuration syntax

Using SOON to schedule jobs repetitively

Example: running a command every five minutes


To use SOON
SOON.EXE: Near-Future Command Scheduler

To use SOON

There are two forms of the SOON command: a scheduling command and a configuration command.

Scheduling

Configuration


Scheduling syntax
SOON.EXE: Near-Future Command Scheduler

Scheduling syntax	  Open Command Prompt now.

The SOON scheduling command takes the following form:

soon [\\computername] [delay] [/interactive] "command"

Where:

\\computername

Specifies a remote computer on which the command is to be scheduled. If this argument is omitted, the command is scheduled on the local computer.

delay

Specifies when the command is to run, expressed as a number of seconds from now. If this argument is omitted, SOON will use one of its default delay settings, as follows:

If the job is to be run on the local computer, SOON uses its LocalDelay.

If the job is to be run on a remote compute, SOON uses its RemoteDelay.

/interactive

Allows the job to interact with the desktop of the logged on user when the job runs. If this argument is omitted, SOON uses its current InteractiveAlways (/i—see Configuration) setting, as follows:

If InteractiveAlways is on, the job will interact with the desktop.

If InteractiveAlways is off, the job will NOT interact with the desktop.

command

Specifies the command to be scheduled (enclosed in double quotation marks).


Configuration syntax
SOON.EXE: Near-Future Command Scheduler

Configuration syntax	  Open Command Prompt now.

The SOON configuration command takes the following form:

soon /d [/l:n] [/r:n] [/i:{on | off}]

Where:

/d

Instructs SOON to modify or display its default settings.

If /d is omitted, SOON assumes that this is a Scheduling command

If /d is specified on its own, SOON displays its current default settings.

If /d is specified with other arguments, SOON modifies its default settings accordingly.

/l:n

Sets the value of LocalDelay—default delay for Local jobs—initially 5 seconds. Specify a positive decimal integer for this value.

/r:n

Sets the value of RemoteDelay—default delay for Remote jobs—initially 15 seconds. Specify a positive decimal integer for this value.

/i:[on|off]

Sets the value of InteractiveAlways—initially off.


Using SOON to schedule jobs repetitively
SOON.EXE: Near-Future Command Scheduler

Using SOON to schedule jobs repetitively

SOON is extremely useful when creating and debugging scheduled jobs. This task often requires that the same job be scheduled repetitively as a one-off job, with debugging and corrections to the job between iterations.

Using the AT command to schedule jobs repetitively in this manner can be time-consuming, because AT accepts only absolute times to determine when the job should be run. Rescheduling a job with AT requires, at the very least, that you edit the time in the AT command. Rescheduling such a job with SOON can save a lot of debugging time.


SOON example: running a command every five minutes
SOON.EXE: Near-Future Command Scheduler

SOON example: running a command every five minutes

If, for example, you wish to run SOMEPROG.EXE every five minutes, create a command file as follows:

EVERY5.CMD:

SOON  300  EVERY5.CMD

SOMEPROG.EXE

Then schedule EVERY5.CMD by using AT or SOON (for example, run SOON EVERY5.CMD). When EVERY5.CMD runs, it immediately reschedules itself to run 5 minutes (300 seconds) in the future, and then proceeds to perform the intended task by running SOMEPROG.EXE.

Alternatively, if you wish to run SOMEPROG.EXE repetitively, but wish to have five minutes "idle time" between runs of SOMEPROG.EXE, create a command file as follows:

IDLE5.CMD:

SOMEPROG.EXE

SOON  300  IDLE5.CMD

Then schedule IDLE5.CMD by using AT or SOON (for example, run SOON IDLE5.CMD). When IDLE5.CMD runs, it performs the intended task by running SOMEPROG.EXE, and then reschedules itself to run again 5 minutes (300 seconds) in the future.


SRVANY.EXE: Applications as Services Utility
Computer Administration/Configuration Tools

SRVANY.EXE: Applications as Services Utility

With SRVANY, you can run any Windows NT application as a service.

This allows:

applications to run within a logon account different from that of the current user

applications to keep running when one user logs off and another logs on

server applications to service requests even when nobody is logged on to the server

SRVANY works best with 32-bit applications written for Windows NT. You can use this utility to start 16-bit Windows applications as services, but some 16-bit applications are not able to keep running after a user logs off from the computer.

Note	All SRVANY services should be disabled when installing or upgrading Windows NT Server, Windows NT Workstation, or applications.

SRVANY topic

To install SRVANY

For more information

For technical details on using SRVANY.EXE, see the SRVANY.WRI Write file.

Open SRVANY.WRI now.

Files required


Files required for SRVANY.EXE

SRVANY.EXE

SRVANY.WRI


To install SRVANY
SRVANY.EXE: Applications as Services Utility

To install SRVANY

Open Command Prompt now.

1	Install SRVANY as a Windows NT service. Use the command-line syntax:

instsrv MyService c:\path\srvany.exe

Where

MyService

is the name you want to assign to the service.

c:\path\

is the full path to SRVANY.EXE.

Open Control Panel now.

2	In Control Panel, double-click the Services icon to open the Services dialog box.

3	Then click the Startup button to open the Service dialog box.

4	Under Startup Type, choose either Manual or Automatic.

5	Under Log On As, specify the user account the service will use to log on.

If you need access to the screen and keyboard, you must choose System Account and check the "Allow Service to Interact with Desktop" box. Note that System Account is local and doesn't have network access. Otherwise, choose any account and specify the correct logon password.


SRVCHECK.EXE
User Account Administration Tools

SRVCHECK.EXE

This command-line utility lists the non-hidden shares on an computer running Windows NT and enumerates the users on the ACLs for that share.

Files required


File required for SRVCHECK

SRVCHECK.EXE


SRVINFO.EXE
Network Diagnostic Tools

SRVINFO.EXE

Server only	Included in the Windows NT Server, but not Workstation, Resource Kit.

This command-line utility displays information about a remote server.

SRVINFO.EXE topics

SRVINFO syntax

SRVINFO example

Files required


File required for SRVINFO

SRVINFO.EXE


SRVINFO.EXE

SRVINFO syntax

SRVINFO example


SRVINFO syntax
SRVINFO.EXE

SRVINFO syntax	  Open Command Prompt now.

srvinfo [-s] [-d] [-od] [\\computer_name ] [-?]

Where

-ns

does NOT show any service information.

-d

shows service drivers and service.

-od

shows only disk drive info in csv format.

\\computer_name

specifies the name of a remote server.

If omitted, information on the local computer is displayed.

-?

displays this usage screen.


SRVINFO example
SRVINFO.EXE

SRVINFO example

c:\srvinfo

Server Name: NTRKALPHA

Security: Users

NT Type: WinNT Server

Version: 4.0, Build = 1344

Domain: NTWKSTA

PDC: \\PHOENIX

IP Address: 157.55.88.78

CPU[0]: DEC-321064

Drive: [Filesys] [Size] [Used] [Free]

  C$     NTFS     1004    907     97

  D$      FAT        6      1      5

Services:

   [Running]    Alerter

   [Running]    Computer Browser

   [Stopped]    ClipBook Server

   [Running]    DHCP Client

   [Running]    EventLog

   [Running]    Server

   [Running]    Workstation

   [Running]    License Logging Service

   [Running]    TCP/IP NetBIOS Helper

   [Running]    Messenger

   [Stopped]    Network DDE

   [Stopped]    Network DDE DSDM

   [Running]    Net Logon

   [Running]    NT LM Security Support Provider

   [Running]    Plug and Play

   [Stopped]    Directory Replicator

   [Stopped]    Remote Procedure Call (RPC) Locator

   [Running]    Remote Procedure Call (RPC) Service

   [Stopped]    Schedule

   [Running]    Spooler

   [Stopped]    Telephony Service

   [Stopped]    UPS

Network Card [0]: Intel EtherExpress PRO Ethernet Adapter

Protocol[0]: [NET0] WINS Client(TCP/IP) 4.0

System Up Time: 186 Hr 36 Min  9 Sec


SRVINSTW.EXE: Service Installer Wizard
  Computer Administration/Configuration Tools

SRVINSTW.EXE: Service Installation Wizard

Run SNMP Monitor now.

Service Installation Wizard provides an easy method of installing or deleting services and device drivers. It can connect to and configure services on both local and remote computers.

To run SRVINSTW, you must have administrative privileges. The user must have Administrator privileges on the target computer to successfully configure services. All file and directory paths should be relative to the target computer when configuring services on remotecomputers.

Caution	Use extreme care when deleting services and device drivers. Removal of certain services can cause your system and applications to become unstable or unusable.

A command-line application, Service Installer (INSTSRV.EXE), is also available in the Windows NT Resource Kit to install services on the local computer.

Related topics

Files required


File required for Service Installer Wizard

SRVINSTW.EXE


SU.EXE
User Account Administration Tools

SU.EXE

Run SU.EXE now.

SU lets you start a process running as an arbitrary user. It is named after the SU (Switch Users) utility of the UNIX family of operating systems.

To start a process in this way, you must have the correct password and domain, along with the username, of the arbitrary user. The new process will then run in the security context of the specified user.

The new process will start with an environment block representing the per-user environment variables that Windows NT maintains. In the new process, The Registry hive representing the target user, accessed through the HKEY_CURRENT_USER Registry key, will be available. Both of these behaviors can be disabled.

The caller of this application needs the following privileges:

SeTcbPrivilege "Act as part of the operating system"

SeIncreateQuotaPrivilege "Increase Quotas"

SeAssignPrimaryTokenPrivilege "Replace a process level token"

SeRestorePrivilege "Restore files and directories" (required only for user Registry hive preparation)

By default, only the Local System account has the SeTcbPrivilege and SeAssignPrimaryTokenPrivilege. You will therefore need to grant the above privileges to the user accounts/groups which are authorized to execute SU. These privileges can be granted via User Manager (part of the Windows NT operating system): on the Policies menu, click User Rights, then click Show Advanced User Rights. Privileges granted in this way will take affect when the user who was granted them logs on.

For more information

Open SU.TXT now.

Files required


File required for SU

SU.EXE

SU.TXT


SYSDIFF.EXE
Computer and Network Setup Tools

SYSDIFF.EXE

This utility enables you to pre-install applications, including those that do not support scripted installation, as part of an automated setup.

With SYSDIFF, you first create a "snapshot" of Windows NT Workstation after it has been installed on a reference computer. Then, you install the desired applications on the reference computer and create a difference file with information on the applications. Finally, you apply the difference file to new installations on other computers, as part of an unattended setup or at any later time after installation is complete.

If many applications must be installed, the difference file can become unmanageably large, as it contains the files and settings for all the applications. In this case, SYSDIFF allows you to create an information (.INF) file, containing only Registry and initialization file directives, from the difference file and use this to install the applications.

SYSDIFF also enables you to view the difference file in a readable format.

For more information

Open SYSDIFF Help now.

Related topics

Files required


Files required for SYSDIFF

SYSDIFF.EXE

SYSDIFF.HLP


TDISHOW.EXE: TDI Tracing Utility
Network Diagnostic Tools

TDISHOW.EXE: TDI Tracing Utility

Use the TDI Tracing Utility to collect and display the contents of packets being sent across the Transport Driver Interface (TDI) layer, which is the interface between the Windows NT operating system and the network.

Generally, you'll need to use the TDI Tracing Utility only if instructed to do so by Product Support Services.

TDI Tracing Utility topics

To install the TDITRACE driver

To use the TDI Tracing Utility

To save TDI tracing information

TDISHOW syntax

Files required


Files required for the TDI Tracing Utility

The files for the TDI Tracing Utility are installed by the Resource Kit in the %NTRESKIT%\TDITRACE folder.

OEMSETUP.INF

TDISHOW.EXE

TDITRACE.SYS


TDISHOW.EXE: TDI Tracing Utility

To install the TDITRACE driver

To use the TDI Tracing Utility

To save TDI tracing information

TDISHOW syntax


TDISHOW.EXE: To install the TDITRACE driver
TDISHOW.EXE: TDI Tracing Utility

To install the TDITRACE driver

You must have already installed the Windows NT Resource Kit onto the computer being traced.

Open Control Panel now.

1	In Control Panel, double-click the Network icon.

2	Click the Protocols tab

3	Click the Add button

4	Click Have Disk

5	Type the name of the drive and path containing TDITRACE.SYS and OEMSETUP.INF, and click OK.

The driver will be installed.

6	Reboot thecomputer.

The computer must be rebooted before the utility will function.


TDISHOW.EXE: To use the TDI Tracing Utility
TDISHOW.EXE: TDI Tracing Utility

To use the TDI Tracing Utility	  Open Command Prompt now.

1	At the command prompt, type tdishow.

The TDISHOW main menu appears, containing five options.

2	To capture TDI information from the TDITRACE buffer, type 1.

3	To display the TDI information on the monitor, type 2. Then in the resulting menu, choose the level of detail you want displayed.

4	To save the captured information to a file, type 3 and follow the instructions. For more detailed instructions, see To save TDI tracing information.

5	To clear and reset the TDITRACE buffer so that you can capture new information, type 4.

6	Repeat steps 2-5 as necessary.

7	When finished, type 5 to exit TDISHOW.


TDISHOW.EXE: To save TDI tracing information
TDISHOW.EXE: TDI Tracing Utility

To save TDI tracing information

Choosing 3 from the TDISHOW main menu (see To use the TDI Tracing Utility) displays these instructions:

"Turn ON Quick Editing and use CUT & PASTE to save this info"

The following procedure explains how to do this in more detail.

1	Click the Control-menu box of the command-prompt window in which you are running TDISHOW. The Control-menu box is the small square box containing a white bar in the upper-left corner of the window, next to the title bar.

2	From the window menu, choose Properties...

The "Command Prompt" Properties dialog box opens.

3	On the General Settings tab, check the QuickEdit Mode box. In the Apply Properties dialog box, choose either option according to your needs.

You can now use the mouse to select blocks of text displayed on the screen.

4	Select the text you want to save.

5	From the Control Menu, choose Edit and then choose Copy.

The text you marked is saved to the Clipboard. You can now paste this data into another application, such as Notepad, and save it to a file.


TDISHOW.EXE: TDISHOW syntax
TDISHOW.EXE: TDI Tracing Utility

TDISHOW syntax	  Open Command Prompt now.

TDISHOW version 2.0 captures and displays information in the TDITRACE buffer.

tdishow [/h] [/?] [/d] [/l:n] [/r]

Where

tdishow

without switches, runs TDISHOW in the interactive mode.

/h or /?

prints TDISHOW help.

/d

captures and displays information in the TDITRACE buffer.

/l:n

specifies the level of details: n can be 1, 2, or 3.

/r

resets the TDITRACE buffer.


Telnet Server
Internet and TCP/IP Services/Tools

TELNETD.EXE: Telnet Server Beta

Telnet Server has two components: the service itself (TELNETD.EXE) and an underlying component, the Remote Session Manager (RSM.EXE).

The Telnet Server service operates by connecting to the Remote Session Manager component.

Remote Session Manager (RSM) is responsible for initiating, terminating, and managing the character-oriented remote telnet session on a given system. RSM affects only the services provided in the Telnet Server service; it does not affect Microsoft's Remote Access Service (RAS), or other layered products.

Telnet Server Beta topics

Limitations of Telnet sessions

Telnet security

For more information

Open TELNET.WRI now.

Related topics

Files required


Files required for Telnet Server Beta

For a list of files for Telnet Server Beta, see TELNET.WRI.

Open TELNET.WRI now.


Telnet Server Service

Limitations of Telnet sessions

Telnet security


Limitations of Telnet sessions
Telnet Server

Limitations of Telnet sessions

The Windows NT Resource Kit 4.0 Telnet Server Beta provides a solution for running command-line utilities, scripts and batch-files from OS-independent clients. It is not intended to be a full commercial-grade Telnet solution.

Telnet Server Beta supports remote, character-based sessions, while Windows NT 4.0 is designed primarily to support graphics-based applications. This has imposed some constraints on remote session support in the Telnet Server service.

The only sure way to determine whether an application can successfully be run via a Telnet session is to test it.

In most cases, graphical applications cannot even be started successfully from within a remote session. Applications that do manage to start, create a window on the desktop of the host computer. This situation is rather disconcerting to any local user on that computer.

Applications that run properly in a remote textual session, but that also occasionally display warnings or messages in graphical dialog boxes, will not be able to display those warnings and messages. Some applications compensate for this correctly.

The number of Telnet connections is no longer limited by the Telnet Server service (although it might be constrained by memory, disk space, or other factors).


Telnet security
Telnet Server

Telnet security

Telnet sessions are conducted in the clear. This means that if a user uses Telnet to connect from computer A to computer B, a user on computer C on the same network segment might be able to capture information transmitted during the session and obtain user names, passwords, and other information.

If all the users on the segment normally share data on the computer, this is a negligible risk. However, it is still a risk and should be considered when using Telnet.


TEXTVIEW.EXE: TextViewer
File Tools

TEXTVIEW.EXE: TextViewer

Run TextViewer now.

TextViewer provides a graphical interface for quickly viewing text files on local or shared drives. While it provides basic editing and searching capabilities, it is primarily intended for viewing similar files within multiple sub-folders.

For example, TextViewer could be used for skimming through all the *.TXT files within the Windows NT Resource Kit or all the source files (*.C; *.CPP; *.CXX) within the Software Developers Kit.

Against an image of a local or shared drive, the utility displays all of the "files of interest," based on a default or user-entered file mask. To select files for viewing, you double-click them.

Files required


File required for TextViewer

TEXTVIEW.EXE


TIMEOUT.EXE
Batch Tools

TIMEOUT.EXE

TIMEOUT.EXE is a command-line utility that causes the command processor to pause execution for the number of seconds specified by the time (#) parameter, after which it continues without requiring a user keystroke. A user keystroke, however, will cause execution to resume immediately even if the timeout period has not expired.

The functioning of TIMEOUT is similar to that of the MS-DOS PAUSE command merged with SLEEP.EXE. TIMEOUT is typically used in batch files.

TIMEOUT topic

TIMEOUT syntax

Related topics

Files required


File required for TIMEOUT

TIMEOUT.EXE


TIMEOUT syntax
TIMEOUT.EXE

TIMEOUT syntax	  Open Command Prompt now.

timeout #

Where:

#

Specifies the decimal number of seconds (between -1 and 100000) to wait before continuing.

The value -1 causes the computer to wait indefinitely for a keystroke. This value makes TIMEOUT function identically to the PAUSE command.

Running timeout without any parameter displays a brief description of usage.


TIMESERV.EXE: Time Synchronizing Service
  Computer Administration/Configuration Tools

TIMESERV.EXE: Time Synchronizing Service

Server only	Included in the Windows NT Server, but not Workstation, Resource Kit.

This service sets the system time accurately and keeps Windows NT workstations and servers synchronized with a primary or secondary timesource that you specify. TIMESERV always keeps the computer in sync, even when no one is logged on. The service can be run from either the Services Control Panel or the command prompt.

A primary timesource is one that provides the highest accuracy, such as a GPS-based board, NIST ACTS, or a radio clock. A secondary timesource is one that is set from a primary timesource, typically over a network. Typical clients set themselves from a secondary timesource by using the NET TIME command or its equivalent in TIMESERV. For convenience, you can set the LanmanServer timesource by typing timesource=yes in the TIMESERV.INI file.

Time Synchronizing Service works with Windows NT 3.5 or later.

Time Synchronizing Service topics

To install Time Synchronizing Service

To edit TIMESERV.INI

To run TIMESERV.EXE

For more information

Open TIMESERV.WRI now.

Files required


Files required for Time Synchronizing Service

TIMESERV.EXE

TIMESERV.INI

TIMESERV.DLL

TIMESERV.WRI


TIMESERV.EXE: Time Synchronizing Service

To install Time Synchronizing Service

To edit TIMESERV.INI

To run TIMESERV.EXE


To install Time Synchronizing Service
TIMESERV.EXE: Time Synchronizing Service

To install Time Synchronizing Service

1	Copy the TIMESERV.EXE and TIMESERV.DLL files to the %SYSTEMROOT%\SYSTEM32 folder.

2	Copy the TIMESERV.INI file to the %SYSTEMROOT% folder.

3	Edit the TIMESERV.INI file to configure TIMESERV.

After making changes in the .INI file, you must run timeserv -update from the command prompt. The next time you restart the service (or reboot), it will use the new settings.

Open Command Prompt now.

4	At the command prompt, type:

timeserv -automatic

or

timeserv -manual

depending on how you want the service to start. This must be done to complete the installation process. You must be logged on with administrator privileges to do this.


To edit TIMESERV.INI
TIMESERV.EXE: Time Synchronizing Service

To edit TIMESERV.INI

You edit the TIMESERV.INI file by removing the remark symbol (;) from the lines you want to enable and adding it to the beginning of lines you want to disable.

After making changes in the .INI file, you must run timeserv -update from the command prompt. The next time you restart the service (or reboot), it will use the new settings.

This topic gives fuller descriptions of the types of time syncing than those found in the TIMESERV.INI remarks. For descriptions of the other settings in TIMESERV.INI, open TIMESERV.INI in any text editor and read the remarks.

Open TIMESERV.INI now.

TIMESERV.WRI contains more extended descriptions of the following types and of other supported types of time sources, along with other technical information on Time Synchronizing Service.

Open TIMESERV.WRI now.

Descriptions of types in TIMESERV.INI

PRIMARY

SECONDARY

NIST ACTS

USNO

INTERNET

NTP

NRC

BBC

COMPUTIME

EUROPE

MSL

SPECTRACOM


Primary type
Editing TIMESERV.INI

Primary

A mode of operation that obtains the time from any server specified in the PrimarySource list by using the "NetRemoteTOD" feature of Microsoft LAN API.


Secondary type
Editing TIMESERV.INI

Secondary

A mode of operation that obtains the time from any "TimeSource" in the current domain/workgroup (or specified Secondary Domain).


NIST ACTS type
Editing TIMESERV.INI

NIST ACTS

A service from the National Institute of Standards and Technology operated from Boulder, Colorado.

A modem answers at 300 bps, 1200 bps, or higher, and supplies UTC in ASCII. Measurements can be made of line delay so that the "On Time Marker" arrives within 10 ms (typically it is more accurate, and will be +/-2 ms relative time when using the same modem). The call is typically long distance and less than 30 seconds. These specifications are for 1200 bps, but 300 bps may yield +/-1 ms absolute.


USNO type
Editing TIMESERV.INI

USNO

A service of the U.S. Naval Observatory. It operates only at 1200 bps, and requires a modem with Remote Digital Loopback (RDL) features using &T6 and related AT commands. The service is located in Washington, D.C.; if that is a local call for you, it would make sense to try USNO.


Internet type
Editing TIMESERV.INI

Internet

An alternative way to access USNO and NIST. It uses TCP/IP and doesn't include a proper delay measurement. See also NTP, another Internet type.


NTP type
Editing TIMESERV.INI

NTP

NTP is the Network Time Protocol, which uses IP, usually over the Internet. TIMESERV uses only a Simple adaptation of NTP, which should not be confused with the more accurate and reliable full NTP. An NTP server must be specified (there is no default). See also Internet type.


NRC type
Editing TIMESERV.INI

NRC

A service of the National Research Council Canada INMS. It only operates at 300 bps, and supports propagation delay measurement. The location is Ottawa (it would make sense to try NRC if that is a local call for you).


BBC type
Editing TIMESERV.INI

BBC

The British Broadcasting Company Radio Time Standard Dial-in Time Service over PSDN. It operates only at 300 bps, and supports propagation delay measurement. The call is a Premium Rate service (British Telecom Callstream). The telephone number specified should be for the UTC Leitch Clock System Controller (not the UK TOD number); otherwise, a one-hour error will occur in summer. The source for the Controller includes MSF (Nat.Phys.Lab.) and GPS receivers.


Computime type
Editing TIMESERV.INI

Computime

Telstra's (Australia) dial-up time service over PSTN. It operates only at 1200 bps and does not support propagation delay measurement.

Note:	You must choose a PSTN number that matches your state, because local time and date are used (rather than UTC). This means that the time set will be many hours off if you call from a country such as the U.S.A.


Europe type
Editing TIMESERV.INI

Europe

A name for the common format used by services such as Sweden's Precision Time, Austria's TUG, Germany's PTB, and Italy's IEN. They operate at 1200 bps, and propagation delay measurement is not done for Italy. The locations are Sweden, Austria, Germany, and Torino, Italy (it would make sense to try EUROPE if that is a local call for you). Note that Italy's number is user-paid-service and Sweden's number is a premium number (they can only be dialed from within their country).


MSL (New Zealand) type
Editing TIMESERV.INI

MSL

MSL is New Zealand Measurement Standards Laboratory computer time setting service. It operates at 1200bps and propagation delay measurement is not done. The call is an 0900 service and therefore costs around $1.50 incl. of GST (it can only be dialed from within New Zealand).


SPECTRACOM type
Editing TIMESERV.INI

SPECTRACOM

Spectracom Corporation's (East Rochester, NY) NETCLOCK/2 is a WWVB radio receiver clock that supplies time code in ASCII format with +/-3 ms accuracy. Although not tested, the older Model 8170 clock and newer NETCLOCK/GPS should be compatible.


To run TIMESERV.EXE
TIMESERV.EXE: Time Synchronizing Service

To run TIMESERV.EXE

Open Control Panel now.

1	In Control Panel, use the Services application to start or stop TIMESERV, or change the startup type (automatic or manual).

2	Use the Application Log in Event Viewer to view any error or informational events from TIMESERV (errors typically mean that the service has stopped).


TIMETHIS.EXE: TimeThis
Computer Diagnostic Tools

TIMETHIS.EXE: TimeThis

TimeThis times how long it takes the system to execute a given command.

You provide as a parameter the name of the command you want executed and timed. TimeThis executes the specified command, then reports when command execution started and finished, and how long it took to run, in HH:MM:SS.TTT format.

TimeThis is useful for determining the start, end, and elapsed execution times of any command. It is easy to use interactively, and can also be used to time commands in .BAT or .CMD files—simply prefix the command(s) you wish to time with the TIMETHIS command.

TimeThis topics

TimeThis syntax

Example: timing a DIR command

For more information

For brief usage instructions, run TIMETHIS without arguments.

Files required


File required for TimeThis

TIMETHIS.EXE


TIMETHIS.EXE: TimeThis

TimeThis syntax

Example: timing a DIR command


TimeThis
TIMETHIS.EXE: TimeThis

TimeThis syntax	  Open Command Prompt now.

timethis commandname

Where:

commandname

specifies the name of the command you want executed and timed.

You can also specify the arguments for the command. For example:

timethis   net  use  x:  \\server\share  /user:billybob

will run net  use  x:  \\server\share  /user:billybob and report how long it took.

Quotes around the command are required when the command involves redirection via <, >, >>, or |, etc. Quotes ensure that the redirection is applied to the command being timed, rather than the TIMETHIS command itself. For example:

timethis "dir > dirlist.txt"


TimeThis example: timing a DIR command
TIMETHIS.EXE: TimeThis

Example: timing a DIR command

This command:

c:\>timethis dir c:\users\default\temp

produces this output (lines in boldface type are TIMETHIS output):

TimeThis :  Command Line :  DIR C:\USERS\DEFAULT\TEMP

TimeThis :    Start Time :  Thu Aug 03 11:23:22 1995

   Volume in drive C has no label.

   Volume Serial Number is 8C25-C783

   Folder of C:\USERS\DEFAULT\TEMP

03/08/95  11:04         <DIR>          .

03/08/95  11:04         <DIR>          ..

20/03/95  12:31                 54,717 BIGLMH

20/03/95  14:57                 55,801 HOSTS

20/03/95  14:57                 55,801 LMHOSTS

17/03/95  05:10                 24,274 LMHOSTS.000

               6 File(s)        190,593 bytes

                               39,556,096 bytes free

TimeThis :  Command Line :  DIR C:\USERS\DEFAULT\TEMP

TimeThis :    Start Time :  Thu Aug 03 11:23:22 1995

TimeThis :      End Time :  Thu Aug 03 11:23:23 1995

TimeThis :  Elapsed Time :  00:00:00.972

C:\>


TIMEZONE.EXE
Computer Administration/Configuration Tools

TIMEZONE.EXE

This command-line utility updates the daylight savings information for a timezone in the Registry. In some countries, the start and end of daylight savings time are changed every year, and there is no fixed start and/or end date.

This tool works on Windows NT and Windows 95.

Files required


File required for TIMEZONE

TIMEZONE.EXE


TLIST.EXE: Task List Viewer
Computer Diagnostic Tools

TLIST.EXE: Task List Viewer

The Task List Viewer is a command-line utility that displays a list of tasks, or processes, currently running on the local computer. For each process, it shows the process ID number, process name, and, if the process has a window, the title of that window.

TLIST works much like PULIST, but the latter can also enumerate an owner for processes on a local computer.

Task List Viewer topics

TLIST syntax

Example of TLIST output

Related topics

Files required


File required for Task List Viewer

TLIST.EXE


TLIST.EXE: Task List Viewer

TLIST syntax

Example of TLIST output


TLIST syntax
TLIST.EXE: Task List Viewer

TLIST syntax	  Open Command Prompt now.

tlist [/t]

Where:

/t

specifies that the output is to be displayed based on which processes are children/parents of which other processes.

Once you have used TLIST.EXE to find the processes running on your computer, you can end one or more of those processes by using KILL.EXE: Task Killing Utility.


Example of TLIST output
TLIST.EXE: Task List Viewer

Example of TLIST output

The following is an example of output from running tlist without the /t option. For each process, the process ID, process name, and window title (if any) are shown.

   0 System Process

  15 System

  29 smss.exe

  22 csrss.exe

  17 winlogon.exe

  42 services.exe

  40 lsass.exe

  57 spoolss.exe

  85 tcpsvcs.exe

 111 LOCATOR.EXE

 102 RPCSS.EXE

  37 nddeagnt.exe      NetDDE Agent

  78 progman.exe       Task List

  92 CMD.EXE           Command Prompt - tlist

  49 ntvdm.exe         Microsoft Word - Document2

 115 scm.exe

 138 INVWIN32.EXE

 135 PCMSVC32.EXE

 142 SMS.EXE           Microsoft SMS Administrator

 158 tlist.exe


TLOCMGR.EXE: Telephony Location Manager
Computer Administration/Configuration Tools

TLOCMGR.EXE: Telephony Location Manager

Run Telephony Location Manager now.

Telephony Location Manager was written for laptop computer users who use telephone applications, such as Dial-Up Networking, from several locations. It is useful for anyone who changes Telephony API (TAPI) locations—for example, taking a laptop from the office to home, where the computer no longer has to dial a "9" prefix. For a laptop user with a hot-docking setup, this utility will automatically change the TAPI location.

When you start Telephony Location Manager, an icon appears in your Taskbar notification area (near the clock).

A menu from this icon enables you to quickly:

change your current TAPI location (click the icon with the left mouse button).

bring up dialing properties (click with the right mouse button).

run Phone Dialer (click with the right mouse button).

Files required


File required for Telephony Location Manager

TLOCMGR.EXE


TOPDESK.EXE: Multiple Desktops
Desktop Tools

TOPDESK.EXE: Multiple Desktops

Run TopDesk now.

TopDesk provides a powerful way to switch between and organize applications while conserving screen space.

In TopDesk, you can use either the the keyboard or the mouse. In general, use the left mouse button to move objects and use the right mouse button to display pop-up menus that enable you to choose actions.

For more information

For online Help while working with TopDesk, press F1.

Open TopDesk Help now.

Related topics

Files required


Files required for TopDesk

TOPDESK.EXE

TOPDESK.HLP

TOPHOOK.DLL


TZEDIT.EXE: Time Zone Editor
Computer Administration/Configuration Tools

TZEDIT.EXE: Time Zone Editor

Run Time Zone Editor now.

The Windows NT Time Zone Editor can be used to create and edit time zone entries for the Date/Time icon in Control Panel.

To use Time Zone Editor

1	Click the Start button.

2	Point to Programs.

3	Point to Resource Kit 4.0.

4	Point to Configuration

5	Click Time Zone Editor.

6	Select a time zone and click the Edit button to edit a time zone, or click the New button to create a new time zone entry.

For online Help, click the Help button or press the F1 key.

For more information

Open Time Zone Editor Help now.

Files required


Files required for Time Zone Editor

TZEDIT.EXE

TZEDIT.HLP


UPTOMP.EXE: Uni to Multiprocessor Utility
Computer Administration/Configuration Tools

UPTOMP.EXE: Uni to Multiprocessor Utility

Run Uni to Multiprocessor Utility now.

The Uni to Multiprocessor Utility upgrades your operating system from single-processor to multiprocessor. Use UPTOMP only if more processors have been added to a single-processor computer after Windows NT was installed.

Note:	While this utility will run on any computer, you should use it only on multiprocessor computers.

Uni to Multiprocessor Utility topic

To use the Uni to Multiprocessor Utility

For more information

Open UPTOMP.TXT now.

Files required


Files required for the Uni to Multiprocessor Utility

UPTOMP.EXE

UPTOMP.INF

UPTOMP.TXT


To use the Uni to Multiprocessor Utility
UPTOMP.EXE: Uni to Multiprocessor Utility

To use the Uni to Multiprocessor Utility

Run Uni to Multiprocessor Utility now.

1	Click the Start button.

2	Point to Programs.

3	Point to Resource Kit 4.0.

4	Point to Configuration

5	Click Uni to Multiprocessor.

The Processor Upgrade Utility dialog box appears.

6	Make sure that the New HAL File Path box contains the path to the CD folder that matches the platform type of the computer.

7	From the HAL To Install box, select the appropriate HAL and click the OK button.

A confirmation dialog box appears.

8	Make sure that the path to the computer's folder containing the KERNEL.DLL, NTDLL.DLL, GDI32.DLL, and WINSRV.DLL files appears in the dialog box, and click the Continue button.

Another confirmation dialog box appears.

9	Click OK to upgrade the computer.

Once the computer has been upgraded, you should use the RDISK utility to create a new emergency repair disk for the computer with the new multiprocessor configuration.


USRSTAT.EXE
User Account Administration Tools

USRSTAT.EXE

Server only	Included in the Windows NT Server, but not Workstation, Resource Kit.

This command-line utility displays username, fullname, and last login date and time for each user in a given domain.

USRSTAT syntax

Open Command Prompt now.

usrstat domain [/?]

Where

domain

specifies the domain on which to enumerate users/servers.

/?

displays this usage description.

Files required


File required for USRSTAT

USRSTAT.EXE


USRTOGRP.EXE: Add Users to a Group
User Account Administration Tools

USRTOGRP.EXE: Add Users to a Group

The USRTOGRP utility adds users to a local or global group according to information in a user-specified input text file.

The USRTOGRP utility creates the specified group if it does not already exist. Then, for each user name specified in the file, it searches the specified computer or domain for the user account. If you are adding users to a local group, the utility also searches trusted domains for the user account. If you are adding users to a global group, the utility only searches the specified domain, not any trusted domains. Once the account is found, USRTOGRP adds the account to the group. Note that if the username exists in multiple domains, only the first instance of that username that USRTOGRP finds is added to the group.

USRTOGRP does not create user accounts. Each user specified in the text file you create must have an existing account. For global groups, users must have an account in the specified domain. For local groups, users must have an account on the local computer, the specified domain, or in a trusted domain. Only accounts that exist on your local computer will be used if your Windows NT Workstation computer is a member of a Workgroup rather than a Domain.

This utility is most beneficial when used in a trusted domain structure. It is useful for granting large numbers of users membership in a group, especially if you don't know in which trusted domain the user accounts are contained. The utility works on all Windows NT Workstation and Windows NT Server computers.

Note: You must be a member of the Administrators or Account Operators group in the specified computer or domain.

USRTOGRP topics

To add users to a group

USRTOGRP examples

Related Topics

Files required


File required for USRTOGRP

USRTOGRP.EXE


USRTOGRP.EXE: Add Users to a Group

To add users to a group

USRTOGRP examples


To add users to a group
USRTOGRP.EXE: Add Users to a Group

To add users to a group

1	Create a text file with the following format:

domain: domainname

localgroup(or globalgroup): groupname

User1

User2

User3

(etc...)

Open Command Prompt now.

2	At the command prompt, type:

usrtogrp filename

Where:

filename

is the text file you created in Step 1. If the file is not in the current folder, type the full path to the file.

For example:

c:\reskit> usrtogrp c:\public\tools\file.txt


USRTOGRP.EXE: Example
USRTOGRP.EXE: Add Users to a Group

USRTOGRP.EXE: Examples

A text file for adding users to a group on the local computer:

domain: localmachine

globalgroup: sms users

donbr

lauras

chrisdr

A text file for adding users to a group on the REDMOND domain:

domain: redmond

localgroup: Second level Administrators

jimp

donbr

lauras

anniep


VDESK.EXE
Desktop Tools

VDESK.EXE

Run VDESK.EXE now.

VDESK.EXE is a simple desktop switcher that enables you to maintain multiple desktops on a computer running Windows NT Workstation.

VDESK also provides a task manager to replace the default Task Manager program. VDESK's task manager displays the PID (process ID) of each task and also switches to new desktops if required.

With VDESK, users can also log on as another user, such as an administrator. This means that you can be logged on as a non-administrative user and be able to switch to a new desktop and perform administrative tasks.

For more information

Open VDESK.TXT now.

Related topics

Files required


File required for VDesk

VDESK.EXE

VDESK.TXT


Web Administration of Microsoft Windows NT Server
Internet and TCP/IP Services/Tools

Web Administration of Microsoft Windows NT Server

Server only	Included in the Windows NT Server, but not Workstation, Resource Kit.

This ISAPI DLL allows limited remote administration of Windows NT Server via HTML browsers (including Internet Explorer 2.0 and later) from Windows, Macintosh and UNIX platforms. The most recent version of Web Administration of Microsoft Windows NT Server is also available for download from the Microsoft World Wide Web site:

http://www.microsoft.com/

This tool does not replace existing administrative tools for Windows NT Server, but rather assists administrators when they do not have access to existing tools—for example, when they are away from their normal administrative workspace. This tool will be particularly useful for Windows NT administrators who are already experienced with the current administrative tools on Windows NT Server 3.51 and 4.0.

With Web Administration, "roaming" administrators can view performance and other server statistics and remotely manage:

user and group accounts

services and devices

event logs

printers

shares and sessions

To use Web Administration , the administrator navigates through a series of HTML pages with a Web browser.

Web Administration of Microsoft Windows NT Server topics

To install Web Administration of Microsoft Windows NT Server

To use Web Administration of Microsoft Windows NT Server

For more information

Once you have installed Web Administration of Microsoft Windows NT Server, you can click the following link:

Open the Web Administration of Microsoft Windows NT Server documentation (README.DOC) now.

Files required


Files required for Web Administration of Microsoft Windows NT Server

The files for this utility are contained in the \apps\webadmin folder on the Resource Kit CD.


Web Administration of Microsoft Windows NT Server

To install Web Administration of Microsoft Windows NT Server

To use Web Administration of Microsoft Windows NT Server


To install Web Administration of Microsoft Windows NT Server
Web Administration of Microsoft Windows NT Server

To install Web Administration of Microsoft Windows NT Server

Before installing this utility, Windows NT Server 4.0, Internet Information Server (IIS, included with Windows NT Server 4.0) and an HTML browser must already be installed on your computer. Web Administration is best viewed with Internet Explorer 3.0.

To download Internet Explorer 3.0 from the Microsoft home page, click the following link (you must have an Internet connection):

http://www.microsoft.com/ie/

1	Click the "Web Administration" button on the Windows NT Server Resource Kit Master Setup program.

The master setup program auto-launches when the Resource Kit CD is installed, or you can run MSETUP.EXE from the CD root directory.

or

Run SETUP.EXE from the \apps\webadmin folder on the Resource Kit CD.

This setup program installs all the files for the correct platform into two directories on your server, %inetsrv_root%\scripts\NTAdmin, %inetsrv_root%\wwwroot\NTAdmin, and makes the required Registry entries.

2	Configure Internet Information Server

a	Click Start, point to Programs, then Microsoft Internet Server, and click Internet Service Manager.

b	Make sure that the WWW service is running.

c	Configure Authentication on the Web server.

Web Administration requires that either "Basic", "NT Challenge Response," or both be enabled for Password Authentication in the WWW service.

To determine which IIS configurations will work for your configuration and browser, you must look at the Browser/Authentication matrix in the “Troubleshooting and Common Issues” section of the utility documentation (README.DOC).

If you have installed Web Administration of Microsoft Windows NT Server in the default directories, you can click the following link to:

Open the Web Administration of Microsoft Windows NT Server documentation (README.DOC) now.

See the IIS documentation for additional information on how to configure the WWW service.

For further instructions on installation, see the utility documentation (README.DOC).


To use Web Administration of Microsoft Windows NT Server
Web Administration of Microsoft Windows NT Server

To use Web Administration of Microsoft Windows NT Server

1	Make sure domain\username for your account is a member of the local Administrators group of the computer on which Web Administration is installed.

2	Type http://server_name/NTAdmin/NTAdmin.htm in the address line of your browser, where server_name is the name of your server on the World Wide Web or your Intranet. This URL is the home page of the tool. This tool is best viewed with Internet Explorer 3.0.

3	Select a link to an area of Windows NT administration:

Accounts

Users

Groups

Workstations

Devices

Event Logs

Maintenance

Broadcast message

Remote Console

Reboot Server

Web Administration Preferences

Printers

Services

Sessions

Shares

Shares

Files & Folders

Status

Server Configuration

Performance Counters

Server Statistics


WhoAmI
Batch Tools

WhoAmI

This command-line utility returns the username of the user who is currently logged on.

WhoAmI syntax

Open Command Prompt now.

whoami

The response is displayed in the format:

domain_or_computername\username

Files required


File required for WhoAmI

WHOAMI.EXE


WINLOGO.DOC: "Designed for Windows NT and Windows 95" Logo Handbook for Software Applications
Tools for Developers

"Designed for Windows NT and Windows 95" Logo Handbook for Software Applications

The “Designed for Windows NT and Windows 95 Logo Handbook for Software Applications” describes the technical requirements that must be satisfied by an application in order to receive the Designed for Windows NT and Windows 95 logo.

Developers of software applications can use the Logo Handbook as a guide for developing applications that are compatible with both Windows NT 4.0 and Windows 95.

End users can use this handbook to determine what Windows NT and Windows 95 “compatibility” means and what features to expect in an application that carries the Logo.

For more information

The Logo Handbook only describes the technical requirements that must be met in order to receive the Logo. To apply for the Logo, developers should refer to the complete application information located on:

http://www.microsoft.com/windows/thirdparty/winlogo/

If you have an Internet connection, you can click this link to go there now.

Files required


File required for "Designed for Windows NT and Windows 95" Logo Handbook for Software Applications

WINLOGO.DOC


WINAT.EXE: Command Scheduler
Computer Administration/Configuration Tools

WINAT.EXE: Command Scheduler

Run Command Scheduler now.

Command Scheduler can be used to schedule commands on a local or remote computer to occur once or regularly in the future. The Workstation service must be started to use this application.

The current AT commands for the local computer are displayed by default when Command Scheduler is started. The list of AT commands is automatically refreshed, so the display is always current. AT commands are displayed in a format similar to that of the command-line AT command.

You can run Command Scheduler from within Windows NT or from the command line.

Note	See the Command Reference in Windows NT Help for a full description of the AT command with notes and examples.

Command Scheduler topics

To use Command Scheduler

To run Command Scheduler from the command prompt

Security and the AT command

For more information

While working in Command Scheduler, press F1 for online Help, or:

Open Command Scheduler Help now.

Related topics

Files required


Files required for Command Scheduler

WINAT.EXE

WINAT.HLP


WINAT.EXE: Command Scheduler

To use Command Scheduler

To run Command Scheduler from the command prompt

Security and the AT command


To use Command Scheduler
WINAT.EXE: Command Scheduler

To use Command Scheduler

Run Command Scheduler now.

1	Click the Start button.

2	Point to Programs.

3	Point to Resource Kit 4.0.

4	Point to Configuration

5	Click Command Scheduler.

WinAT opens displaying the window for the local computer.

To view commands on a remote computer

1	On the File menu, click New.

2	Enter the name of the computer on which you wish to view AT commands.

For online Help, press F1 while working in Command Scheduler.


To run Command Scheduler from the command prompt
WINAT.EXE: Command Scheduler

To run Command Scheduler from the command prompt

Open Command Prompt now.

At the command prompt, type:

winat [\\computername]

Where

computername

is the name of another computer.

Note 1	If you want the command you are executing to work across a network, then the account the Schedule service is using must be able to work across that network. The System Account cannot access a network.

Note 2	If you want a command to access NTFS protected files, the account the Schedule service uses must have access to those files.


Security and the AT command
WINAT.EXE: Command Scheduler

Security and the AT command

Caution	AT jobs will NOT run under the security context of the user requesting it. Rather, they will run in whatever context the Schedule service is running, typically the operating system's context.

By default, only Administrators can submit commands with the AT utility. If you set the following Registry key value:

Hive:	HKEY_LOCAL_MACHINE

Key:	System\CurrentControlSet\Control\Lsa

Value:	Submit Control [REG_DWORD] 0x00000001

then System Operators will also be able to submit AT commands. There is no way to allow anyone else to submit AT commands.


WINDIFF.EXE: File and Directory Comparison
File Tools

WINDIFF.EXE: File and Directory Comparison

Run WINDIFF now.

WINDIFF shows the differences between specified ASCII text files or folders of ASCII text files. This is particularly useful for program source code.

The display either shows a summary of the comparison status of a list of files (outline mode) or a detailed line-by-line comparison of one of the files (expanded mode).

You can run WINDIFF like any other Windows-based application, using menu commands to choose files to compare and perform other actions. Or you can run WINDIFF from the command prompt with switches.

WINDIFF topics

Running WINDIFF with Menu Choices

File Menu

Edit Menu

Expand Menu

View Menu

Options Menu

Outline Mode Display

Expanded Mode Display

Running WINDIFF from the command-line

For more information

Open WINDIFF Help now.

Files required


Files required for WINDIFF

WINDIFF.EXE

WINDIFF.HLP

GUTILS.DLL


WINDIFF.EXE: File and Directory Comparison

Running WINDIFF with Menu Choices

File Menu

Edit Menu

Expand Menu

View Menu

Options Menu

Outline Mode Display

Expanded Mode Display

Running WINDIFF from the command-line


Running WinDiff with Menu Choices
WINDIFF.EXE: File and Directory Comparison

Running WINDIFF with Menu Choices

Run WINDIFF now.

To run WINDIFF using the menu

1	Click the Start button.

2	Point to Programs.

3	Point to Resource Kit 4.0.

4	Point to Desktop Tools.

5	Click File and Directory Comparison.

To compare two files with WINDIFF

1	On the File menu, click Compare Files.

2	In the Select First File dialog box, specify a filename for the first file in the comparison. Then select the other file to compare in the Select Second File dialog box.

To compare folders with WINDIFF

1	On the File menu, click Compare Directories.

2	In the Select Directories dialog box, specify two folder names and, if you want, check the Include Subdirectories check box.

WINDIFF menu topics

Menu Commands

Outline Mode View

Expanded Mode View


WINDIFF Menu Commands

File Menu

Edit Menu

View Menu

Expand Menu

Options Menu


WinDiff File Menu
WINDIFF.EXE: File and Directory Comparison

File Menu

Compare Files...

Displays a dialog box that allows you to select files to compare. It displays the standard Open File dialog box twice, once for each file.

Compare Directories

Displays a dialog box that allows you to select two folders to compare. UNC names are allowed. The names can be absolute paths or paths relative to the current folder. The Include Subdirectories check box determines whether the comparison will include the trees, starting from the given paths, or only the folders named.

Abort

Dimmed unless an operation is in progress, then allows that operation to be terminated before completion.

Save File List

Allows you to save the outline mode data in a file. During the file comparison, a checksum is calculated for each file (which is useful if the network is not working). These can be recorded together with the filenames, if required.

Copy Files...

Displays a dialog box for writing the listed files to a disk. WINDIFF can copy any combination of the four categories (identical, and so on). If greater selectivity is required, then save the file list (without checksums), and edit the file into a .BAT file to do the copying.

For a remote compare, this will compress the files before sending them across the network.

Print

Prints the file list or the expanded comparison.


Checksums in WINDIFF

For each file compared, a checksum is calculated. This is a 4-byte number derived from some combination of the values of all the bytes in the file in such a way that it is extremely unlikely that two files that are different will have the same checksum, while ensuring that files that are identical always have the same sum.

(The odds of two different files giving the same sum are about 1 in 4 billion, which is to say that you could compare 1 file a second for the next 100 years and only have about a 50/50 chance of seeing it happen.)


WinDiff Edit Menu
WINDIFF.EXE: File and Directory Comparison

Edit Menu

Edit Left File

Edit Right File

Edit Composite File

These commands allow a text editor to be invoked from WINDIFF. You can edit either the left file, the right file, or the merged file.

Set Editor

Allows you to select which editor is invoked.

%p

represents the path to edit (that is, the filename, which may be a name created by WINDIFF).

%l

represents the line number.

The default is

notepad %p

If you use the Slick editor, you should set this to

s %p -#%l


WinDiff Expand Menu
WINDIFF.EXE: File and Directory Comparison

Expand Menu

Left File Only

Shows only lines from left file (but colored to highlight changed lines).

Right File Only

Shows only lines from right file (but colored to highlight changed lines).

Both Files (default)

Shows a merge of both files. All the lines in the left file are shown in the order in which they occur in that file; the same is true for the right file. Lines that are only in the left file are shown in red. Lines that are only in the right file are shown in yellow.

Left Line Numbers (default)

Line numbers are shown, based on the left file.

Right Line Numbers

Line numbers are shown, based on the right file.

No Line Numbers

Line numbers are turned off.


WinDiff View Menu
WINDIFF.EXE: File and Directory Comparison

View Menu

Outline

Sets outline mode, showing lists of files.

Expand

Sets expanded mode, showing a comparison of two selected files.

Picture

Shows picture (turning the picture off saves space on the screen).

Previous Change

Skips to previous point of difference in the file.

Next change

Skips to next point of difference in the file.


WinDiff Options menu
WINDIFF.EXE: File and Directory Comparison

Options Menu

Ignore Blanks

Blanks are ignored in the expanded mode, so that lines that differ only in white space are shown as identical.

The next four options control which files (if any) are displayed in outline mode:

Show Identical Files

Includes files that are identical in each path.

Show Left-Only Files

Includes files that occur only in the left path.

Show Right-Only Files

Includes files that occur only in the right path.

Show Different Files

Includes files that occur in both paths, but that are not the same.


WinDiff Outline Mode Display
WINDIFF.EXE: File and Directory Comparison

Outline Mode Display

In outline mode, the display shows one file per line with the files listed in alphabetical order—except files contained in sub-folders appear after all files in higher folders. The paths shown are all relative to the root path given when the comparison is invoked.

For example, this command:

windiff c:\temp d:\progs\new

might show:

.\myfile.txt	identical

.\hisfile.txt	files differ

.\newest\myfile.txt	only in C:\TEMP

.\newest\x.x	only in D:\PROGS\NEW

.\oldest\file	identical

In this case, the full paths would be:

.\myfile.txt	c:\temp\myfile.txt and d:\progs\new\myfile.txt

.\hisfile.txt	c:\temp\hisfile.txt and d:\progs\new\hisfile.txt

.\newest\myfile.txt	c:\temp\newest\myfile.txt

.\newest\x.x	d:\progs\new\newest\x.x

.\oldest\file	c:\temp\oldest\file and d:\progs\new\oldest\file

The status of a file can be one of the following:

Identical

The files are identical, including white space.

Files Differ or Different Sizes

The two files differ, but possibly only in white space.

Only In path

The file exists only in one folder or the other, specified by path.

Files Differ? (Left Unreadable)

The file in the left path existed, but could not be read. There are many possible reasons. Some of the common ones are Network Error and Access Denied.

Files Differ? (Right Unreadable)

The file in the right path existed, but could not be read. The file in the left path was successfully read.

Unreadable files are treated as being different (highlighted in red, and so on).

The Options menu allows for files in any of the four categories to be either displayed or suppressed (that is, any of the 16 combinations). The categories are:

Identical

Differ (including unreadable)

Left only

Right only

Note:	A common source of puzzlement is a blank display caused by having only files in categories that are turned off from the Options menu. For example, all the files are identical, but identical files are not being displayed.


WinDiff Expanded Mode Display
WINDIFF.EXE: File and Directory Comparison

Expanded Mode Display

The left of the screen shows a pictorial view of the comparison. Blocks of color represent sections of the files. The left column of blocks represents the left-hand file, the right column represents the right-hand file.

Where blocks of lines match in the two files, these are shown as white blocks joined by a line connecting the block in each file. Lines that do not match are represented by a red block in the left file or a yellow block in the right file (with no connecting line).

The picture can be turned off by using the View menu.

Lines of text are displayed using the same colors. That is, lines that occur only in the left file are shown with a red background; lines that occur only in the right file are shown with a yellow background. Lines that are moved are shown with blue text against the appropriate background.

The Expand menu allows you to choose whether to look at the left file, the right file, or (the default) a merge of the two files. This merged file contains all the lines that are in either file in the order in which they occur in that file.

Lines that are common to the two files are normally shown only once. (Moved lines are shown twice: once with a red background showing where the line was in the left file, and once with a yellow background showing where the line is in the right file.)

Lines are numbered. The numbering can be turned off to save screen space or can be shown based on the left file or shown based on the right file by using the Expand menu.


Running WinDiff with Command-Line Switches
WINDIFF.EXE: File and Directory Comparison

Running WINDIFF from the command-line	  Open Command Prompt now.

windiff [paths] [saveoption]

Where:

paths

specifies path names for the comparison as a relative or absolute, network or local path to a folder or file, according to the following:

path compares what's at path with what's in the current folder.

path1 path2 compares what's at path1 with what's at path2.

saveoption

is -s {s | l | r | d} savefile

where {s | l | r | d} is any combination of these four letters to write the names of files that are:

s	the same in both paths

l	only in the left path

r	only in the right path

d	in both paths, but the two files are different

Colors

red background = left file

yellow background = right file

blue text = moved line

black text = everything else


WINEXIT.SCR: Windows Exit Screen Saver
Desktop Tools

WINEXIT.SCR: Windows Exit Screen Saver

Run Windows Exit Screen Saver now.

WINEXIT is a screen saver that logs the current user off after the specified time has elapsed. In other respects it is similar to other screen savers and can be configured and tested on the Screen Saver tab of the Display Properties dialog box in Control Panel.

WINEXIT displays a dialog box in which it displays the countdown timer and a user-defined message. When the countdown timer reaches zero, the logoff process is initiated.

Note	In order for non-administrators to be able to use WINEXIT, you must add Set Value and Create Subkey permissions for the group Everyone on the Registry key:

HKEY_Local_Machine\Software\Microsoft\WindowsNT\CurrentVersion.

WINEXIT topic

To activate WINEXIT

For more information

Open WINEXIT.HLP now.

Files required


Files required for WinExit

WINEXIT.SCR

WINEXIT.HLP


To activate WINEXIT
WINEXIT.SCR: Windows Exit Screen Saver

To activate WINEXIT

Open Control Panel now.

1	In Control Panel, double-click the Display icon.

2	On the Screen Saver tab, select Windows Exit from the Screen Saver list.

3	In the Wait box, select the number of minutes of inactivity before the screen saver appears.

4	To configure the screen saver, click the Settings button.

In the Force Logoff box, select the Force Application Termination checkbox to have the system close all running applications regardless of their current state.

By default, this checkbox is not selected and the system queries applications to see if work needs to be saved before shutting them down. Use this setting with caution since applications with unsaved data will not have a chance to save their work.

In the Time To Log Off box, enter the time WinExit will display its logoff dialog box before proceeding with the logoff process. Enter a value between 0 and 999 seconds.

In the Logoff Message box, enter a message to display in the logoff dialog box. The message is limited to 255 characters and will be truncated if extra characters are entered.

5	To start the screen saver temporarily so you can see what it looks like, click the Preview button. To return to Windows, move your mouse or press any key.

Note	You can now test Windows Exit screen saver with the Preview button on the Screen Saver tab without WINEXIT attempting to log you off.

When activated, WINEXIT beeps, indicating that the logoff process is about to begin, and displays the logoff dialog box. If no action is taken and the countdown timer reaches zero, the system will initiate the logoff procedure. You can abort the process before the countdown timer reaches zero by either moving the mouse pointer over the dialog box or pressing any key on the keyboard.


WinMSDp
Network Diagnostic Tools

WinMsdP

WinMsdP is a command-line version of WINMSD.EXE. It provides information about your system configuration and status.

WinMsdP reads the Windows NT Registry to gather information about your system. It then dumps this information to a text file named MSDRPT.TXT. The file is saved in your current folder. If a previous file already exists with this name, it will be renamed.

The main advantage of WinMsdP is that it can run from the command line without a graphical interface. The regular version of WINMSD.EXE can print to a file, but this requires a user interaction.

WinMsdP can be run from a Remote Command prompt like the one provided by RCMD.EXE or REMOTE.EXE. This allows users to run the utility over the network on remote systems, which is not possible with the standard version of WINMSD.EXE.

In addition, by using WinMsdP's command-line parameters, users can create automated batch files. These batch files can be run from the Windows NT AT.EXE Scheduling Service. This allows users to gather system information at regular intervals.

WinMsdP topic

WinMsdP syntax

Files required


File required for WinMSDp

WINMSDP.EXE


WinMsdP syntax
WinMsdP

WinMsdP syntax	  Open Command Prompt now.

winmsdp [/a] [/d] [/e] [/i] [/m] [/n] [/o] [/p] [/r] [/s] [/u] [/w] [/y] [/?]

Where each switch specifies one of the 12 different types of information that WinMsdP can provide. To dump all system information, use the /a switch.

Note:	Only one switch may be specified at a time.

/a

all settings

/d

drives

/e

environment

/i

interrupt resources

/m

memory

/n

network

/o

operating system version

/p

port resources

/r

drivers

/s

services

/u

DMA resources

/w

hardware

/y

memory resources

/?

command-line help


WINSCHK.EXE
Internet and TCP/IP Services/Tools

WINSCHK.EXE

This command-line utility checks name and version-number inconsistencies that may appear in Windows Internet Name Service (WINS) databases, monitors replication activity, and verifies the replication topology in an enterprise network. It is particularly useful for WINS administrators.

With WINSCHK, you can remotely check and resolve WINS database replication issues. You can isolate some of the most common problems that lead to database inconsistencies with an easy-to-use tool that can be run in a central location.

This tool supplements WINSCL with options geared towards flagging possible causes for database inconsistencies, such as:

1	asymmetric replication topologies

2	high communication failures (WINSCHK can detect these and warn the administrator)

The tool also helps monitor the actual replication activity by allowing the user to:

1	check for version number inconsistencies

2	check for the state of one or more names at various WINS databases in the network.

The tool can be used in interactive or non-interactive mode. In the latter, a log of all the tool activity is kept in the local directory (WINSTST.LOG). The option to monitor WINS activity can be run in the background, which dumps all logs into MONITOR.LOG.

For more information

The options supported by WINSCHK are detailed in WINSCHK.TXT.

Open WINSCHK.TXT now.

Related topics

Files required


Files required for WINSCHK

WINSCHK.EXE

WINSCHK.TXT


WINSCL.EXE
Internet and TCP/IP Services/Tools

WINSCL.EXE

Server only	Included in the Windows NT Server, but not Workstation, Resource Kit.

WINSCL is a command-line administrative tool for managing Windows Internet Name Service (WINS).

WINSCL can monitor WINS activities and examine WINS databases. It can also send commands to WINS to initiate an activity such as replication, scavenging, registering/querying a record, or doing backup/restore operations. The Windows NT 4.0 version adds a command to do consistency checking on the WINS database.

Note	This is potentially a high-overhead operation and a network-bandwidth hog, as it results in full replication of the entire database. It is best done when network activity is low.

Unlike WINS Manager, however, WINSCL cannot configure a WINS.

Note	If you attempt to delete a non-existent or incorrect name (for example, with lowercase letters that should be uppercase), WINSCL will return a status of SUCCESS even though the database was not modified since the parameter was incorrect. This could be misleading, as it may appear that the database has been correctly updated when in fact it was not.

For more information

The commands supported by WINSCL are detailed in WINSCL.TXT.

Open WINSCL.TXT now.

Related topics

Files required


Files required for WINSCL

WINSCL.EXE

WINSCL.TXT


WINSDMP.EXE
Internet and TCP/IP Services/Tools

WINSDMP.EXE

Server only	Included in the Windows NT Server, but not Workstation, Resource Kit.

WINSDMP is a command-line administrative tool that dumps all the records out of a WINS database and prints them to STDOUT in .CSV (comma-separated values) format.

You can use WINSDMP to do a complete listing of WINS records. Because the .CSV output is a form of text file, it can be easily parsed by other utilities and applications, such as word processors and spreadsheets. Microsoft Excel, for example, can load .CSV files directly.

WINSDMP topic

WINSDMP syntax

Related topics

Files required


Files required for WINSDMP

WINSDMP.EXE

WINSDB.DLL

WINSRPC.DLL


WINSDMP syntax
WINSDMP.EXE

WINSDMP syntax	  Open Command Prompt now.

winsdmp WINS_server [/?]

Where:

WINS_server

is either the IP address or the DNS name of the server.

WINSDMP will connect to that WINS server, loop through the owners in the database, and print out the records.

/?

displays command-line help.


WNTIPCFG.EXE: Graphical IPConfig Utility
Computer and Network Setup Tools

WNTIPCFG.EXE: Graphical IPConfig Utility

Run Graphical IPConfig Utility now.

WNTIPCFG is a graphical version of the IPConfig utility that is shipped with the Windows NT operating system. Use this utility to manage the Internet Protocol (IP) addresses and view IP information for computers that run the TCP/IP protocol.

Graphical IPConfig Utility topic

To use WNTIPCFG

Files required


File required for Graphical IPConfig Utility

WNTIPCFG.EXE


To use Graphical IPConfig Utility
WNTIPCFG.EXE: Graphical IPConfig Utility

To use Graphical IPConfig Utility

Run Graphical IPConfig Utility now.

1	Click the Start button.

2	Point to Programs.

3	Point to Resource Kit 4.0.

4	Point to Internet Utls.

5	Click Graphical IPConfig Utility.

A short dialog box appears, with a list of the adapters on your computer. The title bar of the dialog box shows the symbolic name of the currently selected adapter. For the selected adapter, the following IP-related information also appears:

Adapter Address: The MAC address of the network adapter card.

IP Address: The computer's IP address.

If the computer has more than one IP address (and corresponding subnet mask), a "..." button appears to the side of the IP address field. Choosing this button sequences through the computer's IP addresses, and the IP address and subnet mask fields are updated accordingly.

Subnet Mask: The computer's subnet mask.

Default Gateway: The default gateway for the computer.

6	Click the button for the task you want to perform.

OK

Release

Renew

Release All

Renew All

More Info


OK

Ends the utility.


Release

Releases the IP address lease of the currently selected adapter. This button is unavailable if the IP address for this is static, rather than assigned by a DHCP server.


Renew

Renews the IP address lease of the currently selected adapter. This button is unavailable if the IP address for this is static, rather than assigned by a DHCP server.


Release All

Releases the IP address leases of all the computer's adapters. This button is unavailable if the IP address for this is static, rather than assigned by a DHCP server.


Renew All

Renews the IP address leases of all the computer's adapters. This button is unavailable if the IP address for this is static, rather than assigned by a DHCP server.


More Info

Extends the dialog box to give more information. (Note that if you start the utility with the command wntipcfg /all, all of this information appears as soon as the utility starts.)

The additional information is as follows:

Host Name: The fully qualified hostname of this computer.

DNS Servers: A list of DNS servers used to resolve calls that use DNS names. If there is more than one DNS server in the list, a "..." button appears to the side. Choosing this button sequences through the list of DNS servers.

Node Type: The WINS node type. This can be Broadcast, Peer-Peer, Hybrid, or Mixed.

NetBIOS Scope Id: The NBT scope ID.

IP Routing Enabled: A check mark appears here if IP Routing is enabled.

WINS Proxy Enabled: A check mark appears here if WINS proxy is enabled.

NetBIOS Resolution Uses DNS: A check mark appears here if DNS is used for NetBIOS name resolution.

DHCP Server: The DHCP server that issued the IP address lease to this computer.

Primary WINS Server: The Primary WINS Server of this computer.

Secondary WINS Server: The Secondary WINS server for this computer.

Lease Obtained: When the current IP address lease was obtained.

Lease Expires: When the current IP address lease will expire.


Alphabetical List of Utilities

In the following list, some utilities are listed twice: once by their filename, once by their full name. The second listing by full name is in italics.

3DPAINT.EXE: Three-Dimensional Paint

- A -

Add Users to Groups (USRTOGRP.EXE)

ADDUSERS.EXE: AddUsers

ANIEDIT.EXE: Animated Cursor Creator

APIMON.EXE: API Monitor

AppleTalk network device ANaLYZeR (ATANLYZR.EXE)

Applications as Services Utility (SRVANY.EXE)

ASSOCIATE.EXE

ATANLYZR.EXE: AppleTalk network device ANaLYZeR

AUDITCAT.HLP: Audit Categories Help

AUTOEXNT.EXE: AutoExNT Service

AUTOLOG.EXE: Windows NT Auto Logon Setter

Automated Mirror Break/Restore Utility (BREAKFTM.EXE)

- B -

Batch File Wait (SLEEP.EXE)

BREAKFTM.EXE: Automated Mirror Break/Restore Utility

BROWMON.EXE: Browser Monitor

BROWSTAT.EXE: Browser Status

- C -

C2CONFIG.EXE: Windows NT C2 Configuration Manager

CLIP.EXE: Clip

CHOICE.EXE: Input from Batch Files

Command Scheduler (WINAT.EXE)

Command-line Service Controller (NETSVC.EXE)

COMPREG.EXE

COMPRESS.EXE: File Compress

CPU Usage by Processes (QSLICE.EXE)

Crystal Reports Event Log Viewer

- D -

dbWeb

DELPROF.EXE: User Profile Deletion Utility

DELSRV.EXE

"Designed for Windows NT and Windows 95" Logo Handbook (WINLOGO.DOC)

Desktop Themes for Windows NT 4.0

DESKTOPS.EXE: DeskTops

Device Driver Information (DRIVERS.EXE)

DFLYDIST.EXE: Compound File Layout User Tool

DH.EXE

DHCPCMD.EXE: DHCP Administrator's Tool

DHCPLOC.EXE: DHCP Server Locator Utility

DIRUSE.EXE: Directory Disk Usage

DISKMAP.EXE

DiskProbe (DSKPROBE.EXE)

DISKSAVE.EXE

DNSSTAT.EXE

DOMMON.EXE: Domain Monitor

DRIVERS.EXE: Device Driver Information

DSKPROBE.EXE: DiskProbe

DUMPEL.EXE: Dump Event Log

- E -

EM2MS.EXE

EMWAC Server CGI Gateway Scripts

Enhanced Network File-Copying Utility (ROBOCOPY.EXE)

Enumerating Remote Access Users (RASUSERS.EXE)

ENUMPRN.EXE

Event Logging Utility (LOGEVENT.EXE)

EXCTRLST.EXE: Extensible Performance Counter List

EXETYPE.EXE: Finding the Executable Type

EXPNDW32.EXE: File Expansion Utility

- F -

File Access Permissions per User (PERMS.EXE)

File and Directory Comparison (WINDIFF.EXE)

File Compress (COMPRESS.EXE)

File Copy with Security (SCOPY.EXE)

File Expansion Utility (EXPNDW32.EXE)

FINDGRP.EXE: Find Group

Finding the Executable Type (EXETYPE.EXE)

FLOPLOCK.EXE: Lock Floppy Disk Drives

FORFILES.EXE

FREEDISK.EXE

FTEDIT.EXE: FT Registry Information Editor

FTPCONF.EXE: FTP Configure

- G -

GETMAC.EXE

GETSID.EXE

GLOBAL.EXE

Graphical IPConfig Utility (WNTIPCFG.EXE)

GRPCPY.EXE: Group Copy

- H -

HCL40.HLP: Hardware Compatibility List

HEAPMON.EXE

- I -

IFMEMBER.EXE

IMAGEDIT.EXE: Image Editor

Index Server

INET.EXE

Input from Batch Files (CHOICE.EXE)

INSTALLD.CMD (NTDETECT.COM): Startup Hardware Detector

INSTSRV.EXE: Service Installer

- J -

No entries

- K -

KERNPROF.EXE: Kernel Profiler

KILL.EXE: Task Killing Utility

KIX32.EXE: KiXtart 95

- L -

LAYOUT.DLL

LOCAL.EXE

Lock Floppy Disk Drives (FLOPLOCK.EXE)

LOGEVENT.EXE: Event Logging Utility

Logon and FAT File System Settings (REGKEY.EXE)

LOGTIME.EXE

- M -

Mail Server

MIBCC.EXE: SNMP MIB Compiler

MONITOR.EXE: Performance Data Logging Service and Configuration Tool

MultiDesk (now DESKTOPS.EXE: DeskTops)

Multiple Desktops  (TOPDESK.EXE)

MUNGE.EXE

- N -

Near-Future Command Scheduler (SOON.EXE)

NETCLIP.EXE: Remote Clipboard Viewer

NETSVC.EXE: Command-line Service Controller

NetTime for Macintosh

NETWATCH.EXE: Net Watcher

NLMON.EXE

NLTEST.EXE

NOW.EXE: Now

NTCARD40.HLP: Windows NT Adapter Card Help

NTDETECT.COM (INSTALLD.CMD): Startup Hardware Detector

NTUUCODE.EXE: 32-Bit UUDecode and UUEncode Utility

- O -

OLEVIEW.EXE: OLE/COM Object Viewer

OS2API.TXT

- P -

Page Fault Monitor (PFMON.EXE)

PASSPROP.EXE

PATHMAN.EXE: Pathman

PERF2MIB.EXE: Performance Monitor MIB Builder Tool

PerfLog: Performance Data Log Service

PERFMTR.EXE: Performance Meter

Performance Data Logging Service and Configuration Tool (MONITOR.EXE)

Performance Data Log Service (PerfLog)

Performance Tools

Perl 5 Scripting Language

PERMCOPY.EXE

PERMS.EXE: File Access Permissions per User

PFMON.EXE: Page Fault Monitor

PMON.EXE: Process Resource Monitor

POLEDIT.EXE: Windows NT System Policy Editor

POSIX Utilities

Process and Thread Status (PSTAT.EXE)

Process Resource Monitor (PMON.EXE)

Process Viewer (PVIEWER.EXE)

PSTAT.EXE: Process and Thread Status

PULIST.EXE

PVIEWER.EXE: Process Viewer

- Q -

QSLICE.EXE: CPU Usage by Processes

QUICKRES.EXE: Quick Resolution Changer

- R -

RASLIST.EXE

RASUSERS.EXE: Enumerating Remote Access Users

RCMD.EXE: Remote Command Service

REGBACK.EXE: Registry Backup

REGCHG.EXE

REGDEL.EXE

REGENTRY.HLP: Windows NT Registry Entries

Regina REXX Scripting Language

REGINI.EXE: Registry Change by Script

REGKEY.EXE: Logon and FAT File System Settings

REGREAD.EXE

REGREST.EXE: Registry Restoration

REGSEC.EXE

Remote Access Manager

Remote Command Service (RCMD.EXE)

Remote Console

Remote Kill

Remote Shutdown (SHUTDOWN.EXE)

Remote Shutdown GUI (SHUTGUI.EXE)

REMOTE.EXE: Remote Command Line

RESTKEY.EXE

REXX (Regina) Scripting Language

RIPROUTE.WRI: Routing with Windows NT Server

RMTSHARE.EXE: Remote Share

ROBOCOPY.EXE: Enhanced Network File-Copying Utility

RREGCHG.EXE

RSHSVC.EXE: TCP/IP Remote Shell Service

- S -

SAVEKEY.EXE

SC.EXE

SCANREG.EXE

SCOPY.EXE: File Copy with Security

SCLIST.EXE

SECADD.EXE

SECEDIT.EXE

Service Installer (INSTSRV.EXE)

Service Installer Wizard (SRVINSTW.EXE)

SETUPMGR.EXE: Setup Manager

SETX.EXE

ShareUI

SHOWACLS.EXE

SHOWDISK.EXE

SHOWGRPS.EXE

SHOWMBRS.EXE

SHUTDOWN.EXE: Remote Shutdown

SHUTGUI.EXE: Remote Shutdown GUI

SLEEP.EXE: Batch File Wait

SNMP MIB Compiler (MIBCC.EXE)

SNMPMON.EXE: SNMP Monitor

SNMPUTIL.EXE: SNMP Browser

SOON.EXE: Near-Future Command Scheduler

SRVANY.EXE: Applications as Services Utility

SRVCHECK.EXE

SRVINFO.EXE

SRVINSTW.EXE: Service Installer Wizard

Startup Hardware Detector: NTDETECT.COM (INSTALLD.CMD)

SU.EXE

SYSDIFF.EXE

- T -

Task Killing Utility (KILL.EXE)

Task List Viewer (TLIST.EXE)

TCP/IP Remote Shell Service (RSHSVC.EXE)

TDISHOW.EXE: TDI Tracing Utility

Telephony Location Manager (TLOCMGR.EXE)

TELNETD.EXE: Telnet Server Beta

TEXTVIEW.EXE: TextViewer

Three-Dimensional Paint (3DPAINT.EXE)

Time Zone Editor (TZEDIT.EXE)

TIMEOUT.EXE

TIMESERV.EXE: Time Synchronizing Service

TIMETHIS.EXE: TimeThis

TIMEZONE.EXE

Time Synchronizing Service (TIMESERV.EXE)

TLIST.EXE: Task List Viewer

TLOCMGR.EXE: Telephony Location Manager

TOPDESK.EXE: Multiple Desktops

TZEDIT.EXE: Time Zone Editor

- U -

UPTOMP.EXE: Uni to Multiprocessor Upgrade Utility

User Profile Deletion Utility (DELPROF.EXE)

USRSTAT.EXE

USRTOGRP.EXE: Add Users to Groups

UUDecode and UUEncode Utility, 32-Bit (NTUUCODE.EXE)

- V -

VDESK.EXE

- W -

Web Administration of Microsoft Windows NT Server

WhoAmI

WINAT.EXE: Command Scheduler

WINDIFF.EXE: File and Directory Comparison

Windows Exit Screen Saver (WINEXIT.SCR)

Windows NT Adapter Card Help (NTCARD40.HLP)

Windows NT Auto Logon Setter (AUTOLOG.EXE)

Windows NT C2 Configuration Manager (C2CONFIG.EXE)

Windows NT Registry Entries (REGENTRY.HLP)

WINEXIT.SCR: Windows Exit Screen Saver

WINLOGO.DOC: "Designed for Windows NT and Windows 95" Logo Handbook

WinMsdP

WINSCHK.EXE

WINSCL.EXE

WINSDMP.EXE

WNTIPCFG.EXE: Graphical IPConfig Utility

- X -

No entries

- Y -

No entries

- Z -

No entries


Batch Tools

ASSOCIATE.EXE

AUTOEXNT.EXE: AutoExNT Service

CHOICE.EXE: Input from Batch Files

CLIP.EXE: Clip

FORFILES.EXE

KIX32.EXE: KiXtart 95

LOGTIME.EXE

MUNGE.EXE

NOW.EXE: Now

Perl 5 Scripting Language

Regina REXX Scripting Language

SETX.EXE

SLEEP.EXE: Batch File Wait

TIMEOUT.EXE

WhoAmI


Computer Administration/Configuration Tools

C2CONFIG.EXE: Windows NT C2 Configuration Manager

FLOPLOCK.EXE: Lock Floppy Disk Drives

FTEDIT.EXE: FT Registry Information Editor

INSTSRV.EXE: Service Installer

PATHMAN.EXE: Pathman

PERMS.EXE: File Access Permissions per User

POLEDIT.EXE: Windows NT System Policy Editor

SOON.EXE: Near-Future Command Scheduler

SC.EXE

SECEDIT.EXE

SRVANY.EXE: Applications as Services Utility

SRVINSTW.EXE: Service Installer Wizard

TIMESERV.EXE: Time Synchronizing Service

TIMEZONE.EXE

TLOCMGR.EXE: Telephony Location Manager

TZEDIT.EXE: Time Zone Editor

UPTOMP.EXE: Uni to Multiprocessor Upgrade Utility

WINAT.EXE: Command Scheduler


Computer and Network Setup Tools

HCL40.HLP: Hardware Compatibility List

NTCARD40.HLP: Windows NT Adapter Card Help

NTDETECT.COM (INSTALLD.CMD): Startup Hardware Detector

SETUPMGR.EXE: Setup Manager

SYSDIFF.EXE

WNTIPCFG.EXE: Graphical IPConfig Utility


Computer Diagnostic Tools

AUDITCAT.HLP: Audit Categories Help

Crystal Reports Event Log Viewer

DRIVERS.EXE: Device Driver Information

DUMPEL.EXE: Dump Event Log

ENUMPRN.EXE

EXCTRLST.EXE: Extensible Performance Counter List

FINDGRP.EXE: Find Group

GETMAC.EXE

KILL.EXE: Task Killing Utility

LOGEVENT.EXE: Event Logging Utility

MONITOR.EXE: Performance Data Logging Service and Configuration Tool

PERFMTR.EXE: Performance Meter

PerfLog: Performance Data Log Service

Performance Tools

PFMON.EXE: Page Fault Monitor

PMON.EXE: Process Resource Monitor

PSTAT.EXE: Process and Thread Status

PVIEWER.EXE: Process Viewer

QSLICE.EXE: CPU Usage by Processes

Remote Kill

SHOWACLS.EXE

TIMETHIS.EXE: TimeThis

TLIST.EXE: Task List Viewer


Desktop Tools

3DPAINT.EXE: Three-Dimensional Paint

ANIEDIT.EXE: Animated Cursor Creator

Desktop Themes for Windows NT 4.0

DESKTOPS.EXE: DeskTops

IMAGEDIT.EXE: Image Editor

LAYOUT.DLL

MultiDesk (now DESKTOPS.EXE: DeskTops)

QUICKRES.EXE: Quick Resolution Changer

TOPDESK.EXE: Multiple Desktops

VDESK.EXE

WINEXIT.SCR: Windows Exit Screen Saver


Disk/Fault Tolerance Tools

BREAKFTM.EXE: Automated Mirror Break/Restore Utility

DISKMAP.EXE

DISKSAVE.EXE

DSKPROBE.EXE: DiskProbe

FTEDIT.EXE: FT Registry Information Editor

SHOWDISK.EXE


File Tools

COMPRESS.EXE: File Compress

DIRUSE.EXE: Directory Disk Usage

DFLYDIST.EXE: Compound File Layout User Tool

EXETYPE.EXE: Finding the Executable Type

EXPNDW32.EXE: File Expansion Utility

FREEDISK.EXE

PERMCOPY.EXE

ROBOCOPY.EXE: Enhanced Network File-Copying Utility

TEXTVIEW.EXE: TextViewer

SCOPY.EXE: File Copy with Security

WINDIFF.EXE: File and Directory Comparison


Internet and TCP/IP Services Tools
Internet and TCP/IP Services/Tools

dbWeb

DHCPCMD.EXE: DHCP Administrator's Tool

DHCPLOC.EXE: DHCP Server Locator Utility

DNSSTAT.EXE

EM2MS.EXE

EMWAC Server CGI Gateway Scripts

FTPCONF.EXE: FTP Configure

Index Server

INET.EXE

Mail Server

NTUUCODE.EXE: 32-Bit UUDecode and UUEncode Utility

RIPROUTE.WRI: Routing with Windows NT Server

RSHSVC.EXE: TCP/IP Remote Shell Service

TELNETD.EXE: Telnet Server Beta

Web Administration of Microsoft Windows NT Server

WINSCHK.EXE

WINSCL.EXE

WINSDMP.EXE


Network Diagnostic Tools

ATANLYZR.EXE: AppleTalk network device ANaLYZeR

BROWMON.EXE: Browser Monitor

BROWSTAT.EXE: Browser Status

DOMMON.EXE: Domain Monitor

MIBCC.EXE: SNMP MIB Compiler

NETWATCH.EXE: Net Watcher

PERF2MIB.EXE: Performance Monitor MIB Builder Tool

SNMPMON.EXE: SNMP Monitor

SNMPUTIL.EXE: SNMP Browser

SRVINFO.EXE

TDISHOW.EXE: TDI Tracing Utility

WinMsdP


Network/Server Administration Tools

DH.EXE

KERNPROF.EXE: Kernel Profiler

NETCLIP.EXE: Remote Clipboard Viewer

NETSVC.EXE: Command-line Service Controller

NetTime for Macintosh

NLMON.EXE

NLTEST.EXE

PASSPROP.EXE

RASLIST.EXE

RASUSERS.EXE: Enumerating Remote Access Users

RCMD.EXE: Remote Command Service

Remote Access Manager

Remote Console

REMOTE.EXE: Remote Command Line

RMTSHARE.EXE: Remote Share

SCLIST.EXE

ShareUI

SHUTDOWN.EXE: Remote Shutdown

SHUTGUI.EXE: Remote Shutdown GUI


Registry Tools

COMPREG.EXE

DELSRV.EXE

REGBACK.EXE: Registry Backup

REGCHG.EXE

REGDEL.EXE

REGENTRY.HLP: Windows NT Registry Entries

REGINI.EXE: Registry Change by Script

REGKEY.EXE: Logon and FAT File System Settings

REGREAD.EXE

REGREST.EXE: Registry Restoration

REGSEC.EXE

RREGCHG.EXE

SAVEKEY.EXE

SCANREG.EXE

SECADD.EXE


Tools for Developers

APIMON.EXE: API Monitor

HEAPMON.EXE

OLEVIEW.EXE: OLE/COM Object Viewer

OS2API.TXT

POSIX Utilities

PULIST.EXE

WINLOGO.DOC: "Designed for Windows NT and Windows 95" Logo Handbook


User Account Administration Tools

ADDUSERS.EXE: AddUsers

AUTOLOG.EXE: Windows NT Auto Logon Setter

DELPROF.EXE: User Profile Deletion Utility

GETSID.EXE

GLOBAL.EXE

GRPCPY.EXE: Group Copy

IFMEMBER.EXE

LOCAL.EXE

SHOWGRPS.EXE

SHOWMBRS.EXE

SRVCHECK.EXE

SU.EXE

USRSTAT.EXE

USRTOGRP.EXE: Add Users to Groups


Copyright
Copyright Information

Information in this online document is subject to change without notice.

Companies, names, and data used in examples herein are fictitious unless otherwise noted. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Microsoft Corporation.

© 1985-1996 Microsoft Corporation. All rights reserved.

Microsoft is a registered trademark and Windows NT is a trademark of Microsoft Corporation.

Adaptec is a trademark of Adaptec Inc. Apple, AppleShare, LocalTalk, and Macintosh are registered trademarks and System 7 is a trademark of Apple Computer, Inc. Compaq is a registered trademark of Compaq Computer Corporation. DEC is a registered trademark of Digital Equipment Corporation. Everex is a trademark of Everex Systems, Inc. HP is a registered trademark of Hewlett-Packard Company. IBM and PS/2 are registered trademarks of International Business Machines Corporation. Intel is a registered trademark of Intel Corporation. Novell is a registered trademark of Novell, Inc. SMC is a registered trademark of Standard Microsystems Corporation. Toshiba is a registered trademark of Kabushiki Kaisha Toshiba. UngermanBass is a registered trademark of Ungermann-Bass, Inc.

The files for the Perl 5 scripting language, POSIX Utilities, and Regina REXX scripting language are the only files covered by the GNU Library General Public License. All other files are copyrighted by Microsoft Corporation or the respective owners, and are subject to the terms of a separate license agreement.


  Introductory Topics

Introduction

Disclaimer

New utilities

Updated utilities

Utilities included only in Windows NT Server Resource Kit

Resource Kit information on the Internet


Introduction
Introductory Topics

Introduction

This Help file presents an overview of the utilities available on the Windows NT Resource Kit CD. For more information on a particular tool, see the online Help or print documentation for that tool or the appropriate Resource Kit book.

Online and print cross-references are listed for many tools, and some topics include links (an icon and underlined green text) that allow you to open the tool's Help or documentation file or to run the tool. For these links to work properly, the Resource Kit must be installed on your computer. Links to utilities that require further installation are preceded by explanatory notes.

Some of these links are to Internet sites. To use these links, you must have have a World Wide Web browser (or in some cases a Gopher or FTP client) installed on your computer and an Internet connection. Windows NT 4.0 includes Internet Explorer, a World Wide Web browser which can connect to any World Wide Web, Gopher, or FTP link.

Finding the tool you need

Finding tools by name

Finding tools by category

Getting a menu with the right mouse button

Using the right-mouse-button menu

Understanding notation and terminology used in this document

The following conventions for usage and notation are observed in this document:

Procedural conventions

Notational conventions

Keyboard conventions

Terminology conventions

This Help file assumes that you are already familiar with Windows NT. For more general information about Windows NT, including keyboard equivalents to menu and mouse actions, see the Windows NT online Help.

Sending feedback on the Windows NT Resource Kit

Sending feedback


Introduction

Finding tools by name

Finding tools by category

Using the right-mouse-button menu

Procedural conventions

Notational conventions

Keyboard conventions

Terminology conventions

Sending feedback


Finding tools by name
Introduction

Finding tools by name

If you know the name of the tool you are looking for, you can look it up in the Alphabetical List. To open this list, double-click "Alphabetical List of Utilities" on the Contents tab, or click the A-Z List button on the button bar. You can also search for the name of the tool on the Index tab of the Help Topics window, which you can open by clicking the Index button on the button bar.


Finding tools by category
Introduction

Finding tools by category

If you are looking for a particular type of tool, double-click one of the categories of tools on the Contents tab. You can open the Contents tab of the Help Topics window by clicking the Contents button on the button bar.


Using the right-mouse-button menu
Introduction

Using the right-mouse-button menu

If you click the right mouse button in any Help window, a context menu pops up with commands useful in that particular location. Overview of Windows NT Resource Kit Tools adds three commands to this menu that enable you to open Explorer, Control Panel, and Registry Editor from any point in the Help file (but not in the opening Help Topics window).


Procedural Conventions
Introduction

Procedural conventions

Clicking this button  [image]  or the text that follows moves you directly into another Help topic.

Clicking this button  [image]  or the text that follows opens a pop-up window with links to other topics.

Procedures describing how to do a task are preceded by a triangular bullet  [image]  for a single step or numbers for multiple steps.

An instruction to "type" information means to press the key or keys and then press the ENTER key.

An instruction to "select" information means to highlight folders, filenames, text boxes, menu bars, and options, or to select options in a dialog box.

An instruction to "choose" something means to carry out a command from a menu or dialog box with mouse or keyboard actions.

"Note" alerts you to supplementary information.

"Caution" alerts you to possible data loss or breaches of security.


Notational Conventions
Introduction

Notational conventions

Convention	Meaning
bold	Characters that you type exactly as shown, including commands and switches. Menus and commands on them are also bolded.
italic	Variables for which you supply a specific value. For example, filename in a path name could refer to any valid filename for the case in question.
ALL CAPITALS	Names of paths, folders, files, and acronyms. Unless otherwise indicated, you can use uppercase or lowercase when you type paths, folders, or filenames.
Courier type	Examples of code.
[ ] (square brackets)	In syntax descriptions, square brackets enclose optional items. If you include the item, type only the information between them, not the square brackets themselves.
{choice1 | choice2} (braces)	In syntax descriptions, braces enclose items which require a choice, such as {yes | no}. Type only one of the choices, not the braces or the dividing line.
Menu | Command (menus)	In referring to menu choices, Edit | Paste, for example, means to select the Edit menu and then choose the Paste command from it.


Keyboard Conventions
Introduction

Keyboard conventions

Convention	Meaning
+  (a plus sign between two or more key names)	Indicates that you must press the keys at the same time; for example, ALT + TAB.
,   (a comma between two or more key names)	Indicates that you must press each key consecutively; for example, ALT, F, X.


Terminology Conventions
Introduction

Terminology conventions

"MS-DOS" refers to Microsoft MS-DOS.

"Command prompt" refers to the point on the MS-DOS screen where you enter commands, typically designated by "C:\>" (or other characters indicating the current drive and folder). To reach the command prompt in Windows NT 4.0, click Start, point to Programs and click MS-DOS Prompt.

"Command-line application" or "console-based application" refers to an application designed to run under MS-DOS or in an MS-DOS window, and which cannot run in a Windows or Windows NT window.

"Windows-based application" or "GUI application" refers to an application which must run in a Windows or Windows NT window. All such applications follow similar conventions for the arrangement of menus, dialog box styles, and keyboard and mouse use.

"%SYSTEMROOT%" refers to the folder in which Windows NT is installed.

"%NTRESKIT%" refers to the folder in which the Windows NT Resource Kit is installed.

"CD_drive:" refers to the drive letter for the CD-ROM drive, which may vary from computer to computer depending on what other hardware is installed.

"Tool" and "utility" are used synonymously to refer to application programs on the Windows NT Resource Kit CD.


Sending feedback
Introduction

Sending feedback

You can send feedback, comments, or bug reports for these tools, or for any Resource Kit documentation, by electronic mail to RKINPUT@MICROSOFT.COM on the Internet. If you have an Internet e-mail connection, you can click the following icon or text to send mail now:

mailto:rkinput@microsoft.com


Disclaimer
Introductory Topics

Disclaimer

Many of these tools were developed internally at Microsoft. Any use of any of these tools is at your own risk. These tools are provided "AS IS" without warranty of any kind. Microsoft disclaims any implied warranty of merchantability and/or fitness for a particular purpose.

These tools have NOT been localized: they are written and tested in English only. Using these tools with a different language version of Windows NT may produce unpredictable results.

Many of these tools are designed to work only if you logged on as a member of an Administrators group.


New utilities
Introductory Topics

New utilities

The following utilities are new for the Windows NT Server 4.0 and Windows NT Workstation 4.0 versions of the Resource Kits:

APIMON.EXE: API Monitor

ASSOCIATE.EXE

ATANLYZR.EXE: AppleTalk network device ANaLYZeR

BREAKFTM.EXE: Automated Mirror Break/Restore Utility

dbWeb

DELPROF.EXE: User Profile Deletion Utility

DELSRV.EXE

Desktop Themes for Windows NT 4.0

DESKTOPS.EXE: DeskTops

DFLYDIST.EXE: Compound File Layout User Tool

DH.EXE

DISKMAP.EXE

DNSSTAT.EXE

DSKPROBE.EXE: DiskProbe

EM2MS.EXE

ENUMPRN.EXE

EXCTRLST.EXE: Extensible Performance Counter List

FORFILES.EXE

FREEDISK.EXE

FTEDIT.EXE: FT Registry Information Editor

GLOBAL.EXE

GRPCPY.EXE: Group Copy

HEAPMON.EXE

Index Server

KERNPROF.EXE: Kernel Profiler

KIX32.EXE: KiXtart 95

LAYOUT.DLL

LOCAL.EXE

LOGTIME.EXE

MultiDesk (now DESKTOPS.EXE: DeskTops)

MUNGE.EXE

NETCLIP.EXE: Remote Clipboard Viewer

NetTime for Macintosh

NLMON.EXE

NLTEST.EXE

OLEVIEW.EXE: OLE/COM Object Viewer

PASSPROP.EXE

PATHMAN.EXE: Pathman

PerfLog: Performance Data Log Service

PERMCOPY.EXE

POLEDIT.EXE: Windows NT System Policy Editor

PULIST.EXE

QUICKRES.EXE: Quick Resolution Changer

RASLIST.EXE

REGCHG.EXE

REGDEL.EXE

REGREAD.EXE

REGSEC.EXE

Remote Access Manager

Remote Console

Remote Kill

RESTKEY.EXE

RIPROUTE.WRI: Routing with Windows NT Server

RREGCHG.EXE

SAVEKEY.EXE

SC.EXE

SCANREG.EXE

SCLIST.EXE

SECADD.EXE

SECEDIT.EXE

SETX.EXE

ShareUI

SHOWACLS.EXE

SHOWGRPS.EXE

SHOWMBRS.EXE

SRVCHECK.EXE

SRVINFO.EXE

SRVINSTW.EXE: Service Installer Wizard

SYSDIFF.EXE

TELNETD.EXE: Telnet Server Beta

TIMEZONE.EXE

TLOCMGR.EXE: Telephony Location Manager

USRSTAT.EXE

Web Administration of Microsoft Windows NT Server

WINLOGO.DOC: "Designed for Windows NT and Windows 95" Logo Handbook

WINSCHK.EXE


Updated utilities
Introductory Topics

Updated utilities

The following utilities (or in some cases their installation or configuration) have been updated for the Windows NT Server 4.0 and Windows NT Workstation 4.0 versions of the Resource Kits:

ADDUSERS.EXE: AddUsers

HCL40.HLP: Hardware Compatibility List

Mail Server

MIBCC.EXE: SNMP MIB Compiler

NTCARD40.HLP: Windows NT Adapter Card Help

PERF2MIB.EXE: Performance Monitor MIB Builder Tool

Performance Tools

Perl 5 Scripting Language

PFMON.EXE: Page Fault Monitor

POSIX Utilities

RASUSERS.EXE: Enumerating Remote Access Users

REGBACK.EXE: Registry Backup

REGENTRY.HLP: Windows NT Registry Entries

ROBOCOPY.EXE: Enhanced Network File-Copying Utility

SETUPMGR.EXE: Setup Manager

SU.EXE

TIMESERV.EXE: Time Synchronizing Service

WhoAmI

WINAT.EXE: Command Scheduler

WinMsdP

WINSCL.EXE


Utilities included only in Windows NT Server Resource Kit
Introductory Topics

Utilities included only in Windows NT Server Resource Kit

The following utilities are included in the Windows NT Server 4.0, but not the Windows NT Workstation 4.0, version of the Resource Kit:

BREAKFTM.EXE: Automated Mirror Break/Restore Utility

BROWMON.EXE: Browser Monitor

BROWSTAT.EXE: Browser Status

Crystal Reports Event Log Viewer

dbWeb

DHCPCMD.EXE: DHCP Administrator's Tool

DHCPLOC.EXE: DHCP Server Locator Utility

DOMMON.EXE: Domain Monitor

EMWAC Server CGI Gateway Scripts

FINDGRP.EXE: Find Group

GETSID.EXE

GRPCPY.EXE: Group Copy

Index Server

KIX32.EXE: KiXtart 95

Mail Server

NETSVC.EXE: Command-line Service Controller

RASLIST.EXE

RASUSERS.EXE: Enumerating Remote Access Users

RCMD.EXE: Remote Command Service

Remote Console

RIPROUTE.WRI: Routing with Windows NT Server

RSHSVC.EXE: TCP/IP Remote Shell Service

SNMPMON.EXE: SNMP Monitor

SRVINFO.EXE

TIMESERV.EXE: Time Synchronizing Service

USRSTAT.EXE

Web Administration of Microsoft Windows NT Server

WINSCL.EXE

WINSDMP.EXE


Resource Kit information on the Internet
Introductory Topics

Resource Kit information on the Internet

Several Microsoft sites on the Internet provide further information and updates on the Windows NT Server Resource Kit. If you have an Internet connection and a Web browser, you can click the following links to visit these sites.

Windows NT Resource Kit Utilities Web Site

http://www.microsoft.com/BackOffice/ntutil.htm

Windows NT Resource Kit Web Site

http://www.microsoft.com/BackOffice/READING/msntrkit.htm

Microsoft Press Online Support Web Site

http://www.microsoft.com/mspress/support/

Windows NT Server Web Site

http://www.microsoft.com/NTServer/

Windows NT Workstation Web Site

http://www.microsoft.com/NTWorkstation/

Internet Explorer Web Site

http://www.microsoft.com/InfoServ/

Internet Information Server Web Site

http://www.microsoft.com/InfoServ/

Windows NT Hardware Compatibility List - Web Version

http://www.microsoft.com/ntserver/hcl/hclintro.htm

Windows NT Troubleshooting Guides

http://www.microsoft.com/support/products/backoffice/winnt/content/nttroubleshoot/

Microsoft TechNet

http://www.microsoft.com/TechNet/

NNTP Newsgroups (unofficial discussion area)

http://www.microsoft.com/support/news/

Updates to utilities on the Internet

From the Microsoft FTP site, you can download updates to some Resource Kit utilities and documentation, as well as the POSIX and Perl public domain source files. If you have an Internet connection and FTP, you can click this link to go to the FTP site now.

Windows NT Resource Kit FTP Site

ftp://ftp.microsoft.com/bussys/winnt/winnt-public/reskit/

Microsoft Home Page

URLs (Internet addresses) for specific topics may occasionally be moved during maintenance or changed. If you have any problem reaching a link, point your browser to:

Microsoft Home Page

http://www.microsoft.com/

On the Microsoft Home Page, you can search for the topic you are seeking.


I want to ...

Install Windows NT on multiple computers

Configure hardware and software

Maintain critical configuration information about my disks

Establish security standards for a computer or network

Protect computing resources

Recover a crashed operating system

Plan a Windows NT network

Set up and administer an Internet server


Install Windows NT on multiple computers
I want to ...

Install Windows NT on multiple computers

If you need to set up Windows NT Workstation or Server on large numbers of computers, the Windows NT Server Resource Kit contain useful tools for automating and customizing the process.

I want background on the setup process

For a conceptual overview of automating and customizing the installation process for Windows NT Workstation, see Chapter 2, "Customizing Setup," in Windows NT Workstation Resource Guide.

If you have Online Books installed, click to:

Open Windows NT Workstation Resource Guide in Online Books.

I want to perform multiple network installations

Setup Manager (SETUPMGR.EXE), used in conjuction with WINNT or WINNT32 (included in the operating system), simplifies installing and customizing multiple copies of Windows NT over a network.

I want to know more about Setup Manager.

I want to install applications as part of the multiple installations

SYSDIFF.EXE enables you to pre-install applications that do not support scripted installation as part of an automated setup.

I want to know more about SYSDIFF.


I want to install Windows NT on multiple computers

Setup Manager (SETUPMGR.EXE)/WINNT32

Computer Profile Setup


Setup Manager (SETUPMGR.EXE)/WINNT32
I want to install Windows NT on multiple computers

Setup Manager (SETUPMGR.EXE)

Simplifies installing multiple copies of Windows NT over a network in conjunction with WINNT and WINNT32. With it, you can customize installations by using different unattended answer files (UNATTEND.TXT) and Uniqueness Database Files (UDFs).

For a brief overview of Setup Manager:

Show me the topic on Setup Manager in this overview.

For details on how to use Setup Manager:

Show me online Help for Setup Manager (SETUPMGR.HLP).

For background on Setup Manager, WINNT, and WINNT32, see Chapter 2, "Customizing Setup," in Windows NT Workstation Resource Guide.

If you have Online Books installed, click to:

Open Windows NT Workstation Resource Guide in Online Books.

To use Setup Manager:

Run Setup Manager (SETUPMGR.EXE).


SYSDIFF.EXE
I want to install Windows NT on multiple computers

SYSDIFF.EXE

Enables you to pre-install applications that do not support scripted installation as part of an automated setup. With SYSDIFF, you create a snapshot of a reference system, then install the applications and create a difference file with information on the applications, which you then apply to other computers.

For a brief overview of SYSDIFF:

Show me the topic on SYSDIFF in this overview.

For details on how to use SYSDIFF:

Show me online Help for SYSDIFF (SYSDIFF.HLP).

For background on SYSDIFF, see Chapter 2, "Customizing Setup," in Windows NT Workstation Resource Guide.

If you have Online Books installed, click to:

Open Windows NT Workstation Resource Guide in Online Books.

To run SYSDIFF:

Show me SYSDIFF command-line help.


Configure hardware and software
I want to ...

Configure hardware and software

If you are setting up or upgrading computers running Windows NT, you may need to determine if specific hardware is compatible with Windows NT Workstation and Server, or need information on installing and configuring peripherals and software. The Windows NT Server Resource Kit contains tools that can help.

I want to find out if a piece of hardware is compatible with Windows NT

Hardware Compatibility List (HCLFEB96.HLP) documents computers and peripherals that are Windows NT-compatible.

I want to know more about Hardware Compatibility List.

I want to configure an adapter card

Windows NT Adapter Card Help (NTCARD40.HLP) provides detailed information on how to configure network, SCSI, and sound cards, and services to work with Windows NT.

I want to know more about Windows NT Adapter Card Help.

I want to upgrade to multiple microprocessors

Uni to Multiprocessor Utility (UPTOMP.EXE) upgrades the Windows NT Workstation or Server operating system from single-processor to multiprocessor when more processors have been added after the operating system was installed.

I want to know more about Uni to Multiprocessor Utility.


I want to configure hardware and software

Hardware Compatibility List (HCLFEB96.HLP)

Windows NT Adapter Card Help (NTCARD40.HLP)

Uni to Multiprocessor Utility (UPTOMP.EXE)


Hardware Compatibility List (HCLFEB96.HLP)
I want to configure hardware and software

Hardware Compatibility List (HCLFEB96.HLP)

For a brief overview of Hardware Compatibility List:

Show me the topic on Hardware Compatibility List in this overview.

To use Hardware Compatibility List:

Open Hardware Compatibility List (HCLFEB96.HLP).


Windows NT Adapter Card Help (NTCARD40.HLP)
I want to configure hardware and software

Windows NT Adapter Card Help (NTCARD40.HLP)

For a brief overview of Windows NT Adapter Card Help:

Show me the topic on Windows NT Adapter Card Help in this overview.

To use Windows NT Adapter Card Help:

Open Windows NT Adapter Card Help (NTCARD40.HLP).


Uni to Multiprocessor Utility (UPTOMP.EXE)
I want to configure hardware and software

Uni to Multiprocessor Utility (UPTOMP.EXE)

For a brief overview of Uni to Multiprocessor Utility:

Show me the topic on Uni to Multiprocessor Utility in this overview.

For details on how to use Uni to Multiprocessor Utility:

Show me the text file on Uni to Multiprocessor Utility (UPTOMP.TXT).

To use Uni to Multiprocessor Utility:

Run Uni to Multiprocessor Utility (UPTOMP.EXE).


Maintain critical configuration information about my disks
I want to ...

Maintain critical configuration information about my disks

If your computer crashes, or disk information becomes corrupted, you can more easily rebuild the disk or recover the data if you routinely back up data and maintain configuration information for your disks.

I want to know what backups and configuration information I should be maintaining

For a conceptual overview of what you can do to be prepared, see the "Preparing for and Performing Recovery" chapter in Windows NT Server Resource Guide.

If you have Online Books installed, click to:

Open Windows NT Server Resource Guide in Online Books.

I want to view, save, or restore Master Boot Records, partition tables, or Partition Boot Sectors

You can use DiskProbe, a new Windows NT-based utility in this Resource Kit.

I want to know more about DiskProbe.

I want to back up the Master Boot Record or Partition Boot Sector on an x86-based computer

You can use DiskSave, a new MS-DOS-based utility in this Resource Kit, to back up and restore these disk sectors.

I want to know more about DiskSave.

I want to create or update my Emergency Repair Disk

The Repair Disk utility on the Windows NT Workstation or Windows NT Server product CD enables you to update the repair information for your Windows NT installation and write the information to a floppy disk.

I want to view or print a report about the configuration of a hard disk on my computer

You can use DiskMap, a new command-prompt utility in this Resource Kit.

I want to know more about DiskMap.

I want to know how to create and use fault-tolerant disk volumes (Windows NT Server only)

Windows NT Server supports mirror sets and stripe sets with parity, which are fault-tolerant disk volumes. If one disk in the volume fails, you can still access all of the data, because the disks in the volume contain redundant information.

I want a description of mirror sets and stripe sets with parity.

See the chapter on "Planning a Reliable Configuration" in Windows NT Server Resource Guide.

I want to know how to configure these kinds of  volumes and to recover data following a failure of a disk.

See the chapter on "Preparing for and Performing Recovery" in Windows NT Server Resource Guide.

If you have Online Books installed, click to:

Open Windows NT Server Resource Guide in Online Books.


Maintain critical configuration information about my disks

Disk Probe (DSKPROBE.EXE)

DiskSave (DISKSAVE.EXE)

DiskMap (DISKMAP.EXE)


DiskMap (DISKMAP.EXE)
Maintain critical configuration information about my disks

DiskMap (DISKMAP.EXE)

For an overview of and syntax information for DiskMap:

Show me the topic on DiskMap in this overview.


Establish security standards for a computer or network
I want to ...

Establish security standards for a computer or network

If you are responsible for security planning, the Windows NT Server Resource Kit provides background information and tools to help you evaluate your current security arrangements and establish standards appropriate for your needs. Windows NT Workstation and Server allow you to establish a full range of security levels, from none at all to the U.S. government's C2 level and the European E3 standard.

I want to plan security for a system

For a conceptual overview of Windows NT security planning, see the "Windows NT Security Model" chapter in Windows NT Server Resource Guide.

If you have Online Books installed, click to:

Open Windows NT Server Resource Guide in Online Books.

For a conceptual overview of Windows NT network security and administration, see the chapter on "Network Security and Domain Planning" in Windows NT Server Networking Guide.

If you have Online Books installed, click to:

Open Windows NT Server Networking Guide in Online Books.

I want to see how my current security compares with government standards

Windows NT C2 Configuration Manager (C2CONFIG.EXE) compares the current security configuration on your Windows NT Workstation with the U.S. government's C2-level security requirements.

I want to know more about Windows NT C2 Configuration Manager.


Windows NT C2 Configuration Manager (C2CONFIG.EXE)
I want to establish security standards for a computer or network

Windows NT C2 Configuration Manager (C2CONFIG.EXE)

For a brief overview of Windows NT C2 Configuration Manager:

Show me the topic on Windows NT C2 Configuration Manager (C2CONFIG.EXE) in this overview.

For details on how to use Windows NT C2 Configuration Manager:

Show me online Help for Windows NT C2 Configuration Manager (C2CONFIG.EXE).

To use Windows NT C2 Configuration Manager:

Run Windows NT C2 Configuration Manager (C2CONFIG.EXE).


Protect computing resources
I want to ...

Protect computing resources

If you need to protect hardware, software, or data from damage, theft, or unauthorized use [image] or make it more accessible [image] the Windows NT Server Resource Kit offers tools to help you.

I want to monitor audit events on a computer

Audit Categories Help (AUDITCAT.HLP) provides information on the categories of audit event records displayed by Event Viewer (a utility that is part of Windows NT Workstation and Server). These audit categories allow a user to automatically filter audit events of interest.

Run Audit Categories Help (AUDITCAT.HLP).

I want to see who has what permissions for files

File Access Permissions per User (PERMS.EXE) displays users' access permissions for a specified file or set of files

I want to know more about File Access Permissions per User.

I want to back up security-sensitive data from NTFS partitions to floppy disks

File Copy with Security (SCOPY.EXE) copies files and directories from NTFS partitions with their security intact, enabling you to back up security-sensitive data from your hard disk without using a tape drive.

I want to know more about File Copy with Security .

I want to restrict access to floppy disk drives

The FloppyLock (FLOPLOCK.EXE) service prevents unauthorized installation of software or introduction of viruses via floppy disks by controlling access to floppy drives.

I want to know more about FloppyLock.


I want to protect computing resources

File Access Permissions per User (PERMS.EXE)

File Copy with Security (SCOPY.EXE)

FloppyLock (FLOPLOCK.EXE)


File Access Permissions per User (PERMS.EXE)
I want to protect computing resources

File Access Permissions per User (PERMS.EXE)

For a brief overview of File Access Permissions per User:

Show me the topic on File Access Permissions per User in this overview.

To use File Access Permissions per User:

Run File Access Permissions per User.


File Copy with Security (SCOPY.EXE)
I want to protect computing resources

File Copy with Security (SCOPY.EXE)

For a brief overview of File Copy with Security:

Show me the topic on File Copy with Security in this overview.

To use File Copy with Security:

Run File Copy with Security.


FloppyLock (FLOPLOCK.EXE)
I want to protect computing resources

FloppyLock (FLOPLOCK.EXE)

To learn how to install, configure, turn on or off, or remove the FloppyLock service:

Show me the topic on FloppyLock in this overview.

For more details on using the FloppyLock service:

Show me the text file on FloppyLock (FLOPLOCK.TXT).


Recover a crashed operating system
I want to ...

Recover a crashed operating system

If you have to get computers that won't boot back up and running or are responsible for planning more robust configurations, the Windows NT Server Resource Kit provides background information and tools to help you.

I want background on setting up a more reliable and recoverable system

For a conceptual overview of reliability and recoverability, see the "Reliability and Recoverability" section in Windows NT Server Resource Guide.

If you have Online Books installed, click to:

Open Windows NT Server Resource Guide in Online Books.

I want to analyze problems on my hard disk

You can use DiskProbe, a new Windows NT-based utility in this Resource Kit.

I want to know more about DiskProbe.

I want to back up and restore boot information

DiskSave, a new MS-DOS-based utility in this Resource Kit, allows you to save the Master Boot Record and Boot Sector as binary image files.

I want to know more about DiskSave.

I want to recover a broken system

The Repair Disk utility on the Windows NT Workstation or Windows NT Server product CD and the Emergency Repair Disk enable you to fix errors and recover a system that isn't booting.


Recover a crashed operating system

Disk Probe (DSKPROBE.EXE)

DiskSave (DISKSAVE.EXE)


Disk Probe (DSKPROBE.EXE)
I want to recover a crashed operating system

DiskProbe (DSKPROBE.EXE)

For a brief overview of DiskProbe:

Show me the topic on DiskProbe in this overview.

For details on how to use Disk Probe:

Show me online Help for DiskProbe (DSKPROBE.EXE).

To use Disk Probe:

Run DiskProbe (DSKPROBE.EXE).


DiskSave (DISKSAVE.EXE)
I want to recover a crashed operating system

DiskSave (DISKSAVE.EXE)

For a brief overview of DiskSave:

Show me the topic on DiskSave in this overview.

For details on how to use DiskSave:

Show me the text file on DiskSave (DISKSAVE.TXT).


Plan a Windows NT network
I want to ...

Plan a Windows NT network

If you need to plan a Windows NT network or domain, information on these topics is included in Windows NT Server Networking Guide.

I want background on planning a Windows NT network

For a conceptual overview of network planning, see the "About Windows NT Server Networking" section in Windows NT Server Networking Guide.

If you have Online Books installed, click to:

Open Windows NT Server Networking Guide in Online Books.


Set up and administer an Internet server
I want to ...

Set up and administer an Internet server

Windows NT Server provides a powerful platform for any compatible Internet server software, and includes the Microsoft Internet Information Server (IIS). The Windows NT Server Resource Kit provides background information and tools to help you set up and administer Internet servers.

I want background on using Windows NT Server on the Internet

For a conceptual overview of working with Internet Information Server and Internet clients on Windows NT Server, see Windows NT Server Internet Guide and the documentation for Internet Information Server.

If you have Online Books installed, click to:

Open Windows NT Server Internet Guide in Online Books.

I want to set up an SMTP/POP server providing simple e-mail access:

Mail Server (MAILSRV.EXE) is a basic SMTP (Simple Mail Transport Protocol) and POP3 (Post Office Protocol) service for Windows NT Workstation and Windows NT Server. Providing e-mail access for up to 10 accounts, Mail Server supports Internet-based mail clients and is completely separate from the Microsoft Mail program.

I want to know more about Mail Server.

For a conceptual overview of setting up the Mail Server service, see the chapter on setting up a mail server in Windows NT Server Networking Guide.

If you have Online Books installed, click to:

Open Windows NT Server Networking Guide in Online Books.

I want to set up a Telnet server

Telnet Server Beta (TELNETD.EXE) provides a solution for running command-line utilities, scripts and batch-files from OS-independent clients. It is not intended to be a full commercial-grade Telnet solution. Telnet Server Beta supports remote, character-based sessions, while Windows NT 4.0 is designed primarily to support graphics-based applications.

I want to know more about Telnet Server Beta.

I want to set up a World Wide Web server or site, a Gopher server, or an FTP server

Internet Information Server (IIS) includes a World Wide Web server, a Gopher server, and an FTP server. With the World Wide Web server, you can create and administer Web sites on the World Wide Web or internal Webs (intranets). IIS is included in the Windows NT Server 4.0 operating system.

For a conceptual overview of setting up World Wide Web, Gopher, and FTP servers and troubleshooting IIS, see Windows NT Server Internet Guide.

If you have Online Books installed, click to:

Open Windows NT Server Internet Guide in Online Books.

For more details on Internet Information Server (IIS):

I want to know more about Internet Information Server (IIS).

I want to index sites and documents for Internet Information Server

Index Server is the Microsoft content-indexing and searching solution for Microsoft Internet Information Server (IIS), which is included with Windows NT Server 4.0, and Peer Web Services (PWS), which is included with Windows NT Workstation 4.0. An add-on module for IIS and PWS, Index Server is designed to index the full text and properties of documents on an IIS or PWS-based server.

For more details on Index Server:

I want to know more about Index Server.


Set up or administer an Internet server

Mail Server (MAILSRV.EXE)

Telnet Server Beta (TELNETD.EXE)

Internet Information Server (IIS)

Index Server


Mail Server (MAILSRV.EXE)
I want to set up or administer an Internet server

Mail Server (MAILSRV.EXE)

For a brief overview of Mail Server:

Show me the topic on Mail Server in this overview.

For details on how to use Mail Server:

Show me the HTML documentation for Mail Server .

For a conceptual overview of setting up the Mail Server service, see the chapter on setting up a mail server in Windows NT Server Networking Guide.

If you have Online Books installed, click to:

Open Windows NT Server Networking Guide in Online Books.


Telnet Server Beta (TELNETD.EXE)
I want to set up or administer an Internet server

Telnet Server Beta (TELNETD.EXE)

For a brief overview of Telnet Server Beta:

Show me the topic on Telnet Server in this overview.

For details on how to use Telnet Server Beta:

Open TELNET.WRI now.


Internet Information Server (IIS)
I want to set up or administer an Internet server

Internet Information Server (IIS)

For a World Wide Web site with information on IIS (you must have a Web browser and an internet connection):

Go to the Microsoft Internet Information Server Web site (http://www.microsoft.com/InfoServ/)

For details on how to use IIS, see the IIS documentation.


Index Server
I want to set up or administer an Internet server

Index Server

For a brief overview of Index Server:

Show me the topic on Index Server in this overview.

For details on how to use Index Server, see the Index Server documentation.


Glossary of Terms

- A -

ACL

API

- B -

batch program

browser

- C -

No entries

- D -

daemon

DHCP

DLL

DNS

domain

domain controller

Domain Name System

Dynamic Host Configuration Protocol

dynamic-link library

- E -

No entries

- F -

FAT

fault tolerance

frame

FTP

- G -

gateway

GUI

- H -

HAL

hive

HOSTS

HPFS

HTML

Hypertext Markup Language

- I -

IP address

- J -

No entries

- K -

Kernel

key

- L -

LAN

local area network

- M -

MAC

Master Boot Record

MBR

MIB

- N -

NetBIOS

NTFS

- O -

Object Linking and Embedding

ODBC

OLE

Open Database Connectivity

- P -

page fault

partition

partition table

path

PCMCIA

permissions

POP

POSIX

process

- Q -

No entries

- R -

Reduced Instruction Set Computing

Registry

Request for Comments

RFC

RISC

router

- S -

SAM

script

Security Accounts Manager

Small Computer System Interface

SID

SMB

SMTP

SNMP

SQL

STDERR

STDIN

STDOUT

Structured Query Language

subnet mask

- T -

TCP/IP

TDI

telnet

threads

Transport Driver Interface

transport protocol

- U -

UNC name

Unicode

uniform naming convention name

UNIX

user profile

UUEncoding/Decoding

- V -

No entries

- W -

WAN

wide area network

WINS

- X -

No entries

- Y -

No entries

- Z -

No entries


ACL (defined)
ACL

Access Control List. The part of a security descriptor that enumerates the protections applied to an object.


API (defined)
API

Application programming interface. A set of routines that an application program uses to request and carry out lower-level services performed by a computer's operating system. These routines usually carry out maintenance tasks such as managing files and displaying information.


batch program (defined)
batch program

An ASCII (unformatted text) file containing one or more Windows NT commands. A batch program's filename has a .BAT or .CMD extension. When you type the filename at the command prompt, the commands are processed sequentially. "Script" is often used interchangeably with "batch program" in the Windows NT environment.


browser (defined)
browser

Computer Browser service (in the context of Windows NT). Maintains an up-to-date list of computers and provides the list to applications when requested. When a user attempts to connect to a resource in the domain, the domain's browser is contacted to provide a list of available resources.


daemon (defined)
daemon

Pronounced "demon." A program, usually associated with UNIX systems, that performs utility functions such as housekeeping or maintenance without user intervention or even awareness.


domain (defined)
domain

A networked set of Windows NT workstations and Windows NT servers that share a Security Accounts Manager (SAM) database and that can be administered as a group. A user with an account in a particular domain can log onto and access his or her account from any system in the domain.


domain controller (defined)
domain controller

For a Windows NT Server domain, the server that authenticates domain logons and maintains the security policy and the master database for a domain. Both servers and domain controllers are capable of validating a user's logon, but password changes must be made by contacting the domain controller.


DHCP (defined)
DHCP

Dynamic Host Configuration Protocol. A networking protocol that provides safe, reliable, and simple TCP/IP network configuration and offers dynamic configuration of Internet Protocol addresses for computers. DHCP ensures that address conflicts do not occur and helps conserve the use of IP addresses through centralized management of address allocation.


DLL (defined)
DLL

Dynamic-link library. A feature of the Microsoft Windows family of operating systems and the OS/2 operating system. DLLs allow executable routines, generally serving a specific function or set of functions, to be stored separately as files with .DLL extensions, and to be loaded only when needed by the program that calls them.


DNS (defined)
DNS

Domain Name System. A hierarchical name service for TCP/IP host computers that provides standard naming conventions.

The administrator of a network must configure the DNS with a list of hostnames and IP addresses. This allows users of network computers to query the DNS, specifying remote computers by hostnames, which are character strings with some mnemonic value, rather than IP addresses, which are simply strings of numbers. Windows Sockets applications and TCP/IP utilities, such as FTP and telnet, can use DNS in addition to the HOSTS file to locate particular computers anywhere on the local network or beyond on the Internet.

DNS originated in the UNIX networking environment.


FAT (defined)
FAT

A file system based on a file allocation table (FAT) maintained by the operating system to keep track of the status of various segments of disk space used for file storage.


fault tolerance (defined)
fault tolerance

Assurance of data integrity when hardware failures occur. In Windows NT, fault tolerance is provided by the FTDISK.SYS driver. In Disk Administrator, fault tolerance is provided by using mirror sets, stripe sets with parity, and volume sets.


frame (defined)
frame

One image in a sequence that makes up an animation.


FTP (defined)
FTP

File Transfer Protocol. FTP is both a protocol that defines how to transfer files from one computer to another over the Internet, and an application program that moves files using this protocol.


gateway (defined)
gateway

A device that connects dissimilar networks and passes information from one to the other. A gateway translates information from the communications protocol of the first network into that of the second before transferring it.

In TCP/IP, the default gateway is the address where the Internet Protocol sends packets that are destined for remote networks, unless a different route to the destination network is configured.


GUI (defined)
GUI

Graphical User Interface (GUI is pronounced "gooey"). A display format, like that of Windows NT, that represents a program's functions with graphic images such as pushbuttons and icons, and allows a user to perform operations and make choices by pointing and clicking with a mouse.


HAL (defined)
HAL

Hardware Abstraction Layer. A thin layer of software provided by the hardware manufacturer that hides, or abstracts, hardware differences from higher layers of the operating system.

Through the filter provided by the HAL, different types of hardware all look alike to the rest of the operating system. This allows Windows NT to be portable from one hardware platform to another. The HAL also provides routines that allow a single device driver to support the same device on all platforms.

The HAL works closely with the Kernel.


hive (defined)
hive

A section of the Registry that appears as a file on your hard disk. For example, the hive HKEY_USERS\DEFAULT appears on your hard disk as the file %SYSTEMROOT%\SYSTEM32\CONFIG\DEFAULT\DEFAULT.LOG. Because a hive is a file, it can be moved from one system to another, but can only be edited using Registry Editor.


HOSTS (defined)
HOSTS

A file containing lists of known IP addresses, used by TCP/IP to locate computers on a network or the Internet.


HPFS (defined)
HPFS

High-Performance File System. The file system designed for the OS/2 version 1.2 operating system.


HTML (defined)
HTML

Hypertext Markup Language. A simple markup language used to create hypertext documents that are portable from one platform to another. HTML files are simple ASCII text files with codes embedded (indicated by markup tags) to indicate formatting and hypertext links. HTML is used for formatting documents on the World Wide Web.


IP address (defined)
IP address

Internet Protocol address. The unique logical address identifying each host computer, or node, on a TCP/IP network. An IP address is a 32-bit number expressed as four decimal numbers from 0 to 255 separated by periods, for example:

131.107.2.200

Each IP address has two parts: the network ID and the host ID. The network ID identifies all hosts that are on the same physical network. The host ID identifies a specific host on a network. A subnet mask is used to mask a portion of the IP address so that TCP/IP can distinguish the network ID from the host ID.


kernel (defined)
Kernel

The heart of Windows NT code, the Kernel is the module which manages the computer's processor. The Kernel schedules activities, called threads, for the processor to keep it as busy as possible, and coordinates multiple processors to optimize performance. The Kernel also synchronizes activities among Executive-level subcomponents, such as I/O Manager and Process Manager.

The Kernel works closely with the HAL.


key (defined)
key

An entry in the Registry, which can contain both subkeys and value entries. In the Registry structure, keys are analogous to folders, and value entries are analogous to files. In the Registry Editor window, a key appears as a file folder in the left pane.


LAN (defined)
LAN

Local area network. A communications network connecting a group of computers, printers, and other devices located within a relatively limited area (for example, a building). A LAN allows any connected device to interact with any other on the network. See also WAN.


MAC (defined)
MAC

Media Access Control. A form of network addressing defined by the IEEE 802 standards for the physical and data-link layers of local area networks, following the ISO Open Systems Interconnection model.


Master Boot Record (defined)
Master Boot Record

The most important area on a hard disk, the data structure that starts the process of booting the computer.

The Master Boot Record contains the partition table for the disk and a small amount of executable code. On x86-based computers, the executable code examines the partition table and identifies the system (or bootable) partition, finds the system partition's starting location on the disk, and loads an image of its Partition Boot Sector into memory. The Master Boot Record then transfers execution to the Partition Boot Sector.


MIB (defined)
MIB

Management Information Base. The entire set of objects that a protocol or service uses under SNMP.

SNMP defines a set of variables that the host must keep. Because different network-management services are used for different types of devices or for different network-management protocols, each service has its own set of objects. The SNMP service for Windows NT supports multiple MIBs through an agent API.

Each MIB consists of a hierarchical list of object identifiers describing a managed entity. The MIB handler retrieves object values from the managed entity and sends them to the SNMP console.


NetBIOS (defined)
NetBIOS

An application program interface (API) that can be used by application programs on a local area network or computers running MS-DOS, OS/2, or some version of UNIX. NetBIOS provides a uniform set of commands for requesting lower level network services.


NTFS (defined)
NTFS

Windows NT File System. An advanced file system designed for use specifically with the Windows NT operating system. NTFS supports file system recovery and extremely large storage media, in addition to other advantages. It also supports object-oriented applications by treating all files as objects with user-defined and system-defined attributes.


ODBC (defined)
ODBC

Open Database Connectivity. A standard Microsoft programming interface for databases supported by many different database vendors.


OLE (defined)
OLE

A method for sharing information among applications. The acronym (pronounced oh-LAY) was originally derived from "object linking and embedding."

OLE is an object-oriented technology designed for creating, managing, and accessing object-based components across process and hardware boundaries.

Linking an object (such as a section of a spreadsheet or a graphic) from one document to another inserts a reference to the object into the second document. Any changes made in the object in the first document will also be made in the second document.

Embedding an object inserts a copy of an object from one document into another document. Changes made in the object in the first document will not be updated in the second unless the embedded object is explicitly updated.


page fault (defined)
page fault

In the processor, a page fault occurs when a process refers to a virtual memory page that is not in its working set in main memory.

A hard page fault occurs when data a program needs is not found in its working set (the physical memory visible to the program) or elsewhere physical memory and must be retrieved from disk.

A page fault will not cause the page to be fetched from disk if that page is on the standby list, and hence already in main memory, or if it is in use by another process with which the page is shared. In this case, a soft page fault occurs.


partition (defined)
partition

A logical division of a hard disk, which makes it easier to organize information. Each partition can be formatted for a different file system.

A partition must be completely contained on one physical disk, and the Partition Table in the Master Boot Record for a physical disk can contain up to four entries for partitions.


partition table(defined)
Partition Table

An area of the Master Boot Record that the computer uses to determine how to access the disk.  The Partition Table can contain up to four partitions for each physical disk.


PATH (defined)
path

A list of folders and sub-folders which Windows NT searches for an executable filename, if this is run without an explicit path.

Windows NT manages two different types of paths; the current user's path and the system path. Windows NT keeps a separate user path for every user on a system, but there is only one global system path. When a user logs on to a Windows NT machine, these two paths are combined to create the user's full path.

For backward compatibility, Windows NT also loads path information from old AUTOEXEC.BAT files, which are found in the root folder of computers running MS-DOS and older versions of Windows and Windows NT. The AUTOEXEC.BAT file can contain a PATH command, which also specifies folders in which to search for executables.


PCMCIA (defined)
PCMCIA

Personal Computer Memory Card International Association. A standard for removable peripheral devices (called PC Cards) about the size of a credit card, which plug into a special 68-pin connector found most commonly in portable computers. Currently available PCMCIA cards include memory, hard disk, modem, fax, network, and wireless communication devices.


permissions (defined)
permissions

Windows NT Server settings you set on a shared resource that determine which users can use the resource and how they can use it.


POP (defined)
POP

Post Office Protocol. A maildrop service that allows a client to retrieve mail that the server is holding for it. The most recent implementation is Version 3, or POP3.

On certain types of smaller nodes on the Internet, it is often impractical to maintain a message transport system (MTS): this would require that a workstation or personal computer support an SMTP server and local mail delivery system or remain continuously connected to the Internet. POP permits a node which can support an MTS to function as a server, offering a maildrop service to less endowed client nodes.


POSIX (defined)
POSIX

Portable Operating System Interface for Computing Environments. A set of standards being drafted by the Institute of Electrical and Electronic Engineers (IEEE) that define various aspects of an operating system, including topics such as programming interface, security, networking, and graphical interface.


process (defined)
process

In Windows NT, a type of object that includes an address space, a set of objects (resources) visible to the process, and a set of threads that run in the context of the process.


Registry (defined)
Registry

In Windows NT and Windows 95, a central database for storing configuration data in hierarchical form on hardware, the operating system, device drivers, and applications.

The Registry is roughly analogous to the .INI files used under Windows 3.x, with each key in the Registry similar to a bracketed heading in an .INI file and with Registry values similar to entries under the .INI headings. However, Registry keys can contain subkeys, while .INI files do not support nested headings. Registry values can also consist of binary data, rather than the simple strings used in .INI files.


RFC (defined)
RFC

Request for Comments. A document that defines a TCP/IP standard. RFCs are published by the Internet Engineering Task Force (IETF) and other working groups.


RISC (defined)
RISC

Reduced Instruction Set Computing. A category of microprocessor architecture which increases speed and efficiency by using a smaller set of basic instructions to the microprocessor. RISC microprocessors, such as the Digital Alpha AXP and MIPS R4000, are most commonly used in workstations.


router (defined)
router

A network server that helps LANs and WANs achieve interoperability and connectivity, and can link LANs that have different network topologies, such as Ethernet and Token Ring.

A router looks at the network addresses in the packets it receives before deciding whether to pass them on. Routers make packet forwarding decisions on the basis of addresses in the network layer of the OSI reference model (for example, IP addresses).

A router makes more intelligent decisions than a bridge about data it passes on. A bridge can only decide whether or not to pass on a packet, but a router can choose the best path along the network for the packet to reach its destination address.

In the TCP/IP context, a router is a gateway, a computer with two or more network adapters that is running some type of IP routing software. Each adapter is connected to a different physical network.


SAM (defined)
SAM

Security Accounts Manager. A Windows NT protected subsystem that maintains the SAM database and provides an API for accessing the database.


script (defined)
script

A type of program consisting of a set of instructions to an application or utility program. A script usually expresses instructions using the application's or utility's rules and syntax, combined with simple control structures such as loops and if/then expressions. "Batch program" is often used interchangeably with "script" in the Windows NT environment.


SCSI (defined)
SCSI

Small Computer System Interface (pronounced "scuzzy"). A standard high-speed parallel interface defined by the X3T9.2 committee of the American National Standards Institute (ANSI). A SCSI interface is used for connecting microcomputers to peripheral devices, such as hard disks and printers, and to other computers and local area networks.


SID (defined)
SID

Security ID. A unique name that identifies a logged-on user to the Windows NT security system. A security ID can identify either an individual user or a group of users.


SMB (defined)
SMB

Server message block. A method for sending information between networked computers that provides interoperability between a variety of networks. The SMB protocol, jointly developed by Microsoft, Intel, and IBM, defines a series of commands that pass information between computers. SMB uses four message types: session control, file, printer, and message.


SMTP (defined)
SMTP

Simple Mail Transport Protocol. A protocol used on the Internet to transfer mail reliably and efficiently. SMTP is independent of the particular transmission subsystem and requires only a reliable, ordered data stream channel.

An important feature of SMTP is its capability to relay mail across transport service environments. A transport service provides an interprocess communication environment (IPCE), which may cover one network, several networks, or a subset of a network.

A process can communicate directly with another process through any mutually known IPCE. Mail can be relayed between processes running on hosts on different transport systems by a host connected to IPCEs on both transport systems.


SNMP (defined)
SNMP

Simple Network Management Protocol. A network management protocol installed with TCP/IP, and widely used on TCP/IP and Internet Package Exchange (IPX) networks.

SNMP transports management information and commands between a management program run by an administrator and the network management agent running on a host. The SNMP agent sends status information to one or more hosts when the host requests it or when a significant event occurs.

SNMP defines the form and meaning of the messages exchanged, the representation of names and values in the messages, and the administrative relationships among hosts being managed.


SQL (defined)
SQL

Structured Query Language. A database sublanguage used in querying, updating, and managing relational databases, widely accepted as a standard in database products.


STDERR (defined)
STDERR

Standard Error. One of the standard input/output streams opened automatically in both MS-DOS and UNIX environments when a program starts running. These I/O streams let the program interact with its environment, including peripheral devices. Most commonly, STDERR carries data to a display or file.


STDIN (defined)
STDIN

Standard Input. One of the standard input/output streams opened automatically in both MS-DOS and UNIX environments when a program starts running. These I/O streams let the program interact with its environment, including peripheral devices. Most commonly, STDIN carries data from a keyboard or file.


STDOUT (defined)
STDOUT

Standard Output. One of the standard input/output streams opened automatically in both MS-DOS and UNIX environments when a program starts running. These I/O streams let the program interact with its environment, including peripheral devices. Most commonly, STDOUT carries data to a display or file.


subnet mask (defined)
subnet mask

A logical value that screens out a portion of the IP address so that TCP/IP can distinguish the network ID from the host ID. The host ID identifies individual computers on the network. TCP/IP hosts use the subnet mask to determine whether a destination host is located on a local or a remote network.

A subnet mask is a 32-bit number expressed as four decimal numbers from 0 to 255 separated by periods, for example:

255.255.0.0


TCP/IP (defined)
TCP/IP

Transmission Control Protocol/Internet Protocol. A software communications protocol widely used on the Internet, originally developed by the United States Department of Defense for communication between computers.


TDI (defined)
TDI

Transport Driver Interface. In the Windows NT networking model, a common interface for Network Layer components that communicate with the Session Layer of the Open Systems Interconnection model. The TDI is not a single program, but a protocol specification to which the upper bounds of transport protocol device drivers are written. It allows software components above and below the Transport Layer to be mixed and matched without reprogramming.


telnet (defined)
telnet

A terminal-emulation protocol widely used on the Internet to log on remotely to other computers. "Telnet" also refers to the application program that uses the telnet protocol for remote logons.


thread (defined)
thread

In Windows NT, the most basic entity that can be scheduled. A thread is a type of object with its own set of registers, its own Kernel stack, a thread environment block, and a user stack in the address space of its process.


transport protocol (defined)
transport protocol

Defines how data should be presented to the next receiving layer in the Windows NT networking model, and packages the data accordingly. It passes data to the network adapter card driver through the NDIS Interface, and to the redirector through the Transport Driver Interface (TDI).


UNC name (defined)
UNC name

Uniform naming convention name. A name of a file or other resource that begins with two backslashes (\\), indicating that it exists on a remote computer.


Unicode (defined)
Unicode

A fixed-width, 16-bit character-encoding standard capable of representing the letters and characters of virtually all the world's languages. Unicode was developed by a consortium of U.S. computer companies.


UNIX (defined)
UNIX

A powerful multiuser, multitasking operating system initially developed at AT&T Bell Laboratories in 1969 for use on minicomputers. UNIX (pronounced "ewe-niks") is considered more portable—that is, less machine-specific—than other operating systems because it is written in C language. Newer versions of UNIX have been developed at the University of California at Berkeley and by AT&T.


user profile (defined)
user profile

A definition of the Windows NT configuration for a specific user. By default, each Windows NT computer maintains a profile for each user who has logged on to the computer.

Much of this configuration information is about user settings, such as color schemes, screen savers, and mouse and keyboard layout. Other information includes things that can be set only by a Windows NT administrator, such as access to common program groups or network printers.


UUEncoding/Decoding (defined)
UUEncoding/Decoding

A form of encoding and decoding that allows binary files to be sent as e-mail.

A binary file, such as a program or image, cannot be sent directly over the Internet by e-mail. To send such a file, you must first encode it to hide the control characters. This can be accomplished by converting the binary file to a text file. UUEncoding carries out this conversion, and UUDecoding regenerates the original file.


WAN (defined)
WAN

Wide area network. A communications network connecting geographically separated computers, printers, and other devices. A WAN allows any connected device to interact with any other on the network. See also LAN.


WINS (defined)
WINS

Windows Internet Name Service. A service that maps computer names to IP addresses, allowing users to communicate with other computers without having to remember strings of numbers for the addresses.