Multiple Display in Windows XP Professional

Using Multiple Displays:

Windows XP Professional supports multiple display configurations. Multiple displays allow you to extend your desktop across more than one monitor.


· Use of multiple displays extends the desktop across a miximum of 10 monitors
· Multiple displays must use Peripheral Component Interconnect (PCI) or Accelerated

• Graphics Port (AGP) devices.
  · Hardware requirements for primary (main) and secondary displays differ.
  
  If one the display adapters are built into the motherboard, note these additional considerations:
  
  1. The motherboard adapter always becomes the secondary adapter. It must be multiple-display compatible.
  
  2. You must set up Windows XP Professional before installing another adapter. Windows XP Professional Setup disables the motherboard adapter if it detects another adapter. Some systems completely disable the onboard adapter on detecting an add-in adapter. If you are unable to override this detection in the BIOS, you cannot use the motherboard adapter with multiple displays.
  
  
  Typically, the system BIOS selects the primary display based on PCI slot order. However, on some computers, the BIOS allows the user to select the primary display device.
  
  You cannot stop the primary display. This is an important consideration for laptop computers with docking stations. For Example, some docking stations contain a display adapter; these often disable, or turn off, a laptop’s built-in display. Multiple display support does not function on these configurations unless you attach multiple adapters to the docking station.
  
  Configuring Multiple Displays:
  
  Before you can configure multiple displays, you must install them. When you configure multiple displays, you must configure each one in a multiple-display environment.
  
  To install multiple monitors, complete the following Steps:

1. Turn off your computer and insert one or more additional PCI or AGP video adapters into available slots on your computer
   
2. Plug an additional monitor into each PCI or AGP video adapter that you installed.
   
3. Turn on your computer and allow windows XP Professional to detect the new adapters and install the appropriate device drivers.
   
4. In Control Panel, click Appearance And Themes, and then click Display.
   
5. In the Setting tab, click the monitor icon that represents the monitor you want to use in addition to your primary monitor.
   
6. Select the Extend My Windows Desktop Onto This Monitor check box and then click OK.
   
   
   To configure your display in a multiple-display environment, complete the following steps:
   

• In Control Panel, click Appearance And Themes, and then click Display.
  
• In the Display Properties dialog box, click the Setting tab.
  
• Click the monitor icon for the primary display device.
  
• Select the display adapter for the secondary display, and then select the color depth and resolution.
  
• Click the monitor icon for the secondary display device.
  
• Select the display adapter for the secondary display, and then select the Extend My Windows Desktop Onto This Monitor check box.
  
• Select the color depth and resolution for the secondary display.
  
• Repeat steps 5 through 7 for each additional display.
  
  
  Windows XP Professional uses the virtual desktop concept to determine the relationship of each display. The virtual desktop uses co-ordinates to track the position of each individual display desktop.
  
  The co-ordinates of the top-left corner of the primary display always remain 0, 0.
  Windows XP Professional sets secondary display co-ordinates so that all the displays adjoin each other on the virtual desktop. This allows the system to maintain the illusion of a single, large desktop where users can cross from one monitor to another without losing track of the mouse.
  
  
  To change the display positions on the virtual desktop, in the Setting tab click Identify and drag the display representations to the desired position. The positions of the icons dictate the co-ordinates and the relative positions of the displays to one another.
  
  Troubleshooting Multiple Displays:
  
  If you encounter problems with multiple displays, use the troubleshooting guidelines from the below given table:
  
  Problem: You cannot see any output on the secondary displays
  
  Solution: Activate the device in the Display Properties dialog box. Confirm that you
  chose the correct video driver.
  
  Restart the computer to confirm that the secondary display initialized. If not, check the status of the video adapter in Device Manger.
  
  Switch the order of the adapters in the slots. (The primary adapter must qualify as a secondary adapter)
  
  
  Problem: The Extend My Windows Desktop Onto This Monitor check box is
  unavailable.
  
  Solution: Select the secondary display rather then the primary one in the Display
  prperties dialog box.
  
  Confirm that the secondary display adapter is supported.
  
  Confirm that Windows XP Professional can detect the secondary display.
  
  Problem: An application fails to display on the secondary display.
  
  Solution: Run the application on the primary display.
  
  Run the application in full-screen mode (Microsoft MS-DOS) or
  maximized (Microsoft Windows)
  
  Disable the secondary display to determine whether the problem is specific to multiple-display support.

================================================================================

More Information About Windows 2000 Prof.+ Server

Microsoft® Windows® 2000 Professional,Windows 2000 Server, andWindows 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 . 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 =

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 toWindows 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 withWindows 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 SupportRolling 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::\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 ServiceP.O. Box 724Pleasant Grove, UT 84062-0724Telephone: 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:
:\Documents and Settings\All Users\Start Menu\Programs
The 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:
:\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 “” in store “.” The path specified for the file C:\windows\Profiles\\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\\Local Settings\ApplicationData\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 fromMTXSPM.SharedPropertyGroupManager toCOMSVCSLIB.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 Visual Basic project compiled on Windows 2000.
This is strictly a compile issue. It does not affect run-time code for previously compiled projects, because the former ProgID still exists in the registry and the CLSID for SharedPropertyGroupManager remains unchanged.
As a workaround, manually change the ProgID.
Þ To manually change the ProgID
1. Open the affected Visual Basic project.
2. Change all MTXSPM.SharedPropertyGroupManager references to COMSVCSLIB.SharedPropertyGroupManager.
3. Change all MTXSPM.SharedPropertyGroup references to COMSVCSLIB.SharedPropertyGroup.
4. Change all MTXSPM.SharedProperty references to COMSVCSLIB.SharedProperty.
5. Save the project.
6. Recompile the project (with binary compatibility, if necessary).

Microsoft Visual InterDev® 6.0
When you set up Active Server Pages (ASP) debugging for Visual InterDev 6.0 on Windows 2000, the user’s identity is not set correctly. If you debug a Web project on a remote server, the user is then configured incorrectly in Component Services. The Identity property under COM+ Applications for the Web project is set to “This user” rather than “Interactive user.” Therefore, debugging from a different computer or by a different user results in remote debugging failures. The client user may not have access to the server and cannot change the value to Interactive user.
When you perform ASP debugging locally on the IIS server, you can manually set the value to Interactive user. This setting allows another user on the same computer to debug the ASP, which would be impractical for debugging remotely from a client computer.
Microsoft Visual Studio Enterprise Edition Version 6.0
This section describes issues related to the Microsoft Visual Studio Enterprise Edition version 6.0 application.
Creating a Local User Account
Toward the end of Visual Studio Enterprise Edition 6.0 Setup with either the Visual Studio Enterprise Edition 6.0 client-side or server-side installation, the following message may appear:
“Setup was unable to create a DCOM user account in order to register valec.exe.”
This is followed by a second message indicating that Setup has failed.
Changes to the security policies for user accounts in Windows 2000 cause this problem. Visual Studio Analyzer, one of the products in Visual Studio Enterprise Edition 6.0, cannot create the local user account that it needs to run.
As a workaround, you can install Visual Studio Enterprise Edition 6.0 without Visual Studio Analyzer, install Visual Studio Analyzer separately, and then create the local user account.
Þ To install Visual Studio Enterprise Edition 6.0 without Visual Studio Analyzer
1. Using the Custom setup, on the Visual Studio 6.0 Enterprise - Custom page, select Enterprise Tools, and then click Change Option.
2. On the Visual Studio 6.0 Enterprise - Enterprise Tools page, under Options, make sure the Visual Studio Analyzer check box is not selected.
3. Select all the other Visual Studio components that you want to install, and then click OK.
4. Click Continue, and follow the instructions that appear.

Þ To install Visual Studio Analyzer
1. In Control Panel, double-click Add/Remove Programs, and then click Microsoft Visual Studio 6.0 Enterprise Edition.
2. Click Change/Remove.
3. In Visual Studio 6.0 Enterprise Setup, click Add/Remove.
4. On the Visual Studio 6.0 Enterprise - Maintenance page, select Enterprise Tools, and then click Change Option.
5. On the Visual Studio 6.0 Enterprise - Enterprise Tools page, under Options, select Visual Studio Analyzer, and then click OK.
6. On the Visual Studio 6.0 Enterprise - Maintenance page, click Continue, and then follow the instructions that appear.
When you receive the message, “Setup was unable to create a DCOM user account in order to register valec.exe,” continue with the Visual Studio Setup wizard. Setup reports a failure.
7. When Setup completes, in the Add/Remove Programs window, click Close.

Þ To create a local user account
1. On the computer running Visual Studio Enterprise Edition 6.0, create a local user.
For information about how to create a local user, see Windows 2000 Help.
2. Run Distributed COM Configuration (dcomcnfg.exe).
3. On the Applications tab, select MSVSA Local Event Concentrator Class, and then click Properties.
4. On the Identity tab, set This User to match the user you created in Step 1 of this procedure.

Accessing the Performance Monitor Data
When you install Visual Studio Analyzer 6.0 on Windows 2000, you cannot collect Performance Monitor events. Only interactive users and administrators can access Performance Monitor data in Windows 2000. The Visual Studio Analyzer 6.0 server runs under a user account that does not have these privileges.
As a workaround, determine the user account for Visual Studio Analyzer 6.0 server and then give explicit permission for this user account to access the Performance Monitor data.
Þ To determine the user account for Visual Studio Analyzer 6.0 server
1. Run Distributed COM Configuration (dcomcnfg.exe).
2. On the Applications tab, select MSVSA Local Event Concentrator Class, and then click Properties.
3. On the Identity tab, note the user name for This User.

Þ To give explicit permission for this user account to access the Performance Monitor data
1. Start Regedt32.exe (this program is required for the Security menu).
2. Locate HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Perflib and highlight this registry key.
3. On the Registry menu, click Security Permissions….
4. Click Add, and then select the user name noted for This User in Step 3 of the previous procedure, “To determine the user account for Visual Studio Analyzer 6.0 server.”
5. Close Regedt32.exe.
6. Restart the computer.

Collecting MTS Events
If you have Visual Studio Analyzer 6.0 installed and you upgrade your computer to Windows 2000, Visual Studio Analyzer is no longer able to collect MTS events from that computer. Component Services, which is part of Windows 2000, replaces MTS 2.0, which supported Visual Studio Analyzer.
Component Services generates events that are similar to Visual Studio Analyzer events, but they are not compatible with Visual Studio Analyzer. To fix this problem, install the Visual Studio Analyzer COM+ 1.0 Bridge from the Windows 2000 Platform SDK. This bridge fixes the problem by subscribing to these events and converting them to Visual Studio Analyzer events.
The bridge consists of one file called Vamts.dll, which you must manually register. For additional information, see the COM+ 1.0 Bridge Readme file in the Windows 2000 Platform SDK.
Upgrading from Windows 95 or Windows 98 to Windows 2000
If you have Visual Studio Analyzer 6.0 installed on Windows 95 or Windows 98 and you upgrade to Windows 2000, Visual Studio Analyzer is no longer able to collect events from that computer. In order to fix the problem, complete the steps in the following procedure.
Þ To collect events from the computer
1. Uninstall Visual Studio Analyzer 6.0.
2. Reinstall Visual Studio Analyzer 6.0. At this point, you should be able to connect to this computer in order to collect events.
3. If you want Component Services metrics, install the Visual Studio Analyzer COM+ 1.0 Bridge. For more information, see “Collecting MTS Events,” earlier in this document.
4. In order to collect Performance Monitor events, you must explicitly give permission to the user account that Visual Studio Analyzer server runs for accessing the Performance Monitor data. For more information, see “Accessing the Performance Monitor Data,” earlier in this document.

Default Document Settings
Microsoft Visual Studio sets up several default document settings that are specific to the user who installed the application. After completing the Microsoft Visual Studio 6.0 installation, run the %systemroot%\Application Compatibility Scripts\Install\Msvs6.cmd script. This script updates the default directories to be unique for each user.
The following limitations apply to Visual Studio 6.0:
· All users share a common default project directory for Microsoft Visual Basic 6.0 (which is part of the Microsoft Visual Studio Enterprise Edition).
· Multiple users cannot use the Forms wizard, Label wizard, or Setup wizard in Visual FoxPro® simultaneously. Also, the default macro set in Visual FoxPro is common to all users. If one user sets a default macro set, it applies to all users on the server.
· Quick macros do not support multiple users. Only one user at a time can record a quick macro, and only the user who created the quick macro can run it. The default filename and directory for macro files is common for all users (\Program Files\Microsoft Visual Studio\common\MSDev98\Macros\MyMacros.dsm). Users can run the Visual C++® 6.0 tools from a command prompt by using \Program Files\Microsoft Visual Studio\VC98\Bin\Vcvars32.bat.

NetManage OnNet32 Version 2.0
Before you install OnNet32 version 2.0, you must install Windows Messaging (WMS). If you attempt to install OnNet32 v2.0 on a computer that does not have WMS installed, the OnNet32 installation fails. During the installation, the OnNet32 installer requests the Windows Messaging software, which is found on the Windows NT 4.0 CD. However, after directing the installer to the CD, the following message appears:
“Installation Failed.”
This will be addressed in a future release.
Norton Ghost Walker
Norton Ghost Walker SID Changer 1.13 cannot recognize the FAT32 or NTFS file system. If you attempt to install this program on a drive using FAT32 or NTFS, the following message may appear:
“No bootable NT installations detected on this machine.”
No known workaround is available at this time. For information about updates, 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.

Norton Utilities 2.0 for Windows NT
The disk utilities in Norton Utilities 2.0 do not recognize FAT32. If you use Disk Doctor or Speed Disk on a drive formatted with the FAT32 file system, the following message may appear:
“Partition has an unrecognized error on it, would you like to fix the problem?”
If you click Yes, you may lose data for any information stored on FAT32 partitions.
Novell GroupWise 5.1, 5.2, or 5.5 Client
Before you install GroupWise 5.1, 5.2, or 5.5 Client on Windows 2000, you must install WMS. To do this, run Wms.exe from the Valuadd\Legacy folder on the Windows 2000 CD. WMS provides the MAPI components that GroupWise 5.5 requires.
The MAPI components that GroupWise 5.5 requires may already be present on your computer if you have upgraded your computer to Windows 2000 or if you have installed other programs that use WMS/MAPI (for example, Outlook 97 or Outlook 98). However, the components are not installed during a clean installation of Windows 2000.
After successfully installing WMS, you can install GroupWise Client by using the GroupWise CD. During the GroupWise 5.5 installation process, in the WMS dialog box, clear the options Install the complete Windows Messaging System and Leave Windows Messaging System as it is. If you do not clear these options, an incomplete installation of GroupWise Client occurs.

Note
You should not be prompted to install or update WMS during the GroupWise 5.5 installation. If you receive a message during GroupWise Setup stating that “Only part of the Windows Messaging System is found on your computer,” cancel Setup and reinstall WMS. You do not want to install this version of WMS, which is contained on the GroupWise CD, on Windows 2000.

Pacific Microelectronics Mac-N-Dos 3.0
When you attempt to browse the contents of a Mac-formatted CD-ROM disk, all files and folders may not appear in the Mac-In-Dos portion of the Microsoft Explorer window. No known workaround is available at this time.
Panda Software Panda Anti-Virus 5.0
Panda’s real-time file monitor, Sentinel, does not run on Windows 2000 Professional. After you log on to Sentinel, an “Incorrect Version” message appears. However, the scanner is actually functioning. It still detects infected files when they are copied from one location to another.
If you attempt to print results or log files of scanning sessions on Windows 2000 Professional, the application fails, causing an “Access Violation” message.
For an update or the latest version, visit the Panda Web site at:http://www.pandasoftware.com/

Note
Web addresses can change, so you may be unable to connect to the Web site mentioned here.

PowerQuest Drive Image Version 2.0
You cannot image NTFS5 partitions with version 2.0 of Drive Image. To obtain an upgrade patch to version 2.02, visit the PowerQuest Web site at:http://www.powerquest.com/

Note
Web addresses can change, so you may be unable to connect to the Web site mentioned here.

This patched version can handle the new disk partitions. Version 2.0 of Drive Image can still handle legacy FAT and NTFS (Windows NT 4.0) partitions.
Puma Technologies IntelliSync Software
Puma Technologies IntelliSync software is included on various Toshiba laptops and may also be included on other mobile systems. The software allows computers to communicate by using infrared technology. This software has the following issues:
· If you install IntelliSync software directly on a computer that is running Windows 2000, the software does not function.
· If you install IntelliSync software on a computer that is running Windows 95 or Windows 98 and then you upgrade the computer to Windows 2000, the software does not function.
· If you install IntelliSync software on a computer that is running Windows NT 4.0 and then you upgrade the computer to Windows 2000, the computer may experience instability after you dock it or after you put it in standby or hibernate mode and then resume.

No known workaround is available at this time. To avoid system instability, uninstall this software before you upgrade from Windows NT 4.0 to Windows 2000.
QFX Version 6 and Version 7
QFX versions 6 and 7 rely on the font conversion feature in Windows NT 4.0 to use PostScript Type 1 fonts. This font conversion feature is not available in Windows 2000. Therefore, QFX versions 6 and 7 cannot use PostScript Type 1 fonts in Windows 2000.
If you have questions, contact QFX customer support at the following address or Web site:
Ron Scott, Inc.1000 Jackson BoulevardHouston, TX 77006E-mail: support@qfx.comWeb site: http://www.qfx.com/

Note
Web addresses can change, so you may be unable to connect to the Web site mentioned here.

Raxco Software PerfectDisk NT
PerfectDisk NT cannot defragment disks or partitions formatted as NTFS5. Raxco Software is working on a version of PerfectDisk NT for Windows 2000. For update or upgrade information, visit the Raxco Software Web site at:http://www.raxco.com/

Note
Web addresses can change, so you may be unable to connect to the Web site mentioned here.

Rumba Office Version 5.2
Inserting an object into the Rumba Notebook creates a General Protection Fault (GPF), which causes the program to shut down and causes the computer to stop responding. As a workaround, use the Rumba applets from the Rumba Program group to insert an object.
ScanSoft Pagis Pro 2.0
The following problems occur with Pagis Pro 2.0 on Windows 2000:
· While loading Quick Tour during installation, Pagis Pro 2.0 stops responding. As a workaround, load the Task Manager before installation, and use it to minimize the Setup Pagis Pro 2.0 window after it stops responding. Then, on the window with the “Problem opening “C:\temp”” message, click OK and continue Setup.
· If you choose to display the ISIS drivers during installation or from the Pagis Scan Tool, multiple “Bad Image” messages appear, eliminating approximately 80% of your ISIS Scanner driver selection. No known workaround is available at this time.
· When an older ASPI32.dll and a SCSI adapter are installed and you select an ISIS driver from the driver list, the system may stop responding. ASPI32.sys must be Version 4.0.0.967 or later. If you are unsure about your ASPI32.dll version and a SCSI adapter is installed, do not select any ISIS drivers or scanners. To check for possible upgrades to your existing drivers, visit the Adaptec Web site at:http://www.adaptec.com/support/files/upgrades.html#ASPI
· Some scanners may not work with the Pagis Scan Tool. To find out if your scanner is supported by Pagis under Windows 2000, contact ScanSoft, Inc., or visit the ScanSoft Web site at:http://www.scansoft.com/
Before you select a scanner to work from the Pagis Scan Tool, verify that the scanner works with its own driver software installed. If the Pagis UI has problems controlling the scanner, change the configuration from the Scan Tool to work with the Twain UI instead.
· The Pagis Scan Tool may not work with HP ScanJet Source Rev 1.0, which is included with Windows 2000. HP ScanJet Source Rev 1.0 does not work with the Pagis UI. Instead, configure it to work with the Twain UI.
· Uninstalling Pagis Pro 2.0 causes approximately 90 Severe “\Error decrementing” messages. No known workaround is available at this time.


Note
Web addresses can change, so you may be unable to connect to the Web sites mentioned here.

Seagate Crystal Reports Professional Version 5.0 and Version 6.0
Seagate Crystal Reports Professional version 5.0 and version 6.0 include some duplicate entries in the Font Style list on the Change Font (Format Editor) dialog box. Seagate Crystal Reports calls the EnumFontFamilies API function, which—in Windows 2000—lists an item for the font itself and also for any font substitutes. For example, the Arial font includes four font types: Regular, Bold, Italic, and Bold Italic. Therefore, you see five listings for each font type in the Style menu. These font substitutes do not exist in earlier versions of Windows.
No known workaround is available at this time. Seagate Crystal Reports Professional version 7.0 does not have this problem.
Seagate Crystal Reports Professional 7.0
When you open Map.rpt, a sample report file located in the Reports\Xtreme folder, and you then select a country in tree view in the preview pane, an access violation occurs in Sstree32.dll. The Crystal Reports Designer program uses a local variable that is not initialized. This problem also occurs with the Crystal Reports Professional 7.0 MR1 patch installed. No known workaround is available at this time.
Sierra Windows Draw 7
The Spell Checker in Sierra Windows Draw 7 does not function in Windows 2000. When you click Tools and then click Spell Checker, the following message appears:
“Spelling Dictionary not found.”
No known workaround is available at this time.
Sonic Foundry CD Architect 4.0
CD Architect 4.0 is not compatible with Windows 2000. No known workaround is available at this time. For additional information or updates, contact the application vendor.
SOS Best Defense—eSafe Protect Desktop 1.5
SOS Best Defense 1.5 includes a component named eSafe Protect Desktop. This application exhibited problems when it was tested under the Microsoft Driver Verifier for Windows 2000. If you enable the Driver Verifier in Windows 2000 against the drivers for Protect Desktop, your computer may not start. If this occurs, start your computer in Safe mode and disable the Driver Verifier. Then, you should either disable Protect Desktop or apply an application patch, if available.
For more information about where and how to apply an application patch (if available), visit the eSafe Web site at:http://www.esafe.com/

Note
Web addresses can change, so you may be unable to connect to the Web site mentioned here.

Symantec Applications
Earlier versions of the SymEvent.sys driver, which are used by many different Symantec applications, may cause problems on computers running Windows 2000. These problems range in severity from recoverable errors to the system being unusable. The following Symantec applications have exhibited these problems:
· Norton AntiVirus 4.0x
· Norton AntiVirus 5.x
· Norton Crashguard 2.0
· Norton Crashguard 4.x

Driver versions 10.2.13.4 and later do not have these problems. For more information and the latest driver installation package, contact Symantec or 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.

Symantec pcAnywhere32 Version 8.0
Symantec pcAnywhere32 version 8.0 attempts to replace the Windows 2000 video driver. This process disables most graphics display adapters. If you have already installed pcAnyhwere32, uninstall the application, which reverts the graphics display adapter back to its original driver. No other known workarounds are available at this time.
Trend Micro PC-cillin NT 1.0
The PC-cillin NT 1.0 real-time driver service, which monitors files being opened and run, does not start on Windows 2000. After you install PC-cillin and then restart the computer, the following messages appear:
“At least one service or driver failed...”“Unable to start the Real Time Scanner...”
Versions of PC-cillin written for Windows 95 and Windows 98 do not install on Windows 2000. To obtain the latest version of PC-cillin NT (currently, version 6.0), visit the Trend Micro, Inc. Web site at:http://www.antivirus.com/

Note
Web addresses can change, so you may be unable to connect to the Web site mentioned here.

Veritas Backup Exec 6.11
Backup Exec 6.11 for Single Server does not recognize an installed tape device, even though Windows has already recognized and installed the device. No known workaround is available at this time, and no time frame has been determined for fixing this problem.
Voyetra Audio Station 2
The Voyetra audio utility, Audio Station 2, may not work properly with Windows 2000. This application verifies that the Turtle Beach Montego (Aureal Vortex) audio card is installed and functioning properly. The audio card may require an updated driver that is compatible with Windows 2000. Updating this driver should restore functionality to Voyetra Audio Station 2 and its companion audio utilities.
Wright Design 2.1 by Wright Technologies
Starting Wright Design 2.1 in Windows 2000 prompts Design.exe to execute in Processes. Closing Wright Design 2.1 does not shut down Design.exe. This program continues to run in Processes and may hinder Wright Design from starting again in Windows 2000. As a workaround, shut down Design.exe from the Processes tab in Task Manager.
Þ To shut down Design.exe from the Processes tab in Task Manager
1. On the Windows 2000 task bar, right-click the bar itself, and then click Task Manager.
2. In Task Manager, select Design.exe.
3. On the Processes tab, click End Process.

After you shut down Design.exe in Task Manager, you can restart Wright Design 2.1 in Windows 2000. The application starts and operates correctly.
For product information, you can contact Wright Technologies at the following address or Web site:
Wright America Inc.Fax: 416-360-4568Toll free: 1-800-259-5580Web site: http://www.wrightna.com/

Note
Web addresses can change, so you may be unable to connect to the Web site mentioned here.

Printing Notes
The following sections describe Windows 2000 issues related to printing.
Upgrade Issues
In some cases, you may experience a change in behavior during an upgrade from Windows NT 4.0 to Windows 2000. Setup has identified a set of printer drivers that can create problems in Windows 2000.
Local Printer Upgrade
If your manufacturer-supplied printer driver appears on the “OEM Drivers Incompatible with Windows 2000” list in this section, a Microsoft-based driver is installed and becomes your default driver for that device. If a suitable driver is not available, Setup deletes the Windows NT 4.0 driver during upgrade.
Network Print Server
If your manufacturer-supplied printer driver appears on the “OEM Drivers Incompatible with Windows 2000” list in this section, a Microsoft-based driver is installed and becomes your default driver for that device. If a suitable driver is not available, Setup deletes the Windows NT 4.0 driver during upgrade. This impacts earlier versions of client connections. To resolve this problem, contact the printer manufacturer and obtain an updated driver.
OEM Drivers Incompatible with Windows 2000
To determine whether the original version of your printer driver is incompatible with Windows 2000, refer to the following .inf file:c:\winnt\inf\printupg.inf
where c: is the installation partition on Windows 2000.
If an OEM driver is not compatible, Windows 2000 automatically installs a compatible printer driver in its place.
Brother 1050 2100
In rare circumstances, using the Brother drivers listed in the Printupg.inf file for printing may cause an access violation. As a workaround, change the print processor from Brpproc to Winprint.
Þ To change the print processor
1. Click Start, point to Settings, and then click Printers.
2. Right-click the correct Brother model, and then click Properties.
3. On the Advanced tab, click Print Processor.
4. Change the current Print Processor to Winprint.
5. Click OK.

Common Print Error Messages
If you encounter the new connection, server upgrade, or client upgrade errors described in this section, obtain an updated printer driver from the OEM.
New Connection
The following errors may occur for new connections:
· When you perform a clean installation of Windows 2000 with an incompatible Windows NT 4.0 driver, the following message appears:
“The printer driver you selected is not compatible with your current version of Windows. Select a compatible driver from the list, or contact your administrator for help.”
· When a Windows 2000 client establishes a new Point-and-Print connection to a Windows NT 4.0 server with an incompatible driver installed, the following message appears:
“The server on which the printer resides does not have a suitable printer driver installed. Click on OK if you wish to install the driver on your local machine.”

Server Upgrade
When you upgrade to a Windows 2000 print server and an incompatible driver is deleted during upgrade, the Windows NT 4.0 Point-and-Print client receives the following message:
“Printer does not exist on the computer”
If you attempt to view the printer properties, the following message appears:
“Printer properties cannot be displayed. The printer name is invalid.”
Client Upgrade
When you upgrade a Windows NT 4.0 client to a Windows 2000 client and an incompatible OEM driver is replaced by the Universal Driver (Unidrv.dll) or deleted during the upgrade process, an attempt to re-establish the print connection produces the following message:
“Unable to connect”
If you attempt to view the printer properties, the following message appears:
“Printer properties cannot be displayed. The printer driver is unknown.”
Terminal Services
The following sections describe issues related to Windows 2000 Terminal Services and upgrading from Windows NT 4.0 Terminal Server.
Terminal Services Security—Selectable Application Compatibility Permissions
Windows 2000 provides greater security than Windows NT 4.0. One of the Windows 2000 enhancements controls Users group access to key system registry information at a more granular level. However, some legacy applications dynamically alter these entries to record state and profile information. A typical user cannot run these applications because they require Power Users privileges.
Windows 2000 Terminal Services allows users to select the level of enforcement required. During the application server installation, the administrator can select whether users have permissions compatible with the Windows 2000 Users group, which increases security, or permissions compatible with the Windows NT 4.0 Terminal Server Edition Users group, which increases application compatibility. The administrator can use the Terminal Services Configuration tool to change this setting after installation.
Terminal Services—License Management
Terminal Services in Windows 2000 has specific license management requirements. Using Terminal Services Licensing, you can manage Terminal Services Client Access licenses (CALs) and Terminal Services Internet Connector (IC) licenses from your license server. Terminal Services Licensing is required for Windows 2000 Terminal Servers configured in Application Server mode. Terminal Services Licensing is not required for Windows 2000 Terminal Servers configured in Remote Administration mode.
To use Terminal Services in Application Server mode in Windows 2000, you must enable the Terminal Services Licensing service on a Windows 2000 server on your network. To do this, select Terminal Services Licensing in the Windows Component wizard. For more information about installing Terminal Services Licensing, see Windows 2000 Server Help.
Then, complete the following tasks by using the Licensing wizard in the Terminal Services Licensing administration tool:
· Activate a Windows 2000 Terminal Services license server.
· Install client licenses on the license server.

If you are upgrading from a release candidate build to the final build of Windows 2000 on a Windows 2000 Terminal Server or a Windows 2000 server configured for Terminal Services Licensing, your release candidate licenses are no longer valid. The license database on your release candidate Terminal Services license server will be reset, and you must obtain licenses for your terminal services clients through normal purchase channels. Client licenses are no longer available for testing purposes, and client license codes obtained during the release candidate period will not install on the final build of Windows 2000. Test client licenses issued by your release candidate Terminal Services license server are not valid for use with the final build of Windows 2000 Terminal Server.
For additional information about Terminal Services Licensing, see the following resources:
· Chapter 3, “Planning Your Windows 2000 Server Installation,” in the Microsoft Windows 2000 Server Getting Started online book, which is located in the \Setuptxt folder
· The white paper titled, “Windows 2000 Terminal Services Licensing,” on the Microsoft Windows 2000 Server Web site at:http://www.microsoft.com/windows/server/Technical/terminal/default.asp
· Windows 2000 Help

Terminal Services Remote Administration—Application Notes
Running Terminal Services in Remote Administration mode does not require a special installation. However, some applications may not run properly within a remote session, even though they still run properly from the console. Remote session problems may occur for the following reasons:
· A remote session cannot see the user interface components within the service. If the service itself creates dialog boxes or other user components, they are managed under the system context and are always sent to the console.
· Applications do not make use of the per-session namespace.

To review specific application compatibility information for Remote Administration mode, see Terminal Services in the Technical Resources section of the Microsoft Windows 2000 Server Web site at:http://www.microsoft.com/windows/server/
Terminal Services Application Server—Application Installation
This section describes issues related to the application compatibility scripts.
Multilingual Compatibility Scripts
Windows 2000 multilingual capabilities allow Terminal Services to operate in several languages simultaneously, providing each user with their language preference. Supporting these capabilities requires global application compatibility scripts, which often contain localized file names. When a localized file name contains characters that are not in the server’s default code page, they do not output correctly at the command prompt. To prevent this, before you run the compatibility script, you must set the appropriate code page based on the application names to display. The CHCP command allows you to switch the code page and provides the required page as an argument.
Programs and Scripts
To review specific compatibility information for Application Server, see Terminal Services in the Technical Resources section of the Microsoft Windows 2000 Server Web site at:http://www.microsoft.com/windows/server/
Windows 2000 Domain Controller with Citrix MetaFrame
To successfully upgrade Windows NT 4.0 Terminal Server with Citrix MetaFrame installed to a domain controller in Windows 2000 Server, you must take steps to ensure connections for the client users. This applies to upgrading a Windows NT 4.0 Terminal Server primary or backup domain controller to Windows 2000 Server, or to upgrading a stand-alone Windows NT 4.0 Terminal Server to Windows 2000 Server and promoting it to a domain controller.
In Terminal Server, the group called “Everyone” has the right to log on locally to a Terminal Server by default. Therefore, any user can log on at the Terminal Server console, regardless of the server’s role—as a primary or backup domain controller, or as a stand-alone server. This is different from a standard Windows NT 4.0 Server, which allows only administrators to log on locally by default. The different default rights occur because clients that connect to a Terminal Server are actually using the Terminal Server console.
The ability for any user to log on to a Terminal Server console was considered a possible security risk and has been removed from Windows 2000 Server. Therefore, you must complete the following steps to ensure connections for the client users.
Þ To ensure connections for the client users
1. Before you upgrade Windows NT 4.0 Terminal Server to Windows 2000 Server, create a group specifically for your Terminal Server clients.
2. Grant this group the right to log on locally.
3. Add the Terminal Server client users to this group.
4. Remove the Everyone group, limiting console logon rights to the client group and the administrators.

If a Terminal Server client or a user at the console does not have the right to log on locally, the following message appears:
“Local Policy of this system does not permit you to log on interactively.”
This message also appears if you modify a user’s configuration in User Manager by clearing the Allow Logon to Terminal Server check box.
Þ To grant or remove the right to log on locally in Terminal Server
1. Start User Manager for Domains.
2. Click Policies, and then click User Rights.
3. In the Rights field, click Log On Locally.
4. In the Grant To field, select the users and/or groups that can log on locally.


Note
If you install a Windows NT 4.0 Terminal Server as a backup domain controller, and if policy for the existing primary domain controller is set so that users do not have the right to log on locally, the new backup domain controller inherits that policy. Therefore, no clients can connect to the Terminal Server. If a Terminal Server is a domain controller, the entire domain must use a policy that allows users to log on locally.

Windows 2000 Advanced Server
The following sections describe issues related to Windows 2000 Advanced Server.
Cluster Service
This section describes issues related to Cluster Service.
Unattended Cluster Service Install
If the line “cluster = off” is present in the answer file used to install Windows 2000, Cluster Service is only partially installed. If you decide to install Cluster Service at a later time, remove the partial installation by using Add/Remove Programs in Control Panel and then reinstall Cluster Service. If you intend to use a server as a cluster node in the future, you should select Cluster Service during Windows 2000 Setup.
Cluscfg.exe Does Not Reexamine Disks
You must power on all external disks before you start the cluster configuration. Disks and storage subsystems that are activated while Cluscfg.exe is running do not appear. A message displays if no other shared disks are found.
Cluster Setup
After you connect the shared SCSI bus to both nodes, do not run Windows 2000 Advanced Server on both nodes at the same time until Windows Clustering has been installed on at least one node.
Installing Active Directory on a Microsoft Cluster Server Node
When you promote a server running Windows 2000 Advanced Server to a domain controller, you must not install the directory or log files on an external clustered disk. Active Directory is not cluster-aware; transferring ownership of the external disk to a different node in the cluster makes it inaccessible to Active Directory and causes the domain controller to fail.
Using APM/ACPI Power-Saving Features on a Cluster
You must not enable APM/ACPI power-saving features on server cluster members. A cluster member that turns off disk drives or enters hibernate or standby mode can initiate a failure in the cluster. If multiple cluster nodes have power-saving features enabled, the entire cluster may become unavailable.
Therefore, use Power Options in Control Panel to set the “Always On” power scheme for all cluster members.
Þ To set the Always On power scheme for all cluster members
1. Click Start, point to Settings, and then click Control Panel.
2. Double-click Power Options.
3. On the Power schemes list, select Always On.
4. Verify that Turn off hard disks is set to Never.
5. Verify that System Standby is set to Never.
6. Verify that System Hibernates is set to Never.
7. Click OK.


Note
Installing Terminal Services reduces the power management options available to users. Standby and Hibernate options are not available. Therefore, if you installed Terminal Services, you can omit Steps 5 and 6 in the procedure above.

Services for Macintosh
Windows 2000 does not support Services for Macintosh installed on the shared, cluster storage. Initially, in Windows NT 4.0, this was mainly due to the architectural restraints imposed by Appletalk. However, Windows 2000 does not support Services for Macintosh because it maintains stateful information in memory. Specifically, the MAC Volume Index is located in virtual memory. Windows 2000 does not support using Services for Macintosh volumes as a cluster file share resource. Using these volumes as a cluster file share resource may result in data loss.
DHCP Resource Dependencies
According to the Microsoft Windows 2000 Advanced Server documentation, a DHCP resource should depend on a physical disk resource and an IP resource. However, at this time, the new resource option in the cluster administration tool requires a disk resource, an IP resource, and a network name resource.
WINS Resource Dependencies
According to the Microsoft Windows 2000 Advanced Server documentation, a WINS resource should depend on a physical disk resource. However, at this time, the new resource option in the cluster administration tool requires a disk resource, an IP resource, and a network name resource.
Network Load Balancing
Network Load Balancing requires Windows 2000 Advanced Server. You can automatically upgrade from Windows Load Balancing Service (WLBS) for Windows NT 4.0 Server or Windows NT 4.0 Server Enterprise Edition to Network Load Balancing for Windows 2000 Advanced Server. However, if you attempt to upgrade WLBS to Windows 2000 Professional or Server, a warning message appears and the upgrade fails.
Cluster Service
You should not enable Network Load Balancing on computers that are part of a Cluster Service cluster because it can interfere with the Cluster Service’s use of network interface cards. Microsoft does not support this configuration. Instead, you should use separate clusters for Network Load Balancing and Cluster Service. This will be addressed in a future release.
Assigning Cluster Addresses
After you install and configure Network Load Balancing, you must enter the cluster addresses in TCP/IP properties. Even if you omit this step, the cluster converges and appears to be working properly. However, the cluster host does not accept and handle cluster traffic. This will be addressed in a future release.
Network Adapter Reinitialization and Clusters
When installed into an existing cluster, a new Network Load Balancing host may initially converge as a single host cluster while the network adapter is reinitialized. After the adapter is reinitialized, the host joins the cluster. This process can take up to 30 seconds, and the following event log message may appear:
“Duplicate cluster subnets detected. The network may have been inadvertently partitioned.”
UDP Port 2504 and Port 1717
Network Load Balancing uses User Datagram Protocol (UDP) port 2504 for receiving remote control messages. For backward compatibility, it also responds to port 1717. If you block port 2504 on the firewall to prevent reception of remote control messages, you should also block port 1717.
Scaling NetBIOS Read-Only File Access or Printer Access
When scaling NetBIOS read-only file access or printer access with Network Load Balancing, clients cannot access the cluster by the cluster name.
Supported Network Adapters
Network Load Balancing is designed for use with Ethernet and FDDI network adapters. It is not compatible with ATM, ATM LAN emulation, or token ring adapters.
Using the Wlbs.exe Network Load Balancing Control Program
When you use the Network Load Balancing control program, Wlbs.exe, make sure that none of the host or cluster names begins with a number. If any of those names begins with a number, that name is treated as an IP address and the operation fails. As a workaround, you can use the corresponding IP address rather than the host or cluster name to perform the desired task. This will be addressed in a future release.

Choosing Components to Install :

The Windows Server 2003 family of products includes a wide variety of core components, including a number of administrative tools that Setup installs automatically. In addition, you can choose from a number of optional components that extend the functionality of your server. You can install these components after Setup by using Add or Remove Programs. Another way to install components is to use Manage Your Server, through which you can specify a server role such as a print server, rather than selecting the individual components required for that server role.
For information about Manage Your Server, which includes the Configure Your Server Wizard, see Configuring Roles for Your Server

Choosing more of these components means providing more possibilities on the server. However, choose only the components you need, because each component requires additional disk space. The following table, and the list that follows it, will help you choose the components you need in your installation.

The following list describes the components in the preceding table and all other components that
you can install.

Accessories and Utilities:

Includes the Accessibility Wizard, along with desktop accessories such as WordPad, Paint, and Calculator, and communications and media accessories such as Hyperterminal and Media Player. To select individual items in the Windows Components Wizard, click Details and select from the list.

Application Server:

Includes Internet Information Services, ASP .NET, Message Queuing, and related components, to provide a unified Web platform on which you can run enterprise-class Web applications.The Microsoft .NET Framework is built into all products in the Windows Server 2003 family except for the Itanium-based versions. If you plan to use the Microsoft .NET Framework with ASP .NET, install IIS, ASP .NET, and any other components (such as Message Queuing) that provide services you require.IIS also includes Network News Transfer Protocol (NNTP), File Transfer Protocol (FTP), and Simple Mail Transfer Protocol (SMTP).

Certificate Services:

Provides customizable services for issuing and managing certificates used in software security systems employing public key technologies. Certificates can make it easier for you to provide secure e-mail, Web-based authentication, smart card authentication, and other forms of security. For information about authentication of dial-up users, see Networking Services, later in this list.

E-mail Services:

Includes Post Office Protocol 3 (POP3) service and the Simple Mail Transfer Protocol (SMTP) service. You can use the POP3 service to store and manage e-mail accounts on the mail server.
Fax Services
Provides support for the sending and receiving of faxes. This feature is not available on the Itanium-based versions of the Windows operating systems. This content is not available in this preliminary release.x64

Indexing Service:

Provides indexing functions for documents stored on disk, allowing users to perform fast full-text searches.

Management and Monitoring Tools:

Provides tools for network monitoring as well as tools for communications administration and monitoring, including support for the development of customized client dialers for remote users, and support for the implementation of phone books that can be automatically updated from a central server. In addition, includes the Simple Network Management Protocol (SNMP) and the Windows Management Instrumentation (WMI) SNMP Provider.

Networking Services:

Provides important support for networking, including the items in the following list. To select individual items in the Windows Components Wizard, click Details and select from the list.For information about network monitoring, see "Management and Monitoring Tools," earlier in this list. For background information about services in this list, see Managing Core Network Services Domain Name System (DNS). Provides the name resolution service required by Active Directory. DNS is also the service often used by clients running Windows 2000, Windows XP, and products in the Windows Server 2003 family. With name resolution, users can access servers by name, instead of having to use IP addresses that are difficult to recognize and remember.Dynamic Host Configuration Protocol (DHCP). Gives a server the capability of assigning IP addresses dynamically to network devices. These devices typically include server and workstation computers, but can also include other devices such as printers and scanners. With DHCP, you do not need to set and maintain static IP addresses on any of these devices, except for intranet servers providing the DHCP, DNS, and/or WINS services.Internet Authentication Service (IAS). Performs authentication, authorization, and accounting for dial-up and VPN users. IAS supports the RADIUS protocol.RPC over HTTP Proxy. Supports remote procedure call (RPC) and Distributed Component Object Model (DCOM) over HTTP, through Internet Information Services (IIS).Simple TCP/IP Services. Supports Character Generator, Daytime, Discard, Echo, and Quote of the Day.Windows Internet Name Service (WINS). Provides the name resolution service usually used by clients running Windows NT and earlier versions of Microsoft operating systems. With name resolution, users can access servers by name, instead of having to use IP addresses that are difficult to recognize and remember.

Other Network File and Print Services:

Provides the following:File services for the Macintosh operating system.Print services for the Macintosh operating system. This feature is not available on the Itanium-based versions of the Windows operating systems. This content is not available in this preliminary release.x64 Print services for UNIX.

Remote Installation Services:

Provides services that you can use to create installation images of operating systems or even of complete computer configurations, including desktop settings and applications. You can then make these images available to users at client computers. The target client computers must either support remote startup with the Pre-Boot eXecution Environment (PXE) ROM, or else must be started with a remote-start floppy disk. On the server, you will need a separate partition for Remote Installation Services. For more information, see Considerations when planning disk partitions

Remote Storage:

Provides an extension to your disk space by making removable media such as tapes more accessible. Infrequently used data can automatically be transferred to tape and retrieved when needed.

Terminal Server:

Provides the ability to run client applications on the server, while thin-client software acts as a terminal emulator on the client. Each user sees an individual session, displayed as a desktop, and each session is managed by the server, independent of any other client session. If you install Terminal Server, you must also install Terminal Server Licensing on at least one computer (not necessarily a computer on which you install Terminal Server). However, there is a grace period of 120 days during which you can use Terminal Server even though you have not set up license servers yet and have not installed client license key packs.

Terminal Server Licensing:

Provides a licensing service that allows you to download, issue, and track licenses for Terminal Server clients. If you install Terminal Server, you must also install Terminal Server Licensing on at least one computer (not necessarily a computer on which you install Terminal Server). However, there is a grace period of 120 days during which you can use Terminal Server even though you have not set up license servers yet and have not installed client license key packs.To activate a license server quickly, install it on a computer that has Internet access.During Terminal Server Licensing Setup, you can select from two types of license server: enterprise license server (the default) or domain license server. The basic guideline is to select enterprise license server unless you are installing in a workgroup or installing in a domain where all the domain controllers run Windows NT 4.0. For more information, see Terminal Server Licensing

UDDI Services:

Provides support for publishing and locating information about Web services, based on the industry specification called Universal Description Discovery and Integration (UDDI). With UDDI Services, enterprise developers can efficiently discover, share, and reuse Web services directly through their development tools.UDDI Services is not included with Windows Server 2003, Web Edition. In addition, Windows Server 2003, Standard Edition, supports only stand-alone installations of UDDI Services. Distributed installation support is available with Windows Server 2003, Enterprise Edition, and Windows Server 2003, Datacenter Edition. In a stand-alone installation of UDDI Services, both the UDDI Web server component and the UDDI database component are installed onto a single server. In a distributed installation, UDDI components are distributed across multiple servers.For more information about Windows Server 2003, Web Edition, see Overview of Windows Server 2003, Web Edition

Update Root Certificates:

Provides a service that automatically downloads the most current root certificates for secure email, Web browsing, and software delivery.

Windows Media Services:

Provides multimedia support, allowing you to manage, deliver, and archive Windows Media content, including streaming audio and video, over an intranet or the Internet. This feature is not available on the Itanium-based versions of the Windows operating systems.

=====================================================================c

Windows Server TechCenter:

[Copy and Paste the below givne microsoft link to ur Address bar of Internet Explorer to learn more about Windows 2000 Server]

http://technet2.microsoft.com/WindowsServer/en/Library/552ed70a-208d-48c4-8da8-2e27b530eac71033.mspx?mfr=true

[Coverage: Windows Server 2003 Technical Library

Windows Server Troubleshooting (Beta)

Windows Compute Cluster Server 2003 Technical Library

Windows Rights Management Services (RMS) Technical Library

Windows Server Update Services (WSUS) Technical Library

Internet Information Services (IIS) 6.0 Technical Library

Internet Information Services (IIS) 7.0 (Beta) Technical Library

Microsoft Identity Integration Server (MIIS) 2003 Technical Library

Virtual Server 2005 Technical Library ]

====================================================================

Troubleshooting Specific Remote Desktop Problems:

I cannot copy text from an application on the terminal server to another application that is on my local computer.

Cause: It is possible that Remote Desktop Connection was not installed correctly.

Solution: Uninstall and then reinstall Remote Desktop Connection. If you need assistance, contact the server administrator.

I minimized the Remote Desktop Connection dialog box, and then my screen went blank.

Cause: Using a password-protected screen saver can cause this problem. Your applications are still running on the remote computer, but you can no longer use them.

Solution:Disconnect Remote Desktop Connection, or ask the server administrator to disconnect you.
Solution: Do not minimize the Remote Desktop Connection dialog box if your computer uses a password-protected screen saver.
Solution: Do not use a password-protected screen saver on your local computer.

The screen saver on my Remote Desktop is blank.

Cause: By default, when a screen saver is activated on Remote Desktop, it is blank. This is true regardless of whether you have previously selected a different screen saver.

Solution: Continue to use the blank screen saver.

I'm supposed to be able to connect to a specific application when I log on to the remote computer, but it doesn't start.

Solution: If the remote computer is running Windows XP Professional, the complete contents of the Desktop are always displayed. Start the program you want to use by double-clicking its icon on the Desktop or using the Start menu.

Cause: The client connection might have been configured to start a program upon connection, but the program path and file name are incorrect.

Solution: Check the properties for the client connection to ensure that the program path and file name are correct. Also, confirm that the program exists in this location on the server.

Cause: The server administrator might have specified a different program to start upon connection, using Group Policy, Terminal Services Configuration, or other Terminal Services administration tools.

Solution: Contact the server administrator.

Remote Desktop Connection is very slow.

Cause:A low-bandwidth connection can slow Remote Desktop performance.

Solution: On the remote computer, set the background selection to None.
Solution: Do not run memory-intensive applications over Remote Desktop Connection.
Solution: Consider upgrading your modem or purchasing a high-speed service.

===============================================================================

Troubleshooting Remote Desktop Licensing Error Messages:

Troubleshooting Licensing Error Messages:

This topic lists licensing error messages that can appear on client computers, and it describes the causes of and solutions for these errors. Although these error messages appear on clients, they are frequently caused by problems with the Windows Server 2003 Terminal Server license server or the terminal server. Therefore, when you troubleshoot Terminal Server Licensing issues, it is useful to first determine whether there are server configuration issues or problems with network connectivity.
Important
The solutions in this topic are intended to be implemented by administrators. If you are not an administrator, contact your server administrator for assistance in resolving these error messages. If you are an administrator, to help prevent Terminal Server Licensing issues and to more efficiently diagnose issues, it is highly recommended that you see Guidelines for Deploying Terminal Server (http://go.microsoft.com/fwlink/?LinkID=34627), and Windows Server 2003 Terminal Server Licensing Issues and Requirements for Deployment (http://go.microsoft.com/fwlink/?LinkID=23444).

Which message are you getting?

1. The remote session was disconnected because the local computer's client access license could not be upgraded or renewed. Please contact the server administrator.
2. The remote computer disconnected the session because of an error in the licensing protocol. Please try connecting to the remote computer again or contact your server administrator.
3. The remote session was disconnected because there were network problems during the licensing protocol. Please try connecting to the remote computer again.
4. A licensing error occurred while the client was attempting to connect. (Licensing timed out.) Please try connecting to the remote computer again.
5. The remote session was disconnected because there are no Terminal Server client access licenses available for this computer. Please contact the server administrator.
6. The remote session was disconnected because there are no Terminal Server License Servers available to provide a license. Please contact the server administrator.
7. Because of a security error, the client could not connect to the terminal server. After making sure that you are logged on to the network, try connecting to the server again.

• The remote session was disconnected because the local computer's client access license could not be upgraded or renewed. Please contact the server administrator.
  Cause: The Terminal Server licensing mode on the terminal server might be set to Per Device, while the license server might be configured to issue only Per User client access licenses (CALs). If this is the case, then the license server issues only temporary licenses that cannot be upgraded. When the temporary licenses are within several days of expiring, "Event ID 26, Source: Application Pop-up" appears in the application event log on the client. The event message indicates the number of days remaining before the temporary license expires. Similarly, "Event ID 1011, Source TermService" appears in the application event log on the terminal server.
  Solution: Change the Terminal Server licensing mode from Per Device to Per User.
  Important
  Per User CALs are not monitored by Terminal Server. This means that even though there is a Per User CAL in the license server database, the Per User CAL is not decremented when it is used. This does not remove administrators from End User License Agreement (EULA) requirements to have a valid terminal server CAL for each user. Failure to have a Per User CAL for each user, if Per Device CALs are not being used, is a violation of the EULA.
  The following text is from the EULA for Windows Server 2003:
  "Two different TS CALs are available to you: 'Device' and 'User.' Each TS Device CAL permits one Device (used by any User) to conduct Windows Sessions on any of your Servers. Each TS User CAL permits one User (using any Device) to conduct Windows Sessions on any of your Servers. You may use a mix of TS Device CALs and TS User CALs simultaneously with the Server Software in your environment. You can have a Terminal Server request Per User licenses or Per Device (default) but not both simultaneously."
  See also: Configure the Terminal Server Licensing mode
  The remote computer disconnected the session because of an error in the licensing protocol. Please try connecting to the remote computer again or contact your server administrator.
  Cause: The terminal server might not be able to locate the license server.
  Solution: Perform the following steps:
  1.Verify that the license server is correctly installed.
  2.Verify that the Terminal Server Licensing service is running on the license server.
  3.Verify that the client, the terminal server, and the license server can communicate by ensuring that Domain Name System (DNS) is configured correctly on each computer. To do this, run the ping command from each computer to each computer using the IP address, FQDN, and the NetBIOS name. If any of the ping commands fail, verify the DNS configuration on the network.
  4.On the terminal server, set a preferred licensing server to connect to. You can do this by using the registry, a Windows Management Instrumentation (WMI) script, or, in Windows Server 2003 with Service Pack 1, you can use Group Policy settings or Terminal Server Configuration.

Solution: If the previous solution does not resolve this problem, create a backup of the MSLicensing registry key and its subkeys on the client, and then remove the original key and subkeys by doing the following:
1. On the client, navigate to the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing.
2. Click MSLicensing.
3. On the Registry menu, click Export Registry File.
4. In the File name box, type mslicensingbackup, and then click Save.
5. If you need to restore this registry key in the future, double-click mslicensingbackup.reg.
6. On the Edit menu, click Delete, and then click Yes to confirm the deletion of the MSLicensing registry subkey.
7. Close Registry Editor, and then restart the computer.
When the client is restarted, the missing registry key is rebuilt.

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.

• The remote session was disconnected because there were network problems during the licensing protocol. Please try connecting to the remote computer again.
  Cause: The terminal server might not be able to locate the license server.
  Solution: Perform the following steps:
  1. Verify that the license server is correctly installed.
  2. Verify that the Terminal Server Licensing service is running on the license server.
  3. Verify that the client, the terminal server, and the license server can communicate by ensuring that Domain Name System (DNS) is configured correctly on each computer. To do this, run the ping command from each computer to each computer using the IP address, FQDN, and the NetBIOS name. If any of the ping commands fail, verify the DNS configuration on the network.
  4. On the terminal server, set a preferred licensing server to connect to. You can do this by using the registry, a Windows Management Instrumentation (WMI) script, or, in Windows Server 2003 with Service Pack 1, you can use Group Policy settings or Terminal Server Configuration.
• Solution: On the Windows 2000 license server, do one of the following:
  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.
  
  In the registry, navigate to HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet \Control\Lsa\RestrictAnonymous, and set the RestrictAnonymous registry key to a value of 1 or 0.
  
• In Local Security Policies, open the appropriate policy and, in the console tree, navigate to Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options. Then, enable either Do not allow enumeration of SAM accounts and shares (equivalent to a RestrictAnonymous value of 1 or None) or Rely on default permissions (equivalent to a RestrictAnonymous value of 0).
  
• Notes:
  If the license server is a member of an Active Directory domain and a conflicting security setting is configured for the license server in Group Policy, the Group Policy setting overrides the local security setting. In this case, to ensure that the security setting that you want to apply takes effect, configure the setting in Group Policy.
  
• In Windows Server 2003, you cannot set RestrictAnonymous to a value of 2 to prohibit anonymous connections. If you need to prohibit anonymous users from being granted the same access that is granted to members of the Everyone group, you must use the new Everyone Network access: Let Everyone permissions apply to anonymous users setting in Local Security Policies.

Solution: If the previous solution does not resolve this problem, create a backup of the MSLicensing registry key and its subkeys on the client, and then remove the original key and subkeys by doing the following:
1. On the client, navigate to the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing.
2. Click MSLicensing.
3. On the Registry menu, click Export Registry File.
4. In the File name box, type mslicensingbackup, and then click Save.
5. If you need to restore this registry key in the future, double-click mslicensingbackup.reg.
6. On the Edit menu, click Delete, and then click Yes to confirm the deletion of the MSLicensing registry subkey.
7. Close Registry Editor, and then restart the computer.
When the client is restarted, the missing registry key is rebuilt.

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.

A licensing error occurred while the client was attempting to connect. (Licensing timed out.) Please try connecting to the remote computer again.

Cause: If you are using Internet Protocol security (IPsec) to help protect traffic over TCP between clients and terminal servers, then packet fragmentation might occur. As a result, some packets might not reach their destination, and client connections to terminal servers might fail.

Solution: Configure IPsec to help protect traffic over UDP rather than over TCP.

The remote session was disconnected because there are no Terminal Server client access licenses available for this computer. Please contact the server administrator.

Cause: The license server might not have any remaining Per Device CALs to issue.

Solution: Use Terminal Server Licensing to determine the number of CALs remaining on the license server. To open Terminal Server Licensing, click Start, Programs, Administrative Tools, and then point to Terminal Server Licensing. If the license server does not have any remaining CALs to issue to clients, purchase and install additional CALs as required.

Cause: The Terminal Server licensing mode on the terminal server might be set to Per Device, while the license server might have only Per User CALs. If this is the case, the license server issues only temporary licenses that cannot be upgraded. When the temporary licenses are within several days of expiring, "Event ID 26, Source: Application Pop-up" appears in the application event log on the client. The event message indicates the number of days remaining before the temporary license expires. Similarly, "Event ID 1011, Source TermService" appears in the application event log on the terminal server.

Solution: Change the Terminal Server Licensing mode from Per Device to Per User.

Important:

Per User CALs are not monitored by Terminal Server. This means that even though there is a Per User CAL in the license server database, the Per User CAL is not decremented when it is used. This does not remove administrators from End User License Agreement (EULA) requirements to have a valid terminal server CAL for each user. Failure to have a Per User CAL for each user, if Per Device CALs are not being used, is a violation of the EULA.

The following text is from the EULA for Windows Server 2003:
"Two different TS CALs are available to you: 'Device' and 'User.' Each TS Device CAL permits one Device (used by any User) to conduct Windows Sessions on any of your Servers. Each TS User CAL permits one User (using any Device) to conduct Windows Sessions on any of your Servers. You may use a mix of TS Device CALs and TS User CALs simultaneously with the Server Software in your environment. You can have a Terminal Server request Per User licenses or Per Device (default) but not both simultaneously."

Cause: The terminal server might not be able to locate the license server.
Solution: Perform the following steps:
1.Verify that the license server is correctly installed.
2.Verify that the Terminal Server Licensing service is running on the license server.
3.Verify that the client, the terminal server, and the license server can communicate by ensuring that Domain Name System (DNS) is configured correctly on each computer. To do this, run the ping command from each computer to each computer using the IP address, FQDN, and the NetBIOS name. If any of the ping commands fail, verify the DNS configuration on the network.
4.On the terminal server, set a preferred licensing server to connect to. You can do this by using the registry, a Windows Management Instrumentation (WMI) script, or, in Windows Server 2003 with Service Pack 1, you can use Group Policy settings or Terminal Server Configuration.

Solution:If the previous solution does not resolve this problem, create a backup of the MSLicensing registry key and its subkeys on the client, and then remove the original key and subkeys by doing the following:
1. On the client, navigate to the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing.
2. Click MSLicensing.
3. On the Registry menu, click Export Registry File.
4. In the File name box, type mslicensingbackup, and then click Save.
If you need to restore this registry key in the future, double-click mslicensingbackup.reg.
5. On the Edit menu, click Delete, and then click Yes to confirm the deletion of the MSLicensing registry subkey.
6. Close Registry Editor, and then restart the computer.
When the client is restarted, the missing registry key is rebuilt.

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.

The remote session was disconnected because there are no Terminal Server license servers available to provide a license. Please contact the server administrator.

Cause: The terminal server might not be able to locate the license server.

Solution: Perform the following steps:
1.Verify that the license server is correctly installed.
2.Verify that the Terminal Server Licensing service is running on the license server.
3.Verify that the client, the terminal server, and the license server can communicate by ensuring that Domain Name System (DNS) is configured correctly on each computer. To do this, run the ping command from each computer to each computer using the IP address, FQDN, and the NetBIOS name. If any of the ping commands fail, verify the DNS configuration on the network.
4.On the terminal server, set a preferred licensing server to connect to. You can do this by using the registry, a Windows Management Instrumentation (WMI) script, or, in Windows Server 2003 with Service Pack 1, you can use Group Policy settings or Terminal Server Configuration.

Cause: The client might have exceeded its Terminal Server Licensing grace period, and a license server has not yet been installed or activated to issue the client a CAL.

Solution: Install Terminal Server Licensing, activate the license server, and then install and purchase a sufficient number of CALs to support the clients in your organization.

Because of a security error, the client could not connect to the terminal server. After making sure that you are logged on to the network, try connecting to the server again.

Cause: If you upgraded a Windows NT domain to Windows 2000 or Windows Server 2003, then the certificate on the terminal server might be corrupt. As a result, Windows 2000 Terminal Services clients might be repeatedly denied access to the terminal server.

Solution: On each terminal server and client, perform the following steps:
1. On each terminal server, create a backup of the registry.
2. Navigate to the following registry subkey: HKLM\SYSTEM\CurrentControlSet\Services\TermServices\Parameters.
3. On the Registry menu, click Export Registry File.
4. In the File name box, type exported-parameters, and then click Save.
If you need to restore this registry subkey in the future, double-click exported-parameters.reg.
5. Under the Parameters registry subkey, right-click each of the following values:

Certificate
•X509 Certificate
•X509 Certificate ID

6.Click Delete, and then click Yes to confirm the deletion.
7.Close Registry Editor, and then restart each terminal server.
8.On the client, create a backup of the MSLicensing registry key and its subkeys, and then remove the original key and subkeys by doing the following:
•Navigate to the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing.
•Click MSLicensing.
•On the Registry menu, click Export Registry File.
•In the File name box, type mslicensingbackup, and then click Save.
•If you need to restore this registry key in the future, double-click mslicensingbackup.reg.
•On the Edit menu, click Delete, and then click Yes to confirm the deletion of the MSLicensing registry subkey.
•Close Registry Editor, and then restart the client computer.

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.

Solution: If the client still cannot connect to the terminal server, perform the following variation of this procedure:
1.Deactivate the license server.
2.Reactivate the license server by using the Telephone connection method in the Terminal Server License Server Wizard.
When you activate Terminal Server Licensing by using the Telephone option, Terminal Server Licensing uses a different certificate.
3.On each terminal server, create a backup of the registry, and then delete the Certificate, X509 Certificate, and X509 Certificate ID registry keys, as described in the preceding procedure.
4.Close Registry Editor, and then restart each terminal server.
5.On the client, create a backup of the MSLicensing registry key and its subkeys on the client, and then remove the original key and subkeys as described in the preceding procedure.
6.Close Registry Editor, and then restart the computer.
When the client is restarted, the missing registry key is rebuilt.

Cause: Windows XP-based clients might be attempting to connect to a Windows 2000-based Terminal Services server in a low-bandwidth network environment, in which client sessions are encrypted. In this case, IP packet fragmentation can cause encrypted frames that are sent by a client to be decrypted incorrectly.

Solution: Obtain the latest service pack for Windows 2000.
Cause: The Remote Desktop Protocol (RDP) encryption settings on the terminal server computer and the client might not be compatible. For example, the terminal server might be running 128-bit encryption with an encryption level set to High. When this occurs, "Event ID 50, Source: TermDD" appears in the system event log on the terminal server.Solution: Change the RDP encryption level on the terminal server to Medium or Low.

====================================================================

IF YOU ARE FACING USB UNRECONGNISED PROBLEM...FOLLOW THE STEPS:

This might be an issue with a corrupt or superfluous registry key. You might try the following before purchasing the new USB card. I’ll apologize in advance if the directions appear convoluted as there is no real easy way to describe this process, but rest assured I have
performed it many times with no I’ll effect.

1) Click Start >Run

2)Type “regedit” without the quotes and click the “Ok” button

3)Expand the “HKEY_Local_Machine” key (looks like a folder) by clicking
on the plus sign to the left of it

4) Expand the “System” subkey

5) Expand the “CurrentControlSet” subkey (There will be multiple keys,
but expand the one without any numbers”

6)xpand the “Enum” subkey

7)Expand the “USB” subkey a.The path displayed at the bottom of the
regedit window should look like this
“HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\”

8)here will be multiple subkeys beginning with “Vid_(numbers/letters)”.

a. Example key: Vid_045e&Pid_0039 (Parent key)

b. Example path:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\Vid_045e&Pid_00391
. Under each of these “Vid_” keys there will be multiple subkeys.

1. Example key: 5&2b9568f6&0&1 (child subkey)

2. Example path:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\Vid_045e&Pid_0039
\5&2b9568f6&0&1

1. You will have to navigate through (by highlighting, not expanding)
these subkeys while looking at the “DeviceDesc” field in the right hand
window.

2. When you locate a subkey with a “DeviceDesc” field that has IPAQ
(could be model number, but at any rate will contain you PDA’s device
description) take note of the parent “Vid_” key and proceed to step
1111) Right click on the parent “Vid_” key and click “export” in the
context menu

12) Save a file named regbackup(mm-dd-yyyy).reg to the
desktop a. This will backup the registry key should it be needed
again

13) Right click on the parent “Vid_” key a second time and click
“Permissions” in the context menu a. Select the “Everyone” group and
check the allow box for “Full control” and click ok

14) Right click on
the parent “Vid_” key a third time and click “Delete” in the context
menu

15) Reinstall usb device drivers once again when prompted

====================================================================================