Windows 2000 Service Pack 3 Beta Release Notes

1.0 Introduction

This document provides complementary or late-breaking information about service pack installations of the Microsoft Windows 2000 family of products.

2.0 Corrections

Read these notes carefully before you install Service Pack 3 (SP3). Installation methods may have changed since the last service pack release.

2.1 Remove previous beta builds before upgrade

Remove any previous beta builds of Service Pack 2 before installing an updated build (or final release build). A beta build installed over another beta build is not supported.

2.2. Windows 2000 Datacenter Server customers

If you are a Windows 2000 Datacenter Server customer, please contact your original equipment manufacturer (OEM) for information about how service packs can be deployed on your systems.

2.3. Terminal Services Advanced Client (TSAC) documentation

If you install the optional component TSAC, note that the ReadMe.htm file located in the \ValueAdd\TSAC folder on the SP3 CD refers to Service Pack 1 instead of SP3. There are no current plans to update this file, but the content is valid for SP3.

2.4 Before you install SP3

This section relates to ReadMeSP.htm found on your SP3 CD. The beginning of Section 2.1 Before You Install the Service Pack should read as follows:

2.1 Before You Install the Service Pack

Before you install this service pack:

• Close all debuggers
• Close all antivirus programs.

To maximize recovery of the computer in the event of installation failure, follow these steps:

• Update the system Emergency Repair Disk:

1. Click Start, point to Programs, point to Accessories, point to System Tools, and then click Backup.
2. On the Welcome tab, click Emergency Repair Disk.
3. Select Also backup the registry to the repair directory and then click OK.

• Perform a full backup of the computer.

Continue the installation by following the instructions from Section 2.2 Space Requirements for the Service Pack in ReadMeSP.htm.

2.5 How to Obtain the Windows Installer Package (Update.msi) for SP3

For details about obtaining this package, see the Knowledge Base article Q269732.

2.6 System files backup location

The Service Pack Setup Wizard allows you to choose the directory for backing up your system files. These are necessary if you decide to remove SP3. To save space on the system partition, you can choose to make your backup on a separate disk drive.

To select a location other than the default, click Archive Files and then click Change Folder.

You are advised not to select a drive on a remote computer.

2.7 Message Queuing (MSMQ)

When you upgrade a server cluster that contains an MSMQ resource to the beta version of SP3, the dependent network name resource fails to go online. The same issue occurs with new installations of MSMQ resources on a server cluster running the beta version of SP3. This note provides steps to work around this issue.

Note

This issue does not exist if you are running MSMQ in workgroup mode. You can disregard these steps.

Preparing MSMQ on a cluster for upgrade to the beta version of SP3

If you have configured MSMQ on a cluster, follow this procedure to upgrade to SP3:

1. Identify the dependent Network Name Resource for each MSMQ resource:
   1. Open Cluster Administrator by clicking Administrative Tools and then clicking Cluster Administrator.
   2. Double-click the Message Queuing resource and then click the Dependency tab for each MSMQ resource in the cluster.
   3. Identify each Network Name Resource from the dependency list.
2. At the command line, take each Network Name Resource offline:
   cluster res <NetworkNameResource> /off
    
3. At the command line, run the following for each identified Network Name Resource to set the RequireKerberos property to 1:
   cluster res <NetworkNameResource> /priv RequireKerberos=1:dword
4. Bring the Network Name Resource online.
5. Upgrade any node to the beta version of SP3.
6. After this node has rebooted, move all the resources to that node while upgrading other nodes in the cluster.

This procedure only needs to be completed on one node in the cluster. Other nodes can now be upgraded to the beta version of SP3.

Creating a new MSMQ resource on a cluster running the beta version of SP3

To configure MSMQ on a cluster with the beta version of SP3 installed, follow this procedure:

1. Identify the MSMQ dependent Network Name Resource as described for a standard installation.
2. At the command line, follow this procedure:
   1. Take the Network Name Resource offline:
      cluster res [NetworkNameResource] /off
   2. Set the RequireKerberos property to 1:
      cluster res [NetworkNameResource] /priv RequireKerberos=1:dword
   3. Bring the Network Name Resource online:
      cluster res [NetworkNameResource] /on
3. Create the MSMQ resource and bring it online.

Note

MSMQ resource depends on Physical Disk resource and Network Name resource.

2.8 Removing SP3

If you choose to remove SP3, a dialog box displays the applications you installed since you upgraded to SP3. If you continue with the removal, these applications might not work correctly.

For some applications, multiple descriptions of the application might display instead of a single generic description. These additional descriptions are redundant.

If you find applications do not work correctly after you remove SP3, re-install them.

2.9 Multilingual User Interface (MUI)

If you run the telnet client on a MUI system running the beta version of SP3 and try to access a server that requires logon information, the following dialog box displays in English only, regardless of the language of your interface:

You are about to send your password information to a remote computer in <name of> zone. This might not be safe. Do you want to send it anyway (y/n):

This does not cause any errors or issues with the telnet client.

2.10 Domain controllers running the beta version of SP3

After installing the beta version of SP3 on a domain controller, the Service Control Manager might report a failure during startup. If a dialog box displays at least one service or driver failure during startup, use the Event Viewer to examine the event log:

Click Start, point to Settings, and then click Control Panel. Double-click Administrative Tools, and then double-click Event Viewer. Check the log for the following event type:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7022
Date: <date>
Time: <time>
User: N/A
Computer: <machine name>
Description: The Kerberos Key Distribution Center service hung on starting.

If this event type is reported in the log, open the Services snap-in:

Click Start, point to Settings, and then click Control Panel. Double-click Administrative Tools, and then double-click Services.

Check the Kerberos Key Distribution Center entry. If the Status field is set to Started, the event was generated only because the service took longer than expected to initialize. This does not cause any issues and no action is necessary.