Microsoft Windows 2000 Professional Resource Kit Release Notes (Readme.htm)

This online document contains important information that is not included in the online Help for the Microsoft® Windows® 2000 Resource Kit, including information not available from other sources about setting up the Windows 2000 Professional Resource Kit tools. Also included are very important corrections and new information related to the Windows 2000 Professional Resource Kit book.

Contents

Software

Getting Updated Files

Setup for the Resource Kit Software

General Setup Instructions

Installing from the Command Prompt

Unattended Installation

Online Documents

Individual Tool Release Notes

Runapp.exe (Run Applications)

Counters.chm (Windows 2000 Performance Counters)

POSIX Source Code

GNU Disclaimer

Resource Kit Support Policy

Books: Print Errata


Getting Updated Files

As updates to this Readme and other Windows 2000 Professional Resource Kit files are available, they will be posted to the Web for downloading. For more information, visit the Windows 2000 Resource Kits Web site.

Setup for the Resource Kit Software

The Windows 2000 Professional Resource Kit is located in a series of folders on the Windows 2000 Professional Resource Kit companion CD. The root of the CD contains a Windows Installer file (w2000rkpro.msi), which installs all of the Resource Kit tools and utilities onto your computer's hard drive.

Important   These tools have not been localized: they are written and tested in English only. Using these tools with a different language version of Microsoft® Windows® 2000 might produce unpredictable results.

General Setup Instructions

The Windows 2000 Professional Resource Kit can only be installed on a computer running the Windows 2000 operating system. It cannot be used to upgrade a Microsoft® Windows NT® Resource Kit installed on Microsoft® Windows NT®.

Installing the Windows 2000 Professional Resource Kit

Important   It is highly recommended that you remove all previous versions of the Resource Kit, including Beta versions of the Windows 2000 Professional Resource Kit, before running the Resource Kit installation program.

  1. Start Windows 2000, and then insert the Windows 2000 Professional Resource Kit companion CD in your CD-ROM drive.
  2. Follow the instructions that appear on your screen.

    Note

    If you perform a Custom installation, for example to install individual component(s), then decide you want to install the full kit:

    1. remove the previously installed components
    2. then install using the Typical installation

The Setup program installs Windows 2000 Professional Resource Kit files onto your hard disk. A typical install requires 65 megabytes (MB) of free space. There are additional applications on the CD-ROM that you can install using the Additional Components option, and that require additional hard drive space.

Setup creates a Program Files/Windows 2000 Professional Resource Kit item on the Start menu with a shortcut to the Windows 2000 Professional Resource Kit. From there you can access the tools and online documentation.

Setup also adds the \Program Files\Resource Pro Kit directory (or the directory name you choose for installing the tools) to your computer's PATH statement.

Some Windows 2000 Professional Resource Kit tools require separate or additional setup besides the steps described earlier. For more information about each of these tools and others with additional requirements, as well as a complete list of the tools, see the Windows 2000 Professional Resource Kit Tools Help (W2rktool.chm) online Help file.

Note   On the Windows 2000 Professional Resource Kit companion CD, most tools are compressed into cabinet (.cab) files by category. You cannot run executable files, call other binaries, or open documentation directly from .cab files. If you want to run a tool that you have not installed with the Resource Kit Setup, you must first extract all executable files and dependencies for a tool from the .cab files on the companion CD to your hard drive before running them.

Be aware also that for some tools, the Resource Kit Setup or the tool's own Setup program performs other installation procedures such as making changes in the registry. You might not be able to run these tools even if you extract all their files from the .cab; first install them with the Resource Kit Setup or the tool's own Setup program.

Installing from the Command Prompt

You can install the Windows 2000 Professional Resource Kit tools from the command prompt. For example, you can use the /q option to install or uninstall in silent mode, which requires no further interaction from the user.

The following table lists the command-line options for installing from the command prompt.

Option Parameters Meaning
/i w2000rkpro.msi Installs or configures.
/f [ReinstallModes] w2000rkpro.msi Repairs a previous installation.
/a w2000rkpro.msi Admin Installation. Installs on the network.
/x w2000rkpro.msi Uninstalls.
/l [i|w|e|f|a|r|u|c|m|p|+]Logfile Specifies path to log file. The flags indicate what information to log.

i û Status messages.

w û Non-fatal warnings.

e û All error messages.

f û List of replaced files.

a û Start up of actions.

r û Action-specific records.

u û User requests.

c û Initial UI parameters.

m û Out-of-memory.

p û Terminal properties.

+ û Append to existing file.

/?   Displays online Help.

For example, to install the Resource Kit in the current directory, insert the Windows 2000 Professional Resource Kit companion CD in your CD-ROM drive and type the following at the command prompt:

msiexec /i cd_drive_letter:\w2000rkpro.msi

where:
cd_drive_letter: is the letter indicating the CD-ROM drive (for example, d:).

Unattended installation

To perform an unattended installation of the Windows 2000 Professional Resource Kit, carry out:
msiexec cd_drive_letter:\w2000rkpro.msi /QB

Individual Tool Release Notes

The following section covers release note information for individual Windows 2000 Professional Resource Kit tools. When using a tool, make sure to also check the Windows 2000 Professional Resource Kit Tools Help file (w2rktool.chm) for more information.

Online Documents

The following table describes major online documents available with the Windows 2000 Professional Resource Kit.

Document Description
Counters.chm The Windows 2000 Performance Counters Reference describes all performance objects and counters provided for use with tools in the Performance snap-in of Windows 2000.
Deploy.chm The Deployment Planning Guide provides both rollout planning guidelines and strategies for deploying the various technologies that make up Microsoft® Windows® 2000.
GP.chm The Windows 2000 Resource Kit Group Policy Reference contains: security policies, Windows 2000 Group Policies, Internet Explorer policies, NetMeeting policies, corrections to the Explain Tab
Os2api.txt A text file listing compatible APIs in the OS/2 subsystem.
Regentry.chm This file provides detailed descriptions of Windows 2000 registry content, such as the subtrees, keys, subkeys, and entries that advanced users want to know about, including many entries that cannot be changed by using Windows 2000 tools or programming interfaces.
Rscripts.chm Documentation for Windows 2000 Professional Resource Kit and and Windows 2000 Server Resource Kit VBS scripts.
W2rktool.chm Documentation for Windows 2000 Professional Resource Kit and Windows 2000 Server Resource Kit Tools, describing the required files, syntax, and other usage issues, along with examples for using these tools.
W2000msgs.chm Windows 2000 Messages. This HTML Help file replaces the Windows NT Messages Access database file included in versions of the Windows NT Resource Kit.

Resource Kit Support Policy

The SOFTWARE supplied in the Windows 2000 Professional Resource Kit is not supported under any Microsoft standard support program or service. Customers can, however, report Windows 2000 Professional Resource Kit issues and bugs by sending e-mail to rkinput@microsoft.com. Microsoft will, at its sole discretion, address issues and bugs reported in this manner, and responses are not guaranteed. This e-mail address is only for Windows 2000 Professional Resource Kit-related issues.

The SOFTWARE (including instructions for its use and all printed and online documentation) is provided "AS IS" without warranty of any kind. Microsoft further disclaims all implied warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the SOFTWARE and documentation remains with you.

In no event shall Microsoft, its authors, or anyone else involved in the creation, production, or delivery of the SOFTWARE be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the SOFTWARE or documentation, even if Microsoft has been advised of the possibility of such damages.

For more information about Windows 2000 and the Windows 2000 Professional Resource Kits, visit the Windows 2000 Resource Kits Web site.


Books: Print Errata

The following section describes errata or other late-breaking information for documentation included in the Windows 2000 Professional Resource Kit. In most cases, these items have been corrected in the online versions.


Deployment Planning Guide

The Deployment Planning Guide is shipped only in online form in the Windows 2000 Professional Resource Kit. In most cases, this errata has been corrected in the online versions of the book. Release notes covered include:
  1. Table 1.9 Information Publishing and Sharing contains an error.
  2. NetBIOS/WINS consideration incomplete.
  3. The reference to DHCP is incorrect.
  4. A fully qualified Active Directory DNS domain name is limited to a maximum length of 64 bytes.
  5. SMS cannot be used for clean installation.
  6. Important Page File Setting information for servers with large amounts of RAM.
  7. Winnt and Winn32 setup command parameters are not complete.
  8. Reference to System File Protection does not reflect change in terminology.
  9. Group Policy loopback processing does not work in Windows NT 4.0 domains.
  10. The syntax for folder redirection is incorrect.
  11. Example Sysprep.inf file requires correction.
  12. Sysprep blanks existing TAPI settings.
  13. Additional functionality allows you to reduce the number of master images used for deploying Windows 2000 with Sysprep.
  14. Sysprep resets custom connectoid names.
  15. InstallDefaultComponents key is removed from Unattended Setup.
  16. New appendix: Windows 2000 Server and Professional System Requirements

  1. Chapter 1: Introducing Windows 2000 Deployment Planning, page 28

    Table 1.9 Information Publishing and Sharing contains an error.

    Description
    In Table 1.9 Information Publishing and Sharing, Removable Storage is incorrectly listed as a feature. This table currently reads:

    Table 1.9 Information Publishing and Sharing

    Feature Description Benefits
    Integrated Web services Windows 2000 Server integrated Web services allow you to use a variety of Web publishing protocols. Flexible opportunities for publishing information on your extranet, intranet, or the Web.
    Indexing Services Integrated index services allow users to perform full text searches on files in different formats and languages. Improves productivity.
    Removable Storage Consists of server and tool components for delivering audio, video, illustrated audio, and other types of multimedia over networks. New opportunities in training, collaboration, and information sharing improve productivity.
    Printing Windows 2000 makes all shared printers in your domain available in Active Directory. Allows users to quickly locate the most convenient printing source.
    Resolution
    Corrected Table 1.9:
    Feature Description Benefits
    Integrated Web Services Windows 2000 Server integrated Web services allow you to use a variety of Web publishing protocols. Flexible opportunities for publishing information on your extranet, intranet, or the Web.
    Indexing Services Integrated index services allow users to perform full text searches on files in different formats and languages. Improves productivity.
    Multimedia Services Consists of server and tool components for delivering audio, video, illustrated audio, and other types of multimedia over networks. New opportunities in training, collaboration, and information sharing improve productivity.
    Printing Windows 2000 makes all shared printers in your domain available in Active Directory. Allows users to quickly locate the most convenient printing source.

  2. Chapter 7: TCP/IP and Windows Internet Name Service, page 196

    The following entry in Chapter 7, TCP/IP and Windows Internet Name Service, WINS Design Considerations is not correct.
    Description
    If NetBIOS name resolution is required, each site within a domain needs to have at least one WINS server.
    Resolution

    [Print only. Corrected in the online book.]

    If NetBIOS name resolution is required, you will need to determine the number of WINS servers that you need. Take into consideration the location of routers on your network and the distribution of clients in each subnet. On a smaller network, a single WINS server can adequately service up to 10,000 clients for NetBIOS name resolution requests; larger networks will require more depending on the number of client connections per server.

  3. Chapter 7: Determining Network Connectivity Strategies, page 227

    In Chapter 7, in the Quality of Service section, the reference to DHCP is incorrect.
    Description
    The sentence, "For more information about DCHP..." should read, "For more information about QoS..."
    Resolution
    The sentence should read:
    For more information about QoS, see Windows 2000 Help and "Quality of Service" in the Windows 2000 Server Resource Kit TCP/IP Core Networking Guide.

  4. Chapter 9: Designing the Active Directory Structure, page 286

    A fully qualified Active Directory DNS domain name is limited to a maximum length of 64 bytes.
    Description
    In Chapter 9, "Designing the Active Directory Structure", in the section "Domain Naming Recommendations", the statement, "Length should not be a significant deciding factor when choosing names", is incorrect. The maximum length of a fully qualified Active Directory DNS domain name is 64 bytes. A single ASCII character equals one UTF-8 byte. Non-ASCII characters are encoded in multiple UTF-8 bytes. The exact number of characters allowed depends on the characters used.
    Resolution
    Replace the incorrect sentence with the correct sentence as follows: "A fully qualified Active Directory DNS domain name is limited to a maximum length of 64 bytes."

  5. Chapter 13: "Automating Server Installation and Upgrade", page 469, and Chapter 25: Automating Client Installation and Upgrade, page 921

    SMS cannot be used for clean installation.

    Description
    Tables 13.2 and 25.2, Automated Installation Methods, are not correct. These tables currently read:

    Tables 13.2 and 25.2 Automated Installation Methods

    Method Windows 2000 Edition Upgrade Clean Installation
    Syspart Server and Professional No Yes
    Sysprep Server and Professional No Yes
    SMS Server and Professional Yes Yes
    Bootable CD-ROM Server and Professional No Yes
    Remote Operating System Installation Professional No Yes
    Resolution
    Here is the new table for Tables 13.2 and 25.2:

    Tables 13.2 and 25.2 Automated Installation Methods

    Method Windows 2000 Edition Upgrade Clean Installation
    Syspart Server and Professional No Yes
    Sysprep Server and Professional No Yes
    SMS Server and Professional Yes No
    Bootable CD-ROM Server and Professional No Yes
    Remote Operating System Installation Professional No Yes
    Unattended Setup Server and Professional Yes Yes

  6. Chapter 13: Automating Server Installation and Upgrade, page 492; and Chapter 25: Automating Client Installation and Upgrade, page 947

    Important Page File Setting information for servers with large amounts of RAM.
    Description
    If you have a system with 2 gigabytes (GB) or more RAM, create a .reg file to set the CrashDumpEnabled setting to do a Kernel Dump.
    Resolution
    Add the following text to the section entitled, "Automated Installation Methods": If you have a system with 2 gigabytes (GB) or more RAM, create a .reg file to set the CrashDumpEnabled setting to do a Kernel Dump. To set CrashDumpEnabled in a .reg file:
    1. Open Notepad.
    2. Type the following information:
      Windows Registry Editor Version 5.00
      [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl]
      "CrashDumpEnabled"=dword:00000002
    3. Save the file as CrshDump.Reg.

    Note

    If you are automating an installation on a computer for which you want the Crash Dump Mode set to Kernel Dump, include the following in the [GuiRunOnce] section of the answer file:

    Regedit /s path\CrshDump.reg
    Where, path is the path to the CrshDump.reg file location on the local hard disk.
    Regedit /s path\CrshDump.reg
    Where path is the path to the CrshDump.reg file location on the computer's hard disk. You can also use an .inf to set the Crash Dump option.


  7. Chapter 25: Automating Client Installation and Upgrade, pages 937 and 938

    The Winnt and Winn32 setup command parameters are not complete.

    Description
    In the section, "Reviewing the Windows 2000 Setup Commands":
    • /a and /udf are omitted from the list of Winnt setup command parameters.
    • /cmdcons is omitted from the list of Winnt32 setup command parameters.
    Resolution

    Correct Winnt.exe syntax:

    winnt [/S[:sourcepath]][/T[:tempdrive]]/U[:answer_file]] [/udf:id[,UDF_file]][/R[x]:folder] [/E:command]

    Here is the correct Winnt32.exe syntax:

    winnt32 [/s:sourcepath] [/tempdrive:drive_letter] [/unattend[num][:answer_file]] [/copydir:folder_name] [/copysource:folder_name] [/cmd:command_line] [/debug[level][:filename]] [/udf:id[,UDB_file]] [/syspart:drive_letter] [/noreboot] [/makelocalsource] [/checkupgradeonly][/cmdcons] [/m:folder_name]

  8. Chapter 21: Testing Applications for Compatibility with Windows 2000, page 790

    The reference to System File Protection does not reflect change in terminology.

    Description
    In "Common Compatibility Issues," two references to System File Protection are incorrect. The correct terminology is "Windows File Protection."
    Resolution
    Change all references to System File Protection to Windows File Protection.

  9. Chapter 23: Defining Client Administration and Configuration Standards, page 844

    Group Policy loopback processing does not work in Windows NT 4.0 domains.

    Description
    To use loopback Group Policy processing, both the computer account and the user account must be in Windows 2000 domains. If one of the accounts is in a Windows NT 4.0 domain, loopback is disabled and policy processing occurs without it.
    Resolution
    Use loopback processing only when both the computer account and the user account are in Windows 2000 domains.

  10. Chapter 24: Applying Change and Configuration Management, pages 903, 904

    The syntax for folder redirection is incorrect.

    Description
    In Chapter 24, in the section, "Enabling Roaming User Profiles", the syntax, \\networkShare\Profiles\MaryK is incorrect. Also, in section, Redirecting Folders, the syntax, \\networkShare\Profiles\Username is incorrect.
    Resolution
    The correct syntax is:
    \\networkShare\Profiles\%MaryK%
    \\networkShare\Profiles\%Username%

  11. Chapter 25: Automating Client Installation and Upgrade, page 952

    Example Sysprep.inf file requires correction.

    Description
    The example file currently reads:
    [GuiUnattended]
    ; Specify a non-null administrative password.
    ;Any password supplied here will only take effect if the original source
    ;for the image (master computer) specified a non-null password.
    AdminPassword = ""
    
    Resolution
    It should read instead:
    	
    [GuiUnattended]
    ;Recommended: Specify a non-null administrative password.
    ;Any password supplied in the Sysprep.inf or during the Mini-Setup will only take effect if the
    ;original source for the image (master computer) had a non-null password.
    AdminPassword = *

  12. Chapter 25, Automating Client installation and Upgrade, page 952

    Sysprep blanks existing TAPI settings.

    Description
    When TAPI settings are not included in the Sysprep.inf file, Sysprep clears the existing TAPI settings.
    Resolution
    Add the following note to the section, Sysprep.inf:
    If the customer includes TAPI information in the master computer and runs Sysprep, and the Sysdprep.inf that is used does not include TAPI settings, the TAPI values set on the master computer will be erased. The user will not be prompted for TAPI settings if a Sysprep.inf is used.

  13. Chapter 25: Automating Client installation and Upgrade, page 950, Sysprep files

    Additional functionality allows you to reduce the number of master images used for deploying Windows 2000 with Sysprep.

    Description
    By using Sysprep you can minimize the number of images you need to use for deploying Windows 2000 to both multi-processor (MP) to uni-processor (UP) computers or UP to MP computers. However, this will only work for APIC or Advanced Configuration and Power Interface (ACPI) APIC computers with the compatible HALs.

    Note

    • At the time that Windows 2000 released, most uni-processor computers were using Processor Interrupt Controller (PIC) HALs rather than APIC HALs. PIC is not compatible with APIC, regardless of the number of processors.
    • ACPI and non-ACPI HALs are not compatible.
    • Additionally, you might find that HALs vary between vendors and some computer manufacturers provide their own HALs.
    Resolution

    There are two methods for creating images that you can use between MP and UP systems. Each method has advantages and disadvantages associated with it, as outline in the following sections. Choose the method that works best for you and your environment.

    The following table illustrates the compatibility of computers based on their HAL type. One image is required for each compatibility group.

    The following table illustrates the compatibility of computers based on their HAL type. One image is required for each compatibility group.

    Compatibility ACPI PIC ACPI APIC UP ACPI APIC MP Non-ACPI UP PIC Non-ACPI APIC UP Non-ACPI APIC MP Non-ACPI UP PIC
    ACPI PIC x            
    ACPI APIC UP   x x        
    ACPI APIC MP   x x        
    Non-ACPI APIC UP         x x  
    Non-ACPI UP PIC       x      
    Non-ACPI APIC MP         x x  
    Non-ACPI UP PIC             x

    MP to UP

    For this process, the image is created on an MP master computer. This image can be used on other MP computers or on UP computers.


    Important

    This image can only be used in one of the following configurations depending on the HAL type you are using:

    To create an MP to UP image

    Copy all six files from the Windows 2000 operating system CD under cd-rom:\i386\Uniproc to the \Sysprep\i386 folder of your distribution folders, for example, \$OEM$\$1\Sysprep\i386\Uniproc. These files include: Mp2up.inf, Mp2up.cat, Kernel32.dl_, Ntdll.dll, Win32k.sy_, and Winsrv.dl_. You do not need to expand the unexpanded files since the detection will do this automatically when needed.

    Important

    If a Service Pack becomes available that updates the files in the \i386\Uniproc folder, be sure to update the files on both the master image in the C:\Sysprep\i386\Uniproc folder and on your distribution folders under the \$OEM$\$1\Sysprep\i386\Uniproc folder.


  14. Chapter 25: Automating Client Installation and Upgrade, page 950

    Sysprep resets custom connectoid names.
    Description
    If Sysprep is run with a connectoid that is given a nondefault name, the name is reset to "Local Area Connection."
    Resolution
    Use connectoids with default names while running Sysprep.

  15. Appendix C: Sample Answer Files for Unattended Setup, pages 1041, 1043, 1046, 1049, 1051, 1055

    InstallDefaultComponents key is removed from Unattended Setup.

    Description
    In the Sample Answer Files for Unattended Setup section, InstallDefaultComponents has been removed from Unattended Setup.
    Resolution
    In all references to InstallDefaultComponents in the sample answer files, InstallDefaultComponents=No has no value. The removal of InstallDefaultComponents has no impact on the networking header.

  16. New appendix: Windows 2000 Server and Professional System Requirements

    Windows 2000 Server System Requirements Windows 2000 Professional System Requirements For CD-ROM installation: For network installation: