FREE ESSAY ON WINDOWS 2000

WINDOWS 2000

Microsoft? Windows? 2000 Professional,
Windows 2000 Server, and
Windows 2000 Advanced Server
Release Notes
This document provides late-breaking or other information that supplements the Microsoft
Windows 2000 documentation.
Information in this document, including URL and other Internet Web site references, is
subject to change without notice. Unless otherwise noted, the example companies,
organizations, products, people, and events depicted herein are fictitious and no
association with any real company, organization, product, person, or event is intended or
should be inferred. Complying with all applicable copyright laws is the responsibility of
the user. Without limiting the rights under copyright, no part of this document may be
reproduced, stored in or introduced into a retrieval system, or transmitted in any form
or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for
any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other
intellectual property rights covering subject matter in this document. Except as
expressly provided in any written license agreement from Microsoft, the furnishing of
this document does not give you any license to these patents, trademarks, copyrights, or
other intellectual property.
? 1999 Microsoft Corporation. All rights reserved.
Microsoft, MS-DOS, Active Directory, DirectX, FrontPage, NetMeeting, Outlook, PowerPoint,
Visual Basic, Visual C++, Visual FoxPro, Visual InterDev, Visual Studio, Windows, Windows
Media, and Windows NT are either registered trademarks or trademarks of Microsoft
Corporation in the United States and/or other countries/regions.
This product contains graphics filter software; this software is based in part on the
work of the Independent JPEG Group.
The names of actual companies and products mentioned herein may be the trademarks of
their respective owners.
Contents
Introduction
Networking and Communications
Change and Configuration Management (IntelliMirror)
Windows Management Instrumentation
Security
Directory Services
Component Services
Microsoft Data Access Components
Internet Services
Microsoft Windows 2000 Server Media™ Services
Storage Notes
Hardware
Application Notes
Printing Notes
Terminal Services
Windows 2000 Advanced Server
Introduction
This document provides late-breaking or other information that supplements the Microsoft
Windows 2000 documentation. The Windows 2000 compact disc (CD) includes the following
release notes files:
? Read1st.txt, which contains important preinstallation information and is located in the
Windows 2000 CD root directory
? Installation chapters from the Getting Started Guide, which include system requirements
information and are located in the \Setuptxt folder on your Windows 2000 CD
? Readme.doc, which contains compatibility and post-installation notes and is located in
the Windows 2000 CD root directory
? The Hardware Compatibility List. For the most up-to-date list of supported hardware,
see the Hardware Compatibility List at the Microsoft Web site
(http://www.microsoft.com/hcl/). Your Windows 2000 CD includes a copy of this list
(drive:\Support\Hcl.txt) that was accurate as of the date Windows 2000 was released.
To review the latest Application Compatibility information, see the Microsoft Windows
2000 Product Compatibility Web site at:
http://www.microsoft.com/windows2000/compatible/
To review the latest release notes and updated information for Windows 2000, see the
Microsoft Knowledge Base on the Microsoft Personal Online Support Web site at:
http://support.microsoft.com/support/
Networking and Communications
The following sections describe Windows 2000 issues related to networking and
communications.
Routing and Remote Access
This section describes a known issue related to Windows 2000 Routing and Remote Access.
Enabling Windows NT? 4.0 RAS Servers in a Windows 2000 Domain
If you are using Windows NT 4.0 Remote Access Service (RAS) servers in a Windows 2000
domain, they must be running Service Pack 4 (SP4) or later. Otherwise, they cannot access
the Windows 2000 domain controllers to verify that a user has dial-in permissions. Also,
if you set up a Windows NT 4.0 RAS or Routing and Remote Access Service (RRAS) server as
a member of a Windows 2000 domain, you must make certain adjustments to Active
Directory™ so that the server can access the Remote Access credentials of domain
accounts.
You can adjust Active Directory to allow Windows NT 4.0 RAS servers by using either of
the following methods:
? When you create a Windows 2000 domain by using the Active Directory Installation wizard
to upgrade a server to a domain controller, select the option to allow legacy servers to
access Active Directory. If you enabled this access when you created the domain, no
further action is required.
? If you add a Windows NT 4.0 RAS server to a domain that has not been adjusted to allow
legacy server access, you can use the following command to adjust domain security for
legacy server access:
net localgroup Pre-Windows 2000 Compatible Access everyone /add
After executing this command, you must restart the domain controller.
TAPI
This section describes issues related to TAPI in Windows 2000.
ATI-TV Tuner Video Cards Are Not Supported for Use With TAPI
TAPI does not support the use of ATI video cards that incorporate TV tuners, including
but not limited to ATI-TV, ATI-TV WONDER, and All-in-Wonder models. This will be
addressed in a future release.
Kodak USB Cameras Are Not Supported
Windows 2000 does not include drivers for Kodak Universal Serial Bus (USB) cameras. To
download the latest drivers, visit the Kodak Web site at:
http://www.kodak.com/
This will be addressed in a future release.
Note
Web addresses can change, so you may be unable to connect to the Web site mentioned
here.
DHCP
In the online Help for the Dynamic Host Configuration Protocol (DHCP) servers, the
instructions that describe how to move a DHCP database from one server to another are
incomplete. For complete instructions, see the Knowledge Base on the Microsoft Personal
Online Support Web site at:
http://support.microsoft.com/support/
Autonet
On a multi-homed computer, if two or more interfaces are using an Automatic Private
Internet Protocol Addressing (APIPA)-based address simultaneously, the routing behavior
of the computer for any destination on the APIPA subnet is inconsistent. For more
information about this Autonet issue, visit the Knowledge Base on the Microsoft Personal
Online Support Web site at:
http://support.microsoft.com/support/
Change and Configuration Management (IntelliMirror)
The following section describes Windows 2000 issues related to change and configuration
management.
Group Policy
It is strongly recommended that you limit the computer name used by domain controllers to
15 characters. Longer computer names may cause the installation failure of applications
that are deployed by using the Software Installation snap-in to Group Policy. For more
detailed information, see the Knowledge Base on the Microsoft Personal Online Support Web
site at:
http://support.microsoft.com/support/
Also, to review information about a related issue, see the "Active Directory Domain Name
Length Restriction" topic later in this document.
Windows Management Instrumentation
The following section describes Windows 2000 issues related to Windows Management
Instrumentation (WMI).
WMI ODBC Driver
When you upgrade your computer to Windows 2000, the previous installation of the WMI open
database connectivity (ODBC) driver is deleted. The Windows 2000-compatible driver for
WMI ODBC is located on the Windows 2000 CD in the ValuAdd\MSFT\MGMT\WBEMODBC folder.
Security
The following sections describe issues related to Windows 2000 security features.
Certificate Services
This section describes issues related to Certificate Services in Windows 2000.
Certificate Services Setup Fails
If the name of the computer contains non-International Alphabet 5 (IA5) characters, such
as non-English characters, Certificate Services Setup fails. Use only IA5 characters to
name a computer. This will be addressed in a future release.
PKI Services Fail If the DNS Computer Name Is Greater than 64 Characters
If the fully qualified Domain Name System (DNS) computer name is greater than 64
characters, Public Key Infrastructure (PKI) services fail. This causes the following
processes to fail:
? Enterprise Certificate Authority (CA) installation
? Domain controller and computer automatic enrollment
? Internet Protocol Security (IPSec) enrollment
Installation of Certificate Services in a Child Domain
To install Certification Services for a child domain in the enterprise, you must be a
member of the Enterprise Administrators group, which is in the parent domain.
CA Service Stops Running After a File System Upgrade from FAT to NTFS
The CA service stops running after a file system upgrade from FAT to the NTFS file
system. The following message appears in the application log:
"Certificate Services did not start: Unable to initialize the database connection for
*Your CA Name here*. Class not registered 0x80040154."
As a workaround, uninstall the CA service and then re-install it using the same CA name,
key pair, and database as the previous installation.
Upgrade of Subordinate CA from Windows NT 4.0 Certificate Server
After you upgrade a subordinate CA that is running Windows NT 4.0 Option Pack Certificate
Server 1.0 to Windows 2000, you must perform a CA renewal operation and create a new CA
certificate with the Basic Constraints field set to TRUE for the CA value. Before the SP6
release of Windows NT 4.0, the Certificate Server 1.0 product did not set the CA value to
TRUE in the Basic Constraints field in the CA certificate. In SP6, if you are installing
the CA for the first time, the CA value is set to TRUE in the CA certificate. In Windows
2000, if you are installing the CA for the first time or if you are performing a CA
renewal operation on an existing CA, the CA value is set to TRUE in the CA certificate.
Default Security Settings
This section describes issues related to the default security settings in Windows 2000.
File and Registry Permissions Are Changed During Upgrade
The default security settings for a clean installation are also applied when you upgrade
to Windows 2000. Applying the same default security settings ensures that access
permissions for the registry and for Windows 2000 system directories and files are set
consistently. However, if the default security settings are not sufficient after you
upgrade to Windows 2000, you should reapply any custom settings that you applied before
the upgrade.
Windows NT 4.0 Users May Need Power User Capabilities After Upgrade
The default security settings for a clean installation are also applied when you upgrade
to Windows 2000. For more information about how these default security settings are
applied, see "File and Registry Permissions Are Changed During Upgrade," earlier in this
document.
In Windows 2000, the permissions for users who do not have administrator or power user
privileges are substantially more secure than in Windows NT 4.0. As a result, most
non-certified legacy applications do not run successfully for typical users of Windows
2000. Therefore, after you upgrade to Windows 2000 and default security settings are
applied, you may need to give power user capabilities to Windows NT 4.0 users.
When you upgrade from Windows NT 4.0 Workstation, you can provide power user capabilities
automatically by adding the Interactive group to the Power Users group. Then, when
Windows NT 4.0 users log on locally, they become power users on Windows 2000. Because
Windows 2000 power users have the same access control permissions as Windows NT 4.0
users, these users can continue to run non-certified legacy applications after they
upgrade to Windows 2000.
Notes
When you upgrade from previous versions of Windows 2000 or install Windows 2000 Server,
the Interactive group is not added to the Power Users group.
Certified Windows 2000 applications run successfully for a typical user on Windows 2000.
Therefore, certified applications offer the highest level of security without sacrificing
application functionality.
Service Account Must Be Manually Added to the Power Users Group After Upgrade
The default security settings for a clean installation are also applied when you upgrade
to Windows 2000. For more information about how these default security settings are
applied, see "File and Registry Permissions Are Changed During Upgrade," earlier in this
document.
After the default security settings are applied in Windows 2000, services that previously
ran under a non-administrative or non-system context on Windows NT 4.0 may no longer work
properly. This occurs because Windows 2000 users have fewer permissions than Windows NT
4.0 users. Therefore, after you upgrade to Windows 2000, you must manually add the
service account to the Power Users group.
High Encryption Pack—Upgrading from 128-bit Encryption on Down-Level Platforms
When you upgrade the 128-bit version of Windows 95 with Microsoft Internet Explorer 3.02
to Windows 2000, the encryption is reduced to 40-bit. As a workaround, you can install
the Windows 2000 High Encryption Pack, which enables you to upgrade to 128-bit
encryption.
EFS Recovery and Private Key Issues When Joining a New Windows 2000 Domain
When you upgrade a computer from Windows 95 or Windows 98 to Windows 2000, you may
experience problems after joining the new domain because of issues with Encrypting File
System (EFS) recovery and migrating private cryptographic keys. After you upgrade the
computer, you should not use EFS until the computer actually joins the new domain. If you
use EFS before your computer joins the domain, any files that you encrypt with EFS are
inaccessible to your domain logon account. In addition, you should not run applications
that use private cryptographic keys until the computer actually joins the new domain. If
you generate and use private cryptographic keys before your computer joins the domain,
these keys are unavailable to your domain logon account.
Directory Services
The following sections describe issues related to Windows 2000 directory services
features.
Active Directory Domain Name Length Restriction
The fully-qualified DNS name of an Active Directory domain, for example
example.microsoft.com, is restricted to 64 USC Transformation Format 8 (UTF-8) bytes in
length. This limit does not apply to computer names.
One ASCII character is equal to one UTF-8 byte in length. Non-ASCII characters, such as
other Unicode characters, have a variable length encoding that can be up to three bytes
in length. To estimate the size of a name in bytes, count each ASCII character as one
byte and each non-ASCII character as three bytes.
Before you deploy Active Directory, verify that all of your planned domain names do not
exceed 64 UTF-8 bytes in length.
Message Queuing
This section describes issues related to the installation of Message Queuing.
Installing Message Queuing on Computers that Do Not Have MSMQ 1.0 Installed
This section describes issues related to the installation of Message Queuing on computers
that do not have Microsoft Message Queue Server (MSMQ) 1.0 installed.
Administrative Permissions Required to Run Message Queuing Setup
The following permissions are required to install Message Queuing on a computer:
? When you install Message Queuing in either a workgroup or a domain environment, you
must have local administrative permissions for the computer.
? If you are installing Message Queuing on a Windows 2000 domain controller, you must
have permission to create the msmqSettings object that represents the computer on which
you are installing Message Queuing. The msmqSettings object is located under the
applicable server object. This applicable server object is located under the Servers
object, which is located under the applicable site object in Active Directory Sites and
Services.
Alternatively, you can have domain administrative permissions, or you can belong to the
Domain Administrators group, which has this permission by default.
? If you are installing a Message Queuing server with routing enabled on a
non﷓domain controller, you must have permission to create the applicable server
object that represents the computer on which you are installing the Message Queuing
server. This object is located under the Servers object, which is located under the
applicable site object in Active Directory Sites and Services.
Alternatively, you can have enterprise administrative permissions, or you can belong to
the Enterprise Administrators group, which has this permission by default. In addition,
if?when you are prompted during Message Queuing Setup?you enter the name of a Message
Queuing server that is running on a Windows 2000 domain controller in the local domain,
domain administrative permissions are sufficient.
For more information about object permissions for Message Queuing, see Windows 2000
Help.
Installing Message Queuing in a Windows 2000 Workgroup
For a computer that is a member of a Windows 2000 workgroup, Message Queuing is
automatically installed to operate in workgroup mode. Workgroup mode means that the
ability of the computer to access Active Directory is disabled. For more information
about workgroup mode, see Windows 2000 Help.
In addition, if you move a computer from a workgroup to a domain, Message Queuing
automatically attempts to join the new domain. However, the new domain must be a Windows
2000 domain, and it must contain a Message Queuing server that is running on a Windows
2000 domain controller with a Global Catalog server enabled. In this case, Message
Queuing operates in domain mode, which means that access to Active Directory is enabled.
Installing Message Queuing in a Windows 2000 Domain
This section describes issues related to installing Message Queuing in a domain
environment.
Operating in Workgroup or Domain Mode
If you are installing Message Queuing in a domain environment, you can select whether or
not the computer operates in workgroup mode (no access to Active Directory) or in domain
mode (access to Active Directory) by clicking the Manually select access mode to Active
Directory tab at the beginning of Message Queuing Setup.
Security Limitations for Windows 2000 Domains
All operating configurations?other than Windows 2000 domain users' computers that are
running Message Queuing on Windows 2000?introduce security limitations in Windows 2000
domains. These limitations pertain to the following operating configurations:
? In a mixed-mode domain environment where users' computers are running MSMQ 1.0 on
Windows NT 4.0, Windows 95, or Windows 98, and these computers access Message Queuing
servers running on Windows 2000 domain controllers. If these users are logged on with
Windows 2000 domain accounts, this limitation also applies.
? In a mixed-mode domain environment where users' computers are running Message Queuing
on Windows 2000 in a Windows NT 4.0 domain, and these computers access MSMQ 1.0
controller servers.
? In a Windows 2000 domain environment where users' computers are running Message Queuing
on Windows 2000, and these users are logged on with Windows NT 4.0 domain accounts.
? In a Windows 2000 domain environment where users' computers support only the
Internetwork Packet Exchange (IPX) protocol.
? In an environment where users are logged on with a Local User account regardless of the
operating system.
If any of these operating configurations apply to your organization, then to support
these users, you should weaken security for Active Directory. When Message Queuing Setup
prompts you during the first installation of Message Queuing on the first Windows 2000
domain controller in your forest, select the weakened permissions option.
Specifying a Server Name During Message Queuing Setup
Message Queuing Setup may prompt you to enter the name of a server. In most cases, you
should enter the name of a Message Queuing server that is running Windows 2000. You can
specify the name of an MSMQ 1.0 controller server (such as the primary enterprise
controller [PEC] or a primary site controller [PSC]) instead, but this scenario is
supported only if you are installing an independent client. For all other installation
types, Setup fails.
First Installation of Message Queuing in a Domain Must Be on a Domain Controller
You must install Message Queuing on a Windows 2000 domain controller before you install
Message Queuing software on any other computer in your domain. In addition, to support
Message Queuing clients, this domain controller must have the Trust computer for
delegation property enabled.
On a Windows 2000 domain controller running Windows 2000, this property is enabled by
default. If this property is disabled, Message Queuing clients cannot connect to the
domain controller, and the clients display symptoms similar to when a Message Queuing
server is offline.
Message Queuing with Routing Enabled and Message Queuing on a Domain Controller Must Be
Installed at Every Site
You must install Message Queuing on a Windows 2000 domain controller for each Windows
2000 site. In addition, you must install Message Queuing with routing enabled on a
non-domain controller at every site that has Message Queuing clients; this can be
installed on the same server computer. Failure to install Message Queuing and Message
Queuing with routing enabled may cause messages not to reach their destinations across
sites.
Also, to support MSMQ 1.0 clients running on Windows NT 4.0 in a Windows 2000 domain, you
must install Message Queuing on a Windows 2000 domain controller that is configured as a
Global Catalog server.
Installing Message Queuing on an IPX-Only Computer
When you install Message Queuing on an IPX-only computer that is running Windows 2000,
you must enter the name of a Message Queuing server that is running on a Windows 2000
domain controller when you are prompted to do so during Setup. This server must be in the
local domain.
Installing Message Queuing Using a Windows NT 4.0 Domain User Account
When you install Message Queuing on a computer that is running Windows 2000 and you use a
Windows NT 4.0 domain user account, you should have at least one Message Queuing server
that is running on a Windows 2000 domain controller in the local domain. If this is not
possible, you must enter the name of a server that meets this criteria when you are
prompted to do so during Setup.
Installing MSMQ 1.0 on Windows NT 4.0 in a Windows 2000 Domain
When you install MSMQ 1.0 on a computer that is running Windows NT 4.0 in a Windows 2000
domain, you must enter the name of a Message Queuing server in the local domain when you
are prompted for the name of a PSC during Setup. This Message Queuing server must be
running on a Windows 2000 domain controller that is also configured as a Global Catalog
server.
In addition, if you plan to install MSMQ 1.0 on computers that are running Windows NT 4.0
in a new Windows 2000 domain, you should select the pre﷓Windows 2000 compatible
check box when you run Setup for the first Windows 2000 domain controller in the local
domain.
If you plan to install MSMQ 1.0 on computers that are running Windows NT 4.0 in an
existing Windows 2000 domain, you should verify that the Everyone group is a member of
the "pre-Windows 2000 Compatible Access" group in this domain.
? To add the Everyone group to the pre-Windows 2000 Compatible Access group
1. In the MMC, open the Active Directory Computers and Users snap-in.
2. In the console tree, double-click Builtin.
3. Right-click pre-Windows 2000 Compatible Access, and then click Properties.
4. On the Members tab, click Add, and then in the list, select Everyone (if needed).
5. Click OK.
Installing MSMQ 1.0 on Windows 95 or Windows 98 in a Windows 2000 Domain
When you install MSMQ 1.0 on a computer that is running Windows 95 or Windows 98 in a
Windows 2000 domain, you must enter the name of a Message Queuing server in the local
domain when you are prompted for the name of a PSC during Setup. This Message Queuing
server must be running on a Windows 2000 domain controller that is also configured as a
Global Catalog server.
Also, you must be granted the Create Computer Objects permission, which is located under
the Computers folder object in Active Directory Users and Computers, because the computer
object for these computers does not exist in Active Directory. For more information about
the Create Computer Objects permission, see Windows 2000 Help.
Reinstalling Message Queuing in a Multi-Domain Environment
When you uninstall Message Queuing on a computer in a multi-domain environment, you must
wait for Active Directory replication to occur before you reinstall Message Queuing on
the same computer.
Installing Message Queuing on a Windows 2000 Server Cluster
Message Queuing is dependent on the Microsoft Distributed Transaction Coordinator (MS
DTC) service on a server cluster. To successfully install Message Queuing on a Windows
2000 server cluster, you must first manually cluster the MS DTC service.
? To manually cluster the MS DTC service
1. Create a cluster virtual server, which is a cluster group containing a Disk resource
and a Network Name resource.
2. On the computer node that hosts the cluster virtual server, run Comclust.exe, which is
located in the Winnt\System32 folder.
3. Run Comclust.exe on the other nodes. Do not restart any node until Comclust.exe has
been successfully started on all nodes in the server cluster.
4. Restart each computer node.
Now you can install Message Queuing on each node.
Note
The installation may fail, and a message may appear indicating that you lack the
necessary permissions. In this case, grant yourself permission to create the MSMQ
configuration (msmq) object, which is located under the computer object representing your
cluster virtual server, and then run Message Queuing Setup again. This permission is also
required to manage the cluster virtual server by using the Computer Management snap-in.
As an alternative, you can run Message Queuing Setup with an account that has domain
administrative permissions. By default, domain administrative permissions include the
permission to create the msmq object. This will be addressed in a future release.
Configuring Cluster Resources for Message Queuing
In Windows 2000 Help, the procedure that describes how to configure a cluster resource
for Message Queuing is incorrect; you should complete Step 11 before you complete Step
10. The sequence of all the other steps is correct.
Installing Message Queuing Using Unattended Setup
When you use unattended setup to install a Message Queuing server with routing (RS
installation type), the answer file script automatically attempts to resolve the site to
which the computer belongs. If subnets in your network are not configured correctly,
Message Queuing Setup may fail to resolve the site. In this case, you must specify the
default site containing the Message Queuing server that is running on a Windows 2000
domain controller with which this server will communicate.
? To specify the default site
* Add the following entry to your unattended setup answer file:
Site = *your_domain_controller_site_name*
Upgrading MSMQ 1.0 on Computers Running Windows 2000
This section describes issues related to upgrading MSMQ 1.0 on computers that have been
upgraded to the Windows 2000 operating system.
Upgrading an MSMQ 1.0 Enterprise to Windows 2000
The process of upgrading your MSMQ 1.0 enterprise to Windows 2000 is called migration.
You must perform this multi-step process correctly and in the proper sequence. It is
important that you understand all the issues and implications involved in migration. For
specific information about the issues, preparation, and execution of migration, see
"Migrating from MSMQ 1.0" on the Migration FTP site at:
ftp://ftp.microsoft.com/bussys/distapps/Msmq/Win2000/Migration/
Upgrading MSMQ 1.0 on a Server Cluster
This section provides detailed information about how to upgrade the different MSMQ 1.0
computer types on a server cluster. Unless otherwise stated, use the following general
order of events to upgrade MSMQ 1.0 on all computer types on a server cluster:
1. For a clustered PEC or PSC, run the Message Queuing Upgrade wizard (Mqmig.exe). See
the note below.
2. Upgrade the operating system of the node to Windows 2000 Advanced Server.
3. Upgrade the MS DTC resource.
4. Upgrade the MSMQ resource.
To upgrade a cluster node to Windows 2000 Advanced Server, the computer must be running
Windows NT Server 4.0 Enterprise Edition with SP4 or SP5. Windows 2000 does not support a
rolling upgrade of a Windows NT 4.0 server cluster with MSMQ 1.0 installed.
Note
When you upgrade the MSMQ resource, the Message Queuing Upgrade wizard may prompt you for
the name of a server. You should enter the name of a Message Queuing server that is
running on Windows 2000 rather than the name of an MSMQ 1.0 controller server such as the
PEC or a PSC. Otherwise, the upgrade fails.
Upgrading the MS DTC Resource
After you upgrade the operating system on each node to Windows 2000 Advanced Server, and
before you upgrade the MSMQ resource on any node, you must use Cluster Administrator to
upgrade the MS DTC resource to an active/active configuration.
To upgrade the MS DTC resource on a server cluster, complete the steps in the following
procedure.
? To upgrade the MS DTC resource on a server cluster
1. Take the MS DTC cluster resource offline.
2. Verify that all services dependent on the MS DTC cluster resource?including the
services for Message Queuing, Component Services, Microsoft SQL Server, and Microsoft COM
Transaction Integrator (COMTI)?are stopped.
3. On the node that hosts the cluster virtual server containing the MS DTC cluster
resource, from the command prompt, run Comclust.exe. This program is located in the
system folder (typically, C:\Winnt\System32).
4. On each of the remaining nodes, run Comclust.exe. Do not bring the MS DTC cluster
resource back online until Comclust.exe is running on all nodes in the server cluster.
5. Manually restart all dependent services, and then bring the MS DTC cluster resource
back online.
Upgrading the MSMQ Resource
After you successfully complete the procedure for upgrading the MS DTC resource as
described in the previous topic, "Upgrading the MS DTC Resource," use the Configure
Message Queuing Cluster Resources wizard to upgrade the MSMQ resource to provide
active/active fail-over support.
? To upgrade the MSMQ resource
1. Click Start, point to Programs, point to Administrative Tools, and then click
Configure Your Server.
2. From Configure Your Server, click Finish Setup, and then click Configure Message
Queuing Cluster Resources.
3. Follow the instructions that appear in the Configure Message Queuing Cluster Resources
wizard.
You must have enterprise administrative permissions or belong to the Enterprise
Administrators group to run the Configure Message Queuing Cluster Resources wizard on
computers that hosted MSMQ 1.0 servers (PEC, PSC, BSC, or Routing servers) before the
upgrade.
Upgrading MSMQ Routing Servers, BSCs, and Independent Clients on a Server Cluster
You should upgrade the MSMQ 1.0 routing servers and MSMQ 1.0 Backup Site Controllers
(BSCs) on a server cluster to Message Queuing servers with routing enabled. You should
upgrade MSMQ 1.0 independent clients to Message Queuing independent clients.
To upgrade these computers on a server cluster, complete the steps in the following
procedure.
? To upgrade the MSMQ routing servers, BSCs, and independent clients on a server cluster
1. Upgrade the operating system on each node to Windows 2000 Advanced Server.
2. Use Comclust.exe to upgrade the MS DTC resource on each node.
3. Use the Configure Message Queuing Cluster Resources wizard to upgrade the MSMQ 1.0
resource on each node.
Upgrading the PEC and PSCs on a Server Cluster
In Windows 2000 Message Queuing deployment, the role of the PEC and the PSCs is delegated
to Message Queuing servers running on Windows 2000 domain controllers. Because Windows
2000 domain controllers cannot be clustered, upgrading the PEC and PSCs to Windows 2000
is a multi-step process. During this process, the MSMQ Information Store (MQIS) data is
imported from the PEC or PSC to a Message Queuing server that is running on a Windows
2000 domain controller located outside of the server cluster.
You must perform this upgrade process correctly and in the proper sequence. It is
important that you understand all the issues and implications involved in this process.
For specific information about the issues, preparation, and execution of the PEC and PSCs
upgrade on a server cluster, see "Migrating from MSMQ 1.0" on the Migration FTP site at:
ftp://ftp.microsoft.com/bussys/distapps/Msmq/Win2000/Migration/
NTLM Version 2 Authentication for Windows 95 and Windows 98 Directory Services Clients
For information about how to enable and disable Windows NT LAN Manager (NTLM) version 2
and LAN Manager (LM) authentication for Windows 95 and Windows 98 Directory Services
clients, visit the Knowledge Base on the Microsoft Personal Online Support Web site at:
http://support.microsoft.com/support/
Component Services
The following sections describe issues related to Windows 2000 Component Services
features.
Component Services Setup
Depending on the current configuration of your operating system, you may encounter some
of the following issues that relate to upgrading existing installations of Microsoft
Transaction Service (MTS) and Component Services:
? If you are using either MTS 2.0, which is part of the Windows NT 4.0 Option Pack,
Component Services automatically replaces MTS. All user-defined packages will be upgraded
to COM+ applications. All components should work as they did under MTS 2.0.
? If you are using MTS 1.0, Component Services automatically replaces MTS. However,
user-defined packages are lost, and you must re-create them.
? If you are using either MTS 1.0 or MTS 2.0 and you have installed the SDK option, the
SDK files are removed. You may want to install the latest Component Services SDK, which
is available with the Microsoft Platform SDK.
? If a Component Services application is marked as not changeable, the Comrepl.exe
utility or the Iissync.exe utility does not properly replicate its identity. For this
release, you must mark the application as changeable before initiating the replication.
For additional information about Comrepl.exe, see the Component Services online
documentation. For additional information about Iissync.exe, see the Internet Information
Services (IIS) documentation. This will be addressed in a future release.
? When you re-install over a Component Services application that has been marked as not
deletable, neither the Component Services snap-in nor the Component Services
administrative interfaces return an error. However, the application is not updated. For
this release, you must either mark the application as deletable or modify the
installation code to check whether an application exists before installing it.
To download Component Services documentation and samples, see the Microsoft Platform SDK:
COM Components Web site at:
http://www.microsoft.com/msdownload/platformsdk/com.htm
Upgrading MTS 2.0 Installations to
Windows 2000 with Component Services
When you upgrade a computer running Windows NT 4.0 with Windows NT 4.0 Option Pack,
Windows 95 with Personal Web Server from the Windows NT 4.0 Option Pack, or Windows 98
with Personal Web Server to Windows 2000, Setup automatically migrates all existing MTS
packages to Component Services applications.
Note
Before you use, import, or export the migrated packages, it is important to review the
migration log file that is generated during the migration process even if the upgrade
appears successful. If this migration fails or encounters a problem that is not fatal, a
message appears and an event log entry or log file is generated that describes the reason
for the failure.
As an alternate approach to migrating MTS 2.0 packages to Component Services, do the
following:
1. Use the MTS 2.0 Package Export feature to export the MTS packages on the computer
running Windows NT 4.0, Windows 95, or Windows 98. This export process produces a .pak
file for each exported package and a collection of other files.
2. Perform a clean installation of Windows 2000, or delete the MTS packages and upgrade
to Windows 2000.
3. Use the Application Install feature of the Component Services administrative tool to
install the .pak files on a Windows 2000 computer.
Application Proxy Installation
If an application proxy (.msi file) for the same server application is
re﷓exported, before you install the new application proxy, you must uninstall the
earlier application proxy from the computer. Otherwise, both application proxies appear
when you open Add/Remove Programs in Control Panel. Additionally, changes contained in
the new application proxy may not be applied to the computer. No message or error log is
generated. This will be addressed in a future release.
Upgrading from Component Services (Beta Version) with MSCS
If you are upgrading from a previous beta version of Windows 2000 on a Microsoft Cluster
Server (MSCS) cluster with the Component Load Balancing (CLB) router enabled, you may
have configured the cluster for use with the CLB service. You need to remove the earlier
configurations to avoid unnecessary errors in the event log.
? To remove the earlier configurations
* At the command prompt, type:
comclust -r
Microsoft Distributed Transaction Coordinator
This section describes issues related to the MS DTC.
Performing Distributed Transactions with
Windows NT 3.51 and Windows NT 4.0
MS DTC uses a new protocol for performing distributed transactions on Windows 2000. As a
result of this protocol change, a distributed transaction can no longer flow from a
Windows 95, Windows 98, Windows NT 3.51, or Windows NT 4.0 computer to a Windows 2000
computer. However, a distributed transaction can flow from a Windows 2000 computer to any
of these computers.
If you are running the Window NT 4.0 Option Pack, you can circumvent this limitation by
installing either Windows NT 4.0 SP4 or SP5. If you are running Windows NT 4.0, you can
also circumvent the problem by installing QFE 810, which is located at:
ftp://ftp.microsoft.com/bussys/distapps/MTS/Public-Fixes/usa/DTC/SvcPack/
No patch is available for Windows 95, Windows 98, or Windows NT 3.51.
Reinstalling MS DTC After Installing Microsoft SQL Server™
Whenever you install SQL Server 6.5, SQL Server 7.0, or any SQL Server 6.5 or SQL Server
7.0 SP release, you must reinstall MS DTC. This reinstallation is necessary because SQL
Server Setup installs an obsolete version of MS DTC that is incompatible with Component
Services on Windows 2000.
? To reinstall MS DTC on a non-clustered system
1. Stop the MS DTC service. Also stop any services that depend on MS DTC, including
Component Services, Microsoft SQL Server, Microsoft Message Queuing, and Microsoft
COMTI.
2. Execute the Dtcsetup.exe program, which is located in the System32 folder.
3. Restart any services that depend on MS DTC.
? To reinstall MS DTC on a cluster with an existing MS DTC cluster
1. Use the MSCS Cluster Administrator to stop the MS DTC cluster resource. Also stop any
services that depend on MS DTC, including Component Services, Microsoft SQL Server,
Microsoft Message Queuing, and Microsoft COMTI.
2. Execute the Dtcsetup.exe program, which is located in the System32 folder, on the node
that controls the MS DTC cluster resource. When you are prompted to install MS DTC on the
other nodes in the cluster, run Dtcsetup.exe on those nodes.
Do not restart any system until MS DTC Setup has been successfully run on all systems in
the cluster.
3. Restart all systems and also any services that depend upon MS DTC.
MS DTC Does Not Support
Rolling Upgrades on MSCS Clusters
MS DTC does not support rolling upgrades on MSCS clusters. When you install MS DTC on a
cluster, you must do the following:
1. Stop MS DTC.
2. Upgrade MS DTC on all nodes in the cluster.
3. Restart MS DTC.
These steps are necessary because MS DTC maintains a single MS DTC log file for the
entire cluster, and the new information has been added to the MS DTC log file for the
Windows 2000 release.
In-Memory Database
After evaluating customer feedback from the Microsoft Windows 2000 Beta Program,
Microsoft has determined that the In-Memory Database (IMDB) does not completely address
the needs of most customer scenarios. The IMDB does not support query processing or
stored procedures, and it requires customers to implement a different database access
method.
The Transactional Shared Property Manager (TSPM), which was built on top of IMDB, has
also been removed from Windows 2000. However, the Shared Property Manager technology that
was initially released with MTS in Windows NT 4.0 is still available with Component
Services in Windows 2000.
For additional information about IMDB, see the "What Happened to IMDB?" topic on the MSDN
Web site at:
http://msdn.microsoft.com/library/techart/whatimdb.htm
Removing COMTI Components with Component Services and Windows 2000
COMTI is a component of SNA Server 4.0 and later. When you remove a COMTI component from
a Component Services application, it does not disappear from the COMTI Remote Environment
pane. However, the component is removed from the COM+ Application Components pane.
Although this produces an inconsistent display, you can deploy a new component with the
same Class ID without causing an error.
Microsoft Data Access Components
Microsoft Data Access Components (MDAC) is automatically installed with Windows 2000. To
obtain the most current information about MDAC 2.5 and known MDAC issues, see the MDAC
release notes, which are installed at:
*system drive*:\Program Files\Common files\System\ADO
\MDACReadme.htm
For more information about MDAC, see the Microsoft Universal Data Access Web site at:
http://www.microsoft.com/data/
Internet Services
The following section describes Windows 2000 issues related to Internet services
features.
Internet Information Services
To obtain the most recent information about installation, documentation, and other known
IIS issues, type the following link into the address bar of your browser (or click Start,
click Run, and type the link):
file:\\%systemroot%\Help\Iishelp\Iis\Htm\Core\Readme.htm
where %systemroot% is your Windows 2000 installation path, including drive and directory
(for example, C:\Winnt).
IIS is not installed by default on Windows 2000 Professional. If you cannot view the IIS
release notes from the link above, you need to install IIS by using Add/Remove Programs
in Control Panel.
Client Certificate Is Not Trusted or Is Invalid
A problem in the certificate trusts list (CTL) may cause the following 403.16 message to
display for valid certificates:
"Client certificate untrusted or invalid"
As a workaround, install a copy of the root certificate from the Trusted Root
Certification Authorities to the Intermediate Certification Authorities store for the
Local computer. This will be addressed in a future release.
Cannot Change Anonymous Account
IIS 5.0 restricts changes to the Windows 2000 user account for anonymous authentications
that are made below the service level and that contain an "IUSR_" account prefix. This
restriction ensures proper functioning of the IUSR_computername account, which should not
be altered in any way. If you require multiple anonymous authentication accounts, create
new accounts that do not contain the "IUSR_" account prefix, assign account permissions
to log on locally, and then add the accounts to the Guest User group.
Microsoft Windows 2000 Server Media™ Services
The following sections provide information and describe issues that affect Windows Media
Services, an optional component of Windows 2000.
Logging Multicast and Unicast Client Information in Netscape Navigator
Netscape Navigator 3.04 may fail to obtain the Uniform Resource Locator (URL) of the Web
page that contains the embedded client. This prevents the client information—the
URL value of the cs(Referrer) field—from being properly logged when you use
Netscape Navigator 3.04.
Using Windows Media Services Components and Microsoft Site Server with the Membership
Authentication Plug-In
A known "boot race" problem exists when you use Windows Media Services components with
Microsoft Site Server version 3.0 and you have enabled the Site Server Membership
Authentication plug-in. This plug-in does not load when Windows Media Services starts,
and clients cannot connect to Windows Media Services.
When this problem occurs, the Windows 2000 Server Event Log service does not log the
error. To verify the failure, use Windows Media Administrator to connect to Windows Media
Services. Windows Media Administrator messages appear, indicating that the plug-in has
not started and prompting you to restart the Windows Media Unicast service.
As a workaround, restart the Windows Media Unicast service.
HTTP Streaming Can Cause Errors
After enabling Hypertext Transfer Protocol (HTTP) streaming in the Windows Media
Administrator, you must restart your computer. Otherwise, the Windows Media Services
Event Log fills up with error events.
Storage Notes
The following sections describe Windows 2000 issues related to storage.
Offline Folders
Do not use the Offline Folders feature with Distributed File System (DFS) volumes or
shares.
File Systems
After you convert a FAT file system to NTFS, all files and folders are set with the
following Access Control List (ACL):
? Administrators Full Control (not inherited)
? System Full Control (not inherited)
? Everyone Full Control (inheritable)
You can fix the inheritance settings at the root of the volume in Microsoft Explorer.
? To fix the inheritance settings at the root of the volume in Microsoft Explorer
1. In Microsoft Explorer, right-click the root directory, and then click Properties.
2. On the Security tab, click Advanced.
3. Double-click the Administrators entry.
4. On the Permission Entry page, change Apply onto: to This folder, subfolders and
files.
5. Double-click the System entry.
6. On the Permission Entry page, change Apply onto: to This folder, subfolders and
files.
7. Click OK.
Logical Disk Manager
This section describes known issues that apply to the Logical Disk Manager.
Disks That Are Members of Fault﷓Tolerant Sets (Mirror or RAID﷓5)
If you upgrade from a previous version of Windows 2000, a disk that is a member of a
fault-tolerant set (mirror or RAID﷓5) may become orphaned during graphical user
interface (GUI)﷓mode Setup. No data is lost. You can use the Disk Administrator
MMC snap-in to rebuild the disk.
? To use the Disk Administrator MMC snap-in to rebuild the disk
1. Start the Disk Administrator MMC snap-in.
2. For a mirror disk, click Resynchronize Mirror, or for a RAID﷓5 disk, click
Regenerate Parity.
The redundant information for the volume is rebuilt.
Creating Logical Drives Within Extended Partitions on Basic Disks
If you are upgrading from Windows NT 4.0 to Windows 2000 and you attempt to create
logical drives within extended partitions on basic disks, a drive geometry translation
error may cause the Logical Disk Manager to display the following message:
"Parameter is incorrect."
This may also occur with raw installations on disks with no signatures. No workaround is
available at this time.
Converting System or Boot Volumes from Basic to Dynamic
You should convert system or boot volumes from basic to dynamic independent of any other
volume conversion. In particular, before you attempt to import disks from another
computer, restart your computer.
Mirroring Combined System﷓Boot Volumes on Systems with OEM Partitions
Mirroring combined system﷓boot volumes on systems with Original Equipment
Manufacturer (OEM) partitions may require extra care. Whenever you mirror your system or
boot partition, you should verify that the system starts from both the original and newly
created mirrored partitions. On systems with OEM partitions, complete the following
steps:
1. Ensure that the target disk for the mirror is basic.
2. Create a basic partition equal to the size of the OEM partition.
3. Convert the disk to dynamic.
4. Mirror the system﷓boot volume.
Backup
This section describes known issues that apply to Windows 2000 Backup.
Backup of Remote Storage Files by Legacy Backup Applications
Legacy backup applications include Windows NT 4.0 and earlier versions of Backup, and
also any third-party backup applications that do not ship with Windows 2000 and do not
recognize remote storage files. When using legacy backup applications to back-up remote
storage files which are migrated to tape, Remote Storage opens by default the files with
the FILE_OPEN_NO_RECALL option and streams the migrated data from tape directly to the
backup application. On a volume with large quantities of remote storage files, this may
tie up the server for long periods of time as it reads the data from tape and streams it
to the backup application. Also, the legacy backup client may take an extended period of
time to completely backup the volume.
If you do not need to backup the data in the remote storage files using the legacy backup
application, you can skip these files. On the server containing the remote storage files,
if a registry value of type REG_DWORD: exists and is set to a non-zero value for the
HKEY_LOCAL_MACHINE \System\CurrentControlSet\
Services\RsFilter\Parameters\SkipFilesForLegacyBackup registry key, the remote storage
files are skipped by the legacy backup application. By default this value is not present
in the registry. Therefore, you must add this to the registry to skip the backup of
remote storage files by the legacy backup application.
Caution
Incorrectly editing the registry may severely damage your system. Before making changes
to the registry, you should back up any valued data on the computer.
? To skip the backup of remote storage files
* Cut and paste the following text into a .reg file, and load it into the registry by
using regedit.exe:
REGEDIT4
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RSFilter\Parameters]
SkipFilesForLegacyBackup=dword:00000001
Restoring the IIS Metabase While the IIS Administration Service Is Running
The IIS Administration Service does not hold open the metabase file. Therefore, if you
restore the metabase file while the IIS Administration Service is running, the file is
overwritten by the copy in memory when the service shuts down. Then, when you restart the
computer, the IIS-managed services do not work.
As a workaround, before restoring the IIS metabase, stop the IIS Administration Service
and all the other IIS-managed services. If you do not have the IIS Administration Service
installed when you restore the IIS metabase, no action is required.
Restoring the System State from a Backup Set
When you restore the system state on a computer that is running Windows 2000 from a
backup set, do not attempt to re-join the Windows domain until after the system state has
been restored. If you attempt to rejoin the domain before the system state is restored,
the computer may respond with a message indicating that its computer account is missing.
Mounting Required Media During a Backup or Restore Operation
Do not use the Removable Storage Manager to mount tapes. When you perform a backup or
restore operation, always rely on Windows 2000 Backup to mount the required media.
Computer Not in Domain After System State Restore
After you restore everything on the computer, you must rejoin the computer with the
domain, even though the Network Identification indicates that the computer is already
part of the domain. If the computer does not rejoin the domain, the following message
appears:
"Trust relation failure."
This occurs because the unique identifier for the computer on the network changed during
the system state rebuild process. As a workaround, join a workgroup, restart the
computer, rejoin the domain, and then restart the computer again.
Restoring Applications with Long File Names
In some cases, when you restore application with long file names, Microsoft Office
applications may fail after the restore operation. This failure occurs because some
components (specifically Office) register the location of their binaries in the registry
using the short name (8.3 name). This short name may point to an incorrect location after
the application is restored because the short name generation is based upon which
application was installed first. Therefore, after you restart the computer, you must
reinstall the applications that failed.
Target Must Be as Large as the Original Backup Drive
You must perform the restore operation on partitions that are the same size (or larger)
as the partitions that are backed up. In some cases, Windows 2000 Backup may run out of
disk space while restoring to the same volume. As a workaround, make sure that sufficient
free space is available for the restore operation. When Backup restores active files, it
requires some extra disk space. Backup restores files to temporary locations, and then
moves them to the correct location when you restart the computer. This process also
requires extra disk space.
Removing Only One Piece of Media from a Backup from a Library
If you remove only one piece of media from a backup from a library, you may lose data. If
you remove the first piece of media from a spanned save set and then select the delete
media from system option in Removable Storage Manager for any of the other elements of
that save set, all media belonging to that save set on the drive is erased. If you do not
want to erase your tapes, keep all of your spanned save sets together.
Backup Fails to Start a Scheduled Job Because the Wrong Media is in the Drive
When an unexpected tape is mounted in the drive, Windows 2000 Backup does not start the
scheduled backup operation. When Backup runs, it expects to write to a specific piece of
media. If this media is not in the drive and you are not using a changer, the backup
operation fails. No notification of this failure is provided because the backup operation
is running without the user interface (UI). The backup log identifies the failure.
Backup Stops While Spanning Multiple Disks
When Windows 2000 Backup encounters a write-protected disk while spanning multiple disks,
it stops running. As a workaround, make sure that none of the media using for the backup
operation is write-protected.
Backup Shows Incorrect Elapsed and Estimated Times
Windows 2000 Backup shows the elapsed and estimated times incorrectly. No workaround is
available at this time. You can ignore the displayed time.
Backup Cannot Detect If a Remote Drive Is Removable
Windows 2000 Backup cannot detect if a remote drive is removable. It assumes that all
mapped drives are fixed disks. If a removal storage device (for example, a Jazz drive) is
located and shared from another computer on the network, and the remote device is mapped
to the local computer, Backup does not detect that the device is removable. As a
workaround, do not map a remote drive that is removable. Instead, perform the backup
operation to a remote hard disk, and then copy the files to the removable media.
Restore Does Not Recognize Media When Spanned Across Different Formats
The restore operation does not recognize media when it is spanned across different
formats. If you restore data that has been spanned across several pieces of media and if
the file systems differ across the media (for example, some media are in NTFS and some
are in FAT), the restore operation does not recognize some media as being part of the
backup set.
Backing Up to an 8-mm AME Tape on an Exabyte EXB-220 Changer
When you back up to 8-mm AME tape on an Exabyte EXB-220 changer, Windows 2000 Backup
reports a "write file mark" failure. You should upgrade this firmware to the latest 6.4.3
version.
Files Located at the End of a Large Backup Set
Files that are located at the end of a large backup set may not restore. This can affect
millions of files on data volumes larger than 100 GB. As a workaround, you can use
independent software vendor (ISV) backups that use autoloaders. Alternately, run your
backup operation in segments (start lower in the volume tree).
Backup Restores Some Additional Files from Remote Storage Media
Windows 2000 Backup restores some additional files from Remote Storage media. When Backup
is used to restore tapes created by Remote Storage, additional files may be created.
Remote Storage Manager uses these files, and they have no value outside of the this
system. No workaround is available at this time. You can ignore these files.
Path Names Greater than 1000 Characters in Length
When path names are greater than 1000 characters in length, an access violation occurs in
NTBackup.exe. Avoid using long path names for restore operations.
Restoring an Encrypted File 
that has a File Hard-Linked to it
Restoring an encrypted file that has a file hard-linked to it destroys the link to the
original file. You must manually re-link the file after the restore operation is
completed.
Running Backup over Terminal Services
When you run Windows 2000 Backup over Terminal Services, some settings may get confused.
Backing up drive letters that are mapped on both the local computer and the remote
computer may cause Backup to stop responding at the prompt (Task Manager) for scheduled
backup operations.
Restoring Exchange
If you attempt an Exchange restore operation, the Exchange Service must be running. If
this service is not running, no options display for the Exchange restore operation.
Performing a Complete System Restore
If you perform a complete system restore operation from tape, you must first complete a
minimal installation of Windows 2000 in the same directory as the previous installation.
If the directory or drive is different, the system restore operation fails. Note that
clean installations do not allow an installation location other than the default
directory. In the case where the previous installation was not in the default \Winnt
directory, you must complete a second, minimal installation in the non-default location.
If there is one installation already on the hard disk, Setup prompts you about whether
you want to overwrite the current installation or install to an alternate location.
Beginning a Backup or Restore Operation
When Windows 2000 Backup begins a backup or restore operation, it always attempts to
mount a tape. If the requested tape has already been mounted by another process, the
backup operation fails.
Hardware
The following sections describe issues related to hardware installed on computers running
Windows 2000.
Network LAN and WAN Adapters
The Windows 2000 CD includes network adapter drivers from third-party vendors. These
drivers meet Windows Hardware Quality Lab (WHQL) standards for installation and
operation. During installation, Windows 2000 detects and successfully installs most
adapters, such as Peripheral Component Interconnect (PCI), PC Cards, and Industry
Standard Architecture (ISA) Plug and Play adapters. After Windows 2000 installation
completes, you may need to manually install some adapters.
Some adapters may not function after you upgrade to Windows 2000. Changes in the
registry?such as adapter driver name changes, service dependency changes, or the use of
an obsolete network adapter driver?may cause these problems. Contact your hardware vendor
about updated files for your drivers.
You should not use 8-bit network adapters with Windows 2000. Because of customer
requirements, Windows 2000 still supports some of these adapters, but they may not
perform reliably.
Hardware Compatibility List
For the most up-to-date list of supported hardware, see the Hardware Compatibility List
at the Microsoft Web site (http://www.microsoft.com/hcl/). Your Windows 2000 CD includes
a copy of this list (drive:\Support\Hcl.txt) that was accurate as of the date Windows
2000 was released.
Plug and Play
Windows 2000 is a Plug and Play operating system. If your computer contains ISA cards,
they may be set in a manually configured mode that requires you to define the resources.
These adapters?such as sound cards, network cards, and modems?operate better in Windows
2000 if you set them to operate in ISA Plug and Play mode. For more information, refer to
your hardware vendor documentation.
Upgrading from Windows 95 or Windows 98
When you upgrade from Windows 95 or Windows 98, Windows 2000 may list the following
adapters as not supported:
? 3Com EtherLink III EISA 10/100 (3C597-TX)
? IBM Etherjet ISA Adapters
? Crystal LAN CS8920 ISA Adapter
? Olicom Plug and Play Token-Ring ISA 16/4 (OC-3118) Adapters
However, after you install Windows 2000, they work correctly. In some instances, you may
need to reset static network settings.
Upgrading from Windows NT 4.0
When you upgrade from Windows NT 4.0, Windows 2000 may list the following adapters as not
supported:
? 3Com EtherLink 905x 10/100 series of Adapters
? Compaq Ethernet or Fast Ethernet PCI Adapters
? DEC FDDI Controller PCI (Defpa) Adapters
? HP EN1207D-TX PCI 10/100 Fast Ethernet Adapters
? Intel EtherExpress PRO/10 Adapters
? Intel Pro/100 Intelligent Server Adapters (I960)
However, after you install Windows 2000, they work correctly. In some instances, you may
need to reset static network settings.
Wireless LAN Devices—Upgrading from Windows 95 or Windows 98 to Windows 2000
During the upgrade process from Windows 95 or Windows 98, site-specific configurations
(SSIDs) for wireless LAN cards do not get upgraded. In order to regain connectivity after
the upgrade, you must reapply the site-specific settings.
You can access the configuration for any adapter from the Device Manager by using the
Advanced Properties tab. You can also use some vendor-supplied utilities that are
designed for this task.
Setup Does Not Load Drivers During Upgrade (Code 32)
When you upgrade from previous beta versions of Windows 2000, some devices may be
disabled with a "Code 32" message in Device Manager. Although it is theoretically
possible that this problem could occur for multiple types of devices, it is a race
condition that is most likely to effect CardBus cards. This problem has not been
encountered on other types of devices. Also, it does not effect other upgrade paths, such
as Windows 95, Windows 98, or Windows NT 4.0, nor does it effect clean installations of
Windows 2000. 
As a workaround, you can uninstall and then re-install the device in Device Manager.
? To uninstall and then re-install the device in Device Manager
1. In Device Manager, highlight the device.
2. On the Action menu, click Uninstall.
3. After the device is uninstalled, on the Action menu, click Scan for hardware changes.
This re-installs the device and it should work properly without displaying a yellow "!"
indicator in Device Manager.
PCI Network Adapters and Media Sense
When connecting through non-N-way compliant 10/100 switches and hubs, some PCI Network
adapters that are N-way compliant cannot detect Network Media Speeds.
Adapters that Do Not Support Media Sense and Other Issues
The following adapters do not support Media Sense, do not show the correct connection
speed, cannot update the connection speed after being disabled and enabled, or do not
show that they are connected when the cable is inserted if they are restarted without
network cables attached:
? Hewlett Packard HP 27247A PC LAN/16 ISA Adapters
? Hewlett Packard HP 27250 PC LAN/8 ISA Adapters
? Hewlett Packard HP 27247B PC LAN/16 TP Plus ISA Adapters
? Hewlett Packard HP DeskDirect J2973A 10baseT PCI LAN Adapters
? Intel Pro/10+ PCI Adapters
? SMC EtherEZ 8416
? SMC EtherCard Elite 16 Ultra (8216)
LAN Adapters
This section describes issues with LAN adapters installed on computers running Windows
2000. Some LAN adapters have limited support or no support in Windows 2000.
Adapters with Known Issues
This section identifies LAN adapters with known issues related to installation and
operation on computers with Windows 2000 installed. Adapters are listed in alphabetical
order by manufacturer.
Sporadic Loss of Connectivity Under Heavy Network Load
If you have an adapter that stops sending or receiving data under heavy network load
conditions, you might consider restarting the computer to regain network connectivity.
Although these "deafness" situations are rare, you do not need to restart your computer.
With Windows 2000, with its Plug and Play network stack, you can easily make your
connection functional again by using Network and Dial﷓up Connections in Control
Panel.
? To make your connection functional again
1. Click Start, point to Settings, and then click Network and Dial-up Connections.
2. Right-click the connection that has an issue, and then click Disable.
3. Click Enable.
4. Click OK.
This re-binds the adapter to the network stack dynamically, and it makes the connection
functional again without requiring you to restart the computer.
3Com 3c509 TPC ISA Adapter
If multiple 3Com 3c509 TPC ISA adapters in EISA mode are installed and you attempt to
disconnect them through Network and Dial-up Connections, the adapters do not start again
when you reconnect them to the network. You must restart the computer.
On some computers, the 3Com 3c509 TPC ISA adapter in Plug and Play mode may not start.
This will be addressed in a future release.
3Com Fast EtherLink ISA 100BaseTX Adapter (3C515-TX)
The 3Com Fast EtherLink ISA 100BaseTX adapter (3C515-TX) may cause the computer to stop
responding when you use the Connect/Disconnect feature or when you disable or enable the
adapter through the Device Manager. This will be addressed in a future release.
Adaptec ANA62044 64-Bit 4-Port PCI Fast Ethernet Adapter
The Adaptec ANA62044 64-bit 4-port PCI Fast Ethernet adapter cannot automatically
negotiate a network connection on all four ports (usually two of the four ports show a
connection). Low power causes this problem. The adapter works correctly in a computer
that has a large power supply.
Madge ISA TR Adapter
Windows 2000 does not support multiple Madge ISA TR adapters installed in a computer.
These adapters can cause system instability and loss of network connectivity.
SMC 8216 Ultra, 8216 Ultra Tiger, and 8416 EtherEZ
Adapter resource settings of IRQ 10, I/O address 300, and RAM address CC00 on
dual-processor, Advanced Configuration Power Interface (ACPI)-compliant computers causes
a boot failure. When you install this hardware in ACPI-capable computers, make sure that
adapter resources do not conflict with other system resources. Some resource settings in
this environment can cause undesirable system instability.
When a conflict occurs with these settings in legacy (non-ACPI compliant) computers, the
systems may fail to POST.
SMC EtherEZ 8416 and SMC EtherCard Elite 16 Ultra (8216) Adapters
If you use either the SMC EtherEZ 8416 or the SMC EtherCard Elite 16 Ultra (8216)
adapter, your computer cannot connect to the network using AUI.
Adapters with Limited Support
This section identifies LAN adapters with limited support in Windows 2000. Adapters are
listed in alphabetical order by manufacturer.
The following general information applies to types of adapters with limited support:
? This release of Windows 2000 provides limited support for multiple functional PC Card
adapters. For example, Windows 2000 may detect a PC Card as modem-only when it functions
as both a network adapter and a modem. For the most up-to-date list of supported
hardware, see the Hardware Compatibility List by visiting the Microsoft Web site at:
http://www.microsoft.com/hcl/
? CardBus network adapter support is limited to computers that contain a Programmable
Interrupt Controller. Refer to your manufacturer's manual for your portable computer, or
contact your hardware manufacturer.
? CardBus multifunction adapters currently do not support the advanced power features in
Windows 2000.
? CardBus does not support WOL technology.
? This release of Windows 2000 provides limited support for multiple identical ISA
adapters.
IBM Ethernet Credit Card Adapter II PCMCIA
When the IBM Ethernet Credit Card adapter is installed in an IBM ThinkPad 760EL, 760XD,
or 765D laptop, it does not receive a DHCP address. Therefore, all network connectivity
is lost. This will be addressed in a future release.
Macronix MX98713 Adapter
The Macronix MX98713 adapter causes Advanced Configuration and Power Interface (ACPI) and
ACPI BIOS computers and MPS Hals to stop responding. As a workaround, contact Macronix
for a newer version of this adapter that functions correctly.
Madge Bus Mastering Adapters
Some Madge Bus Mastering PCI adapters may not install correctly in this release. No known
workaround is available at this time.
NE2000 or Compatible Network Adapter
If your NE2000 or compatible network adapter has an input/output (I/O) address at 340h
(0x340) and you install or upgrade to Windows 2000, your computer may stop responding
when you restart the installation in text mode. If this problem occurs, either remove the
NE2000 adapter, or change its I/O address and then restart Setup to continue the
installation. After Setup completes, the NE2000 operates normally at the I/O address
340h.
Xircom CE3 PCMCIA and Compaq Netflex 3 PCI Adapters
If Xircom CE3 PCMCIA or Compaq Netflex 3 PCI adapters are installed, ACPI-compliant
portable and desktop computers do not resume from hibernation or standby modes in Windows
2000.
To avoid this issue, disable Power Management.
? To disable Power Management
1. Click Start, point to Settings, and then click Control Panel.
2. Double-click Power Options.
3. On the Hibernate tab, clear the Enable hibernate support check box.
4. On the Power Schemes tab, in the Turn off hard disks box, click Never.
5. Click OK.
This will be addressed in a future release.
Adapters Not Supported
This section lists LAN adapters that are not supported in this release of Windows 2000.
The bus for each adapter is given in brackets. If your adapter appears in this list,
Microsoft recommends that you replace the adapter with an adapter from the HCL.
The adapters listed in this section are not included on the Windows 2000 HCL or have been
removed from this list because of driver or hardware instability or discontinued support
by the manufacturer. For additional information about discontinued adapters, contact the
manufacturer.
Additional information about some of these adapters follows this list.
3Com
? TokenLink III ISA (3C619B, 3C619C in EISA mode) [ISA]
? EtherLink OEM Adapter (3C508) [ISA]
? FDDILink-F for Optical EISA UTP/STP (3C770) [EISA]
? EtherLink MC 32 Bus Mastering Adapter (3C527) [MCA]
? Fast EtherLink 10/100Mb Bus-Master PCI (3C595-TX) [PCI]
? EtherLink III Bus-Master PCI Ethernet (3C590C) [PCI]
? EtherLink III Bus-Master PCI Ethernet (3C590TPO) [PCI]
? EtherLink III Bus-Master PCI Ethernet (3C590) [PCI]
? XJEM3288 Ethernet+Modem [PCMCIA] 
? EtherLink 16 (3C507) [ISA]
? EtherLink MC (3C523) [MCA]
? EtherLink III MC (3C529) Coax/AUI/Twisted-Pair [MCA]
? EtherLink OEM Adapter (3C508) [MCA]
Adaptec
? Ethernet Quad PeerMaster Adapter [MCA]
Allied Telesyn
? AT-1720 Series Ethernet [ISA]
? AT-1700 Series Ethernet
AMD
? AMD 1500T ISA
? AMD 2100 ISA
? AMD PCnet on-board ISA adapters on some older systems
? AMD PCnet VL [VLB]
Andrew
? Andrew ISA IIA Adapter [ISA]
Cabletron
? F70XX FDDI [EISA]
? F30XX FDDI [MCA]
? E3000 Series [MCA]
? T2000 Series [ISA]
? T3000 Series [MCA]
? E3100 Series [MCA]
? E21xx Series [ISA]
? E22xx Series [ISA]
Compaq
? Ethernet 16TP [ISA]
? Integrated NetFlex with Token Ring Module [EISA]
? Compaq Ethernet PCMCIA LAN Card [PCMCIA]
D-Link
? DE-660T [PCMCIA]
Fujitsu/ICL
? ICL EtherTeam [ISA]
Hewlett-Packard
? HP 27246A MC LAN/16 TP [MCA]
? HP Ethertwist EISA LAN Adapter/32 [EISA]
? HP 27245 PC LAN/8 TP [ISA]
? HP 27252 PC LAN/16 TL Plus [ISA]
IBM
? Ethernet Quad PeerMaster Adapter [MCA]
? EtherStreamer MC 32 Adapter [MCA]
? LANStreamer MC 16 Adapter [MCA]
? Auto LANStreamer MC 32 Adapter[MCA]
? Token Ring 4 MCA Adapter [MCA]
? LANStreamer MC 32 Adapter [MCA]
? Token Ring 4/16 MCA Adapter [MCA]
? Triple LANStreamer TR [PCI]
Intel
? TokenExpress 16S [ISA]
? TokenExpress MCA 16/4 [MCA]
? TokenExpress ISA 16/p [ISA]
? TokenExpress EISA 16/4 [EISA]
? Microdyne (DCA)
? IrmaTrac 16/4 Convertible (MCA) [MCA]
? IrmaTrac PNP 4/16 Token Ring Adapter [ISA]
? IrmaTrac 16/4 Convertible (ISA) [ISA]
? EtherExpress 16 Flash [ISA]
? EtherExpress 16C [ISA]
? EtherExpress 16 [ISA]
? EtherExpress 16TP [ISA]
? Ethernet 16E [ISA]
? EtherExpress Flash 32 [EISA]
? EtherExpress PRO/10 [PCI]
? EtherExpress PRO/100 PCI Adapter
Interphase
? Interphase 5515 155MB ATM Adapter
LinkSys
? LinkSys EC2T PCMCIA Ethernet Adapter [PCMCIA]
Madge
? Smart 16/4 MC Ringnode [MCA]
? Smart 16/4 MC32 Ringnode [MCA]
? Smart 16/4 PC Ringnode [MCA]
Microdyne
? Exos 105 [ISA]
NCR
? StarLAN 16/4 ISA Token Ring NAU [ISA]
? StarLAN 16/4 MCA Token Ring NAU [MCA]
? WaveLan AT [ISA]
? WaveLan MC [MCA]
Network Peripherals
? NP-AT FDDI [ISA]
? NP-MCA/S FDDI [MCA]
? Network Peripherals, Inc. NuCard PCI FDDI Adapter
? Network Peripherals, Inc. EISA FDDI Adapter
Olicom
? Olicom GoCard TR/Modem 288 PC Card [PCMCIA]
? Olicom Token-Ring MCA 16/4 (OC-3129) [MCA]
? Olicom GoCard TR/Modem 144 PC Card (OC-3230) [PCMCIA]
? Olicom Ethernet PCI/II 10 (OC-2185) [PCI]
Ositech
? Jack of Diamonds Multi-function (TR14401/14403)
Packet Engines
? Packet Engines G-NIC II Ethernet Adapter
? Packet Engines PEI100X Gigabit Ethernet Adapter
Proteon
? P1390 ISA Token Ring [ISA]
? P1392 ISA Token Ring [ISA]
? P1990 EISA Token Ring [EISA]
? P1892 MCA Token Ring [MCA]
Racal
? ES3210 EISA Ethernet [EISA]
? Racal InterLan XLerator/EB/NI6510 Adapter [ISA]
RNS
? RNS FDDI PCI Adapter
SMC
? ARCnet Compatible [ISA]
? EtherCard PLUS/A (MCA,BNC/AUX) (WD 8013EP/A) [MCA]
? EtherCard Elite 32 Ultra (8232) [EISA]
? EtherCard PLUS Elite 10T/A (WD/8013WP/A) [ISA]
? EtherCard PLUS Elite 16 (WD/8013EP, 8013EPC) [ISA]
? SMC 8013 WB EtherCard PLUS [ISA]
? EtherCard PLUS Elite 16 Combo (WD/8013EW or 8013EWC) [ISA]
? EtherCard PLUS Elite 16T (WD/8013W, 8013WC) [ISA]
? EtherCard PLUS 16 With Boot ROM Socket (WD/8013EBT) [ISA]
SysKonnect
? SK-NET FDDI MCA SK-52xx [MCA]
? SK-NET TR 4/16+ Token Ring [ISA]
? SK-NET Token Ring PCI [PCI]
? SK-NET G32+ EISA Ethernet [EISA]
? SK-NET FDDI ISA SK-51xx [ISA]
? SK-NET G16 /TP Ethernet [ISA]
? SK-NET FDDI EISA SK-53xx [EISA]
Thomas-Conrad
? Thomas-Conrad ARCNET/TCNS [ISA]
Xircom
? CreditCard Ethernet+Modem II (CEM2) [PCMCIA]
? CreditCard Ethernet (CE-10, CE-10/A, CE-10BT) [PCMCIA]
3Com 3c59x EtherLink III Bus-Master PCI Adapters (3c590, 3c595)
3Com has discontinued driver development and support for the 3c590 and 3c595 PCI Ethernet
adapters. 3Com suggests replacing the following cards with any PCI 10/100 adapters on the
HCL:
? XJEM3288 Ethernet+Modem [PCMCIA] 
? EtherLink 16 (3C507) [ISA]
? EtherLink MC (3C523) [MCA]
? EtherLink III MC (3C529) Coax/AUI/Twisted-Pair [MCA]
? EtherLink OEM Adapter (3C508) [MCA]
Intel EtherExpress PRO/100 PCI Adapter (E100A)
This release of Windows 2000 does not support the original Intel EtherExpress PRO/100 PCI
adapter (E100A). The E100B PCI model has replaced this adapter.
Interphase 5515 155MB ATM Adapter
This release of Windows 2000 does not support the Interphase 5515 155mb ATM adapter
(Flipper). For additional information, contact your hardware manufacturer.
Network Peripherals NuCard PCI FDDI Adapter and EISA FDDI Adapter
The Windows 2000 HCL no longer includes the following Network Peripherals adapters:
? Network Peripherals, Inc. NuCard PCI FDDI Adapter
? Network Peripherals, Inc. EISA FDDI Adapter
For more information about these adapters, contact Network Peripherals.
Packet Engines Gigabit Adapters
The Windows 2000 HCL no longer includes the following Packet Engines Gigabit adapter
models:
? Packet Engines G-NIC II Ethernet Adapter
? Packet Engines PEI100X Gigabit Ethernet Adapter
For more information about these adapters, contact Packet Engines.
RNS FDDI PCI Adapter
The Windows 2000 HCL no longer includes the RNS FDDI PCI adapter. For more information
about this adapter, contact RNS.
WAN Adapters
This section describes issues related to WAN adapters installed on computers running
Windows 2000.
WAN Upgrades
Windows 2000 does not support WAN upgrades from Windows NT 4.0.
Digi International Syncport Adapters
When you configure two Digi Syncport adapters in a back-to-back configuration, you must
edit the media access control (MAC) address on one adapter to establish a successful
connection.
All Eicon Technology WAN Adapters
To remove LAN emulation or to change to the LAN Emulation Protocol, use the Eicon
Configuration Utility, which you can locate from the Start menu. If you use the Device
Manager or the Hardware wizard to uninstall Eicon Technology WAN adapters, the adapters
do not work.
Eicon Technology WAN adapters do not support Power Management functions. Do not attempt
to use standby or hibernation modes with these adapters installed.
Eicon Technology C-Series and S94 Adapters
The Eicon C-Series and S94 adapters do not support multiple-card installations.
ISDN Adapters
This section describes issues related to ISDN adapters installed on computers running
Windows 2000.
AVM, Berlin (All ISDN Adapters)
If you plan to upgrade from Windows NT 4.0 to Windows 2000 and an AVM ISDN adapter is
installed on your computer, you must first uninstall and remove the device. After the
upgrade completes, you can reinstall and reconfigure the adapter.
Digi International Datafire RAS PCI (Primary Rate)
The Digi International Datafire RAS PCI onboard DSP-based modems are not enabled in
Windows 2000. Digi International plans to provide an update driver package. For more
information, visit the Digi International Web site at:
http://www.dgii.com/
Note
Web addresses can change, so you may be unable to connect to the Web site mentioned
here.
Multiport Serial Devices
This section describes issues related to multiport serial devices installed on computers
running Windows 2000.
Multiport Serial Upgrade
All Plug and Play Multiport Serial (MPS) adapters supported in Windows 2000 can be
upgraded from Windows NT 4.0. However, you may lose customized settings.
Comtrol, Digi, Equinox, Specialix, and Stallion ISA, PCI, and EISA Multiport Serial
Cards
If you set an ACPI-compliant computer to automatically hibernate or stand by after a set
period of time, the computer does so even if an open connection exists on the multiport
serial device. As a workaround, if you intend to maintain open multiport serial
connections for data transfer, do not set a timed hibernate or standby.
Comtrol VS1000/1100 and RocketHubs
Comtrol multiport Ethernet devices do not support hibernation or standby modes. No known
workaround is available at this time.
Digi International (IBM OEM) 8-Port PCI Card
The 8-port concentrator connected to the Digi International (IBM OEM) 8-port PCI card
does not allow modems to be successfully installed or supported. No workaround is
available at this time.
Digi International Multiport Serial Cards
After you make changes to the Properties for Digi International Multiport Serial Cards,
the Properties window remains silently active for 20 seconds. During this period, you
cannot close the Device Manager. This issue only occurs if you make changes to the
Properties.
PC Cards
This section describes known issues with various PC Cards.
Known Issues for Heavy Network Traffic
Some network adapters may lose connectivity or stop responding under heavy network
traffic. The following PC Cards may exhibit this behavior:
? 3Com Megahertz 10/100 (3C575)
? Xircom CreditCard Ethernet IIps (PS-CE2-10)
? Earlier versions of the Xircom CE2, which exhibit failures under stress load. Xircom
has resolved this problem in the current CE2 and CE3 products.
? Older legacy cards, such as ASI and Xircom, which are no longer shipped or supported.
Support is still handled on a case-by-case basis.
Modems
This section describes issues with some modems installed with Windows 2000.
Caller ID Support
If you turn on the caller ID feature, some modems may disconnect the call. This occurs
because the answering software picks up the call before the caller ID information is
received.
As a workaround, configure your call manager program (for example, Routing and Remote
Access) to answer the call after the second ring. For information about configuring your
call manager program, refer to the manufacturer's documentation.
Modems That Depend on Windows 2000 Drivers
Windows 2000 provides generic support for modems produced by the following companies,
which depend on drivers installed with the operating system:
? 3Com Corporation
? ESS Technologies
? Conexant Systems (Rockwell)
? IBM
? Lucent Technologies
These devices support data-only calls at a minimum of V.34 (33.6 Kbps). Some devices may
also support V.90 (56 Kbps).
Lucent Modems in Laptop Computers
For Lucent Technologies modems in Compaq Presario portable computers, Windows 2000
detects the modem and installs the necessary driver, but the modem does not work. This
issue will be addressed by an updated BIOS available from Compaq.
Modem Detected as Unknown Modem
Windows 2000 recognizes many modems automatically. However, if Windows 2000 does not
recognize a particular modem, it is treated as an unknown modem. As a result, Windows
2000 may not support some of the modem features.
As a workaround, reinstall the modem using an updated .inf file. To find out whether an
updated .inf file is available for your modem, contact the manufacturer or vendor. If the
.inf file is available on the Internet, download it to a floppy disk, and then install
the updated file on your computer.
? To reinstall the modem using an updated .inf file
1. Click Start, point to Settings, and then click Control Panel.
2. Double-click System.
3. On the Hardware tab, click Device Manager.
4. Expand Ports (COM & LPT), and then double-click your modem.
5. On the Driver tab, click Update Driver.
6. In the Upgrade Device Driver wizard, click Next, click Search for a suitable driver
for my device (recommended), and then click Next.
7. Insert the floppy disk with the correct driver, make sure that Floppy disk drives is
selected, and then click Next.
8. If the correct modem is selected, click Next, and the wizard completes the driver
installation.
Or, if the correct driver is not selected, click Back two times, click Display a list of
the known drivers for this device so that I can choose a specific driver, and then click
Next. When prompted, select the correct driver for your modem, and the wizard completes
the driver installation.
If an updated modem .inf file is not available, manually install the same modem or a
similar modem by the same manufacturer.
Modem Installed Twice
When you upgrade from Windows NT 4.0, Windows 95, or Windows 98, a modem may appear to be
installed twice. Verify which instance of the modem connects correctly. Then, in Control
Panel, use the Add/Remove Hardware wizard to delete the duplicate modem.
Limited Support for Multiple-Function Cards
Windows 2000 has limited support for multiple-function cards, such as PC Card network and
modem cards.
Older Modems May Fail to Reset
Older modems, such as Hayes models 9600 through 14400, may fail to reset or may reset
after several minutes when a line is disconnected during negotiation. If this occurs, a
port does not disconnect, or a BAP callback fails. If a port does not disconnect, upgrade
your modem.
If a BAP callback fails, create an entry in the registry called BapListenTimeout at
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\RasMan\ppp. This entry is a DWORD
and its units are in seconds. The default value for BapListenTimeout is 30 (seconds), and
the allowed range is 0-0xFFFFFFFF.
Important
Incorrectly editing the registry may severely damage your system. Before making changes
to the registry, you should back up any valued data on the computer.
ISDN-TA Support
Windows 2000 provides improved support for ISDN-TA products under Unimodem. You can now
configure the switch type, SPIDs, phone numbers, and protocols by using the Location
Information wizard, which is available through Phone and Modem Options in Control Panel.
Depending on the brand of ISDN-TA and the switch type it's connected to, the ISDN-TA may
sometimes fail to initiate the first call made after a new configuration is installed.
This failure occurs because of the time required to properly re-synchronize with the
switch. To fix the problem, redial the number.
3Com Courier Modem and Courier-I Modem
Windows 2000 cannot properly identify some 3Com Courier and Courier-I modems. When you
install the device, a dialog box offers likely modem names for the device you attached.
If Windows 2000 incorrectly identifies the device, the modem does not function properly.
As a workaround, remove the incorrect device and add a new modem.
? To remove the incorrect device and add a new modem
1. Click Start, point to Settings, and then click Control Panel.
2. Double-click Phone and Modem Options.
3. On the Modems tab, click the incorrect device, and then click Remove.
4. To add a new modem, click Add.
The dialog box that offers likely modem names for the device you attached appears again,
allowing you a second chance to correctly identify the device.
In addition, new firmware is available from 3Com that also corrects the identification
problems.
Storage Devices
This section describes issues with some storage devices installed on computers running
Windows 2000.
Apricorn EZ-GIG PCMCIA Card and Amacom PCMCIA FlipDisk Card
Hard disks that are connected to a system by using the Apricorn EZ-GIG PCMCIA Card or
Amacom PCMCIA FlipDisk card disappear after you restart the computer. When you insert the
Apricorn EZ-GIG PCMCIA Card or an Amacom PCMCIA FlipDisk into your computer, Windows 2000
detects and installs the device, and the hard drives connected with these devices are
accessible and function properly. However, when the computer is turned off and then
turned on again, the hard drives are no longer accessible.
As a workaround, before you turn off the computer, remove the PCMCIA card. Then, reinsert
the card after the computer is fully turned on—the card is detected and useable.
Exabyte EXB-220 Changer (Firmware Version 5.0.10)
When you back up large amounts of data to the Exabyte EXB-220 Changer (firmware version
5.0.10), Windows 2000 Backup displays the following message:
"The device reported an error on a request to write a file mark to media. Error reported:
Unknown error."
As a workaround, upgrade your Firmware to version 6.4.3. To obtain firmware version
6.4.3, visit the Exabyte Web site at:
http://www.exabyte.com/
Note
Web addresses can change, so you may be unable to connect to the Web site mentioned
here.
Iomega Parallel Port Zip Drive
When you use Add/Remove Hardware in Control Panel, Windows 2000 does not detect the
Iomega parallel port zip drive. As a workaround, use the Device Manager to detect the
Iomega parallel port zip drive.
? To detect the Iomega parallel port zip drive using the Device Manager
1. Click Start, point to Settings, and then click Control Panel.
2. Double-click System.
3. On the Hardware tab, click Device Manager.
4. Expand Ports (COM & LPT).
5. Right-click the parallel port that the Iomega parallel port zip drive is connected to,
and click Properties.
6. On the Port Settings tab, select the Enable legacy Plug and Play detection check box.
7. Click OK.
Windows 2000 should then locate the Iomega parallel port zip drive and install the
necessary drivers.
LS-120 Super Floppy Disk Drive
You cannot create startup floppy disks on a computer that has an LS-120 super floppy disk
drive and no standard floppy disk drive. When you attempt to run Makebt32.exe or
Makeboot.exe from the Windows 2000 CD, the following message appears:
"This floppy drive does not support 1.44MB disks."
As a workaround, before you attempt to run Makebt32.exe or Makeboot.exe from the Windows
2000 CD, format a 1.44MB disk for the LS-120.
Mylex DAC960 RAID Controllers
Some ACPI computers with Mylex DAC960 redundant array of independent disks (RAID)
controllers may not return from standby mode correctly. As a workaround, do not enable or
use standby mode for computers with Mylex DAC960 RAID controllers. This problem will be
fixed by Mylex in new hardware versions; no solution is available for their current
hardware.
Graphics Display Adapters and Monitors
This section describes issues with some graphics display adapters and monitors installed
on computers running Windows 2000.
ISA-Based Display Adapters
When you perform a clean installation of Windows 2000 or when you upgrade from Windows NT
4.0, Windows 2000 does not detect ISA-based display adapters. You must manually install
the correct driver for the display adapter.
Chipset-Specific Issues
The issues described in this section were identified by testing the drivers shipped with
Windows 2000. The hardware manufacturers may already provide newer versions of these
drivers that do not exhibit these issues. For newer revisions of these drivers, check
Microsoft Windows Update.
3dfx Voodoo2 Chipset
In Windows 2000, you can use boards based on the Voodoo2 chipset only as a secondary
display adapter in a configuration with more than one monitor. The Windows 2000
architecture does not currently support the use of a 3-D-only board. Therefore, the
Voodoo3 Pass Thru feature and the Scan Line Interleave (SLI) capability are not
available.
Because performance in this configuration is not optimal, the use of Voodoo2﷓based
display adapters on Windows 2000 is, in most cases, appropriate only for development
work. Microsoft and 3dfx provide Voodoo2 device drivers from the following developer
support Web sites:
? The Microsoft DirectX? Web site at:
http://www.microsoft.com/directx/
? The 3dfx Total Immersion Developer's Program Web site at:
http://www-dev.3dfx.com/
Note
Web addresses can change, so you may be unable to connect to the Web sites mentioned
here.
ATI Mach64 Display Adapter
If you use the ATI Mach 64 display adapter with the drivers included in Windows 2000,
when you start Return to Krondor, the application stops responding.
ATI Rage Pro Display Adapter
When you run the Microsoft Combat Flight Simulator application, you may experience
corrupt displays. As a workaround, change the application settings so that they do not
use hardware acceleration.
ATI Rage Pro, Rage LT Pro, Rage Mobility, Rage XL/XC, Rage II, Rage IIC, ATI264-VT4
Display Adapters
The following issues apply to the ATI Rage Pro, Rage LT Pro, Rage Mobility, Rage XL/XC,
Rage II, Rage IIC, ATI264-VT4 (not Rage 128) display adapters:
? Highlighting is not working correctly, and highlighted text disappears.
? When you scroll content in a window or move a window around, your computer stops
responding for several seconds.
As a workaround, create a registry value named FastFillDisabled, data type = REG_DWORD,
value = 1, and then restart your computer. For Rage Pro, LT Pro, Rage Mobility, and Rage
XL/XC display adapters, create the value under
HKLM\SYSTEM\CurrentControlSet\Services\atirage3\Device0. For Rage II, Rage IIC, and
ATI264-VT4 display adapters, create the value under
HKLM\SYSTEM\CurrentControlSet\Services\atirage\Device0.
Cirrus Laguna Chipset
When you upgrade from Windows NT 4.0, the Cirrus Laguna chipset may not retain the
resolution that you previously set for the Windows desktop. When Windows 2000 Setup is
completed, you may need to reset the resolution.
Intel i740 Display Chipset
The Intel i740 display chipset may stop responding on some systems with PCI bus-mastering
disabled. As a workaround, enable PCI bus-mastering in the system BIOS.
Also, when you use the drivers included in Windows 2000, display controllers based on
this chipset may experience incompatibilities with systems that contain the VIA system
chipset.
Intel i810 Video Chipset
The Intel i810 video chipset is different from other onboard display adapters because it
is more closely integrated into the motherboard architecture. Therefore, the amount of
memory that is available to the i810 video chipset is based on the amount of physical
memory present in the computer.
Because of the amount of physical memory required to process basic DirectDraw and
Direct3D functions, the i810 video drivers do not load on any computer with less than 57
MB of physical memory.
nVidia Riva 128 Chipset
Because of an issue in the streaming video decompressor, when you use the nVidia Riva 128
chipset, some streaming video may play inverted (upside-down).
nVidia Riva 128, Riva TNT, and Riva TNT2 Chipsets
When you use the drivers included in Windows 2000, display controllers based on the NV4
display chipset may experience incompatibilities with systems that contain the VIA system
chipset.
Trident Cyber9525DVD
When you run a 16-bit application, toggling between windowed and full-screen modes causes
the display to become corrupted.
Microsoft Windows Update
If you are experiencing display-related issues that are not described in the "Graphics
Display Adapters and Monitors" section, check Microsoft Windows Update for updated
drivers.
Silicon Graphics 320/540 Visual Workstations
To install Windows 2000, Silicon Graphics (SGI) 320/540 visual workstations require a
programmable read-only memory (PROM) upgrade. In Silicon Graphics 320/540 visual
workstations, the PROM is similar to a BIOS. If you are not running version 1.1000 or
later of the PROM, Windows 2000 Setup stops and displays a message indicating that your
PROM is an earlier version and that you must upgrade the PROM before you can continue
with Windows 2000 Setup. If necessary, you can restart your computer and choose the
previous installation of Windows NT 4.0 rather than the default Windows 2000 Setup
startup option.
SGI also provides additional recommended drivers and software for use with Windows 2000.
To obtain the PROM upgrade, the additional recommended drivers and software, and more
detailed instructions, visit the SGI customer support Web site, called "Supportfolio
Online," at:
http://support.sgi.com/nt/
Note
Web addresses can change, so you may be unable to connect to the Web site mentioned
here.
Advanced Power Management
This section describes issues related to the Advanced Power Management (APM) feature in
Windows 2000.
Windows 2000 and Advanced Power Management Support
Windows 2000 detects and installs APM support in the following ways:
? No power management is present—If you do not have an APM BIOS installed on your
computer, Windows 2000 does not install APM. Also, the Advanced Power Management tab
under Power Options in Control Panel does not exist.
? ACPI-compliant BIOS is present—If you have an Advanced Configuration and Power
Interface (ACPI)-compliant BIOS installed on the computer, the system continues to
install and function as an ACPI computer with ACPI Power Management support.
? Corrupted Advanced Power Management BIOS is detected—If Windows 2000 detects a
corrupted APM BIOS, Windows 2000 does not install APM because it will cause problems with
the operating system.
? Neutral—If Windows 2000 detects an APM BIOS that is not fully compliant with
Advanced Power Management 1.2 but may still work, Windows 2000 installs APM but not the
associated driver. Also, the Advanced Power Management tab is visible under Power Options
in Control Panel.
? An Advanced Power Management 1.2-compliant BIOS is detected—If Windows 2000
detects an APM BIOS that is fully compliant with Advanced Power Management 1.2, Windows
2000 installs and automatically enables APM. Also, the Advanced Power Management tab is
visible under Power Options in Control Panel.
Important
You can manually enable APM with legacy battery support by selecting the Enable Advanced
Power Management check box on the Advanced Power Management tab under Power Options in
Control Panel. If your APM BIOS is detected as Neutral and you manually enable Advanced
Power Management, it may not function as expected and Windows 2000 may become unstable.
Therefore, Microsoft does not officially support this scenario. If you manually enable
APM and Windows 2000 becomes unstable, disable APM and contact your motherboard
manufacturer for an updated BIOS.
Note
Windows 2000 Server products do not support APM.
ACPI BIOS
If your computer has an ACPI BIOS and it did not install in ACPI mode, you may have the
option to enable APM under Power Options in Control Panel. Although APM may work if you
enable it on the computer, APM is not supported in Windows 2000 on ACPI-capable
computers.
If your computer has an ACPI BIOS and it did not install in ACPI mode, you should obtain
an updated ACPI BIOS from your hardware vendor and reinstall Windows 2000 after applying
the updated BIOS.
For more information about the Windows 2000 APM implementation, see the Developing for
Windows Operating Systems—OnNow and Power Management Web site at:
http://www.microsoft.com/hwdev/onnow/
Operation During Commercial Air Travel
Some commercial airlines may request that you turn off portable computers during certain
portions of the flight, such as takeoff and landing. To comply with this request, you
must turn off your computer completely.
? To turn off your computer completely
1. Click Start, and then click Shut Down.
2. Click Shut Down, and then click OK.
In standby and hibernation modes, your computer may appear to be turned off. However, in
these modes the operating system may automatically reactivate itself to run certain
preprogrammed tasks or to conserve battery power. To prevent this from occurring during
air travel, shut down your computer completely using the procedure above.
In addition, if your computer is equipped with a cellular modem, you must also turn off
this modem completely during air travel, as required by Federal Communication Commission
regulations.
Failure to comply with these requirements may lead to civil or criminal penalties.
Application Notes
The following sections describe Windows 2000 issues related to applications installed on
computers running Windows 2000.
General Application Issues
This section describes general issues related to applications running on Windows 2000.
Applications in the Upgrade Report
During Windows 2000 Setup, the Upgrade Report window identifies applications that have
known, unfixable problems when you upgrade from Windows 95 or Windows 98 to Windows 2000.
This window also displays system-related data. To prevent problems after you upgrade, you
should carefully read the information in the Upgrade Report window and follow the
recommendations.
After you upgrade to Windows 2000, if you then attempt to start any of the applications
identified in the Upgrade Report window, a "stub" warning message appears in place of the
application. You can choose to run the application anyway, remove the link to the
application permanently, or never show the warning message again. This stub also provides
a link to the Upgrade report (Upgrade.txt), which Windows 2000 saves as a text file in
the Windows folder.
Adaptec CD Creator Version 3.5
To avoid a known problem with Adaptec CD Creator version 3.5b, you can download the new
version 4 release of Adaptec CD Creator.
Adaptec DirectCD 2.0
After you install DirectCD 2.0 and restart the computer, this application prevents
Windows 2000 from starting correctly. To fix this problem, before you restart the initial
installation, download and install the patch for version 2.5. This patch is available
from the Adaptec Web site at:
http://www.adaptec.com/
Note
Web addresses can change, so you may be unable to connect to the Web site mentioned
here.
Adobe Illustrator 8.0.1
Adobe Illustrator 8.0.1 files may appear as black squares rather than as the proper icon
at any location where you save the files (for example, on the desktop, My Documents, a
local drive, or network locations). This problem only occurs when you view the files as
Large Icons. If you select any of the other file viewing options, the file icons display
normally. For information about how to change the appearance of the items in a folder,
see Windows 2000 Help.
Adobe PhotoDeluxe
After you upgrade from Windows 95 or Windows 98 to Windows 2000, you can no longer use
the Adjust Color Printing function on the File menu in Adobe PhotoDeluxe. This function
allows you to calibrate your monitor to match onscreen colors with printer colors.
Reinstalling PhotoDeluxe does not restore this function.
Aldus Freehand 4.0
Aldus FreeHand 4.0 does not run on Windows 2000 because it cannot find the required .dll
files. At the end of Setup, a dialog box prompts you to modify the Autoexec.bat file. The
application does not know how to respond to non-default situations, such as an
Autoexec.bat of zero length, no Autoexec.bat found in the root of the boot drive, or
non-default installation drives. Therefore, modifications to this file may fail, but you
can edit it manually.
This continues to be an issue with this 16-bit version of the application. Macromedia
recommends upgrading to a newer version. You can also use one of the following
workarounds:
? Workaround 1
1. When presented with a dialog box prompting you to allow Setup to modify Startup files
(such as Autoexec.bat) at the end of the setup process, click Manual.
2. Then edit the path statement in %windir%\System32\Autoexec.nt to include the Aldus
directory specified in Setup, for example:
path = c:\dos;d:\foo;g:\aldus
? Workaround 2
1. Right-click on My Computer, select Properties, and then click the Advanced tab.
2. Click Environment variables, and then type the path to the Aldus directory specified
in Setup, for example:
%systemroot%\System32;c:\aldus
Asymetrix ToolBook v1.5 and 1.53 DayBook Month View
ToolBook v1.5 and 1.53 DayBook Month View do not run on Windows 2000 Professional. For
more information or updates about these products, contact the software vendor.
Borlund Delphi Professional 3.0
Running the demo file (Qr2demo.dpr) for Delphi Professional 3.0 on Windows 2000 may
result in numerous error messages. No known workaround is available at this time.
Broderbund Software Calendar Creator Version 5.0
When you start Calendar Creator 5.0 Setup, the following message appears:
"Setup has detected that you do not have Windows NT SP3 installed. Certain files that are
required by Calendar Creator 5.0 are contained in this Service Pack. Calendar Creator may
not function correctly without Service Pack 3. Before running Calendar Creator 5.0, you
should install Windows NT Service Pack 3. If you need SP3, it can be found on the CD in
the folder NT setup."
No known workaround is available at this time.
Cheyenne Inoculan 4.0 for Windows NT
When you scan drives, folders, or network shares that contain compressed cabinet (.cab)
files, Inoculan 4.0 may stop responding and may display an access violation message. The
application then closes.
As a workaround, manually clear the check boxes for the folders containing .cab files, or
delete .cab from the file types you want to scan.
? To delete .cab from the file types you want to scan
1. On the Scan menu, click Options.
2. On the File Types tab, under Compressed Files, click CAB, and then click Delete.
3. Click OK.
For more information or for updated versions of Inoculan, visit the Computer Associates,
Inc. Web site at:
http://www.cai.com/
Note
Web addresses can change, so you may be unable to connect to the Web site mentioned
here.
Command Software Systems Command AntiVirus Version 4.54
Command AntiVirus version 4.54 and all earlier versions are incompatible with Windows
2000 Professional. Do not install any of these versions on your computer. If you do so,
they are unusable until you reinstall Windows 2000. Command Software Systems is working
on a version of Command AntiVirus for Windows 2000. For updates and upgrade information,
visit the Command Software Systems Web site at:
http://www.commandcom.com/
Note
Web addresses can change, so you may be unable to connect to the Web site mentioned
here.
Computer Associates ArcServeIT 6.6
Computer Associates is expected to release a new version of ArcServeIt that will address
problems with this application in Windows 2000. For specific information about this new
product release, contact the manufacturer. A beta release of this application has been
tested with Windows 2000, and known application problems have been fixed.
Conversational Computing Corporation ConversaWeb 3.0.1
ConversaWeb 3.0.132 may not run properly on Windows 2000 until the application is
properly upgraded. You may experience problems with the application when speaking the key
phrases, "open favorites" or "show history." If you are using version 3.0.2 or later, you
should not experience these problems. To upgrade the application, visit the
Conversational Computing Corporation Web site at:
http://www.conversations.com/
Note
Web addresses can change, so you may be unable to connect to the Web site mentioned
here.
Equis MetaStock 6.5
If you installed Equis MetaStock 6.5 on a computer running Windows NT 4.0 (any service
pack) and created a password for the MetaStock Downloader for Windows program, upgrading
to Windows 2000 causes the MetaStock Downloader for Windows program to exit prematurely.
The program closes when you are selecting vendor options from the Tools menu in the
Downloader after the upgrade is complete.
To ensure that the application functions correctly in Windows 2000, before you upgrade,
you must delete the Downloader password. Then after you upgrade to Windows 2000, you can
enter a new password.
? To delete the Downloader password
1. Click Start, point to Programs, and then click MetaStock Downloader for Windows.
2. On the Tool menu, click Vendor Options.
3. Delete the User name and Password, and then click OK.
Eudora Pro Email 4.2
During the upgrade to Windows 2000, Microsoft Outlook Express registers itself as the
default e-mail client. If you start Eudora Pro after the upgrade, a dialog box prompts
you to set Eudora as the default e-mail client. If you do so, the following message
appears:
"Eudora was unable to update the system registry. Your default mail program has not been
changed."
As a workaround, select Eudora as the default e-mail client on the Programs tab under
Internet Options in Control Panel.
HotSync Network
When you upgrade from Windows 95 or Windows 98, the HotSync Network feature cannot
perform a network synchronization until you return the Palm device to the host PC and
complete a local synchronization. After the host PC is upgraded to Windows 2000, simply
place the Palm device in the cradle attached to the host PC and perform a local
synchronization. Then the network synchronization functions properly from any PC that is
configured with a cradle and the appropriate HotSync Network software. This problem does
not occur on a clean installation of Windows 2000.
Hummingbird Exceed 6.1
When you upgrade from Windows 95 or Windows 98 to Windows 2000, the XConfiguration file
for Exceed 6.1 is not saved. The following message appears:
"INETD Error: Error creating configuration file."
To enable the XConfiguration file to be saved, reinstall the Exceed 6.1 program from the
original installation media on Windows 2000. The application creates the necessary link
to the XConfiguration file and allows you to save the settings. Because the CD contains
two versions of Exceed, the problem is resolved when the installer detects Windows 2000
and installs the Windows 2000 version from the CD.
IBM AntiVirus
IBM AntiVirus cannot perform any real-time monitoring of the Windows 2000 system. On
Windows 2000 Professional, the System Shield does not "Check files when accessed." This
product has been sold to Symantec Corporation. For upgrade information, visit the
Symantec Web site at:
http://www.symantec.com/
Note
Web addresses can change, so you may be unable to connect to the Web site mentioned
here.
IBM ViaVoice 98 Executive 5.2 and IBM Simply Speaking Gold 3.5
Because some video cards are not compatible with IBM ViaVoice 98 Executive 5.2 and IBM
Simply Speaking Gold 3.5, the Actor may display as a black square figure when you select
Begin reading. No known workaround is available at this time. This will be addressed in a
future release.
Intergraph DiskShare Version 3.2
Intergraph DiskShare version 3.2 does not install on computers running Windows 2000. The
Setup program terminates at the beginning of the setup process and displays the following
message:
"This Setup process has determined that you are running on the Microsoft Windows NT 5.0
operating system.
This version of DiskShare does not support this operating system.
Please verify that you are installing the correct version of DiskShare."
No known workaround is available at this time.
Intergraph GeoMedia Version 2.0
When you attempt to install GeoMedia version 2.0 on a computer running Windows 2000,
Setup fails with a message that indicates a version checking problem. GeoMedia v2.0 is
designed for installation on the Windows NT? 4.0 Service Pack 3 (SP3) release. No known
workaround is available at this time.
InstallShield 3 Setup Engine
There is a known issue with several programs installing multiple listings under Programs
(from the Start menu). The following or a similar message appears:
"Variable is not large enough for string. Check string declarations. Error 401."
When a program is uninstalled using InstallShield 3, the uninstall engine incorrectly
queries the registry to facilitate the removal of the program's Start menu items. This
causes the program to remain on the Start menu even though the program has been removed.
The following programs exhibit this behavior:
? Raxco Software PerfectDisk
? Panda AntiVirus
? Norton Crashguard
? Executive Software International Diskeeper
? Iomega Windows NT tools for JAZZ drive
? Berkeley Systems After Dark 3.2
? Apple Computer, Inc. QuickTime 3.0 and QuickTime 3.0.2
? Interbase Client & Server
? Master Clips Publisher
? Autodesk AutoCAD 14
This problem may also occur with other programs. No known workaround is available at this
time.
Juno Inc. Juno 2.0
Juno 2.0 is not compatible with Windows 2000. You cannot access existing e-mail accounts
or create new accounts. If you attempt to create a new account, the following message
appears:
"Juno could not access Worldcom_signup, which is necessary to connect to its central
computers."
If you want to run Juno on Windows 2000, upgrade to the most current Juno software. Juno
has released version 3.0 of its e-mail and Web client, which is compatible with Windows
2000. To receive a free download of this new version, visit the Juno Web site at:
http://www.juno.com/
Note
Web addresses can change, so you may be unable to connect to the Web site mentioned
here.
Juno Inc. Juno 3.0
Problems may occur with the Juno version 3.0 (3.0.1092.2818) installation from CD media
only. When you run the application on Windows 2000, it may indicate an access violation.
This problem also affects upgrades to Windows 2000. As a workaround, download a newer
version of Juno 3.0 (version 3.0.1127.3331 or later) from the Juno Web site at:
http://www.juno.com/
Note
Web addresses can change, so you may be unable to connect to the Web site mentioned
here.
Lotus cc:Mail 6.02 and 6.03
If you attempt to start cc:Mail 6.02 or 6.03 on either a clean installation of Windows
2000 or after you upgrade from Windows 95 or Windows 98 to Windows 2000, an invalid
program file name error occurs.
As a workaround, edit the shortcut .pif file for cc:Mail.
? To edit the shortcut .pif file for ccMail
1. Click Start, point to Search, and then click For Files or Folders...
2. In the Search for files or folders named: box, type:
mail.pif
3. Make sure that the Look in: box has Local Harddrives selected, and then click Search
Now.
4. When the Mail.pif file is located, right-click the file, and then click Properties.
5. On the General tab, clear the Read-only Attributes box.
6. Click the Program tab, and then in the Working: box, change the location from C:\ to
the correct folder. For a standard installation, this folder is C:\CCMail.
7. Click Apply.
8. Click the General tab, and then click the Read-only Attributes box.
9. Click OK.
Lotus cc:Mail 6.03 for DOS
When you start the DOS-based cc:Mail 6.03 application from the command prompt, the
following message may appear:
"Fatal Error evm0009: EMM error: error = 8B, function = 5001.
Use 'SET RTVMEXP=0' to disable this usage of Expanded Memory."
To resolve this issue, you must modify the .pif file.
? To modify the .pif file
1. Right-click on the .pif file in the ccmail folder (the shortcut is titled "mail").
2. Clear the Read-only attributes, and then click Apply.
3. On the Memory tab, under Conventional memory, change the Total to 600 and the Initial
environment to 1024.
4. Under MS-DOS? protected-mode (DPMI) memory, change the Total to 4096.
5. Click Apply, and then click OK.
MetaCreations Painter 6
In Windows 2000, if you attempt to save Painter 6 files to a network share using a
Uniform Naming Convention (UNC) path, the following message appears:
"Insufficient disk space on the disk for the file."
As a workaround, save the Painter 6 files to a network share by mapping to the network
share before saving the file.
? To map to a network share
1. On the desktop, right-click My Computer, and select Map Network Drive.
2. Type the network share (for example, \\server\share) in the Folder: text box.
You can also contact MetaCreations at the following address:
MetaCreations Corporation Customer Service
P.O. Box 724
Pleasant Grove, UT 84062-0724
Telephone: 1-800-846-0111, 6:00am-5:00pm MST, Monday-Friday
Microsoft Access 97
When you install Access 97 by using a network share, the appropriate shortcut icons do
not appear on the Start menu. As a workaround, you can add a shortcut to the Start menu
after the installation.
? To add a shortcut to the Start menu
1. Click Start, and then click Run.
2. In the Open: box, type:
*drive*:\Documents and Settings\All Users\Start Menu\Programs
The *drive* is the drive location for the Windows 2000 installation.
3. Click OK.
4. Right-click the window that appears, click New, and then from the context menu, click
Shortcut.
5. If you used the default install path for Access 97, in the Command line: box, type:
*drive*:\Program Files\Microsoft Office\Office\Msaccess.exe
Otherwise, type the location of Msaccess.exe.
6. Click Next.
7. In the Select a name for the shortcut box, type:
Microsoft Access 97
8. Click Finish.
Microsoft FrontPage 98
When you upgrade Windows NT 4.0 servers to Windows 2000 servers, FrontPage 98 may
experience problems accessing Web folders (for example, it cannot open pages on
D:\inetpub\wwwroot). This can occur on Windows NT 4.0 servers that are installed on FAT
partitions and then upgraded to Windows 2000 Server with the default NTFS drive upgrade
selected during installation. During the upgrade, the recommended NTFS drive conversion
may cause problems with the FrontPage server extensions and hinder access to the Web
folders.
To avoid this problem on the upgraded Windows 2000 servers, in Windows 2000 Setup, clear
the Yes, upgrade my drive option for the NTFS file system and instead select No, do not
upgrade my drive. Then, complete the server upgrade from Windows NT 4.0. If the benefits
of the NTFS file system are desired, you can convert the drive to NTFS after the upgrade.
This pertains to upgrading Windows NT 4.0 servers to Windows 2000 servers and does not
address Windows 2000 Professional.
Microsoft Office 95
For Office 95 to work correctly with Windows 2000, you must install the most current
versions of Office 95 applications, including Access 7.0, Excel 7.0, WinWord 7.0,
PowerPoint? 7.0, and Schedule+ 7.0. Also, you must install the Office 95 Year 2000
Update.
To obtain the latest version upgrades for Office 95 applications, contact your local
software dealer or Microsoft technical support.
To install the Office 95 Year 2000 Update, visit the Microsoft Office 95 Year 2000 Update
Web site at:
http://officeupdate.microsoft.com/downloaddetails/o95y2k.htm
Microsoft Office 95, Office 97, and Office 2000
There is a new concept called Merged Folders for the Start menu in Windows 2000. These
folders take some items from both the All Users folder and the Per User folder and
combine these items into one menu. The Office Shortcut bar displays only the Per User
folder, not the All Users folder.
As a workaround, you could copy the shortcuts from your All Users folder to your Per User
folder, but you may not want to do this in a corporate environment.
Microsoft Office 97 Professional SR2
After an administrator or a user with administrative privileges installs Office 97
Professional SR2, a person logged on with user privileges cannot use the Visual Basic?
Editor that is included with Microsoft Office. No known workaround is available at this
time.
Microsoft Office 2000
This section describes issues related to the Microsoft Office 2000 applications.
Nonfunctional Links from Applications After Uninstall
In some cases, after you upgrade from Windows 95 or Windows 98, uninstalling Office 2000
may result in nonfunctional links from Office 2000 applications that remain in the Start
menu and on the desktop. This is caused by the differences between the Windows 95 and
Windows 98 User Profile models and the Windows 2000 User Profile model. In Windows 98 and
Windows 95, you can configure a common User Profile by using the All Users of this
computer use the same preferences and desktop settings setting on the User Profiles tab
under Passwords Properties in Control Panel. In Windows 2000, this setting is not
available.
To resolve the problem of nonfunctional links, use one of the following workarounds:
? After you upgrade to Windows 2000, manually delete the Start menu files.
? After you upgrade to Windows 2000, reinstall Office 2000.
Installing Microsoft Office 2000 with Lotus Notes
If you attempt to install Microsoft Office 2000 on Windows 2000 and Lotus Notes 3.x-5.x
is already installed on the computer, an "Internal Error 2343" displays and Office 2000
cannot continue with the installation process. This issue does not occur with Office 2000
SR1.
If Lotus Notes is already installed on the computer, you can fix this problem by running
the Err2343.exe utility, installing Office 2000, and then restarting the computer. This
utility is available from the Microsoft Knowledge Base on the Microsoft Personal Online
Support Web site at:
http://support.microsoft.com/support/
Microsoft Outlook? 2000
This section describes issues related to the Microsoft Outlook 2000 application.
Reinstalling Outlook 2000 Is Required After Upgrading to Windows 2000
After you upgrade from Windows 95 or Windows 98 to Windows 2000, you must reinstall
Outlook 2000. If Outlook 2000 is part of your Startup folder, reinstallation
automatically begins the first time you log on to Windows 2000. Otherwise, you can begin
the reinstallation process by starting Outlook from the Start menu or desktop shortcut.
The Upgrade.txt report notifies Outlook users about this issue before they begin the
upgrade to Windows 2000. The Outlook reinstallation process progresses slowly, and the
progress bar restarts several times. Do not cancel the reinstallation, even if it does
not make any obvious progress and appears to be in an infinite loop. Canceling the
reinstallation does not restore Outlook. However, you can begin the reinstallation
process again by restarting Outlook 2000 from the Start menu or desktop shortcut.
AutoArchive Feature Becomes Invalid After Upgrading to Windows 2000
When you upgrade from Windows 95 or Windows 98 to Windows 2000, the default path for the
AutoArchive feature of Outlook 2000 becomes invalid. When AutoArchive attempts to start,
the following error appears:
"Error while archiving folder "*foldername*" in store "*store name*." The path specified
for the file C:\windows\Profiles\*your name*\Local Settings\Application
Data\Microsoft\Outlook\Archive.pst is not valid."
This problem occurs because the upgrade process moves the user information located in the
C:\Windows\Profiles directory in Windows 95 and Windows 98 to the C:\Documents and
Settings directory in Windows 2000. Outlook 2000 stores the AutoArchive settings on your
Exchange server, and Windows 2000 Setup cannot modify them.
As a workaround, manually change the path to the new location of the Archive.pst file.
? To manually change the path to the new location of the Archive.pst file
1. From the Folder List view in Outlook, right-click the folder scheduled to AutoArchive,
and click Properties.
2. On the AutoArchive tab, under Move old items to:, click Browse.
3. Browse to and select the following file:
C:\Documents and Settings\*your name*\Local Settings\Application
Data\Microsoft\Outlook\Archive.pst
4. On the Find Personal Folders window and the Inbox Properties window, click OK.
The error no longer occurs, and the AutoArchive feature functions correctly.
Note
This error only occurs if you initially select the default directory to store the
archive.pst file. If you select a directory other than the default
C:\Windows\Profiles\... directory, you do not need to make any changes after you upgrade
to Windows 2000.
Microsoft Proxy Client 2.0
If you upgrade from Windows 95 to Windows 2000 and your computer has Winsock version 1.1,
the Microsoft Proxy Client is uninstalled. A message appears in the upgrade report, and
you must reinstall Proxy Client after you complete the upgrade to Windows 2000. Both
Windows 98 and Windows 98SE include the Microsoft Proxy Client 2.0, so the proxy client
works correctly after the upgrade to Windows 2000.
Microsoft SQL Server™ 6.5 and 7.0
When you install either SQL Server 6.5 or 7.0, a "Configure SQL Server Agent" message box
may appear near the end of Setup, and you may see the following message:
"The password does not meet the password policy requirements. Check the minimum password
length, password complexity, and password history requirements."
This occurs because both versions of SQL Server use an eight (8)-uppercase-character
password for the SQLAgentCmdExec account. This password no longer meets the default
security requirements for Windows 2000. The only available workaround is to modify the
Effective Settings (set by the domain controller) for the Minimum password length and the
Password complexity requirement before installation.
? To modify the Effective Settings
1. Click Start, point to Settings, and then click Control Panel.
2. Double-click Administrative Tools.
3. Double-click Local Security Policy.
4. On the IP Security Policy Management message box, click OK.
5. Double-click the Account Policies branch.
6. Double-click the Password Policy branch.
7. In the right pane, verify that the following two entries are properly set for the
Effective Settings column:
? "Minimum password length *= 8 characters"
? "Passwords must meet complexity requirements = Disabled"
The local computer controls the Local Settings, and the domain controller controls the
Effective Settings. Only the domain controller can modify the Effective Settings.
Microsoft Visual Basic
If you compiled any Visual Basic applications that included a reference to the
Scripting.FileSystemObject (Scrrun.dll) on a computer running Windows 2000 Beta 3 or
Windows 2000 RC1, you must now recompile the applications running a later version of
Windows 2000. Windows 2000 Beta 3 and RC1 include an interface that does not exist in
later versions. Therefore, the recompile is required for the Visual Basic application to
work properly. This requirement does not apply to applications compiled with any versions
of Windows 2000 earlier than Beta 3 or later than RC1.
IIS Applications Do Not Run If Password Complexity Is Enforced in the Domain-Level
Policy
When password complexity requirements are enforced in the domain-level policy, IIS
applications created with Visual Basic 6.0 do not run properly. The following message
appears in Internet Explorer:
"HTTP 500 Internal Server Error"
This occurs because the IIS-created local account for anonymous access does not meet the
default password complexity requirements in the domain-level policy for a Windows 2000
domain with default settings. To resolve this, override the IIS password control
locally.
? To override the IIS password control locally
1. Open the Web Site Properties dialog box in Internet Information Services under
Administrative Tools.
2. On the Directory Security tab, click Anonymous access and authentication control, and
then click Edit.
3. Click Anonymous access—Account used for anonymous access, and then click Edit.
4. Clear the Allow IIS to control password check box.
5. Type a new password that meets the password complexity requirements in the
domain-level policy, click OK, and then retype the password for validation.
6. To accept the new settings, click OK.
7. If an Inheritance Overrides dialog box appears, click Select All, or select individual
projects that you want to inherit the new setting.
8. To accept the new settings, click OK.
SharedPropertyGroupManager Causes Compile Error
The ProgID for the Shared Property Manager has changed from
MTXSPM.SharedPropertyGroupManager to
COMSVCSLIB.SharedPropertyGroupManager. Because of the conversion from COM to COM+,
mtxspm.dll (the typelib where the ProgID was defined) no longer exists. Instead,
comsvcslib (the new typelib) is referenced in a