Copyright: Update Information for Version 3.51
Citation: Update Information for Version 3.51


Welcome
Welcome	1 of 1

Welcome

Welcome to the latest release of Microsoft® Windows NT™ Server, which includes expanded platform support for the PowerPC®, new features, and improvements to existing features.

The Setup program is faster and smoother than ever. It also detects and corrects the floating-point division error associated with some Intel® Pentium™ processors. Microsoft Windows® 95 common controls have been included so that applications designed to run on Windows 95 can run on Windows NT Server 3.51. And you can now compress files on Windows NT file system (NTFS) partitions.

For more information about detecting the Pentium processor’s floating-point division error and Microsoft Windows 95 common controls, see Chapter 1, “New Programs and Features.” For more information about NTFS file compression, see Chapter 2, “Changes to Existing Programs and Features.”

This release includes new tools to make it easier for network administrators to track and manage client license usage on Windows NT Server. For more information see Chapter 5, “Licensing and License Manager.”

Chapter 1, “New Programs and Features,” includes general information about the licensing options presented during the Setup program. You’ll also find information about Console, which is a new Control Panel option, and information about three new command-line utilities.

Chapter 2, “Changes to Existing Programs and Features,” includes information about changes made to everything from configuring Command Prompt windows to assigning user profile paths. Chapter 2 also includes information about the changed functionality of the format and route command-line utilities.

Chapter 3, “Additional Information About Existing Programs and Features,” includes information about using a Windows NT Advanced Server 3.1 primary domain controller (PDC) with a Windows NT Server 3.51 backup domain controller (BDC), Disk Administrator, and information about multimedia improvements.

Chapter 4, “Supplemental Information About TCP/IP,” includes additional information about Transmission Control Protocol/ Internet Protocol (TCP/IP), Simple Network Management Protocol (SNMP), Windows Internet Name Service (WINS), and Dynamic Host Configuration Protocol (DHCP).

Chapter 5, “Licensing and License Manager,” describes the two new licensing tools in Windows NT Server 3.51:  the Licensing option in Control Panel, and the License Manager program in the Network Administration program group.


New Programs and Features
Chapter 1	1 of 22

New Programs and Features

This chapter includes information about the following new programs and features of Windows NT Server 3.51:

Setup.  The Setup program has been changed as follows:

A Choose Licensing Mode dialog box is displayed during Setup in which you must select a licensing mode, and then agree to the terms of the licensing agreement.

5.25 inch Setup floppy disks cannot be used.

The Setup program can run in unattended mode.

The floating-point division error exhibited by some Intel Pentium processors is detected and can be corrected during Setup.

Windows 95 common controls.  Windows 95 common controls and Help are supported in this release of Windows NT Server.

PCMCIA cards.  Windows NT Server now includes increased support for certain Personal Computer Memory Card International Association (PCMCIA) cards.

Online documentation.  Books Online allows you to point to the location of the online Windows NT Workstation or Windows NT Server manuals.

Console.  Console is a new Control Panel option that allows you to change the appearance and position of character-based and command prompt windows.

Command-Line Utilities.  Windows NT Server 3.51 includes three new command-line utilities, pentnt, Books Online (the ntbooks command), and compact.


Selecting and Accepting an Appropriate Licensing Mode
New Programs and Features	2 of 22

Selecting and Accepting an Appropriate Licensing Mode

Licensing for the Microsoft BackOffice family of server products requires a Server License and a license for each client computer to access the server, which is called a Client Access License. These licenses are acquired separately prior to using the product. For Windows NT Server, SQL Server, and SNA Server, the Client Access License can be used in one of two licensing modes (Per Server and Per Seat) offering customers the flexibility to choose the option that best meets their needs.

For more detailed information about and an exact description of either the Per Server or Per Seat licensing modes, see the Microsoft license agreement in your product package or in the online Help for Licensing or License Manager.

Windows NT Server 3.51 Setup presents a Choose Licensing Mode dialog box. It also allows access through Help to online versions of the Microsoft Client Access License and Server License agreements. You will be required to select a licensing option and accept the terms of the license agreement for Setup to complete. In this dialog box, you must indicate whether you want Windows NT Server 3.51 to be installed in the Per Server or Per Seat licensing mode.

Per Server Option

With Per Server licensing, each Client Access License is assigned to a particular server and allows one connection to that server for basic network services (file, print, and communications). Notice that a connection, in this case, is to a server and not just to an individual share point or printers on that server. If you connect to \\PRODUCT\NEW and \\PRODUCT\OLD, that is considered as only one connection for licensing purposes.

You must have at least as many Client Access Licenses dedicated to that server as the maximum number of client computers that will connect to that server at any point in time. If you select the Per Server option, you must specify during Setup the number of Client Access Licenses (which corresponds to the number of concurrent connections) that you have purchased for that server.

Note

When a server reaches the maximum number of concurrent connections, Windows NT Server 3.51 will display an error message and not allow anymore computers to connect. Administrators also receive a warning message when this situation happens and are allowed to connect and fix the lockout situation.

This mode of licensing is available for Microsoft Windows NT Server 3.51 or later, Microsoft SQL Server 4.21a or later, and Microsoft SNA Server 2.11 or later. It is not available for Microsoft Systems Management Server or the Microsoft BackOffice Client Access License. The Per Server option is often the most economical one for networks in which clients tend to connect to only one occasional-use or special-purpose server.

Also, if you are unsure which licensing mode to choose, select the Per Server option. You are legally permitted to convert from Per Server mode to Per Seat mode at no additional cost. (Use the Licensing option in Control Panel for a server on which you are working and License Manager in the Network Administration program group for local or remote servers. For more information on how to use these new licensing tools, see Chapter 5, “Licensing and License Manager.”) This is a one-time, one-way conversion option. It is not necessary for you to notify Microsoft if you elect to make this change. You are not legally permitted to change the licensing mode from Per Seat to Per Server.

Per Seat Option

The Per Seat licensing mode requires a Client Access License for each computer that will access Windows NT Server for basic network services (file, print, and communications). Once a computer is licensed, it may be used to access any Windows NT Server computer at no additional charge.

If you select the Per Seat licensing mode, any number of licensed computers can be used to connect at the same time to any Windows NT Server. However, remember that you must purchase a separate Client Access License for each computer even if you use client operating-system software from Microsoft (including Microsoft Windows for Workgroups or Microsoft Windows NT Workstation), from a third-party vendor, or any of the other client software supported by Windows NT Server. The Per Seat option is often the most economical one for networks in which clients tend to connect to more than one server.

Note

A Client Access License is not included when you acquire Windows for Workgroups, Windows NT Workstation, and (when released) Windows 95. The license must be purchased separately in addition to the operating-system software.

Examples of When To Use Each Mode

The following examples are designed to help clarify the situations under which you would use each licensing mode.

Example One

This first example describes a company that uses Windows NT Server for file and print services. The company has three servers and 100 employees. In this example, all the employees log on to a “home” server and, normally, access one additional server during the day.

If the Per Seat licensing mode is selected, the company would purchase 100 Client Access Licenses, and the employees could access all the servers. If the Per Server licensing mode is selected, the company would have to determine the maximum number of concurrent connections to any one server to guarantee access for all users. Depending on the demand, this may require them to purchase more than 100 Client Access Licenses.

For example, if 33 employees use one of the servers as their home server but, on average, 20 employees normally connect to an additional server, then the maximum number of concurrent connections for each server might be 53. That would require the purchase of 159 Client Access Licenses or 53 for each of the three computers. In general, the Per Seat option is the most economical one to choose when the use of a server is pervasive or guaranteed access is needed to such services as file and print, or business-critical applications.

Example Two

In another situation, a company is planning to use Windows NT Server for remote access services. The company has 200 employees but anticipates that only 50 employees will dial in at any one time.

In this case, the company should license Windows NT Server in the Per Server mode and purchase 50 Client Access Licenses for that server. The Per Server option is the most economical one to choose for occasional-use servers, such as when a great number of clients will only access a server on an occasional basis, or for special-use servers such as those running Remote Access Service, Internet servers, or bulletin board servers.

Example Three

In contrast with example two, when the number of Client Access Licenses in the Per Server mode approaches or is greater than the total number of clients in an organization, then switching to the Per Seat mode becomes more cost effective.

For example, consider a company that has a total of 200 workstations and four Windows NT Server computers, each with 50 Client Access Licenses, for a total of 200 Client Access Licenses in the Per Server mode. The company would want to switch the servers to the Per Seat mode to reduce administrative overhead costs and guarantee access to such services as file and print, or business-critical applications on all the servers.


Alternatives to Using 5.25 Inch Setup Floppy Disks
New Programs and Features	3 of 22

Alternatives to Using 5.25 Inch Setup Floppy Disks

Formerly, when you installed or upgraded Windows NT Server on an x86-based computer, you were provided with or were required to supply three blank, formatted, high-density 3.5 inch or 5.25 inch Setup floppy disks. In Windows NT Server 3.51, 5.25 inch Setup floppy disks cannot be used.

Note

If the 3.5 inch drive on your computer is the drive from which your computer starts, you can continue to use 3.5 inch Setup floppy disks.

Instead of using 5.25 inch Setup floppy disks, you can perform a Setup without using floppy disks. Or, if you have both a 3.5 inch drive and a 5.25 inch drive, you can alter your computer to start from the 3.5 inch drive. For more information about performing Setup without using floppy disks, see the next section. For more information about altering your computer to start from a 3.5 inch drive, consult your hardware documentation.


Performing a Setup Without Using Floppy Disks
New Programs and Features	4 of 22

Alternatives to Using 5.25 Inch Setup Floppy Disks

Performing a Setup Without Using Floppy Disks

To perform a Setup without using floppy disks, you must install Windows NT Server from the CD-ROM or a network distribution point. To begin the Setup program and indicate the floppy disks will not be used during Setup, you must specify the /b parameter with the winnt or winnt32 command at the command prompt. When performing a Setup without floppy disks, files are copied to a temporary directory on your hard disk instead of to blank floppy disks.

For more information about using the winnt or winnt32 command, see “Starting Setup on an x86-Based Computer,” in Chapter 1, “Installing Windows NT Server,” of the Windows NT Server Installation Guide.

For more information about winnt or winnt32 command parameters, change to the directory where the installation files are located, and then type winnt /? or winnt32 /? at the command prompt.

To install Windows NT Server on a computer that is already running MS-DOS [image], use the winnt /b command from the command prompt to perform a new installation of Windows NT Server from a network distribution point or from the Windows NT Server CD-ROM.

To perform an upgrade or to install a new version of Windows NT Server, use the winnt32 /b command from the Windows NT Server command prompt.


Running Setup in Unattended Mode
New Programs and Features	5 of 22

Running Setup in Unattended Mode

The unattended setup mode allows you to install or upgrade Windows NT Server without being present. It also eliminates the need for Setup floppy disks because the necessary files are temporarily copied to your computer during Setup. Therefore, you may need to free additional space on the computer’s hard disk.

Unattended Setup mode saves time when performing new installations of Windows NT Server on five or more computers or when upgrading Windows NT Server on one or more computers.

To run Setup in unattended mode, the answers to all Setup questions, including the questions asked about accepting the license agreement, must be provided in an answer file that you create before running Setup.

For more information about installing Windows NT Server using the unattended Setup mode, see the UNATTEND.TXT file on the Windows NT Server CD-ROM in the \I386, \ALPHA, \MIPS, or \PPC directories.

Note that floating-point division error detection is not performed during an unattended Setup. To determine if your system exhibits the floating-point division error, run the pentnt utility after Setup completes. For more information about the pentnt utility, see “Detecting and Correcting the Floating-Point Division Error,” later in this chapter.

Performing Unattended Upgrades

To perform an unattended upgrade, use the winnt32 command with the /u parameter. The /u parameter indicates unattended Setup. Specifying an answer file in the command is optional because the Setup program can use the existing information on your system.

Be sure to consult the UNATTEND.TXT file for more complete information about controlling the unattended upgrade operation.

For more information about using the winnt32 command, see “Starting Setup on an x86-Based Computer,” in Chapter 1, “Installing Windows NT Server,” of the Windows NT Server Installation Guide.


Detecting and Correcting the Floating-Point Division Error
New Programs and Features	6 of 22

Detecting and Correcting the Floating-Point Division Error

The Setup program also has been changed to automatically detect the Intel Pentium processor’s floating-point division error. If the error is detected on your system, Setup prompts you to indicate whether you want to disable the floating-point hardware on the processor. If you choose not to have the floating-point hardware disabled during Setup, you have the option of doing so after Windows NT Server is installed using a command-line utility called pentnt. For more information about using the pentnt utility, see “New Command-Line Utilities,” later in this chapter or type the pentnt /? command at the command prompt.


Windows 95 Common Controls
New Programs and Features	7 of 22

Windows 95 Common Controls

Windows 95 common controls are supported in Windows NT Server 3.51. Common controls are a set of windows that are supported by the common control library. This means that the appearance of dialog boxes and toolbars in the following programs has changed in Windows NT Server 3.51:  File Manager, Print Manager, Clipboard Viewer, Command Prompt, Chat, CD Player, Media Player, and Sound Recorder.

The dialog boxes in the programs might have tabs instead of menus, or a question mark (?) is displayed in the upper right corner. If the program’s toolbar has changed, tool tips are displayed about the program’s toolbar options.


Using Tabbed Dialog Boxes
New Programs and Features	8 of 22

Windows 95 Common Controls

Using Tabbed Dialog Boxes

Select a tab to view its options.


Displaying Context-Sensitive Help About Dialog Box Options
New Programs and Features	9 of 22

Windows 95 Common Controls

Displaying Context-Sensitive Help About Dialog Box Options

If a question mark is displayed in the upper right corner of a dialog box, you can click the pointing device’s primary button to display the Help cursor. Or you can click the pointing device’s secondary button to display a What’s This? popup. You can use the Help cursor or the What’s This? popup to display context-sensitive Help information about dialog box options. Context-sensitive Help information is specific Help information about a selected option.

To view context-sensitive Help using the question mark

1.	Choose the question mark (?) button.

The Help cursor is displayed.

2.	Click an option in the dialog box to display context-sensitive Help.

Popup Help about the option is displayed.

To view context-sensitive Help using the What’s This? popup

1.	Click an option in the dialog box with the pointing device’s secondary button.

The What’s This? popup is displayed.

2.	Click the What’s This? popup with the pointing device’s primary button to display context-sensitive Help about the option.


Using Tool Tips
New Programs and Features	10 of 22

Windows 95 Common Controls

Using Tool Tips

Tool tips are displayed on some screens when a pointing device, such as a mouse, is used to point to a particular button on the toolbar. Tool tips describe the function of the particular toolbar button.


Additional Help Features
New Programs and Features	11 of 22

Windows 95 Common Controls

Additional Help Features

In addition to the change in the appearance of certain windows, the Windows 95 Help system has replaced the previous Windows NT Server Help system. The Windows 95 Help provides a new full-text search system that works with all Windows 3.1 and Windows NT Server Help files, whether or not they were specifically compiled for full-text searching. Additionally, there is a new Help window that has an Index tab and a Find tab. These tabs allow you to view the index or search within a single Help file or a group of Help files.

The new Help system doesn’t support the previous full-text search indexes (files ending with the .IND extension) that were created for Windows 3.1, Windows for Workgroups 3.11, or Windows NT Server 3.5 Help files. The first time you perform a full-text search in a Windows NT Server 3.51 Help file, you are prompted to build a full-text word list (*.FTS) file if one was not built when the system was shipped.


Performing Full-Text Searches in Help
New Programs and Features	12 of 22

Windows 95 Common Controls

Performing Full-Text Searches in Help

Performing a full-text search means that you can search for specific words and phrases in Help topics as opposed to searching for Help by category. In some instances, you can search across multiple Help files. Before you perform a full-text search, you must first build the full-text search index. The new Windows NT Server Help includes a Find Setup Wizard that aids you in setting up a full-text search file. You only need to build a full-text search word list (*.FTS) file the first time you perform a full-text search in a Help file. After that, the full-text search word list is available each time you open the Help file for which you built the word list.

To build a full-text search file

1.	Open a Help file, and then choose the Find button.

The Find Setup Wizard is displayed.

2.	Choose one of the following options:

Option		Description
Minimize database size (recommended)		Allows full-text searches of all words, but doesn’t search for phrases.
Maximize search capabilities		Allows full-text searches of all words including phrases and matching phrases, untitled topics, annotated or bookmarked topics.
Customize search capabilities		Allows you to customize how much of the maximum search capabilities you want to include.
3.	Follow the instructions in the subsequent dialog boxes that appear.

In some instances, Help files have been grouped to allow for cross-file full-text searches. The full-text search word list for these grouped files has already been created and you won’t be prompted to use the Find Setup Wizard to search.

To perform a full-text search

1.	Open a Help file, and then choose the Find button.

The Help Topics: Windows NT Help dialog box is displayed with the Find tab selected.

2.	Type the text for which you want Help.

3.	Choose one of the buttons in the dialog box to specify more options about the search.

4.	Click the Display button to see Help about a topic you have selected.

– Or –

Double-click the topic.

To search the index for keywords

1.	Open a Help file, and then choose the Search button.

The Help Topics: Windows NT Help dialog box is displayed with the Index tab selected.

2.	Type the keyword or phrase that you are looking for or select a keyword or phrase from the index list.

When building your own full-text search word lists, the information is stored, by default, wherever the Help files that you used to build your word list are located. However, if the Help files are stored on a server, in a directory where you have read-only access, the full-text search files (*.FTS) won’t be written to the read-only directory on the server; they are stored locally.

If for some reason Help was installed on a shared directory where you don’t have write access, your administrator should create the *.FTS files in the directory so that you can access them.


PCMCIA Cards
New Programs and Features	13 of 22

PCMCIA Cards

Support for certain modem cards, small computer system interface (SCSI [image]) controller cards, network adapter cards, and hard disk PCMCIA cards has been included in Windows NT Server 3.51. However, PCMCIA card and socket support has not been included. Be sure to check the Hardware Compatibility List to determine which cards and computers are supported.

To use a supported PCMCIA card, insert the card after shutting down your computer. When the computer is restarted, Windows NT Server detects the card in the socket. You must also shut down Windows NT Server before removing a PCMCIA card. Integrated Device Electronics (IDE) PCMCIA hard disks should be inserted before you install Windows NT Server.

For Windows NT Server to detect a supported SCSI or network adapter PCMCIA card, you must first load a Windows NT Server device driver, or you must configure the network adapter card before shutting down Windows NT Server to insert the card.

Before you insert a PCMCIA card, you might want to check certain applications or look for a particular key in the Registry so that after the card is inserted, you can verify that Windows NT Server detected the card. For more information about using supported modem, SCSI, and network adapter PCMCIA cards, and verifying their installation, see the following sections. For more information about viewing the Registry, see the procedure “To view the Registry,” later in this chapter. For additional information about using the Registry Editor, also see “Editing Registry Values,” in the README.WRI file.


Modem PCMCIA Cards
New Programs and Features	14 of 22

PCMCIA Cards

Modem PCMCIA Cards

To use a supported modem PCMCIA card, simply insert the card after shutting down Windows NT Server. When Windows NT Server is restarted, the PCMCIA card is detected. If you want to verify that the card has been detected before attempting to use it, complete the following procedure.

To verify detection of a modem PCMCIA card

1.	Before shutting down the computer, determine the number of communication ports in use on the computer by using one of the following methods:

Double-click the Ports icon in Control Panel to display the Ports dialog box.

At the command prompt, type the mode command to determine the number of communication ports that are in use.

2.	Shut down Windows NT Server.

3.	Insert a modem PCMCIA card.

4.	Restart Windows NT Server.

5.	When the computer is restarted, repeat step 1. If the PCMCIA card has been detected, an additional communication port is listed in the Ports dialog box.


SCSI PCMCIA Cards
New Programs and Features	15 of 22

PCMCIA Cards

SCSI PCMCIA Cards

For Windows NT Server to detect a supported SCSI PCMCIA card, you must first install the appropriate SCSI driver.

To configure SCSI PCMCIA cards

1.	Double-click the Windows NT Setup icon in the Main program group.

The Windows NT Setup dialog box is displayed.

2.	From the Options menu, choose Add/Remove SCSI Adapters.

The SCSI Adapter Setup dialog box is displayed.

3.	Choose the Add button.

A Setup Message is displayed warning you that Windows NT might not start correctly if you install a SCSI adapter.

For more information about installing SCSI adapters, see “Setting Up a Mass Storage Device,” in Chapter 1, “Installing Windows NT Server,” of the Windows NT Server Installation Guide.

4.	Choose the OK button.

The Select SCSI Adapter Option dialog box is displayed.

5.	Select the name of a PCMCIA SCSI adapter from the list, and then choose the Install button.

6.	In the Windows NT Setup dialog box, specify the location of the Windows NT Server distribution files, and then choose the Continue button.

Windows NT Server installs the SCSI adapter files on the computer.

The adapter you selected should be listed in the SCSI Adapters Setup dialog box.

7.	Choose the Close button.

8.	Select Exit from the Options menu in the Windows NT Setup dialog box.

 – Or –

Choose Close from the Control menu.

A Setup message notifies you that the changes you have made cannot take effect until the computer is restarted.

9.	Shut down Windows NT Server.

10.	Insert the supported SCSI PCMCIA card in the computer.

11.	Restart Windows NT Server.

Verifying SCSI Card Detection

After you have enabled and configured your SCSI PCMCIA card, but before you shut down Windows NT Server to insert the SCSI card, you might want to check the Registry for the key listed below.

HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\SCSI

Then, after you have shut down Windows NT Server, inserted the SCSI PCMCIA card, and restarted Windows NT, the Registry should show either a SCSI key that wasn’t listed before or the name of an additional SCSI device. An additional SCSI device is listed if one had already been installed on your computer. For more information about the Registry, see “Editing Registry Values,” in the README.WRI file.

Caution

The Registry Editor is intended for experienced users. Be careful when using the Registry Editor because incorrect entries made using the utility can cause system errors.

To view the Registry

1.	In File Manager, double-click the REGEDT32.EXE program in the \<systemroot>\system32 directory.

The Registry Editor dialog box is displayed.

2.	Locate the following key in the Registry:

HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\SCSI


PCMCIA Network Adapter Cards
New Programs and Features	16 of 22

PCMCIA Cards

PCMCIA Network Adapter Cards

PCMCIA network adapter cards must be configured using the Network option in Control Panel.

To configure a PCMCIA network adapter card

1.	Double-click the Network icon in Control Panel.

The Network Settings dialog box is displayed.

2.	Choose the Add Adapter button.

The Add Network Adapter dialog box is displayed.

3.	From the Network Adapter Card list, select the name of the PCMCIA adapter card you want to configure.

4.	Choose the Continue button.

The Setup Window for the card you selected is displayed. Check the documentation that accompanied the card for the correct configuration information. Enter the information or accept the default information that is displayed for the card.

5.	Choose the OK button.

The Bus Location dialog box is displayed.

6.	From the Bus Type list, select PCMCIA, and then choose the OK button.

7.	In the Windows NT Setup dialog box, specify the location of the Windows NT distribution files, and then choose the Continue button.

8.	In the Network Settings dialog box, choose the OK button.

The network adapter card must be bound to the protocols you have installed on the computer. For more information about binding network cards to protocols, see the sections starting with “Installing Network Adapter Cards,” in the Control Panel chapter of the Windows NT Server System Guide.

9.	When you have completed all your changes and have closed the Network Settings dialog box, shut down Windows NT Server.

10.	Insert the PCMCIA network adapter card.

11.	Restart Windows NT Server.


Books Online
New Programs and Features	17 of 22

Books Online

Online versions of the Windows NT Workstation or Windows NT Server books can be accessed from a CD-ROM or a network location through a new utility called Books Online. You can use Books Online to access both Windows NT Workstation and Windows NT Server manuals only if you have both products.

Books Online allows you to set the location of the online manuals. The first time you double-click the Books Online icon, you set the location of the online books. Thereafter, whenever you select the icon, you automatically open the online books if they remain at the location specified.

The Books Online icon is created in the Main program group if you performed a new installation of Windows NT Workstation or Windows NT Server. However, if you upgraded Windows NT 3.x to Windows NT Workstation 3.51 or Windows NT Server 3.51, the Books Online icon was not added to your Main program group but the Books Online utility was copied to your computer.

You can run the Books Online utility, from the command line by typing the ntbooks command, or you can use Program Manager to create a program item for the utility. For more information about creating program items, see the Program Manager chapter in the Windows NT Server System Guide. For more information about the ntbooks command, see “New Command-Line Utilities,” later in this chapter.


Console
New Programs and Features	18 of 22

Console

Console is a Control Panel option that allows you to configure the default appearance of all character-based windows (consoles) and command prompt windows.

You can use Console to do the following tasks in character-based and command prompt windows:

Change the cursor size, screen buffer size, and the position of the window.

Enable QuickEdit mode and insert mode.

Select the colors of the text and background for character-based windows and pop-ups.

Alter the font and font size displayed in the window.

The console window properties you can set using Console are identical to the properties you can set using the Properties command from the Control menu in any character-based window. However, the settings specified using the Console option apply to all console windows. The settings specified using the Properties command pertain only to that open console window or to windows with the same title. For more information about the Properties command, see “Command Prompt,” in Chapter 2, “Changes to Existing Programs and Features.”

To start Console

In Control Panel, double-click the Console icon.

The Console Windows Properties dialog box is displayed.

By default, the General Settings tab is selected when the Console Windows Properties dialog box is displayed for the first time. Thereafter, the Console Windows Properties dialog box is displayed with the last selected tab showing.

To exit Console

From the Console Windows Properties dialog box, choose the OK button to save the property settings.

 – Or –

Choose the Cancel button to cancel the settings.

Tip

You can also close the dialog box by selecting the Control menu, and then selecting Close.

Changing Cursor Size, Command History, Window Modes, and Display Options

The cursor size, command history, QuickEdit and Insert modes, and window display option (window or full-screen) are changed in the General Settings tab of the Properties dialog box.

Changing Cursor Size

The size of the cursor in a console window can be set to either small, medium, or large.

To change the cursor size

In the Cursor Size box of the General Settings tab, specify a cursor size.

Changing Command History Settings

The commands executed in a console window are stored in its command history. If you frequently use the same commands, accessing the command history can save you time because you don’t have to retype the commands each time you use them. However, the command history does use memory. By default, it is set to store 50 commands, but you can reconfigure the buffer size so that more commands can be stored.

The command history also stores commands used within character-based programs that accept buffered input, such as software program debuggers. A history buffer (temporary storage place) is created for each running program that accepts buffered input. Use the Number of Buffers option in the General Settings tab to specify the number of buffers to be created for command history.

The command history can be accessed in the following ways. You can:

Use the up and down arrow keys to recall stored commands in sequence.

Press F7 to display a pop-up box with a list of stored commands. You can then use the arrow keys to scroll through the list until the command you want is selected. Press ENTER to issue the command.

Type part of a command, and then press F8 as many times as necessary to retrieve the correct command. You can then edit the command. Press ENTER to issue it.

If you have issued the same command numerous times, command history contains each instance of the command. To maximize the number of different commands that can be retrieved, select the Discard Old Duplicates check box.

To configure the command history buffer size or number of buffers

In the Command History box of the General Settings tab, specify a new buffer size, and then specify the number of buffers to use.

Or, use the up and down arrows next to each option to change the values.

To discard duplicate stored commands from command history

In the Command History box of the General Settings tab, select the Discard Old Duplicates check box.

Changing Window Mode Settings

The QuickEdit mode enables you to use a pointing device (mouse) to cut and paste, bypassing the Edit command in the Control menu of a console window.

Insert mode enables you to insert text at the cursor. If Insert mode is not selected, text typed at the cursor replaces or overtypes existing text.

To enable or disable QuickEdit or Insert mode

In the Display options box of the General Settings tab, select the QuickEdit Mode or the Insert Mode check boxes.

Changing Display Options

Console windows can be used in either window or full-screen mode. By default, console windows open in window mode on your screen.

RISC-based computers do not support full-screen mode. For this reason, the Display Options dialog box does not appear in the Console Windows Properties dialog box if you are using a RISC-based computer.

To toggle between window and full-screen mode

Press ALT+ENTER.

To change the default window display options

In the Display options box in the Console Windows Properties window, select Full Screen.

Changing Fonts for Window Mode

You can choose from different fonts and font sizes for the console window display. When you change fonts, the window size changes to accommodate the new font size.

To change fonts for a console window or command prompt window

1.	In the Console Windows Properties dialog box, choose the Font Selection tab.

2.	In the Font box, choose a font.

3.	In the Size box, choose a size.

In the Window Preview box, view how the size of the window changes based on the font and font size you selected.

If you want to use bold fonts, select the Bold Fonts check box.

4.	Choose the OK button.

Changing Screen Size and Position

The screen buffer size is the size reserved in memory for console window’s display. The buffer size is determined by the number of characters wide multipled by the number of lines high. The position is the current window position on the screen.

Scroll bars are displayed if the current size of the window is smaller than the screen buffer size settings. You cannot resize a console window to be larger than the area set by the screen buffer settings. On x86-based computers, if you switch to full screen display, Windows NT Server displays the number of lines (25, 43, or 50) supported by your hardware that is closest to your window mode configuration.

To change the screen buffer size

1.	In the Console Windows Properties dialog box, choose the Screen Size And Position tab.

2.	In the Screen Buffer Size box, specify the width and height of the window.

The width setting determines the number of characters in width. The height setting determines how many lines are stored in memory.

3.	In the Window size box, specify the width and height of the window.

4.	In the Window Position box, specify the left and top position of the window.

If you would like the system to position the window, select the Let System Position Window check box.

5.	Choose the OK button.

Changing Screen Colors

You can specify the color of the text and background of console windows. You can also specify the color of the text and background of pop-up windows that originate from console windows. Pop-up windows (for example, command history windows) are smaller character-based windows that present information to choose from.

To change screen colors

1.	In the Console Windows Properties dialog box, choose the Screen Colors tab.

2.	Choose colors for screen text, screen background, pop-up text, or pop-up background by selecting the element you want to change, and then selecting the color you want to use.

The selections you make appear in the Selected Screen Colors or Selected Popup Colors box.

3.	Choose the OK button.


New Command-Line Utilities
New Programs and Features	19 of 22

New Command-Line Utilities

Windows NT Server 3.51 includes three new command-line utilities, pentnt, Books Online, and compact.

The pentnt utility can detect whether your computer exhibits the floating-point division error that might occur on computers that have a Pentium processor. The floating-point division error does not affect the operation of Windows NT Server 3.51.

The Books Online utility enables you to point to the online manuals for Windows NT Workstation 3.51 or Windows NT Server 3.51.

The compact utility displays and alters the compression of files on NTFS partitions.


Pentnt Utility
New Programs and Features	20 of 22

New Command-Line Utilities

Pentnt Utility

If your system contains the Pentium processor and you are concerned about the floating-point division error, you can use the pentnt utility to detect and correct the floating-point division error. The utility is able to correct the floating-point division error by both disabling the floating-point hardware on the processor and by emulating the operation of the floating-point hardware (floating-point emulation).

If your system exhibits the floating-point division error, the pentnt utility provides two ways to disable floating-point hardware and turn on floating-point emulation.

Conditional emulation is used to disable the hardware and turn on floating-point emulation if the floating-point division error is detected on your system. Conditional emulation is implemented by specifying a -c parameter with the pentnt command. For example, at the command prompt type:

pentnt -c

Forced emulation is used to disable the hardware and turn on floating-point emulation even if the floating-point division error isn’t detected on your system. Forced emulation is implemented by specifying a -f parameter with the pentnt command. For example, at the command prompt type:

pentnt -f

For more information about the pentnt utility and its parameters, type the pentnt /? command at the command prompt.


Books Online Utility
New Programs and Features	21 of 22

New Command-Line Utilities

Books Online Utility

The Books Online utility enables you to point to the online manuals for Windows NT Workstation 3.51 or Windows NT Server 3.51. You can use the ntbooks command to access both Windows NT Workstation and Windows NT Server manuals only if you have both products.

The Books Online utility has an associated icon called Books Online. However, if you are upgrading to Windows NT Workstation 3.51 or Windows NT Server 3.51, this icon is not automatically created in your Main program group. For more information about the Books Online icon, see “Books Online,” earlier in this chapter.

You can use the ntbooks command to access the manuals from a CD-ROM or a network location. In either case, the last path you specify with the ntbooks command is stored in memory. However, the last path is not displayed.

The next time you type the ntbooks command at the command prompt, the utility automatically activates the CD-ROM drive, if that’s the last place you accessed the online manuals. If the CD-ROM is not in the drive, you are prompted to insert the CD-ROM.

If the last location you specified using the ntbooks command was a network location or a directory on your computer, this location is stored in memory by the Books Online utility.

The following table lists the parameters you can use with the ntbooks command:

Parameter	Description

/s or /server	Forces the utility to access the Windows NT Server books even though you installed Windows NT Workstation.

/n  	Indicates that you are providing a new location for the online books. If this parameter is used, the last connection made is replaced by the new location.

/w or /workstation	Forces the utility to access the Windows NT Workstation online books even though you installed Windows NT Server.


Compact Utility
New Programs and Features	22 of 22

New Command-Line Utilities

Compact Utility

The compact utility is the command line version of the compression functionality in File Manager. The compact command displays and alters the compression of files on NTFS partitions. It also displays the compression state of directories.

For information about using File Manager to compress files on NTFS partitions, see “File Compression on NTFS Partitions,” in Chapter 2, “Changes to Existing Programs and Features.”

The compression state of a directory determines whether files moved to the directory are compressed automatically. Therefore, if you choose to compress a directory or subdirectory, you are actually indicating that you want any files moved to the directory or subdirectory to be compressed automatically.

Compressing a directory means that the existing files in the directory retain their compression state (either compressed or not compressed). However, files moved to the compressed directory are compressed automatically.

If you choose to decompress a directory, or if you choose not to compress a directory, files moved to the directory are not compressed or decompressed automatically. Compressed files in the directory are not automatically decompressed, either. And existing files in the directory or files moved to the directory can still be compressed individually.

You cannot use the compact utility to read, write, or load volumes that have been compressed using the DriveSpace [image] or DoubleSpace [image] disk compression utilities included with the MS-DOS operating system.

The following table lists some of the parameters you can use with the compact command.

For more information about compact and its parameters, type the compact /? command at the command prompt.

Syntax	Description

/c /s	Compresses the files in the current directory and all subdirectories. Additionally, the compressed attribute is set on the current directory and all its subdirectories, which causes files that are moved to these directories at a later time to be compressed automatically. Files that are already compressed are unmodified.

/c /s C:\TMP\*.BMP	Compresses all files that end with the filename extension .BMP in the \TMP directory and all subdirectories of \TMP. The compressed attribute of these directories is not modified unless one of the directories ends with the filename extension .BMP.

/c /f C:\filename	If the system crashes during a compression operation, the file that was being compressed may be left in a partially compressed state. Such a file already has the compressed attribute set, so the /f parameter is required to force the file data to be recompressed in its entirety.

/u C:\TMP	Removes the compressed attribute from the directory C:\TMP. Files created in this directory afterward are not compressed unless the user takes explicit action to compress them. Files currently in the C:\TMP directory are unaffected; if any are compressed before the operation, they are still compressed afterward.


Selecting and Accepting an Appropriate Licensing Mode

Alternatives to Using 5.25 Inch Setup Floppy Disks

Running Setup in Unattended Mode

Detecting and Correcting the Floating-Point Division Error


Changes to Existing Programs and Features
Chapter 2	1 of 18

Changes to Existing Programs and Features

This chapter addresses the changes that have been made to the following programs and features:

Command Prompt.  The property settings for command prompt windows can be configured using the new Properties command, which has been added to the command prompt window’s control menu.

Command-Line Utilities.  The functionality of the format and route command-line utilities has changed.

File Manager.  Windows NT file system (NTFS) file compression functionality has been added to Windows NT Workstation and Windows NT Server.

Print Manager.  A new dialog box has been added to change the tray/form assignment of a PostScript printer.

Registry Size.  The maximum Registry size can be changed using the System option in Control Panel.

Schedule Service.  The cmd command does not load by default.

Sound Recorder.  A new Properties command has been added to Sound Recorder’s File menu.

Telnet.  New functionality has been added which enables Telnet to output command operations to a log file.

Uninterruptible power supply (UPS).  Administrators cannot specify command files that require user input.

User Manager For Domains.  User profile paths can be assigned to the user accounts in the security database of a Windows NT Workstation.

User Profile Editor.  Logon scripts can complete execution before Program Manager starts.


Command Prompt
Changes to Existing Programs and Features	2 of 18

Command Prompt

The command prompt window functions as it always has, except that it cannot be used to configure the default settings for all character-based windows. This task is now done using Console, a new Control Panel option. For more information about Console, see “Console” in Chapter 1, “New Programs and Features.”

While most of the command prompt’s functionality remains unchanged, a new Properties command has been added to its control menu. As always, you can configure the property settings for command prompt windows or character-based windows (called consoles) that have the same title as the open command prompt window.

The Properties command enables you to configure the following types of settings: cursor size, command history, fonts, screen size and position, and screen colors.


Opening and Closing the Command Prompt Window
Changes to Existing Programs and Features	3 of 18

Command Prompt

Opening and Closing the Command Prompt Window

To open the command prompt window

Double-click the Command Prompt icon in the Main program group.

By default, the command prompt opens as a window on the screen.

To close the command prompt window

From the Control menu, choose Close.


Choosing Control Menu Commands
Changes to Existing Programs and Features	4 of 18

Command Prompt

Choosing Control Menu Commands

To choose a command in a command prompt window

Click the Control box in the command prompt window.

 – Or –

Press ALT+SPACEBAR.

The Control menu is displayed, and you can choose a command from the menu.


Choosing the Properties Command
Changes to Existing Programs and Features	5 of 18

Command Prompt

Choosing the Properties Command

The Properties command enables you to change the settings, fonts and font size, and screen size, color, and position of the open command prompt window.

When you choose the Properties command, the “Command Prompt” Properties dialog box is displayed.

For more information about the options in the “Command Prompt” Properties dialog box, see “Console” in Chapter 1, “New Programs and Features.”

The settings for each of the properties are stored based on the initial window title. The settings for each command prompt window are independent for each unique title. This allows you to have different defaults for different needs.

For example, suppose you configure the character-based window Command, and then save the properties for windows with the same title. When you open another window titled Command, the window appears exactly as the  window titled Command appeared. The configuration of all windows titled Command is the same.

To save settings for command prompt windows

1.	Choose Properties from the Control menu, and then configure the settings of the open command prompt window.

2.	Choose the OK button.

3.	In the Apply Properties dialog box, select Apply Properties To Current Window only if you want your selections to be reflected in the current window.

 – Or –

If you want your settings to be saved for future windows with the same title, select Save Properties For Future Windows With Same Title.

4.	Choose the OK button.

For more information about the command prompt, also see Chapter 9, “Command Prompt,” in the Windows NT Workstation System Guide or Windows NT Server System Guide.


Changed Functionality for Command-Line Utilities
Changes to Existing Programs and Features	6 of 18

Changed Functionality for Command-Line Utilities

The functionality of the following command-line utilities has been changed.

Format.  You cannot create new high performance file system (HPFS) partitions using the format command. Support for creating HPFS partitions has been removed from Windows NT Workstation and Windows NT Server versions 3.51. For more information about the format command, type format /? at the command prompt.

Route.  A new parameter, -p, has been added to the TCP/IP route command that enables you to specify persistent IP routes. The -p parameter, when used with the add command, indicates that you want the IP route to be preserved when the computer is restarted. Using this parameter with the print command displays all routes that are marked as persistent.

For more information about the route command, type route /? at the command prompt. For additional information about TCP/IP and its utilities, see Chapter 4, “Supplemental Information About TCP/IP.” Also, see TCP/IP online Help.

If you have Windows NT Server, also see the Windows NT Server TCP/IP book and Chapter 5, “Microsoft TCP/IP,” in the Windows NT Server Installation Guide.

If you have Windows NT Workstation, see Chapter 5, “Microsoft TCP/IP,” in the Windows NT Workstation Installation Guide.


File Compression on NTFS Partitions
Changes to Existing Programs and Features	7 of 18

File Compression on NTFS Partitions

Files on NTFS partitions can be compressed and decompressed using File Manager or a command-line utility called compact. For more information about the compact utility, see “New Command-Line Utilities” in Chapter 1, “New Programs and Features.”

To compress or decompress files using File Manager

Select one of the following methods.

Select the files, and then select Compress or Uncompress from the File menu.

Select the files you want to compress or decompress. From the File menu in File Manager, choose Properties to display the Properties dialog box, and then select the Compressed check box.

The Properties dialog box can also be used to view the compressed size and compression ratio of a selected file.

Select the files you want to compress or decompress, and then click the Compress or Uncompress buttons on the File Manager toolbar.

The compress and uncompress buttons are displayed on the File Manager toolbar only if you customized the File Manager toolbar.

For more information about customizing the File Manager toolbar, see “Customizing the Toolbar,” in the File Manager chapter of the Windows NT Workstation System Guide or Windows NT Server System Guide.


Compressing and Decompressing Directories and Subdirectories
Changes to Existing Programs and Features	8 of 18

File Compression on NTFS Partitions

Compressing and Decompressing Directories and Subdirectories

When you compress a directory or subdirectory, you are indicating that you want any files added to the compressed directory or subdirectory to be compressed automatically.

Decompressing a directory or subdirectory does not mean that compressed files in the directory are decompressed automatically. Decompressing a directory or subdirectory means that files moved to the directory or subdirectory retain their compression state, which is either compressed or uncompressed.

Existing files or subdirectories in compressed or decompressed directories retain their compression state unless you indicate that the compression state should be changed when the directory is compressed or decompressed. When directories are compressed or decompressed, File Manager prompts you to indicate whether all the existing files and subdirectories in the selected directory should be compressed or decompressed.

Other file operations can be performed during compression and decompression.

Note

Compressed files, directories and subdirectories are displayed in blue in File Manager. Therefore, do not configure your desktop to use a blue background or blue text.


Moving and Copying Files Within NTFS Partitions
Changes to Existing Programs and Features	9 of 18

File Compression on NTFS Partitions

Moving and Copying Files Within NTFS Partitions

On an NTFS partition, if you move a file from one directory to another, the compression attribute, like any other attribute of the file, is retained regardless of the compression of either the target or source directory. For example, if you move a file that is not compressed to a compressed directory, the file is not automatically compressed when it is moved to the compressed directory.

However, if you copy a file from one directory to another, the compression attribute of the file is changed to that of the target directory. For example, if you copy a compressed file to a directory that is not compressed, the file is automatically decompressed when it is copied to the directory.

Files moved or copied from another file system to NTFS always inherit the compression attribute of the target directory.


New Appearance of the Customize Toolbar Option in File Manager
Changes to Existing Programs and Features	10 of 18

New Appearance of the Customize Toolbar Option in File Manager

You can customize the File Manager toolbar to include the Compress and Uncompress buttons. You also have several other buttons that you can add to the toolbar. You can remove buttons from the toolbar, as well.

The procedures for customizing the File Manager toolbar have not changed. However, Windows 95 common controls are now included in the Customize Toolbar dialog box. For information about using the common controls, see “Windows 95 Common Controls,” in Chapter 1, “New Programs and Features.”


Changing the Tray/Form Assignment of a PostScript Printer
Changes to Existing Programs and Features	11 of 18

Changing the Tray/Form Assignment of a PostScript Printer

The PostScript [image] Printer Setup dialog box has been changed within Print Manager. This dialog box is used to change the tray/form assignment of a PostScript printer. For more information about setting up a printer, see “Setting Printing Options,” in the Print Manager chapter of the Windows NT Workstation System Guide or Windows NT Server System Guide. You might also want to consult Print Manager online Help.

To access the dialog box for an existing printer

1.	Double-click the Print Manager icon in the Main program group.

2.	From the Printer menu, select Properties.

The Printer Properties dialog box is displayed.

3.	Choose the Setup button.

The PostScript Printer Setup dialog box is displayed.

By default, when you create a printer, all the paper trays are assigned to a letter-size form. Also by default, the paper tray that feeds the printer is automatically selected by the printer (Auto Select). To determine which tray the printer will feed from, check the PPD (PostScript Printer Data) file that accompanied the printer.

To change the paper tray/form assignment

1.	In the PostScript Printer dialog box, select the tray/form that you want to change.

2.	Choose the Change button.

 – Or –

Double-click the tray/form assignment.

The Change Form Assignment dialog box is displayed.

3.	In the Form In Cassette box, select the form that you want to be assigned to the tray.

4.	Choose the OK button.

The PostScript printer dialog box shows the new tray/form assignment with an asterisk(*) next to the form that will be fed only from the selected tray.

Selecting the Draw Form From Selected Tray Only check box means that even if the same form is assigned to multiple paper trays, only the forms with asterisks are fed to the printer.

For example, for the printer shown, all letter-size print jobs are fed only from the cassette paper tray even if the manual feed has letter-size paper in it.

Note that if you don’t have permission to administer the printer, you can only view the tray/form assignment. The Change button and the Draw Form From Selected Tray Only check box is disabled.


Setting Maximum Registry Size Using the System Option
Changes to Existing Programs and Features	12 of 18

Setting Maximum Registry Size Using the System Option in Control Panel

To increase the number of user and group accounts that is supported on a Windows NT Server domain, change the maximum amount of space that can be consumed by registry data. Setting the maximum registry size can be done in both Windows NT Workstation and Windows NT Server. However, specifying the maximum registry size is most useful for Windows NT Server primary and backup domain controllers.

You can set the maximum registry size using the Virtual Memory button in the System option of Control Panel.

To set the maximum registry size

1.	In Control Panel, double-click the System icon.

The System dialog box is displayed.

2.	Choose the Virtual Memory button.

The Virtual Memory dialog box is displayed.

3.	In the Registry Size box, type the maximum registry size.

By default, the maximum registry size is 25 percent of the paged pool size.

If you do not have the Increase Quotas user right, the changes to the maximum registry size cannot take effect until the next time the computer is restarted. You can grant yourself this right using User Manager in Windows NT Workstation or User Manager for Domains in Windows NT Server. For more information, see “Managing the User Rights Policy,” in the User Manager chapter of the Windows NT Workstation System Guide. In the Windows NT Server System Guide, see the User Manager for Domains chapter. Increase Quotas is an advanced user right.

You can also use the Registry Editor to adjust the maximum registry size by modifying the REG_DWORD value of the following key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\RegistrySizeLimit

For more information about viewing the Registry, see the procedure “To view the Registry,” in Chapter 1 “New Programs and Features.” For additional information about using the Registry Editor, also see “Editing Registry Values,” in the README.WRI file.


Schedule Service
Changes to Existing Programs and Features	13 of 18

Schedule Service

The command interpreter, cmd, is no longer loaded by default when running the schedule service. However, certain commands, for example, dir, copy, and > or >> (redirection) do not work without cmd.

When you use the at command, you should also specify the cmd command with it unless you are scheduling an executable file (a file with the .EXE extension) to run.

Use the syntax shown in the following examples:

cmd /c dir > c:\test.out

cmd /c f: & cd directory name > batch.out

Note

If you do not include the /c parameter with the cmd command, the command interpreter terminates when the operation is completed. The command interpreter continues to use resources until the computer is restarted.

When using the at command from the command line with redirection and/or conditional processing symbols, you must include the command in quotes. See the following examples.

Example with redirection symbols:

at 14:30 "cmd.exe /c dir > c:\dir_out.log"

Examples with conditional processing symbols:

at 14:45 "cmd /c f: & cd directory name > batch.out"

at 14:30 "cmd.exe /c copy c:\*.log d:\old_logs\*.* || net send other 'copy failed'"


Converting a Recorded Sound Using Sound Recorder
Changes to Existing Programs and Features	14 of 18

Converting the Format of a Recorded Sound Using Sound Recorder

Sound Recorder has a new Properties command in its File menu. Selecting Properties displays the properties of a specified sound file. Properties also enables you to convert the sound format of a file.

To convert the format of a recorded sound

1.	From the File menu, select Properties.

The Properties For Sound dialog box is displayed.

2.	In the Choose From box, specify whether you want to choose from all formats, playback formats, or recording formats.

3.	Choose the Convert Now button.

The Sound Selection dialog box is displayed.

4.	Specify the Name, Format, and Attributes options in this dialog box. Then choose Save As if you want to save the settings to a file.

5.	Choose the OK button.

6.	In the Properties For Sound dialog box, choose the OK button.

For more information about Sound Recorder, see Sound Recorder online Help.


Creating a Telnet Log File
Changes to Existing Programs and Features	15 of 18

Creating a Telnet Log File

The telnet utility now enables you to capture the screen output of your telnet session to a log file. For more information about the telnet utility, see TCP/IP online Help. If you have Windows NT Server, also see the “Utilities Reference” chapter of the Windows NT Server TCP/IP manual.

For additional information about TCP/IP and its utilities, see Chapter 4, “Supplemental Information About TCP/IP.”

To create a telnet log file

1.	Double-click the Telnet icon in the Accessories program group.

The Telnet dialog box is displayed.

2.	From the Terminal menu, select Start Logging.

The Open log file dialog box is displayed.

By default, TELNET.LOG is the filename that is listed in the File Name box. Telnet log files are not required to use a .LOG filename extension.

If you want to write the log file to a remote computer, choose the Network button.

3.	Type a log filename in the File Name box.

4.	Choose the OK button.

The command and the command output are written to the filename that you specified.

Note that if you select the same filename repeatedly, the existing information in the log file is overwritten. Two or more log files can be combined from the command line.

To stop logging commands and command output, select Stop Logging from the Terminal menu.


Uninterruptible Power Supply
Changes to Existing Programs and Features	16 of 18

Uninterruptible Power Supply

The uninterruptible power supply (UPS) option in Control Panel allows administrators to specify a command file to run immediately before shutting down the operating system. However, administrators can no longer specify a command file that causes a dialog box to appear.

Dialog boxes can require user input and would therefore impede a graceful shutdown of the system.


User Profile Paths for User Accounts Using User Manager
Changes to Existing Programs and Features	17 of 18

Assigning User Profile Paths for User Accounts Using User Manager for Domains

This information pertains only to Windows NT Server.

In earlier versions of Windows NT Server, User Manager for Domains would allow user profile paths to be assigned for user accounts in the security database of a Windows NT Server domain only.

User Manager for Domains can now be used to assign user profile paths for user accounts in the security database of a Windows NT Workstation.

User Manager (Windows NT Workstation) does not enable you to administer user profile paths. However, user profile paths on Windows NT Workstations could always be administered with the net user (net.exe) command.

For more information about User Manager for Domains, see Chapter 13, “User Manager for Domains,” in the Windows NT Server System Guide.

For more information about User Manager, see Chapter 13, “User Manager,” in the Windows NT Workstation System Guide.

To assign user profile paths for user accounts on a Windows NT Workstation

1.	Double-click the User Manager for Domains icon in Administrative Tools.

2.	From the User menu, select Select Domain.

The Select Domain dialog box is displayed.

3.	In the Domain box, type the name of the workstation whose user accounts you want to modify.

Note

Be sure to precede the workstation name with two backslashes (\\).

4.	Choose the OK button.

5.	Select the user accounts you want to modify. Then select Properties from the User menu.

6.	In the User Properties dialog box, choose the Profiles button.

7.	Enter the profile path (using %USERNAME%, if appropriate) in the User Profile Path box, and then choose the OK button.

The User Profile Path field would have been disabled on earlier versions of Windows NT Server.


Controlling Logon Script Execution Using User Profile Editor
Changes to Existing Programs and Features	18 of 18

Controlling Logon Script Execution Using User Profile Editor

Logon scripts can now run asynchronously or synchronously during the logon process. The scripts run synchronously when you select the new Wait for Logon Script to Complete Before Starting Program Manager check box in the User Profile Editor dialog box.

If you select the Wait for Logon Script to Complete Before Starting Program Manager check box, when a user logs onto the domain, the user’s logon script completes before Program Manager starts. This situation allows the logon script to map network drives and copy files that Program Manager can reference in the Startup group.


Windows NT Adv. Server 3.1 PDC with Windows NT Server 3.51 BDC
	Additional Information About Existing Programs and Features	1 of 4
Using a Windows NT Advanced Server 3.1 PDC with a Windows NT Server 3.51 BDC

When a Windows NT Server 3.51 backup domain controller (BDC) is in a domain with Windows NT Advanced Server 3.1 primary domain controller (PDC), the Windows NT Server 3.51 BDC disables (without notifying the administrator) the account lockout features, new user rights, and so on of the BDC until its secure channel is established with the Windows NT Advanced Server 3.1 PDC.

To avoid this situation, put the Windows NT Server 3.51 BDC and the Windows NT Advanced Server 3.1 PDC in separate domains. Or, upgrade the PDC to Windows NT Server 3.51.

When you use Windows NT Server 3.51 as the PDC, the entire system automatically acquires the added functionality that Windows NT Server 3.51 provides. If you use Windows NT Advanced Server 3.1 as the PDC, you lose the added functionality on any services provided with Windows NT Server 3.51.


Specifying Hard Disk Partitions
	Additional Information About Existing Programs and Features	2 of 4
Specifying Hard Disk Partitions

Hard disks can be partitioned. Each partition can have a different file system, such as file allocation table (FAT) or Windows NT file system (NTFS). If you want more than one file system on your hard disk, you must have more than one partition on the hard disk before you install Windows NT Workstation or Windows NT Server.

Note that support for creating high performance file system (HPFS) partitions is not available in Windows NT Workstation 3.51 or Windows NT Server 3.51.

If you are installing Windows NT Workstation or Windows NT Server on a computer with other operating systems, you should use the fdisk utility (or another comparable utility) that is included with MS-DOS to determine the number of existing partitions on the disk. If the disk has only a single primary partition, Disk Administrator cannot divide that primary partition. Disk Administrator can only divide extended partitions.

Thus, if you want multiple partitions (and file systems) and your existing hard disk has only one partition, you must use the fdisk utility to create multiple partitions prior to installing Windows NT Workstation or Windows NT Server.

For more information about specifying disk partitions, see the section “Specifying the Disk Partitions,” in Chapter 1, “Installing Windows NT Workstations” of the Windows NT Workstation Installation Guide or in Chapter 1, “Installing Windows NT Server,” of the Windows NT Server Installation Guide.

For more information about Disk Administrator, see the Disk Administrator chapter in the Windows NT Workstation System Guide or Windows NT Server System Guide.


Using a Windows for Workgroups Computer as a Browse Master
	Additional Information About Existing Programs and Features	3 of 4
Using a Windows for Workgroups Computer as a Browse Master

Windows NT Server 3.51 includes updated files, VSERVER.386, VREDIR.386, and NET.EXE, that enable a Windows for Workgroups computer on a subnetwork to act as browse master for the subnetwork. This means that a Windows for Workgroups computer on an internet protocol (IP) subnetwork with only Windows for Workgroups or Windows 95 computers can browse Windows NT Workstation and Windows NT Server domains.

As browse master for the subnetwork, the Windows for Workgroups computer shares browse lists with a Windows NT Server PDC for the entire wide area network (WAN).

The Windows for Workgroups browse master on the subnetwork performs the same tasks that a Windows NT Server browse master would if one were added to the subnetwork. The local list is uploaded to the PDC every fifteen minutes by the Windows for Workgroups computer and the global list is downloaded from the PDC. Any Windows for Workgroups computer on the subnetwork that browses the network for the merged list can obtain it from the local browse master.

For browsing to work correctly from a Windows for Workgroups computer:

You must have Microsoft transmission control protocol/internet protocol (TCP/IP) installed on the computer.

You must use the Windows Internet Name Service (WINS) for name resolution. WINS can be running on any Windows NT Server computer in the WAN.

The domain must have a PDC. The PDC must be a WINS client.

Your Windows for Workgroups computer must be in a workgroup that has the same name as the domain and must be a WINS client.

The updated files are located on the Windows NT Server CD-ROM in the \CLIENTS\WFW\UPDATE directory. Copy the VSERVER.386 and VREDIR.386 files from the Windows NT Server CD-ROM to the WINDOWS\SYSTEM directory on the Windows for Workgroups computer. Copy the NET.EXE file to the WINDOWS directory on the Windows for Workgroups computer.


Multimedia Improvements
	Additional Information About Existing Programs and Features	4 of 4
Multimedia Improvements

Video Capture

Video capture has been made faster in many circumstances because of the elimination of a data copy during normal capture-to-disk operations.

Playback

The display control interface (DCI) is supported in Windows NT Workstation 3.51 and Windows NT Server 3.51. DCI enables an application to write directly to the display’s video buffer. If a display driver supports that specification, video playback often runs smoother through fewer memory copies without requiring a context switch to the display server.

Audio Compression Manager (ACM)

Audio codecs are no longer loaded into processes that will not be using audio. This situation improves the performance of the ACM and reduces the working memory required by the ACM. The Registry use has also been improved.

Musical Instruments Digital Interface (MIDI)

In certain circumstances, significant throughput improvements have been made by moving some support code into the kernel. Fewer ring transitions are required, thereby enabling greater data rates.

Sound Recorder

Sound Recorder has been enhanced to support non-realtime compression of any format for which there is an installed audio codec. Previously, Sound Recorder would only support codecs that could record and compress in realtime. For more information, see Sound Recorder online Help.

Media Player

Media player supports the following new command-line parameters:

mplay32 [/open] [/play] [/close] [/embedding] [/WAVE] [/MIDI] [/VFW] [filename]

The following table lists the parameters you can use with the mplay32 command.

Parameter	Description

/open	Opens a specified file. If no file is specified, the Open File dialog box is displayed.

/play	Plays a specified file.

/close	Closes a specified file after playing. (Use this parameter only when using the /play parameter.)

/embedding	Runs as an OLE server.

/wave	Opens a wave file.

/midi	Opens a MIDI file.

/vfw	Opens a VFW file.

filename	Filename or device on which to perform a specified operation.

Drag and drop from Media Player now works with applications that implement OLE’s drag and drop programming/programmatic interface. However, Media Player itself doesn’t currently support the drag and drop programming/programmatic interface. For more information about Media Player, see Media Player online Help.

CD Player

Using the Preferences dialog box in CD Player, you can choose to continue playing a track after closing CD Player. The dialog box also enables you specify an introduction play length between 5 seconds and 15 seconds when you select CD Player’s intro play option. For more information about CD Player, see CD Player online Help.

CD Player can now be started from the command line by typing either the cdplayer /play command or the cdplayer /track command. When you specify the cdplayer /play command, the CD Player icon is minimized on the screen. CD Player plays the tracks in the play list if any tracks are listed. Play lists are defined using the CD Player icon.

When you specify the cdplayer /track command, the CD Player dialog box is displayed. Then, you can choose the Play button to begin playing tracks in the play list.

You can use the following parameters with the cdplayer /play command.

cdplayer /play [driveletter] [trackname]

cdplayer /play [/track | tracklist]

Parameter	Description

driveletter	The drive letter of the CD-ROM drive. Specify the drive letter, for example, cdplayer /play e: to play every track on the CD. Specify the drive letter and a backslash to play the tracks on the play list. For example, type the command cdplayer /play e:\ to play only the tracks on the play list.

trackname	Includes the driver letter of the CD-ROM and the number of the track followed by a .CDA extension. Tracknames must include the .CDA extension. For example, type the command e:\track09.cda.

/track	Plays tracks in the specified track list. A track list contains one or more track names. It overrides any play list that might already be stored for the current CD. The /play parameter must precede the /track parameter.

tracklist	A list of tracknames to play. Each trackname must be preceded with the drive letter of the CD.

For example, to play track number 8 from a disc contained in the E: drive, type the following command at the command prompt:

cdplayer /play e:\track08.cda

To play track numbers 9, 1, and 3, type the following command at the command prompt:

cdplayer /play /track e:\track09.cda e:\track01.cda e:\track03.cda

where e:\track09.cda e:\track01.cda e:\track03.cda comprise the track list.


Supplemental Information About TCP/IP
Chapter 4	1 of 11

Supplemental Information About TCP/IP

The following information was not included in the Windows NT Server 3.5 TCP/IP manual. Also note that Simple Network Management Protocol (SNMP), Windows Internet Name Service (WINS) Servers, and Dynamic Host Configuration Protocol (DHCP) Servers are Windows NT Server features only.

If you have Windows NT Workstation, see Chapter 5, “Microsoft TCP/IP,” in the Windows NT Workstation Installation Guide. Also see TCP/IP online Help.


SNMP
Supplemental Information About TCP/IP	2 of 11

SNMP

This information pertains only to Windows NT Server.

Installing SNMP

Although the Windows NT Server SNMP service supports managing consoles over both the Internet Package Exchange (IPX) protocol and User Datagram Protocol (UDP), SNMP must be installed in conjunction with the other TCP/IP services. No additional configuration is needed to manage over IPX once SNMP is installed. If IPX is installed, SNMP automatically runs with it.

Additional configuration might be the addition of IPX addresses for trap destinations or for permitted hosts. The addresses can be entered using the Network option in Control Panel. In the Network Settings dialog box, select the SNMP service, and then choose Configure. You can set trap destinations in the SNMP Configuration dialog box. To set permitted hosts, choose Security.

The addresses should be entered in an 8.12 format. For example, XXXXXXXX.YYYYYYYYYYYY where X represents the network number and Y represents the network address of the computer.

Using SNMP with DHCP and WINS Servers

DHCP servers can be monitored, but not configured, using SNMP. WINS servers can be configured and monitored using SNMP. Most DHCP and WINS configuration parameters can be set using SNMP.

However, all of the DHCP and WINS parameters can be set using the Registry Editor. Management information base (MIB) objects are used to access various WINS configuration parameters. Each of the WINS configuration parameters is accessible as a managed object in the WINS MIB. For more information about the configuration parameters, see the Windows NT Server 3.5 TCP/IP manual. Also see the manual for a description of the related MIB object types. For more information about the Registry Editor, see “Editing Registry Values” in the README.WRI file.


WINS Servers
Supplemental Information About TCP/IP	3 of 11

WINS Servers

This information pertains only to Windows NT Server.

Lowering the Refresh Time Interval

Do not lower the refresh time interval just before upgrading the WINS server. It might cause some of the names in your database to be prematurely deleted.

Record Expiration

Expiration of the record means different things, depending upon the ownership of the record.

If the record is owned by the WINS server to which WINSADMN is connected, the record undergoes a change of state (or deletion if the record is extinct) at the time indicated in the timestamp unless the record is renewed. Static records never expire.

If the record is owned by another WINS server, upon expiration the record is revalidated at the time indicated by the timestamp. The record is deleted if it does not exist in the database of the WINS server that owns the record.

Assigning an IP Address to a WINS Computer

A computer running the WINS server should be assigned a fixed IP address. The WINS server computer should not be a DHCP client. If the WINS server computer has more than one network adapter card, make sure the binding order of IP addresses is not disturbed.

WINS always binds to the first network adapter card in the list of adapters bound by TCP/IP. Make sure that this network adapter card address is not set to 0.

Setting Renewal Intervals

The default renewal interval value for records in the WINS database is four days. WINS clients register and refresh every two days. These default settings reduce network traffic and allow WINS to increase its service to more nodes. It is not recommended that you change the default settings. It is highly recommended that the primary and backup WINS servers have the same renewal interval value.

Setting Time Intervals

The extinction interval, the extinction timeout interval, and the verify interval are derived from the specified refresh interval and the replication time interval. The WINS server adjusts the values specified by the administrator to ensure that the window of inconsistency between the databases at the WINS server and its partners remains small.

The extinction interval cannot be set to a value greater than four days.

The extinction timeout interval cannot be set to a value less than one day.

Database Initialized

The Database Initialized option in the WINS Manager dialog box is incorrectly defined in the Windows NT Server TCP/IP manual. The manual defines the option as the time when this WINS database was initialized. The correct definition of the Database Initialized option is the most recent time when static mappings were imported from a file into this WINS database.

Primary and Backup WINS Servers Must Replicate with Each Other

The primary and backup WINS servers must both be push and pull replication partners with each other in order for the databases to remain consistent.

Setting Replication Time Interval

The value of the replication time interval should be the same as, or less than, the lowest refresh time interval that is set on any of the replicating WINS servers.

Blocking Partners’ Records in WINS

You can specify WINS servers whose records should not be inserted into the local database during pull replication with other WINS servers.

To block one or more partners’ records during replication with other WINS servers, use the Registry Editor to set the PersonaNonGrata entry under the following Registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Wins\Partners

The following table describes the values for this entry:

Entry 	Value

Name	PersonaNonGrata

Data type	REG_MULTI_SZ

Description	Specify the IP addresses of owners (WINS servers) whose records should not be inserted into the database of the WINS server during pull replication.

Range 	None

Default value 	None

Automatic Partner Configuration

You can instruct the WINS server to configure itself automatically for replication. WINS servers announce their presence through periodic announcements. If you set up a WINS server for automatic replication configuration, it monitors for these announcements and adds the IP addresses of any new WINS servers it finds as both push and pull partners. It performs pull replication every 2 hours.

If a WINS server was discovered through multicasting, it is removed as a partner after it terminates gracefully, unless the administrator has made changes to or simply touched this WINS server’s partnership-related information in the Registry using WINS Manager.

UseSelfFndPnrs

Use the Registry Editor to set the UseSelfFndPnrs entry under the following Registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Wins\Parameters

The following table describes the values for this entry:

Entry	Value

Name	UseSelfFndPnrs

Data type	REG_DWORD

Description	If the parameter is set to 1 and network routers support multicasting, the WINS server automatically finds other WINS servers on the network and configures them as push and pull partners. If the parameter is set to 1 and network routers do not support multicasting, the WINS server finds only those WINS servers that are on its own subnetwork.

Range 	0 or 1

Default value 	0

McastIntvl

Use the Registry Editor to set the McastIntvl entry under the following Registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Wins\Parameters

The following table describes the values for this entry:

Entry	Value

Name	McastIntvl

Data type	REG_DWORD

Description	This parameter specifies the time interval (in seconds) at which the WINS server sends a multicast announcement to announce its presence to other WINS servers.

Range 	The minimum allowable value is 2400 seconds (40 minutes).

Default value 	2400 (seconds)

McastTtl

Use the Registry Editor to set the McastTtl entry under the following Registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Wins\Parameters

The following table describes the values for this entry:

Entry	Value

Name	McastTtl

Data type	REG_DWORD

Description	This parameter specifies the number of jumps across a router that a WINS multicast announcement can take.

Range	1 to 32

Default value 	6

Setting the Update Count

The minimum number of updates to a WINS database before a push notification is sent to a partner is now 20.

Using SNMP to Query WINS

When querying a WINS server, it might be necessary to increase the SNMP timeout on the SNMP administration tool that is being used. If some WINS queries work, and others time out, the timeout should be increased.

Pausing WINS

You can pause and continue the WINS service using the Services option in Control Panel or by typing the net pause wins command at the command prompt. When paused, the WINS server does not accept name packets from clients. This situation enables a WINS administrator to prevent a client from using the WINS server while the administrator continues the administration, replication, and scavenging of old records.

Priority Class

You can specify the priority class of WINS in the Registry. Only the high and normal priority classes are valid for WINS. This situation is useful if you want WINS running in high priority class to ensure that other processes, such as electronic mail or other applications, do not preempt WINS. The default priority class of a WINS server is normal.

Use the Registry Editor to set the PriorityClassHigh entry under the following Registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Wins\Parameters

The following table describes the values for this entry:

Entry	Value

Name	PriorityClassHigh

Data type	REG_DWORD

Description	Specifies the priority class of WINS. Set to 1 for high priority class. The priority class can be changed without restarting the WINS computer.

Range 	0 to 1

Default value 	0

Number of Worker Threads

By default, WINS creates as many worker threads (to handle name query packets from clients) as the number of processors on the system. You can change this situation in the Registry.

Use the Registry Editor to set the NoOfWrkThds entry under the following Registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Wins\Parameters

The following table describes the values for this entry:

Entry	Value

Name	NoOfWrkThds

Data type	REG_DWORD

Description	Specifies the number of worker threads. This situation can be changed without restarting the WINS computer.

Range	1 to 40

Default value 	Number of processors in computer

Pause Until First Replication

You can set the Registry entry to specify that WINS should start in the paused state until it has replicated with its partners (or failed in the attempt) once. After the first replication, WINS starts accepting name packets from WINS clients.

This behavior is useful if the WINS database is corrupt and cannot be restored from backup. A WINS computer must be configured with pull partners for this Registry entry to take effect.

Use the Registry Editor to set the InitTimePause entry under the following Registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Wins\Parameters

The following table describes the values for this entry:

Entry	Value

Name	InitTimePause

Data type	REG_DWORD

Description	If InitTimePause is set to 1, it is recommended that the Wins\Partners\Pull\InitTimeReplication value be either set to 1 or you remove the InitTimeReplication entry in the Wins\Parameters\Pull key. Either method ensures WINS replicates with its listed partners on starting.

Range	0 to 1

Set it to 1 to instruct WINS to remain in the paused state until the first replication.

Default value 	0

Path to Log File

You can specify the directory for WINS log files (files created by the database engine used by WINS). These files are used for recovery in case of a software failure (WINS fails and/or has abrupt termination).

Use the Registry Editor to set the LogFilePath entry under the following Registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Wins\Parameters

The following table describes the values for this entry:

Entry	Value

Name	LogFilePath

Data type	REG_SZ or REG_EXPAND_SZ

Description	Specifies the directory for WINS log files.

Range 	None

Default value 	\systemroot\SYSTEM32\WINS

Specifying the WINS Database File

You can specify the file for the WINS database file in the Registry.

To specify the WINS database file, use the Registry Editor to set the DbFileNm entry under the following Registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Wins\Parameters

The following table describes the values for this entry:

Entry	Value

Name	DbFileNm

Data type	REG_SZ or REG_EXPAND_SZ

Description	Specifies the directory for WINS log files.

Range 	None

Default value 	\systemroot\SYSTEM32\WINS.MDB

Setting the Start Version Number

You can set the start version number for WINS records using WINS Manager. This number is not accepted by WINS if it is set to more than 231. Also note that WINS might adjust the value you specify to a higher one to ensure that database records are replicated to other WINS servers quickly. Typically, the adjustment is in the range of 0 to 500.

Performing a Periodic Backup

If a backup directory path has been specified via WINSADMN (in the Advanced Configuration dialog box), WINS performs a full backup of its database every 24 hours to that directory.

Compacting WINS and DHCP Databases

The WINS and DHCP database files (that is, the .MDB files) expand over time and need to be compacted using the jetpack utility. It is recommended that the administrator compact the database files whenever they expand to more than 30 MB for WINS or above 10 MB for DHCP. Doing it earlier, though, would also improve performance. If a database is not compacted for long periods of time, performance degradation can occur.

Compaction can be started only after the WINS and DHCP services have been stopped. For example, to compact the WINS and DHCP databases, use the following procedure.

To compact WINS or DHCP database files

1.	Type one of the following commands at the command prompt to stop the WINS or DHCP services respectively.

net stop wins

 – Or –

net stop dhcpserver

2.	Change to the directory where the WINS database (WINS.MDB) or DHCP database (DHCP.MDB) is stored.

The default location of the WINS database is
\systemroot\SYSTEM32\WINS.MDB.

The default location of the DHCP database is
\systemroot\SYSTEM32\DHCP.MDB.

3.	Type one of the following commands at the command prompt to compact the WINS or DHCP databases respectively.

jetpack wins.mdb wins.tmp

 – Or –

jetpack dhcp.mdb dhcp.tmp

Note

Do not compact the SYSTEM.MDB database file because the configuration information for the WINS and DHCP databases can be corrupted.

The size of the WINS and DHCP database files depends on the number of records contained in them. This number is dependent upon the number of nodes in the network.

The databases expand over time as a result of WINS server and DHCP server activity. This expansion is caused by the fragmentation of deleted space.

The rate of growth in a WINS database depends upon the following:

The number of WINS clients in the network serviced by one or more WINS servers

The number of domains and domain controllers in the network

The number of multihomed nodes in the network

Other parameters, such as configuration intervals and replication frequency

The rate of growth in a DHCP database depends upon the following:

The number of new DHCP clients added to the network

The lease time set on the DHCP server

The number of mobile clients that are serviced by the DHCP server on the network

The administrator can compact the WINS and DHCP databases at intervals or when each database reaches a certain size. After the administrator compacts the database, the compacted database size and growth rate can be determined. Based on a few such compactions, the administrator can determine at what interval or database-size threshold, offline compaction should be done.

For more information about the WINS and DHCP database, see the Windows NT Server TCP/IP manual.

Backup on Termination

In the Configuration dialog box in WINS Manager, there is a check box called Backup On Termination. The documentation for the 3.5 release incorrectly states that when this option is selected, the [WINS] database is backed up automatically when WINS Manager is closed. The correct statement should be that when this option is selected, the [WINS] database is backed up automatically when the WINS Service is stopped except when the system is being shutdown.

Primary Domain Controller Entries in WINS

If you have a primary domain controller (PDC) on a computer not running versions 3.51 or 3.5 of Windows NT Server, you should make a static entry for the PDC in the WINS database on the WINS server. The name entered in the WINS database should be the domain name with 1B as the 16th byte. The address should be the IP address of the PDC.

For example, suppose that the PDC’s domain is ABC, and the PDC is running on a computer with address 11.11.12.1. You should have the following line in a static initialization file (LMHOSTS, for instance) and import the file into the WINS database using WINS Manager:

11.11.12.1   "ABC        \0x1B"

Notice that ABC is padded up to the 16th byte with spaces. The 16th byte is the hexadecimal value 1B.

Notice also that you are not required to perform the preceding action if you have the PDC listed as a member of the domain in the static initialization file. However, if you put the 1B entry in the WINS database, it improves performance (that is, clients are able to find the PDC faster) and reduce network traffic.

Administrators will also want to do this because when a user changes a password, the first query is to the 1B name to find the PDC. If the WINS database does not have this name, the query goes to the 1C internet group name. The node then sends a datagram to each of the members of this group to find out which one is the PDC. If the PDC is a computer running something other than Windows NT Server 3.51 or Windows NT Server 3.5, it does not register either the 1B name or the 1C name in the WINS database. However, as stated before, the 1B name is not required. Its existence improves performance.

The following NetBIOS names with suffixes and sources are registered by different services and drivers running on Windows NT Workstation and Windows NT Server:

NetBIOS Names	Description

<computer name><00>	Redirector/machine name

<computer name><03>	Messenger service name

<computer name><20>	LAN Manager server name

<domain name><1B>	Domain master browser name

<domain name><1C>	Internet group name containing domain controllers

<domain name><1D>	Master browser name

<domain name><1E>	Group master browser election name

<username><03>	Registered by messenger service

Primary and Backup Domain Controller Entries in WINS

A computer running Windows NT Server version 3.5 or later, when designated as a primary or backup domain controller, automatically creates an internet group name entry for the domain in the WINS database with hexadecimal 1C as the 16th byte. Some WINS clients use this entry to locate domain controllers in the domain.

A computer running Windows NT Advanced Server version 3.1 does not automatically create this entry in the WINS database, so you must create a static entry. The name entered in the WINS database should be the domain name with hexadecimal 1C as the 16th byte. The address should be the IP address of the domain controller.

For example, suppose that XYZ is a backup domain controller running Windows NT Advanced Server 3.1, its IP address is 11.11.12.2, and it is in the ABC domain. You should have the following line in a static initialization file (LMHOSTS, for instance) and import the file into the WINS database using WINS Manager:

11.11.12.2   "ABC        \0x1C"

Notice that ABC is padded up to the 16th byte with spaces. The 16th byte is the hexadecimal value 1C.

Multihomed Computers

It is not recommended that the WINS service be run on a computer with two or more network cards (multihomed) on disjoint networks. Disjoint networks are networks that are not connected.

Clients that query the WINS server might not be able to reach computers with multiple network cards that access disjoint networks because the MS-DOS clients that query the WINS server always pick the first IP address supplied by the WINS server. If all the multihomed computers IP addresses are not reachable from the MS-DOS client, the client can fail to connect to the multihomed computer because the MS-DOS client might be using one of the unreachable addresses supplied by the WINS server. MS-DOS clients do not attempt to connect using a second address supplied by the WINS server.

You can configure a multihomed computer to register with different WINS servers for each adapter card. If the multihomed computer accesses two disjoint networks, the computers on either side would use the WINS server on their network to resolve names, and the WINS server would return only the IP address registered on the requesting clients network.

A larger problem arises if the multihomed computer is also running WINS since that computer always registers its names with the local WINS server. Therefore, it is not possible for a multihomed computer running WINS to register with two different WINS servers, if its adapters are on disjoint nets.

If the WINS service runs on a multihomed computer, the IP address of the WINS service corresponds to that of the first adapter to which NetBIOS over TCP/IP (NetBT) is bound. Therefore, when configuring clients’ WINS addresses, you must specify this address and not another IP address, such as that of an adapter that might be on the same subnet as the client. This task is necessary because, in some cases, the client needs to determine when the WINS service sends its messages, and WINS messages always originate from the first adapter to which NetBT is bound.


DHCP Server
Supplemental Information About TCP/IP	4 of 11

DHCP Server

This information pertains only to Windows NT Server.

For more information about DHCP Server, see the Windows NT Server TCP/IP manual.

Bootstrap Protocol (BOOTP) Clients

In this release of the DHCP server, BOOTP clients are not supported.

This statement simply means that the DHCP server does not interoperate with (that is, exchange packets with) BOOTP clients. The server simply recognizes and drops BOOTP requests. However, the DHCP server can exist on the same wire and subnet with an existing BOOTP installation. A cutover scenario can take as long as needed. The only constraint is that the address ranges distributed by the DHCP and BOOTP server must not overlap.

DHCP Database

For information about compacting DHCP databases, see “Compacting WINS and DHCP Databases" in the preceding WINS Servers section.

Database Backup and Restore

For protection, a backup of the DHCP database and database log files (the working versions are in the \systemroot\SYSTEM32\DHCP directory) is done at regular intervals and whenever the DHCP Server service is stopped, including when the computer is shut down.

When the service restarts and it detects a corrupt database, the database is restored from the \systemroot\SYSTEM32\DHCP\BACKUP\JET directory. However, there is no guarantee that a corrupt database will be caught during backup. Hence, it is recommended that the backed up database periodically be saved to another secure location.

If the DHCP Server does not seem to be working properly, and is logging database errors in the event log (see Event Viewer in the Administrative Tools group), a restore might be in order. Stopping and starting the DHCP Server service using the net stop dhcpserver and net start dhcpserver commands forces a backup and a restore if a problem is detected.

If the DHCP Server service fails to restart because of a database problem (again, check the event log), you can save off the existing database and try restarting with a backup copy that you have previously saved. However, unless you reconcile the database after restoring from a backup, new IP address leases are noted in the Registry but not in the database, and these addresses may be permanently lost from the address range. For more information about reconciling IP address leases, see “Reconciling Inconsistent IP Addresses” later in this topic.

Scope Setup

The address range chosen for a scope should not include addresses of existing statically configured computers. These addresses should either be outside the range being selected or should immediately be excluded from the range. The server does not try to figure out if an address in the range is in use; there is simply no way a server can tell about addresses that are in use by machines that are not currently connected to the network. When setting up the range of IP addresses to be leased, you must ensure that the addresses to be given out are not in use on your network.

Note that the DHCP server address must not be included in the range. The DHCP server does not check each address it leases to make sure it is not its own.

The current address range allows only a single address range (or scope) per subnet. Therefore, to implement several address ranges, create a range subnetting all of them and exclude the addresses between the intended ranges. The range can be expanded later (using the Properties command from the Scope menu) if you need more addresses, so you need only start with the range required.

The Properties command in the Scope menu does not allow you to shrink the size of the address range. However, unwanted addresses might be excluded.

For more information about scopes, see the Windows NT Server TCP/IP manual.

Infinite Leases

Although infinite IP address leases are allowed, their use is discouraged. Even in a relatively static environment, there will still be clients coming and going (such as portable computers and network adapter cards that have been replaced). Yet, once an infinite lease is granted, no administrative control exists. Recovery of an address is again a manual operation requiring you to inspect the client computer or verify that it no longer exists. Instead, use a very long lease (for example, six months). This method ensures, at least, that the addresses are ultimately recovered and the DHCP server gives a snapshot (that is no more than a lease time out of date) of current clients.

In general, if a net configuration is active (with a lot of computers being added or deleted) or address space is tight, the lease time should be kept short. If the network configuration is relatively static or there is plenty of unused address space, then the lease times can be long.

Option Defaults

Options that take an array of IP addresses as their value have a default value of 0.0.0.0. This address is obviously invalid and might cause problems with some implementations. It is recommended that you reset the default (using the Default command in the DHCP Options menu) of any of these options that you intend to use. Otherwise, be sure to remove the 0.0.0.0 default value when you set the option value in the Global or Scope option dialog box.

Option Overlays

The DHCP server does not support option overlays or expand the DHCP packet beyond 548 bytes. This situation allows more than enough space for a reasonable set of options.

Using Vendor-Specific Options

DHCP Manager cannot format the vendor-specific options that need to be distributed to clients running third-party software. However, if you know the format of the client’s vendor-specific option, you can enter the option’s binary format using DHCP Manager. Clients running Windows NT Workstation and Windows NT Server do not use vendor-specific options.

Active Leases

Selecting the Active Leases command from the Scope menu opens the Active Leases dialog box. Some of the information might be slightly confusing. The following are a few points to keep in mind.

When managing client leases, you can now also obtain information on the following.

Total addresses in scope

Active/Excluded (number and percentage)

Available (number and percentage)

This information is available by selecting the scope from the DHCP Servers list in the DHCP Manager window and then, from the Scope menu, selecting Active Leases. The three items appear at the top of the Active Leases dialog box.

Extended Leases

Leases are kept in the server database for approximately one day after lease expiration. These extended leases protect against an address being re-leased while a client is still using it because of drift in clocks or a time-zone shift. They also enable the server to continue giving a client the same address even if the client was down or off the net during lease renewal and expiration.

These extended leases show up in the client list and in the Active/Excluded count. They are distinguished by a blurry icon.

Excluded addresses are included in the Active/Excluded count, meaning you could have a large Active/Excluded count even with very few addresses leased. To get a count of actual active leases, record the exclusion count (that is, record the Active/Excluded count) before activating the scope.

Exclusions

Existing address leases block an attempt to exclude an address range. Before attempting to exclude an address range, delete the address leases, and then retry excluding the range. For more information about excluding an address range, see the Windows NT Server TCP/IP manual. For more information about deleting IP address leases, see the procedure “To delete a lease” later in this topic.

Address Resolution Protocol (ARP) Conflicts

Microsoft DHCP clients send an arp command before loading TCP/IP with an address acquired from a DHCP server. If an ARP conflict occurs, TCP/IP does not start and a popup alerts the user. These addresses should be deleted from the Active leases list, then excluded until the rogue clients are tracked down and fixed. If the address is not excluded, the DHCP server continues to offer the same conflicting address to the client each time it retries.

Reservations

A reservation is an IP address that is set aside by the server to distribute to a specified client. The reservation might also contain specific options that override those generally given out to clients in the scope. The main purpose of a reservation is to statically configure a particular host but still maintain administrative control. The most obvious purpose for reserving addresses is to configure those well-known servers whose addresses are retrieved by clients using a Domain Name System (DNS) or host file and thus should remain fixed.

If multiple DHCP servers are serving a particular subnet, after setting up a new IP address reservation for a client on one server, there is no guarantee that the client will get the reservation. There is nothing in the packet from the server giving the reserved address that indicates its priority. The best policy is to make reservations on all servers serving a particular subnet.

Making a reservation does not automatically force any existing client off the reserved address, or force the client to take the reserved lease.

Before reserving an IP address for a new DHCP client or for a client that already has an address lease, you should verify that the address you want to reserve has not already been leased to another client. If another client is using the address, note the client, so that you can force it to seek another address lease. You should force the client currently using the address to seek another address lease only after you have made the reservation. Otherwise, the DHCP server might give the address that you want to reserve back to the client or to another client.

To force a client to use another IP address

1.	Reserve the IP address.

2.	At the command prompt of the client currently using the IP address, type the ipconfig /renew command.

Restarting the computer is required for clients running MS-DOS and can be required by clients running third-party software. The key point is to force the client to seek lease renewal, so that it is forced off its existing lease. If the client is not forced to seek lease renewal, and both computers are on the network, the two clients will try to use the same address.

Likewise, a reserved client does not acquire its new lease until it seeks a renewal of its lease or until the computer is restarted. After making the reservation and moving any previous client to a new lease, type the ipconfig /renew command at the  reserved client to force it to move to the new reservation.

Setting Reservation Options

When adding a reservation, you might find the Options button dimmed. To set reservation-specific options, add the reservation, then, using the Active Leases dialog box, select the reservation, and then add the option.

In the Active Leases dialog box, the Lease Expires field indicates an Infinite lease for reservations. Even though reservations do not expire, their leases do not differ from those issued to clients without reservations. Reserved clients must also go through the regular renewal process.

Reservations are considered to be active leases and are included in the Active/Excluded count. Reservations are clearly labeled either Reservation or Reservation In Use.

Lease Deletion

DHCP is a client-server protocol. The server has no way to communicate information to the client except in response to client requests. Therefore, deleting a lease from the DHCP server does not stop the client’s use of the address it was assigned. The client continues to run until its lease expires unless you force it to seek renewal of its lease after reserving its current lease address for another computer to use.

To delete a lease

1.	Delete the lease entry in the Active Leases list box.

2.	Reserve the IP address or exclude an IP address.

3.	At the client that is currently using the IP address, type the following command at the command prompt to force the client to release the address.

ipconfig /release

4.	Type the following command at the command prompt to force the client to seek another IP address lease.

ipconfig /renew

It is important to complete this step immediately after the previous step.

Note

Failure to execute the last step can cause two clients to attempt to use the same IP address, which can cause serious problems.

There is no mechanism in the DHCP server to prohibit a particular client from getting a lease. Even after a deleted client’s lease expires, the client attempts to get another lease and will succeed if leases are still available. The Delete function is simply to remove lease information that conflicts with an IP address exclusion or to add a client reservation.

Reconciling Inconsistent IP Addresses

Reconcile is a new button in the Active Leases dialog box of the DHCP Manager. When you reconcile the DHCP database with the Registry, a consistency check is done on the DHCP database. All inconsistent IP addresses are listed. Inconsistent IP addresses are addresses that the Registry says are leased but the DHCP database does not reflect this information. The consistency check is performed at the scope level. Therefore, if a server is configured with multiple scopes, reconcile should be run separately for each scope.

If an administrator chooses to fix inconsistent IP addresses, the reconcile program either restores those IP addresses to the original owner or creates temporary reservations for a lease time that is assigned to the scope. The lease time prevents the inconsistent IP addresses from being reused while the IP address is being used by a client. Any client using an inconsistent IP address can continue to use it until the lease expires. However, when the lease time expires, the IP address is recovered automatically for future reuse by other clients.

Run the reconcile program whenever a DHCP database is restored from a backup copy or after a system crash. It is also a good idea to run the reconcile program periodically to keep the DHCP database clean.

To reconcile IP addresses

1.	Select a scope.

2.	From the Scope menu, select Active Leases.

The Active Leases dialog box appears.

3.	Choose the Reconcile button.

The leased IP addresses in the Registry are compared with the leased IP addresses in the DHCP database.

4.	If the IP addresses are consistent, a message appears that says the database is consistent. Choose the OK button.

 – Or –

If the database is inconsistent, the Reconciling Database dialog box appears. The dialog box lists the IP addresses that need to be reconciled with the addresses in the Registry.

Choose the OK button.

5.	The Active Leases dialog box appears with the reconciled addresses listed in the Client box.

Note that if an address in the Client box has the address repeated next to it, instead of a friendly computer name, the client that leased the address has not yet renewed its lease. Until the client seeks lease renewal, the DHCP server cannot convert the address to a friendly computer name, such as peteo_nt.

6.	Choose the OK button to close the Active Leases dialog box.

If you double-click the IP addresses that have not been converted into friendly computer names, the Client Properties dialog box appears. Each IP address whose lease has not been renewed has the structure shown in the Unique Identifier field as shown in the following screen.


DHCP Relay Agents
Supplemental Information About TCP/IP	5 of 11

DHCP Relay Agents

This information pertains only to Windows NT Server.

The following changes are not reflected in the TCP/IP manual.

Configuring DHCP Clients Across IP Routers

Because the ability of DHCP clients to obtain configuration information dynamically is based on network broadcasts, support is needed in your network’s IP routers to support the configuration of DHCP clients from a DHCP server on another IP subnetwork. All major router vendors are in the process of adding DHCP relay agent support (as described in the DHCP Internet Requests for Comments) to their routing software.

Microsoft has tested versions of this software support from the following vendors: Cisco, Proteon, Wellfleet [image], and 3Com [image]. Please contact your router vendor for updates to their software to support DHCP.

Cisco Router Software Update for DHCP Support

If you use Cisco routers with software versions prior to versions 9.21(3.2) and 10.0(2.1), and use DHCP servers in your network, you must obtain a software update from Cisco Systems.

BOOTP extensions to support DHCP (per RFC1542) were integrated into 9.21(3.2) and 10.0(2.1) Cisco software. It is recommended that you use these versions of the router software for better compatibility with DHCP servers.

3Com Router Software Update for DHCP Support

If you use 3Com routers with software versions prior to version 7.1, and use DHCP servers in your network, you must obtain a software update from 3Com.

BOOTP extensions to support DHCP (per RFC1542) were integrated into versions 7.0.04, 7.1, and later systems. It is recommended that you use these versions of the router software for better compatibility with DHCP servers.

Wellfleet Communications Router Software for DHCP Support

If you use Wellfleet router software versions other than 5.75 you should contact Wellfleet Communications and update to the version that fully supports DHCP.

Version 5.75 supports BOOTP extensions to support DHCP (per RFC1542). However, if you move a client from the same network segment of a DHCP server to a remote network segment (across a wide area network), the client starts with the original IP address. You must issue the commands ipconfig\release, and then ipconfig\renew from the command prompt on the client. Contact Wellfleet for a version that fixes this problem.

BOOTP extensions to support DHCP (per RFC1542) were integrated into Wellfleet version 7.71 (fix4) software. It is recommended that you use these versions of the router software for better compatibility with DHCP servers.

Ungermann-Bass Networks Router Software for DHCP Support

If you use Ungermann-Bass [image] ASM83xx routers with software versions prior to version 7.2 and use DHCP servers in your network, you must obtain a software update from Ungermann-Bass Networks.

BOOTP extensions to support DHCP (per RFC1542) were integrated into version 7.2 router software. It is recommended that you use these versions of the router software for better compatibility with DHCP servers.


DHCP Client
Supplemental Information About TCP/IP	6 of 11

DHCP Client

Options Supported

Currently, Microsoft DHCP clients make use of only the following options.

DHCP protocol options:

Host Name (12)

Requested Address (50)

Server Identifier (54)

DHCP Message Type (53)

Lease Time (51), Renewal Time (58), Rebind Time (59)

Client ID (61)

Parameter Requested List (65)

DHCP information options:

Subnet Mask (1)

Default Router (3)

DNS Server (6)

DNS Domain Name (15)

WINS Server (NetBIOS Name Server) (44)

NetBIOS Node Type (46)

NetBIOS Scope Id (47)

Any other options received by the client are ignored and discarded. They are not available through any mechanism.

Option Overlays

The DHCP client does not recognize option overlays. If a server running third-party software is sending the options, make sure that all the options fit within the standard option field or at least that those options (listed above) used by the clients running Microsoft software are contained in the standard option field.

Moving a Client to a New Address

When a DHCP client is moved to a new reserved address or is moved from an address to make way for an exclusion or another client’s reservation, first release the client’s current address and then get a new address for the client.

To move a client to another IP address

1.	Type the ipconfig /release command at the client’s command prompt.

2.	Type the ipconfig /renew command to get a new address.

ARP Conflicts

Before the TCP/IP protocol comes up with the address acquired using DHCP, the protocol ARPs (attempts to find the hardware address) for the address. If a computer is already using the address, a popup message is displayed on the client that informs the user of the address conflict. Users should contact the DHCP server administrator when this situation occurs. For more information, see “Address Resolution Protocol (ARP) Conflicts” in the DHCP Server section earlier in this chapter. Once the administrator has excluded the conflicting address on the DHCP server, use the ipconfig /release and ipconfig /renew commands to move the client where the message was displayed to a new address. For more information, see the procedure “To move a client to another IP address” in the preceding topic. If the client does not move to another address, try restarting the client.

Multihomed Computers

Currently, a computer can have only a single NetBIOS scope ID, NetBIOS node type, DNS Domain Name, and DNS server list from DHCP. These values are not set per network adapter card.

In the case of a multihomed computer straddling two networks, each with its own DHCP servers, the DNS domain name and server list, and NetBIOS node type and scope ID of these two networks should be identical. If they are not identical, the last DHCP client to configure and hence write these values to the Registry will set those values for the whole computer. This situation could lead to some unexpected behavior and the client might not be able to access the network.

The safest workaround is to set these values manually on multihomed machines either using the Network option in Control Panel or directly in the Registry. Any manually configured values overrides the DHCP values.


NetBIOS over TCP/IP
Supplemental Information About TCP/IP	7 of 11

NetBIOS over TCP/IP

Default NetBIOS Name Resolution

Windows NT Workstation 3.51 and Windows NT Server 3.51 computers run in b-node mode. However, if you have specified a WINS server using the Network option in Control Panel or if DHCP Manager has specified a WINS server for the client, Windows NT Workstation and Windows NT Server computers run in h-node mode. For more information about NetBIOS name resolution modes, see the Microsoft TCP/IP chapter in the Windows NT Workstation Installation Guide or see “NetBIOS over TCP/IP and Name Resolution” in the Windows NT Server TCP/IP manual.

Running in P-Node Mode

Computers configured as NetBIOS p-nodes (point-to-point), cannot locate computers running as NetBIOS b-nodes (broadcast). Computers running Windows NT 3.1 are b-node only. Therefore, if you have a network comprised of computers running either Windows NT 3.1 or Windows NT 3.5x, be sure not to configure the computers running Windows NT 3.5x as p-nodes.

Instead configure the Windows NT 3.5x computers as h-nodes which is the default mode when a WINS server is specified. Once all the computers running Windows NT 3.1 have been upgraded to Windows NT 3.5x, the computers can be configured as p-nodes.

Broadcast Addresses

NetBT normally uses the subnet broadcast address (for sending broadcast name queries) where the host portion is all 1’s. For example:

11.1.255.255

This address can be changed to be any other value, such as a host portion that is all zeroes. For example:

11.1.0.0

To change the values, set the following Registry key to the appropriate value:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NetBT\ Parameters\BroadcastAddress

This Registry key is a DWORD. The value must be entered using the correct format in hexadecimal. (For example, 0b010000 is 11.1.0.0.) When this key is not present, NetBT defaults the host portion of the broadcast address to 1’s.

NetBIOS Node Type

A computer can be one of four NetBIOS node types: broadcast, mixed, point-to-point, or hybrid. The node type cannot be specified by network adapter card. In some circumstances, it might be preferable to have one or more network adapter cards function as broadcast nodes and to have other network adapter cards function as hybrids.

You can accomplish this task by setting the node type to broadcast node and configuring WINS name server addresses for the network adapter cards that function as hybrids. The presence of the WINS addresses effectively override the broadcast node setting for the adapters on which they are set.

To make an adapter a broadcast node, configure DHCP to set the node type to b-node, or in the absence of DHCP, a computer will assume b-node behavior by default.

Including Remote LMHOSTS Files

You must modify the Registry of a computer if network clients use the LMHOSTS file on the computer. The share containing the LMHOSTS file must be in the Null Sessions list on the Server by adding the share name to the following Registry key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManServer\ Parameters\NullSessionShares

Interoperation of WINS and Ungermann-Bass TCP/IP

When running a network comprised of computers running Ungermann-Bass (UB) TCP/IP or Microsoft TCP/IP, do not configure the computers running UB TCP/IP use a WINS server. The friendly computer names (for example, SHARC2) of the computers running UB TCP/IP will not be refreshed correctly and will be dropped from the WINS server.

Computers running Microsoft TCP/IP can be configured to use a UB NetBIOS name server if the RefreshOpCode value is added to the Registry under the following key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NetBT\Parameters

RefreshOpCode is a REG_DWORD. Set its value to 9 to interoperate with UB NetBIOS name servers.

Using DNS for Name Resolution

To perform domain operations across a router using DNS name resolution, you must add the domain name to the DNS server or local hosts file with the IP address of the primary domain controller (PDC) as its IP address. This step is necessary to join a domain, become a backup domain controller (BDC), or browse a domain.

The following entry is an example of what would appear in the local hosts file:

11.11.11.45	controller	controller.domain	controller.domain.company

11.11.11.45	domain

Where controller is the name of the PDC and domain is the name of the Windows NT domain. The Windows NT domain name does not need to be the same as the DNS domain name.

NetBIOS Scope ID

Currently, the NetBIOS scope ID is not kept per adapter. Rather, the value specified in the Network option in Control Panel or given by a DHCP server becomes the scope ID for all interfaces on the system. For more detailed information, see “Scopes” in the preceding DHCP Server section. If the other interfaces are on subnets that do not share this scope ID, they will no longer be able to communicate with other systems using NetBIOS.

There is no workaround solution for this problem. The best solution is to avoid using NetBIOS scope IDs, or make sure they are the same on all subnets where multihomed systems are required to use NetBIOS on both networks.


NFS Client Software on Windows NT Workstation or Server 3.51
Supplemental Information About TCP/IP	8 of 11

NFS Client Software on Windows NT Workstation 3.51 or Windows NT Server 3.51

If you are currently running third-party network file system (NFS) client software with version 3.1 of Windows NT Workstation or Windows NT Server, you need to get an update from your NFS vendor to run version 3.51 on Windows NT Workstation and Windows NT Server. Version 3.1 of this software no longer works because of the tight integration NFS has with Windows NT Workstation and Windows NT Server.


Routing
Supplemental Information About TCP/IP	9 of 11

NFS Client Software on Windows NT Workstation 3.51 or Windows NT Server 3.51

Routing

The route command converts destination names to addresses using the networks database file (<systemroot>\SYSTEM32\DRIVERS\ETC\NETWORKS). For the route command to execute properly with an address in this file, the address must fully specify all four octets in dotted-decimal notation.

For example, the following command-line entry requires that an additional entry be added to the NETWORKS file:

route add campus MASK 255.255.255.0 campus_gwy

The following additional entry is required in the NETWORKS file:

campus  284.122.107.0

The following entry, as shown in the examples in the NETWORKS file, is incorrect:

campus  284.122.107

Multihomed Routing Issues

If a system has both a statically configured interface and a DHCP configured interface, the default gateway for the static interface is preferred. This situation occurs because static interfaces are initialized before DHCP configured ones. All non-TCP traffic that is to be routed through a default gateway goes through the gateway for the static interface. If it is detected that a gateway is not currently available for some reason, TCP traffic is routed through the other interface if necessary.

Destination Routes

Different network interfaces cannot be specified to add routes for the same destination network. For example, consider a multihomed machine with the following IP addresses and gateways.

Net1: 	11.101.7.77

Gateway: 	11.101.0.1

Net2: 	11.222.7.77

Gateway: 	11.222.0.1

Suppose a network, 130.20.0.0, is accessible through two gateways, 11.222.0.2 and 11.101.0.2. If you want to add a route to network 130.20.0.0, you can type the following command:

route add 130.20.0.0 MASK 255.255.0.0 11.101.0.2

This step will set up the route table in such a way that any datagrams destined to the 130.20.0.0 network will go through 11.101.0.2 using the 11.101.7.77 interface. If you add another route to 130.20.0.0 through 11.222.0.2, the route entry will get added to the route table, but the interface on which the traffic will go out will still be the interface in the first route, that is, 11.101.7.77, instead of 11.222.7.77.

To set up the route in such a way that the second interface gets used, you will have to delete both of the route entries and re-add them in reverse order. However, in all cases, the same network interface will be used for the routes to the same destination regardless of the network the gateway lies on.

In particular, this problem affects default gateways on multihomed workstations, which are specified by a destination of 0.0.0.0. in the route table. The workaround for default gateways is to use the Advanced portion of the TCP/IP configuration dialog in the Network option in Control Panel and enter the gateways in the preferred order.

The route command also does not properly delete multiple routes to the same destination. It deletes the first route to a particular destination. In particular, if the system has multiple default gateways (destination 0.0.0.0), the route command will always delete the first one in the list, regardless of the gateway specified.

Multiple Default Gateways

When more than one default gateway is specified for a given IP network or for multiple IP networks on different network cards, the first default gateway for the first network card is always used to route IP network traffic. All the subsequent gateways are used as backups when the first default gateway is discovered to be unavailable. The Unavailable Gateway Detection mechanism is used only with TCP (connection-oriented traffic).

When a TCP-based utility uses the Unavailable Gateway Detection mechanism to change the default gateway, the unavailable gateway is marked as such. Then the next gateway in the default gateway list is made the current default gateway.

Datagram-based utilities, such as ping, will not cause the Unavailable Gateway Detection mechanism to activate, but datagram-based utilities will use the current default gateway. Note that this situation applies only to IP datagrams that have to be routed to a remote network (that is, to a network to which the workstation is not directly connected).

For example, consider a computer with two network cards, Netcard1 and Netcard2, and the following IP addresses and default gateways:

Netcard1:

	IP Address:	11.101.7.77
	Mask:	255.255.0.0
	Default Gateway:	11.101.0.1
		11.101.0.2
Netcard2:

	IP Address:	11.222.7.80
	Mask:	255.255.0.0
	Default Gateway:	11.222.0.1
If you want to use telnet to communicate with a workstation with an IP address of 130.20.20.100, the IP datagrams will be routed through the 11.101.0.1 gateway. If 11.101.0.1 is detected to be unavailable, the IP datagrams will use the second gateway, 11.101.0.2, and so on. Again, notice that this situation applies only to datagram-based utilities. Telnet, FTP, and NetBIOS Session service network traffic use TCP for network communications.

Also consider the case where the two networks connected to Netcard1 and Netcard2 are disjoint (that is, not connected to each other through any other router). If there is a network (say 22.101.x.x) that is accessible only through Netcard2, the IP datagrams for this network will still be routed through 11.101.0.1. To route IP datagrams destined to network 22.101.x.x through 11.222.0.1, you will have to add a static route to the routing table using the route utility. To add the route, type the following command:

route add 22.101.0.0 MASK 255.255.0.0 11.222.0.1

This behavior is by design and conforms to the TCP/IP specifications.


Utilities
Supplemental Information About TCP/IP	10 of 11

Utilities

FTP Server Registry Parameters

The following two entries control logging of FTP server activity. The Registry path for these entries is the following:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FtpSvc\Parameters

The following table describes the values for this entry:

Entry	Value

Name	LogFileAccess

Data type	REG_DWORD

Description	Sets the logging behavior for FTP Server file access. Set this entry to one of three values.

0  Do not log file accesses (default).

1  Log file accesses to FTPSVC.LOG.

2  Log file accesses to FTyymmdd.LOG where yy is the current year, mm is the current month, and dd is the current day. New log files are opened daily as necessary.

Range	0 to 2

Default value	0

Entry	Value

Name	LogFileDirectory

Data type	REG_SZ

Description	Specifies the target directory for the log file(s). The log file(s) can be off of the system partition.

Range	None

Default value	\systemroot\SYSTEM32

Getting Command Prompt Help for TCP/IP Commands

To view command-line Help for TCP/IP utilities, type the command name and the /? parameter at the command prompt. For example, if you type help <TCP/IP utility> /? at the command prompt, the following message is displayed on the screen:

This command is not supported by the Help utility. Try <cmd> /?.

To display online Help topics on TCP/IP utilities

Type the following command at the command prompt

<TCP/IP utility> /?

Using the Rexec Command

The rexec command might not terminate if the service is not present on the target host.

To terminate the rexec command

Press CTRL+C.

Using Simple TCP/IP Services

The Discard service is not listed in the port list box in the Connect dialog box of Telnet even though the service is available. To start the Discard service, you can type either discard or the Discard service port number in the port list box.

To start the Discard service from the command line

Type one of the following commands:

telnet host <discard>

 – Or –

telnet host <discard service port number>

Printing Nontext Files with the Lpr Command

To print a nontext file (for example a PostScript file) from a computer running Windows NT Workstation or Windows NT Server to a printer controlled by a UNIX [image] computer, use the lpr command with the -ol parameter. For example, type the following command at the command prompt:

lpr -ol -S <unix host> -P <print queue name> <non-text file>

To print a nontext file (for example PostScript) from a UNIX computer to a printer controlled by Windows NT Workstation or Windows NT Server, you should consult your UNIX documentation for the exact switch provided by you implementation. Many implementations provide a -l parameter. For example, type the following command at the command prompt:

lpr -l -P <print queue name> <postscript file>

Printing with JetDirect Cards

JetDirect cards that do not have the LPD software in read-only memory (ROM) do not operate with Windows NT Workstation or Windows NT Server TCP/IP unless a Hewlett-Packard UNIX computer is available to download the LPD software to the JetDirect card.

Utility Documentation Errata

The route command converts destination names to addresses using the NETWORKS file. For the route command to execute correctly, the IP addresses in, or added to, the NETWORKS file must specify all four octets in dotted-decimal notation. For example, the following command-line entry requires that an additional entry to be added to the NETWORKS file:

route add campus MASK 255.255.255.0 campus_gwy

The following additional entry is required in the NETWORKS file:

campus	284.122.107.0

For example, the following command-line entry does not execute correctly because you must specify all four octets using dotted-decimal notation:

campus	284.122.107

The nbtstat command in Chapter 11 of the Windows NT Server TCP/IP manual does not list all the possible parameters you can use. Use the online Command Reference (the NTCMDS.HLP file) for a complete list of all the nbtstat parameters.


Internetwork Printing with TCP/IP
Supplemental Information About TCP/IP	11 of 11

Internetwork Printing with TCP/IP

When using the lprmon utility (the printer is using the lpr port), you should not use the Job Prints While Spooling option because print jobs do not print efficiently.

Microsoft TCP/IP printing supports printing only to UNIX computers running the LPD service (for example, Berkeley Software Distribution (BSD) UNIX computers). Microsoft TCP/IP printing does not work with UNIX computers running the LPSCHED daemon (for example, Sun Microsystems [image] System V computers).

System V-derived UNIX computer users may want to install a publicly available LPD program on their computer, in order to support Microsoft TCP/IP printing.

For LPDSVC to print to a Windows NT Workstation or Windows NT Server computer network share using the universal naming convention (for example, \\NTPRINTSERVER\HPLASER), the share must be designated as a null share. Designate a null share by adding the share names to the value of the following Registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer \Parameters\NullSessionShares

You must restart the computer for the change to take effect.

LPDSVC cannot print to network shares on a server running Microsoft LAN Manager for OS/2 [image].


Licensing and License Manager
Chapter 5	1 of 7

Licensing and License Manager

Network solutions generally have the following two components:

Servers that contain information and provide services

Clients that access information and services

With the Microsoft BackOffice licensing model, these components are licensed separately, so you purchase only what you need to build a network solution for your company’s particular requirements. Each server requires a license and each client computer accessing a server also requires a license (called a Client Access License).

The license agreements for certain Microsoft BackOffice server products (such as Windows NT Server, SQL Server, and SNA Server) also provide the flexibility of two licensing modes: Per Server and Per Seat. With Per Server licensing, each Client Access License is assigned to a particular server and allows one connection to that server for basic network services (file, print, and communications). The Per Seat Licensing mode requires a Client Access License for each computer that accesses Windows NT Server for basic network services. Once a computer is licensed in the Per Seat mode, it may access any Windows NT Server computer installed on the network at no additional charge.

Client Access Licenses are separate from the desktop operating system software you use to connect to Microsoft server products. Purchasing Microsoft Windows for Workgroups, Windows NT Workstation, or any other desktop operating system (such as Macintosh [image]) that connects to Microsoft server products does not constitute a legal license to connect to those Microsoft server products. In addition to the desktop operating system, Client Access Licenses must also be purchased.

During Windows NT Server Setup, a detailed Choose Licensing Mode dialog box appears that enables administrators to do the following activities:

Obtain online Help describing the two licensing modes: Per Server and Per Seat

View online versions of the Windows NT Server 3.51 Client Access License and Server License agreements

Select the licensing mode that best suits their network or business requirements

Agree to the terms and conditions of the license agreement

For more information on changes to Setup in Windows NT Server 3.51 and for definitions with graphic descriptions of the Per Server and Per Seat licensing modes, and examples of when to use each mode, see Chapter 1, “New Programs and Features.”

Tracking licenses manually on local computers or within a small domain is time consuming but possible. Tracking licenses without the assistance of automated tools across an entire organization or enterprise with multiple domains can be very difficult, extremely costly, and overly time consuming. A tool that manages and tracks licenses and usage throughout an organization can help contain these costs. A tool that automatically replicates licensing data from all the primary domain controllers (PDCs) in the organization to a centralized database on a specified master server can also make it easier for a company to comply with legal requirements.

Windows NT Server 3.51 includes the following two new administrative tools that help to reduce these costs and the administrative overhead of license tracking:

The Licensing option in Control Panel

The License Manager program in the Network Administration program group

These tools provide a way for administrators to track Client Access Licenses across an organization and ensure compliance with the requirements of the Microsoft BackOffice family license agreements.

After the initial Setup process, an administrator can use the Licensing option in Control Panel if they need to change the licensing mode on that local computer from Per Server to Per Seat (a one-time only option). They can also use it to configure licensing replication for that computer.

Administrators can use the License Manager program to obtain a centralized view of Per Seat and Per Server licenses across the organization, manage the purchasing or deleting of licenses for products on network servers over which they have administrative rights, view usage statistics per user, and balance the licensing replication load across the network.

Note

Licensing replication does not depend on nor does it use the server replication process.


Licensing
Licensing and License Manager	2 of 7

Licensing

When Windows NT Server 3.51 is installed, a Licensing icon is added to Control Panel. If you have administrative authority for your local server or for your server’s domain, you can double-click the Licensing icon to display the Choose Licensing Mode dialog box. In this dialog box, you can perform a one-time, one-way licensing mode change from Per Server to Per Seat. This change is currently possible only with Windows NT Server 3.51, SQL Server, and SNA Server. You cannot legally change the licensing mode from Per Seat to Per Server.

Notice that, if you select the Per Server licensing mode for those server products, you must specify the number of computers that can concurrently connect to the server on which the product is installed.

The online Help for the Choose Licensing Mode dialog box provides descriptions of these two licensing modes, the dialog-box options, and online versions of the license agreements. It also has an overview of Microsoft’s licensing model and provides answers to frequently asked questions regarding Client Access Licenses.

License tracking can be local, by domain, or across an entire organization or enterprise. By maintaining a reasonably up-to-date historical database of all purchases and deletions on a centralized master server, an administrator can ensure the company’s legal compliance with license agreements for the various software products on their network. To do this task, they need to be able to replicate licensing information on a regular basis from each server to this master server.

Choosing the Replication button displays the Replication Configuration dialog box. In this dialog box, you can either accept the default values shown or specify the master server to which all licensing information for that domain will be replicated and how frequently that will happen.

The master server is a server in an organization that has been designated as the final centralized repository of all licensing data for that organization. It can be either the PDC for that individual domain or a specified enterprise server. An enterprise server is the server to which multiple PDCs in a large organization will replicate. (In the box next to Enterprise Server, you need to type a network name for that server, such as ENTERPRISE, without two backslashes [\\].)

The primary domain controller is the default master server for all servers in a domain and all backup domain controllers. Those servers will replicate automatically to this PDC. Selecting and specifying a different enterprise server will not change that automatic functionality. You should only select the Enterprise Server option if your computer is one of the following:

A standalone server in its own domain, but still part of a larger organization or enterprise

The PDC for that domain, and you want to replicate to a higher server

For more details on replication, see the “Server Browser” section later in this chapter or the online Help files.


License Manager
Licensing and License Manager	3 of 7

License Manager

Windows NT Server 3.51 provides a new tool, License Manager, in the Network Administration program group to assist administrators in managing licensing for computers running Windows NT Server on which they have administrative rights. With License Manager, administrators can remotely change the licensing mode of products, such as Windows NT Server 3.51 (which provides basic network services such as file, print, and communications), SQL Server, and SNA Server from Per Server to Per Seat, and add or delete Client Access Licenses for the Microsoft BackOffice family of server products.

License Manager tracks users and relates users to licenses. Legal license agreements cover computers accessing or using the server. In most cases, one user is associated with one computer. However, in cases where multiple users physically use the same computer, administrators need to take additional steps, such as creating or editing license groups (see the Options Advanced menu), to track usage properly and ensure compliance.

With Per Server licensing, once the specified limit is reached, Windows NT Server 3.51 does not allow more computer connections to that server. The administrator is considered one of the numbered concurrent connections until the limit is reached. At that time, though, the administrator is allowed to connect to manage the lockout situation.

Note

You can also check the Application log in Event Viewer on the master server to view any license violation alerts.

To start License Manager, double-click the License Manager icon in the Network Administration program group. You automatically connect to the enterprise server.

Upon starting License Manager, you see an opening screen with the following four main tabs that provide overall information as well as paths into the tool’s principal management functions:

Purchase History

Products View

Clients (Per Seat)

Server Browser

Each tab provides a different view of the information (products, product licenses, clients, and servers) tracked by License Manager and access to various Properties screens with additional tabs for information that is specific to that item.


Purchase History
Licensing and License Manager	4 of 7

License Manager

Purchase History

The Purchase History screen is the opening screen. It provides an historical overview of the licenses purchased for products installed within the selected domain or enterprise. It also shows the quantity of licenses purchased and deleted, the date of installation or deletion, and the identity of the administrator (the one who certifies that the company purchased the license) who either installed or deleted the product license. The comments that appear were entered during installation (using the New Client Access License dialog box) or deletion (using the Delete Client Access Licenses dialog box). There are no additional Properties screens for this view.

However, you can do the following activities that are available from almost all views by choosing from a menu or clicking on a toolbar button:

Add new Client Access Licenses

Create or edit license groups

Select a new domain to administer

Refresh the screen display to update information on network server activity

Sort each column by clicking the column title or choosing the appropriate title name from the Options Sort By menu  —  not available for the Server Browser tab

Format the screen either in icon or list format  —  available only for the Products View and Clients (Per Seat) tabs

Change the screen’s font style and size

Choose whether or not to view the toolbar and/or the status bar

Move the toolbar to anywhere on the screen by clicking the toolbar with the pointing device (mouse), and then dragging it to a new location

Save specified settings upon exiting

See online Help for detailed instructions on how to do these activities.


Products View
Licensing and License Manager	5 of 7

License Manager

Products View

The second main tab is for the Products View screen, which contains information on the products in the selected domain or the entire enterprise. This screen shows, for Per Seat mode, how many licenses have been purchased for those products and how many licenses have been allocated to users’ computers for all the products. For Per Server mode, it shows the total number of licenses that have been purchased for each product on all the servers in the domain or enterprise with that product on them. It also shows the maximum number of concurrent connections reached up to that date on all the servers in the domain or enterprise with that product on them.

You can use both the numerical and graphical information in this screen to determine the following:

What products are in compliance with legal licensing requirements

What products are not in compliance with legal licensing requirements

What products have reached the legal limit and for which you might want to purchase additional licenses

While in this screen, you can also do the following activities:

Add new Client Access Licenses

Delete existing Client Access Licenses for a product

Open the selected product’s Properties screen

Select a new domain to administer

Refresh the screen display to update information on network server activity

Sort each column by clicking the column title

Format the screen either in icon or list format

See online Help for detailed instructions on how to do these activities.

Double-clicking the product name opens the Properties screen for that product and enables you to access three more tabs with information that is specific to that product: Clients (Per Seat), Purchase History, and Server Browser. You can also open the Properties screen by clicking the View Properties toolbar button, choosing the Properties command under the License menu, or selecting the user name, and then pressing ENTER.

Clients (Per Seat)

The Clients (Per Seat) tab on the product’s Properties screen shows which users in that domain or the enterprise are using the product, the last date they used it, and how many times they have used that product. The icon next to the user’s name shows whether or not a license for that product has been allocated to that user.

This information shows the administrator if client usage for that product is exceeding the number of Per Seat licenses purchased. The date and frequency information also enables administrators to tell if a user really needs to have a Client Access License for their computer, or if it would be better to release that license permanently for use by another user’s computer.

While in this screen, you can do the following activities:

Double-click the user’s name to open the Properties screen for that user

Revoke individual Client Access Licenses

Sort each column by clicking the column title

Select another tab

See online Help for detailed instructions on how to do these activities.

Purchase History

The Purchase History tab on the product’s Properties screen provides the same information as the main Purchase History tab, but only for that product.

Buttons are provided for adding new Client Access Licenses and deleting existing ones. Deletions are shown as a separate new line item. You can use the Comment field in the New Client Access License and Delete Client Access Licenses dialog boxes to include brief comments. The total number of Client Access Licenses purchased is also shown.

While in this screen, you can do the following activities:

Add new Client Access Licenses

Delete existing Client Access Licenses

Sort each column by clicking the column title

Select another tab

See online Help for detailed instructions on how to do these activities.

Server Browser

The Server Browser tab on the product’s Properties screen shows a list of servers on which that product is installed, the quantity of licenses purchased in Per Server mode, and the number of connections reached as of that date. Administrators can use this information when considering how to balance the load between servers.

While in this screen, you can do the following activities:

Use the Edit button or double-click the selected server’s name to open the Properties screen for that server

Sort each column by clicking the column title

Select another tab

See online Help for detailed instructions on how to do these activities.


Clients (Per Seat)
Licensing and License Manager	6 of 7

License Manager

Clients (Per Seat)

The third main tab is for the Clients (Per Seat) view, which provides information on a list of clients (or users) that have used the products in that domain or enterprise. It also shows how many of the listed products (licensed in Per Seat mode) they are licensed to use and how many they are not licensed to use.

These users can be either single users or members of license groups. Members of license groups can be viewed by choosing the Options Advanced menu, and then choosing the Edit License Groups command.

You can use both the numerical and graphical information in this screen to determine the following:

What users are in compliance with legal licensing requirements

What users are not in compliance with legal licensing requirements

While in this screen, you can also do the following activities:

Add new Client Access Licenses

Delete a user

Open the selected user’s Properties screen

Create a new license group

View or edit existing license groups

Select a new domain to administer

Refresh the screen display to update information on network server activity

Sort each column by clicking the column title

Format the screen either in icon or list format

See online Help for detailed instructions on how to do these activities.

Double-clicking the user’s name opens the Properties screen for that user and enables you to access a Products View tab. You can also open the Properties screen by clicking the View Properties toolbar button, choosing the Properties command under the License menu, or selecting the product name, and then pressing ENTER.

Products View

The Products View tab on the user’s Properties screen shows which products in that domain or enterprise are being used, the last date they used them, and how many times they have used those products. A Revoke button is also provided for revoking a user’s Client Access License for a product.

When a user accesses three or more server products, the system automatically converts (or upgrades) them to a Microsoft BackOffice Client Access License, if any are available in the pool, and selects the check box for that option. However, an administrator can upgrade a user at any time, even if they only use one server product.

The administrator can also override the automatic upgrade and clear the check box for the Upgrade to BackOffice License option, which would return them to using an individual product Client Access License. The system does not automatically upgrade them again after that change.

While in this screen, you can do the following activities:

Double-click the product’s name to open the Properties screen for that product

Revoke the user’s Client Access License for that product

Upgrade the user to a Microsoft BackOffice Client Access License and use the Apply button to make it effective immediately

Override an automatic upgrade and use the Apply button to make it effective immediately

Sort each column by clicking the column title

See online Help for detailed instructions on how to do these activities.

License Groups

To obtain correct licensing information when working with Per Seat licenses, you might need to group certain users and make them members of a license group with a descriptive name. You can use the Options Advanced menu to create a new license group or to edit existing ones.

License groups show a relationship (also known as a mapping) between users and computers and should be used only when one of the following configurations is true:

Many users to one computer, such as when people share jobs or there are multiple shifts using the same computers.

Many users are using many computers but there are still a different number of users than computers, such as in a university computer lab or in a retail store.

One user to many computers, such as happens in many software developers’ offices where they need to develop on one computer and test their applications on several different computer-hardware platforms.

In the first instance with multiple users but only one computer, you need only one Client Access License. You are licensing the number of computers, not the number of users.

The same logic also applies to the second configuration. For example, if you have 100 users accessing 10 computers, you only need to purchase 10 Client Access Licenses to cover those 10 computers. But you might want to keep track of all 100 users and how often they use each computer to access various servers.

In the last case, the one user needs multiple Client Access Licenses to be in compliance with legal licensing requirements even though License Manager only shows one user.

New License Group

Under the Options Advanced menu, choose New License Group to open a dialog box in which you can create a new license group. You need to enter a short descriptive name for the group, and then provide additional details in the Description field. For example, the Group Name could be “Test Lab1” and the Description could be something short, such as “10-members on Dev Team, 3rd flr.” If they have four computers in this lab, they need four licenses in the Per Seat mode.

To create a list of the users who are members of this license group, choose the Add button to open the Add Users dialog box. Select the appropriate domain, and then select the individual users from the Users box. Choose the Add button, and the names of the selected users will appear in the Add Users box.

If you change your mind about somebody or make a mistake, you can select their name in the Add Users box and then choose the Delete button. When the list is complete, choose the OK button. If you change your mind again, you can delete more users now from within the New License Group dialog box with the Delete button before choosing the OK button and creating this new license group.

Edit License Groups

Under the Options Advanced menu, choose Edit License Groups to open a dialog box in which you can view a list of the names of all the existing license groups, the number of Per Seat licenses allocated to each group, and a short description.

While in this dialog box, you can do the following activities:

Add a new license group without leaving this dialog box

Delete a selected license group that no longer has any members

Use the Edit button or double-click the selected license group’s name to open the Properties screen for that license group

Sort each column by clicking the column title

See online Help for detailed instructions on how to do these activities.


Server Browser
Licensing and License Manager	7 of 7

License Manager

Server Browser

The final main tab is for the Server Browser view, which lists all the domains and servers in the enterprise. This tab enables an administrator to view and edit server and server product licensing information in any domain over which they have administrative authority. Representative icons also precede the names to aid in easy identification of the level reached (domain, server, or product) and the licensing mode of the products.

While in this screen, you can access these three levels and do the following appropriate activities:

At all levels, add new Client Access Licenses

At the server and product levels, open the selected item’s Properties screen

At all levels, select a new domain to administer

At all levels, refresh the screen display to update information on network server activity

See online Help for detailed instructions on how to do these activities.

Double-clicking a domain name displays a list of all the servers located in that domain. Double-clicking a server name displays a list of all the products installed on that server. Double-clicking a product name has the same result as choosing the Properties command, which at this level simply displays the Choose Licensing Mode dialog box for changing the licensing mode.

You can also open the Properties screen for a server or product by clicking the View Properties toolbar button, choosing the Properties command under the License menu, or selecting the server or product name, and then pressing ENTER. Clicking the secondary button on the pointing device (mouse) over a server name or product name displays the Properties command, which you can then click again with either button to open the Properties screen for that server or product. When you open the Properties screen for a server, you can access two more tabs: Products View and Replication.

Products View

The Products View tab on the server’s Properties screen displays a list of all the products installed on that server, their licensing mode, and the number of licenses purchased for that mode.

It also enables you to select a product, and then choose the Edit button to display the Choose Licensing Mode dialog box in which you can change the licensing mode for that product. Remember that you are legally permitted to convert from Per Server mode to Per Seat mode at no additional cost. This conversion is a one-time, one-way option. It is not necessary for you to notify Microsoft if you elect to make this change. You are not legally permitted to change the licensing mode from Per Seat to Per Server.

While in this screen, you can do the following activities:

Use the Edit button or double-click the selected product’s name to open the Properties screen for that product

Sort each column by clicking the column title

Select another tab

See online Help for detailed instructions on how to do these activities.

Replication

The Replication tab on the server’s Properties screen is the same as the Replication Configuration dialog box in the Licensing option in Control Panel. In this view, you can either accept the default values shown or specify the master server to which all licensing information for that domain will be replicated and how frequently that will happen.

The master server is a server in an organization that has been designated as the final centralized repository of all licensing data for that organization. It can be either the PDC for that individual domain or a specified enterprise server. An enterprise server is the server to which multiple PDCs in a large organization will replicate. (In the box next to Enterprise Server, you need to type a network name for that server, such as ENTERPRISE, without two backslashes [\\].)

The PDC is the default master server for all servers in a domain and all backup domain controllers. Those servers will replicate automatically to this PDC. Selecting and specifying a different enterprise server will not change that automatic functionality. You should only select the Enterprise Server option if your computer is one of the following:

A standalone server in its own domain, but still part of a larger organization or enterprise

The PDC for that domain, and you want to replicate to a higher server

The following table shows graphically the availability of each option and under what circumstances you would select each one.

If the server is a		Select domain controller	Select enterprise server
Server in a domain		Default option	Not available
Standalone server in its own domain		If you don’t want to replicate	If you want to replicate to a higher server
Backup domain controller		Default option	Not available
Primary domain controller		If you don’t want to replicate	If you want to replicate to a higher server
Enterprise server		Default option	Not available
The default value for replication frequency is 24 hours. If an administrator accepts the default replication frequency for all the servers in a domain, licensing changes made on an individual server within a domain might take up to 48 hours (that is, 24 hours to replicate to the PDC and 24 more hours to replicate to the enterprise server) to be replicated to the overall database on the organization’s master server for licensing. This delay should be kept in mind when studying the licensing data.

Another thing to keep in mind is how to balance the licensing replication load on the network caused by servers sending licensing data at specified times on a daily basis to their PDCs, and then to the enterprise server in large organizations with multiple PDCs. If you select the Start At option, you need to come up with a strategy for varying the starting times on each server.

If you select the Start Every option, the system automatically staggers the replication of licensing data from each server, and load balancing will not be an issue. With this option, you can also have multiple replications each day or only replicate once every several days. The minimum is every 6 hours, and you can go up to a maximum of 72 hours between replications.

While in this screen, you can do the following activities:

Specify a master server for the selected server

Specify when or how often replication will occur for the selected server

Select another tab

See online Help for detailed instructions on how to do these activities.