These notes support a preliminary release of a software program that bears the project code name Whistler.

Information in this document, including URL and other Internet Web site references, is subject to change without notice and is provided for informational purposes only. The entire risk of the use or results of the use of this document remains with the user, and Microsoft Corporation makes no warranties, either express or implied. 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.

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.

Whistler Beta 2 is a time-limited release and will expire 180 days after initial installation is completed. Due to the nature of pre-release software, it is not recommended for production systems, and some of your applications and hardware might not function correctly. This product does not include an uninstall feature: therefore, we recommend that you back up your data before installing this release.

ã 2001 Microsoft Corporation. All rights reserved.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Contents

Welcome to the Beta 2 release notes for Microsoft Whistler Personal, Whistler Professional, Whistler Server, Whistler Advanced Server, Whistler Datacenter Server, Whistler Professional for Intel Itanium systems, Whistler Advanced Server for Intel Itanium systems, and Whistler Datacenter Server for Intel Itanium systems. This is a limited technical release that expires 180 days from the date of installation.

This document provides late-breaking or other information that supplements the Whistler documentation. In addition, there are several other release notes files on your Beta 2 compact disc (CD) that you should read:

The following list includes the policy settings in the System.adm file that use action lists.

Applies to users: administrators

Applies to users: administrators

Applies to users: administrators

Administrators need to remember that:

Applies to users: administrators

Applies to users: administrators

On computers running Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, Internet Explorer Maintenance displays a message when Resultant Set of Policy (RSoP), in logging mode, successfully reports the RSoP data. This issue will be addressed in a future release.

Applies to users: administrators

On computers running Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, Public Key Policies settings write data to registry keys. The data remains in the registry keys even if these policies are later removed.

Applies to users: administrators

On computers running Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, to force a refresh of Group Policy for either the user or the computer, use the new command line tool GPUpdate.exe. The RefrGp.exe tool used in Whistler Beta 1 is no longer available. Secedit.exe also cannot refresh all of Group Policy as it did in Windows 2000, but can still be used to refresh security policies. This issue will not be addressed in a future release.

Applies to users: administrators

The following issues apply to Resultant Set of Policy (RSoP).

Applies to users: administrators

On computers running Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, if you use Resultant Set of Policy (RSoP) in planning mode to analyze a user in a domain different from the domain you are in, RSoP does not function correctly. To work around this issue, select a Whistler domain controller in the user's domain to perform the simulation. This issue will be addressed in a future release.

Applies to users: administrators

On computers running Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, the Resultant Set of Policy Wizard uses your logon server by default to perform the RSoP planning mode simulation. In a mixed computing environment where both Windows 2000 and Whistler domain controllers exist, if your logon server is a Windows 2000 domain controller, the RSoP data is not generated and the simulations do not function correctly. To work around this issue, always ensure that you select a Whistler domain controller during the RSoP installation. This issue will be addressed in a future release.

Applies to users: administrators

On computers running Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, users cannot gain access to roaming user profiles located on Novell NetWare, or other non-Server Message Block (SMB) shares. Users with profiles stored on non-SMB shares will see the following message when logging on:

"Windows cannot locate the server copy of your roaming profile and is attempting to log you on with your local profile. Changes to the profile will not be copied to the server when you logoff. Possible causes of this error include network problems or insufficient security rights. If this problem persists, contact your network administrator. DETAIL - The network path was not found."

If the user previously logged onto this computer, Whistler loads the user’s locally cached profile. Users who have never logged on are issued a temporary profile. To work around this issue, relocate the user's profile to an SMB based-share and update the users' profile path in their user object. This issue will be addressed in a future release.

Applies to users: administrators

On computers running Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, you cannot change the system access control lists (SACLs) on WMI filters stored in Active Directory. The default SACLs on these objects allow only domain administrators to add or remove WMI filters from Active Directory.

This issue will be addressed in a future release.

Applies to users: administrators

Applies to users: administrators

Applies to users: administrators, developers, original equipment manufacturers (OEMs)

On computers running Whistler Advanced Server and Whistler Datacenter Server, Services for Macintosh (SFM) is not supported on a server cluster and might result in data loss. This is a result of the current implementation of Services for Macintosh, not the Cluster service.

Applies to users: administrators, developers, OEMs

Applies to scenarios: improving technology

On computers running Whistler Advanced Server or Whistler Datacenter Server, Terminal Server (also known as Terminal Services in application server mode) is no longer blocked on a server cluster. In Windows 2000, Terminal Server installation was blocked on a server cluster. Although Terminal Server can be deployed on a cluster (it can co-exist with Windows Clustering on a server), it does not fail over.

Applies to users: administrators, developers, OEMs

The following scenario is a known issue. Assume that you have DNS 1 and DNS 2 and both are domain controller integrated (and have latency in replicating changes). Node 1 forms a cluster and the cluster name is registered at DNS 1. Node 2 cannot join and verify the cluster name at DNS 2 unless DNS 1 replicated its changes to DNS 2. To work around thisissue, wait for replication to occur or manually perform the DNS replication.

Applies to users: administrators, OEMs

The Whistler Setup Wizard generates a message if a fully qualified domain name (FQDN) is entered for the computer name for computers running Whistler Advanced Server or Whistler Datacenter Server. If an FQDN is entered as the computer name when either forming or joining a cluster, the Setup Wizard generates a message stating that the name does not comply with DNS specifications. This issue will be addressed in a future release.

Applies to users: administrators, OEMs

If the incorrect IP address is entered during cluster setup on computers running Whistler Advanced Server or Whistler Datacenter Server, the cluster forms but the cluster IP resource is incorrectly labeled as "failed."

Applies to users: administrators, OEMs

On computers running Whistler Advanced Server or Whistler Datacenter Server, if you change the Cluster service account used to start Cluster service, you might not be able to evict a node from the cluster. It might display the following message: "Not enough storage is available to complete the operation." The Cluster service account must be a domain-level account that is a member of the local Administrators group.

Applies to users: administrators, OEMs

If you are running a cluster on Whistler Advanced Server or Whistler Datacenter Server configured with QLogic QLA2200 Fibre Channel adapter with driver version 7.4.8.0–8.0.0.3 through a Fibre Channel fabric Switch, you might encounter one of the issues.

To work around this issue, use the QLogic software to update the following QLogic BIOS settings to the following values on all cluster nodes:

Applies to users: administrators, OEMs

Applies to scenarios: improving technology

• user: Name@company.com
• password: Enter your password
• domain: Name@company.com

The Cluster Administrator does not provide a prompt for credentials when you are trying to create a cluster with insufficient privileges, which results in this message appearing.

To work around this issue, log on to the local node with a domain-level account that is a member of the local Administrators group. Add the node to the cluster again. This issue will be addressed in a future release.

Applies to users: administrators, OEMs

On computers running Whistler Advanced Server or Whistler Datacenter Server, Dynamic Host Configuration Protocol (DHCP) cluster resource or Windows Internet Name Service (WINS) cluster resource might not start or install because DHCP or WINS:

Only one instance of a DHCP resource and WINS resource is allowed per cluster. If the cluster resource has already been installed or started, you cannot install or start another instance of the resource. To work around this issue, delete the DHCP or WINS resource, and then recreate the resource. This issue will be addressed in a future release.

Network News Transfer Protocol (NNTP) and Simple Mail Transfer Protocol (SMTP) no longer provide cluster dynamic-link libraries (DLLs) in Whistler Advanced Server or Whistler Datacenter Server. This issue will not be addressed in a future release.

Applies to users: administrators, developers, OEMs

Applies to scenarios: improving technology

If you add a host to the Network Load Balancing cluster using Network Load Balancing Manager, you will not be able to immediately remove the new host from the cluster. This happens because the icon for the new host is displayed in Network Load Balancing Manager before Windows Management Instrumentation (WMI) has finished binding Network Load Balancing on the host and adding the cluster IP address to the host. To work around this issue, wait a few minutes before removing the host from the cluster. This issue will be addressed in a future release.

Applies to users: administrators

Applies to scenarios: improving user experience

On computers running Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, the following three-step scenario results in an issue with Network Load Balancing.

Applies to users: administrators, developers

Applies to scenarios: improving technology

On computers running Whistler Professional and Whistler Advanced Server, Message Queuing has multiple forest limitations. For example, if a user in Forest A logs on to a computer in Forest B, the user is required to specify the Directory Services server to install Message Queuing. All queries for queues issued by this user do not work correctly.

Applies to users: administrators, developers

Applies to scenarios: improving technology

Applies to users: administrators, developers

Applies to scenarios: improving technology

On computers running Whistler Professional or Whistler Advanced Server, Message Queuing supports sending messages to queues on the Internet and an intranet by introducing the following URL-style format name:

DIRECT=HTTP://sitename/msmq/queuename

This Message Queuing subcomponent installs Internet Information Services (IIS) and creates an IIS extension for Message Queuing, called MSMQ, during Setup. In this Beta 2 release, the SOAP_ENVELOPE and the COMPOUND_MESSAGE properties are not available for messages sent to local queues and the maximum size of a message sent using the new DIRECT=HTTP format name is limited to 2 MB. This issue will be addressed in a future release.

Applies to users: administrators, developers

Applies to scenarios: improving technology

On computers running Whistler Professional or Whistler Advanced Server, Message Queuing does not support the Internetwork Packet eXchange (IPX) network protocol.

Applies to users: administrators, developers

Applies to scenarios: improving technology

The following issues apply to computers running Whistler Professional or Whistler Advanced Server.

• Message Queuing is designed to support message delivery to Internet Protocol (IP) multicast groups using the Pragmatic General Multicast IP multicast protocol. In this Beta 2 release, messages sent to multicast addresses while the sending computer is off-line are lost. This issue will be addressed in a future release.
• When the multicast address for a public queue is sent from a computer other than the one hosting the queue, the queue might not start accepting the messages until after a sufficient delay for Active Directory replication (commonly about 15 minutes).

Applies to users: administrators, developers

Applies to scenarios: improving technology

Applies to users: administrators, developers

Applies to scenarios: improving technology

On computers configured as a dependent client running Whistler Professional or Whistler Advanced Server, Message Queuing does not support the new functionality in Whistler. Message Queuing functions with clients in MSMQ 1.0 and 2.0 domains where the Microsoft Message Queue Server is installed on a domain controller to provide directory service functionality. Message Queuing supports upgrades from previous versions of MSMQ independent clients, dependent clients, and routing servers.

Applies to users: administrators, developers

Applies to scenarios: improving technology

Applies to users: administrators, developers

Applies to scenarios: improving technology

The Message Queuing COM object model does not support multiple-element format name addressing through the MSMQQueueInfo.FormatName property. To utilize multiple-element format name addressing, use the new object MSMQDestination introduced in Whistler. To work around this issue, set MSMQDestination.FormatName to a multiple-element format name and pass the object to MSMQMessage.Send. You can optionally call MSMQDestination.Open before passing it to MSMQMessage.Send.

Applies to users: administrators, developers

Applies to scenarios: improving technology

Message Queuing introduces a new Active Directory object called a queue alias (CN=MSMQ-Custom-Recipient) that has a single Message Queuing queue format name attribute (MSMQ-RecipientFormatName). This object can act as a reference to any Message Queuing queue. This is particularly useful in allowing private queues and URL-named queues to be elements of a Message Queuing distribution list object.

Applies to users: administrators, developers

Applies to scenarios: improving technology

Message Queuing also supports sending messages to distribution lists (DL) hosted in Active Directory as objects in the group class. Usage and format are similar to that of Public Queues: DL=GUID.

Creating and managing a distribution group object in Active Directory is done by using the Active Directory Service Interfaces (ADSI) API or by using Active Directory Microsoft Management Console (MMC) snap-ins. Messages can also be sent to multiple destinations by constructing a quotation-mark-enclosed list of comma-delimited destinations in various formats, called a multiple-element format name, for the destination parameter when sending a message.

For example, a multiple-element format name containing a direct format name, a public format name, and a distribution list format name has the following form:

"DIRECT=OS:Computer\Queue,PUBLIC=GUID,DL=GUID"

Applies to users: administrators, developers

Applies to scenarios: improving technology

The following issues apply to Microsoft Distributed Transaction Coordinator (MS DTC).

Applies to users: administrators

On computers running Cluster services on Whistler Professional or Whistler Advanced Server, if MS DTC clients select the Use network name option in Cluster service for the client cluster resources, they might not be able to connect to MS DTC. To work around this issue, select the Network Client Access option.

Applies to users: administrators

On computers running Whistler Professional or Whistler Advanced Server, MS DTC does not support rolling upgrades on the Cluster services clusters.

Applies to users: administrators

On computers running Whistler Professional or Whistler Advanced Server, if you use an inactive node of a cluster, the Component Services administrative tool might not connect to the shared MS DTC instance. To work around this issue, select the Network Clients option in the MS DTC security configuration, and restart the node. This ensures that the system program is restarted.

Applies to users: administrators

On computers running Whistler Professional or Whistler Advanced Server, administrators cannot access the MS DTC property sheet by clicking Properties on the specific computers in the Component Services administrative tool. To work around this issue, administrators can configure MS DTC by clicking Configure Microsoft DTC. This issue will be addressed in a future release.

Applies to users: administrators

MS DTC does not support Microsoft Cluster Service clusters with a subset of member nodes that are domain controllers on computers running Whistler Professional or Whistler Advanced Server. Either all nodes in the cluster must be domain controllers or none of the nodes can be domain controllers.

Applies to users: administrators

On computers running Whistler Professional or Whistler Advanced Server, if you have a single-node cluster and the MS DTC log is on the local quorum disk, the MS DTC resource might not come online.

Or, delete the log file in the winnt\System32\MsDTC\Msdtc.log folder.

Applies to users: administrators

On computers running Whistler Professional or Whistler Advanced Server, by using MS DTC you can turn off certain features such as Transaction Internet Protocol (TIP), Extended Architecture (XA), Network Transactions, Network Administration, and Network Clients. This minimizes the security risks involved with running unused features that open network ports or load user DLLs. In addition, MS DTC was also modified from running under the LocalSystem account to running under the lower privileged Network Service account. This change lessens the potential for damage to the system if there is a security problem. By default, TIP, Network Administration and Network Clients are turned off on all installations. In addition, on domain controllers, XA and Network Transactions are also turned off. These features are important because the administrator needs to enable features before existing client software is supported.

Applies to users: administrators

nltest /sc_query:domain

Or, you can verify the trust from Windows 2000. Trusts from Window 2000 to Whistler verify correctly. This issue will be addressed in a future release.

Applies to users: administrators

On computers running Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, to convert a one-way forest trust to a two-way forest trust, first delete the existing one-way trust and then create the new two-way trust. If you use the New Trust Wizard to convert a one-way forest trust to a two-way forest trust without deleting the existing trust first, it creates an external trust instead. This issue will be addressed in a future release.

Applies to users: administrators

Applies to scenarios: improving user experience, improving technology

In Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, the default security descriptors of various objects are adjusted to strengthen Active Directory security. By default, domain controllers that are upgraded from Windows 2000 to Whistler do not receive these security enhancements, and the security descriptors of existing objects are not changed.

A script is supplied with Whistler to add these enhancements to existing domains and the forest. You MUST run this script if you wish to retain compatibility with services running on Windows 2000 or earlier systems. If you do not run this script, services on Windows 2000 or earlier systems that read data from the directory, such as Remote Access and Terminal Server, might fail to authenticate properly. This script must be run immediately after introducing the first Whistler domain controller into an existing Windows 2000 domain.

Note that a Whistler domain controller can be added to an existing forest by upgrading a Windows 2000 domain controller to Whistler or by promoting a Whistler server to the domain controller role. The script is located in the \support\tools\UpgradeACL folder. For details about the changes the script makes and directions for running the script, see the UpgradeACLReadme.txt file in the \support\tools\UpgradeACL folder. This issue will be addressed in a future release.

Applies to users: administrators

On computers running Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, when using Create Replica From Media to promote a replica domain controller, you should restore a backup copy of the system state data of an existing domain controller.

A user can restore a System State backup to an alternate location by using Ntbackup.exe. An alternate location is a user-specified folder where the data will be restored with its original directory structure in place. These restored backup files must be present on a local drive of the computer that will be promoted using Create Replica From Media.

Due to an issue in Beta 2 with restoring large system state files, it is not possible to restore an Active Directory backup that is over 40 GB in size to a mapped drive on a remote computer. To work around this issue, copy the backup file to the computer to be promoted and restore it locally on that computer. If the backup is on tape, either restore it directly to the computer to be promoted or restore it to a different computer and copy it to the computer to be promoted. This issue will be addressed in a future release.

Applies to users: administrators

A change in the domain controller computer name might cause failure to bind to any domain controller in the same domain. Change in the global catalog computer name might cause failure to bind to any domain controller in the same forest. The type of workaround that you choose depends on whether a domain controller exists in the same site where the renamed domain controller resides.

Applies to scenarios: improving user experience

Applies to users: administrators, OEMs

Applies to scenarios: improving user experience

On computers running Whistler Server, Network News Transfer Protocol (NNTP) does not function when used with the default settings. To work around this issue, give the Everyone group write permissions for the Inetpub\Nntpfile directory. This problem will be addressed in a future release.

Applies to users: administrators

On computers running Whistler Server or Whistler Advanced Server, system resources become depleted when the World Wide Web service is started on systems with greater than 3800 sites.

To work around this issue, control system resources by setting the following registry parameter:

Setting this key overwrites the internally set default value. LogBufferSize is a REG_DWORD type, and the values are in bytes.

You can also increase paged pool memory for the kernel by using the following registry key:

Set PagedPoolSize to -1 (0xFFFFFFFF), which is the maximum possible paged pool for the kernel memory.

This issue will be addressed in a future release.

Applies to users: administrators

Applies to scenarios: improving user experience

On computers running Whistler Personal, Whistler Professional, Whistler Server, or Whistler Advanced Server, when using the German language version of certification authority and proxy Web pages, the user is requested to download and register the Xenroll.dll ActiveXâ control every time the user visits the Web page because the control is not correctly registered. This issue will be addressed in a future release.

Applies to users: administrators

Applies to users: administrators

On all versions of Whistler, there is a known issue in the Whistler Beta 2 release because the MMC 2.0 class ID is not set correctly in the registry. The registry key

For example, the workaround for VBScript is:

Set objMMC = WScript.CreateObject("MMC20.Application.1")

For example, the workaround for Visual Basic is:

Set objMMC = CreateObject("MMC20.Application.1")

This issue will be addressed in a future release.

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.

Applies to users: administrators, developers

Applies to scenarios: improving user experience

On computers running Whistler Personal, Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, new Connection Manager client features include the following:

Applies to users: administrators

Applies to scenarios: improving user experience

On computers running Whistler Personal, Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, new Connection Manager Administration Kit (CMAK) features include the following:

• The Connection Manager client features listed above are not available for clients running Windows 2000.
• Users logging on to a Windows operating system with a Connection Manager profile might encounter problems authenticating the connection. To work around this issue, users should retype their password information.
• Users might experience a temporary delay when they open the Properties dialog box of a Connection Manager profile. To work around this issue, administrators should set the HideICSTab key to 1 in the .cms file of the profile.
• Some Connection Manager profiles might not be fully compatible with Internet Connection Sharing or Internet Connection Firewall. Users might encounter unexpected results if they choose to designate a Connection Manager profile as a shared connection.

These issues will be addressed in a future release.

Applies to users: administrators

Applies to scenarios: improving user experience

The dial-up properties of the user account contain the following:

The caller ID, callback options, static IP address, and static routes properties are designed for a dial-up client dialing into a network access server (NAS).

To turn on the processing of the dial-up properties of the user account, set the Ignore-User-Dialin-Properties attribute at its default value, which is 0. For example, for the remote access policy that is designed for dial-up connections, no additional configuration is needed.

To turn off the processing of the dial-up properties of the user account, set the Ignore-User-Dialin-Properties attribute to the value of 1. For example, for the remote access policy that is designed for wireless or authenticating switch connections, set the value of the Ignore-User-Dialin-Properties attribute to 1.

When the dial-up properties of the user account are ignored, remote access permission is determined by the remote access permission setting of the remote access policy. These issues will be addressed in a future release.

Applies to users: administrators

Applies to users: administrators

Applies to users: administrators

The Windows 2000 tool Ipsecpol.exe does not function on any version of Whistler. Ipseccmd.exe replaces Ipsecpol.exe in Whistler. This issue will be addressed in a future release.

Applies to users: administrators

On computers running Whistler Personal, Whistler Professional, or Whistler Server, the following network and communications issues involve Internet Protocol (IP) telephony and Telephony Application Programming Interface (TAPI). These issues will be addressed in a future release.

By using Phone Dialer

1. On the Start menu, point to Programs, point to Accessories, point to Communications, and then click Phone Dialer.
2. On the Edit menu, click Options.
3. On the Audio/Video tab, clear the Enable acoustic echo cancellation check box.

By using the Tuning Wizard

1. Right-click Start, and then click Explore.
2. In Microsoft Windows Explorer, click the Program Files folder, and then click the Windows NT folder.
3. Double-click Rtcclnt.exe to open Phoenix.
4. On the Tools menu, click Tuning Wizard. Follow the instructions that appear.
5. Select the I am using a headset check box.

• You cannot install Dialogic boards on computers running Whistler Beta 1 or Whistler Beta 2. To work around this issue, install Dialogic (DNA 3.x) boards on a computer running Windows 2000, and then upgrade to Whistler Beta 1 or Whistler Beta 2.
• If the computer name is changed after publishing the Tapisrv.exe, which is a service process for telephony service providers, you will not be able to run Tapisrv.exe on this computer.
• Whistler TAPI and real-time communications clients were tested and are known to work with the following video cameras:

• Intel PC Camera Pack USB
• Intel PC Camera Pro Pack USB
• Intel Create and Share Camera Pack USB 2.0
• Philips PCA645VC PC Camera VGA USB with Video Creator SW
• Philips Vesta Pro SuperVGA USB PC Camera
• Philips PCA646VC USB PC Camera
• Intel Create and Share Camera Pack USB 1.0

Applies to scenarios: improving user experience

Applies to users: developers, OEMs

Applies to scenarios: improving technology

Support for the following networking protocols has been removed from all versions of Whistler. This issue will not be addressed in a future release.

http://www.microsoft.com/hiserver/

Applies to scenarios: improving technology

On computers running Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, turning on the group policies that prohibit Windows 2000 group policies for administrators results in undefined behavior. These policies do not work correctly and administrators still have all privileges with regards to the connections folder and other entities managed by the Network Configuration Group Policy engine. This affects all user policies for administrators when the policy called Enable Windows 2000 policies for administrators is turned on. Computer policies (ICF, Bridge and Shared Access UI) will still work correctly. This issue will be addressed in a future release.

Applies to users: administrators

Applies to scenarios: improving user experience, improving technology

Applies to scenarios: improving user experience

Whistler Personal, Whistler Professional, Whistler Server, Whistler Advanced Server, and Whistler Datacenter Server Beta 2 versions include new Routing and Remote Access service and virtual private network (VPN) client features, as detailed below:

Applies to users: administrators

Applies to scenarios: improving user experience

All Beta 2 versions of Whistler include new Routing and Remote Access service and virtual private network server features.

• The routing interface that sends packets in IP tunneled mode (IP-in-IP interface) is no longer supported.

This issue will be addressed in a future release.

Applies to users: administrators

Applies to scenarios: improving user experience

Guest

In the Password box, do not make any entries. This issue will be addressed in a future release.

Applies to users: administrators

Applies to scenarios: improving user experience

On a computer running Whistler Personal, when sending a data packet on a token ring adapter, there might be a loss of functionality because the data packet could contain a variable length MAC header. This bug check will be in Generic Packet Classifier (GPC) caused by QoS Packet Scheduler or in the Packet Scheduler itself. To work around this issue, restart your computer and uninstall the QoS Packet Scheduler driver. This issue will be addressed in a future release.

Once these steps are completed, you can upgrade to Whistler.

Applies to scenarios: improving user experience

The following sections address issues for Remote Installation Services (RIS).

The following issues apply to using the RIPrep.exe tool with Remote Installation Services (RIS).

Applies to users: administrators, OEMs

Applies to users: administrators, OEMs

Applies to users: administrators, OEMs

Applies to users: administrators

On computers running Whistler Server or Whistler Advanced Server, a Certificate Manager allowed to manage a group (issue and revoke certificates for that group) cannot manage a user within that group. To work around this issue, add the Certificate Manager user account to the Pre-Windows 2000 Compatible Access group in the domain of the group being managed. This issue will be addressed in a future release.

Applies to users: administrators

Applies to users: administrators

On computers running Whistler Server or Whistler Advanced Server, Certrqxt.asp currently does not display any certificate templates that are a CROSS_CA type. This is a new certificate type in addition to MACHINE and USER. Therefore, cross-certificates cannot be issued through the Web enrollment pages in Whistler Beta 2.

To work around this issue, cross-certificates can still be issued by using the command line tool Certreq.exe. This issue will be addressed in a future release.

Applies to users: administrators

On computers running Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, a Netscape 4.76 client enrolling to a Microsoft Enterprise certification authority (CA) fails and the message "Request Status Code: 0x80094805 (-2146875387) -- The request is missing a required SMIME capabilities extension. Request Disposition: 0x1f (31) -- Denied Request Disposition Message: Denied by Policy Module" appears. This issue will be addressed in a future release.

Applies to users: administrators

On computers running Whistler Professional, Whistler Server, or Whistler Advanced Server, Web enrollment to a cross-certified root CA with the Enable user root store Group Policy object turned off causes the Web enrollment client to fail while downloading the root certificate. Although a message to the contrary does appear, the certificate was issued successfully and the message can be ignored. This issue will be addressed in a future release.

Applies to users: administrators

A Whistler Server or Whistler Advanced Server Enterprise certification authority (CA) in a Windows 2000 domain issues certificates with a blank subject name or fails to issue certificates from version 2 templates. To work around this issue, upgrade the schema of the forest to a Whistler schema. This issue will be addressed in a future release.

Applies to users: administrators

On computers running Whistler Server or Whistler Advanced Server, when you configure a Web proxy to a stand-alone certification authority and both computers are not in a Windows 2000 or Whistler domain, certificate requests do not function correctly. The message "Access Denied" also appears. This issue will be addressed in a future release.

Applies to users: administrators

On computers running Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, domain tree depth is limited for logging onto a network between forests when using Kerberos V5 authentication. The server can be located in the first (root), second, or third level of the domain tree in the trusted forest. The client must be located in the first or second level of the domain tree in the trusting forest. If the client's domain is any lower in the tree, Kerberos V5 authentication to a server in a trusted forest fails. NTLM is not affected. Thus, deeper domain trees can be used with applications that request authentication protocol negotiation because they will roll back to NTLM.

Applies to users: administrators

Applies to scenarios: improving user experience

On all versions of Whistler, to enable monitoring of Microsoft's internal smart card testing, code has been added to Winlogon to record smart card usage. When configured and able to connect to the appropriate database, the monitoring code writes information to a SQL server such as: successfully logging on with a smart card, failure while logging on with a smart card, error code on failure, computer name, smart card reader type, and smart card type. Monitoring is switched off by default. A key exists to switch on logging; it is switched off by default. Microsoft is investigating ways of making the schema available to enterprises planning on deploying smart cards. The value used to switch on monitoring is:

This value is of type REG_DWORD. The default value is 0 (0 = disabled, 1 = enabled).

Applies to users: administrators

Applies to scenarios: improving user experience

On all versions of Whistler, certificate auto renewal fails for smart card certificates on Gemplus smart cards when the card has been used to log on to the session where renewal is initiated. This issue will be addressed in a future release.

Applies to users: administrators

Applies to scenarios: improving user experience, improving technology

When enrolling users for logging on using a smart card by using the Smart Card Enrollment Station or the Certificates MMC snap-in on all versions of Whistler, you cannot use the smart card enrolled for logging on from a Windows 2000 computer. If you want to use the smart card to log on from a Windows 2000 computer, the enrollment should take place from a Windows 2000 computer. You can use the smart card enrolled in this way to log on from a Windows 2000 or Whistler computer.

Applies to users: administrators

Applies to scenarios: improving user experience, improving technology

Or, ensure that your users are aware that Terminal Server requires the user to press CTRL+ALT+END (instead of CTRL+ALT+DEL) to open the password dialog box.

Applies to users: administrators, OEMs

Applies to scenarios: improving user experience, improving technology

To turn it back on, you need to set the following registry value:

There are certain scalability limitations for Whistler Beta 2 that were fixed after the feature was developed. These changes could cause problems in certain stress conditions. You should turn on this feature only on Terminal Server to test the usability of the smart card logon feature. This issue will be addressed in a future release.

Applies to users: administrators, OEMs

Applies to scenarios: improving user experience, improving technology

Applies to scenarios: improving user experience

Applies to scenarios: improving user experience

On computers running Whistler Personal, Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, some AMD Duron processors are reported incorrectly by the System Properties dialog box as Athlon processors. This information is being reported directly as a text string from the AMD processor and is not the result of a problem with the Whistler operating system.

Applies to users: OEMs

Applies to scenarios: improving user experience

On computers running Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, the following are guidelines for using the Windows Management Instrumentation (WMI) command line tool.

• To start the application tool, at the command prompt, type

wmic

Or, in Windows Explorer, double-click Wmic.exe.

• For help and support, at the WMIC wmic:root\cli> prompt, type

alias name /? or switch name /?

• For list of the syntax and available aliases, at the WMIC wmic:root\cli> prompt, type

/?

• For options available for the Process alias, at the WMIC wmic:root\cli> prompt, type

process /?

• For running a specific command, at the WMIC wmic:root\cli> prompt, type

alias name or switch name

• For help, at the command prompt, type

wmic /?

• For a brief list of processes running on the current computers (nodes), at the command prompt, type

wmic process list brief

Applies to users: administrators, developers, OEMs

Applies to scenarios: improving user experience

These issues will not be addressed in a future release.

Applies to users: developers, OEMs

Applies to scenarios: improving technology

If you upgrade your computer from Windows 95, Windows 98, Windows 98 Special Edition, or Windows Millennium Edition to Whistler Personal or Whistler Professional and apply special user security to the WMI namespaces, the namespaces are removed and replaced with system defaults. To work around this issue, add the WMI namespaces by adding the WMI Control snap-in to MMC. This issue will be addressed in a future release.

Applies to scenarios: improving user experience

On computers running Whistler Personal, Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, when an application running at the identity level of impersonation creates a subscription using IWbemServices::ExecNotificationQuery/Async for events generated by a decoupled provider, the first notification query does not function correctly. The message "Access denied" appears unless a permanent subscription for the same event is already registered. The second notification query succeeds and functions correctly.

Applies to users: administrators, developers, OEMs

On computers running Whistler Personal, Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, the following issues pertain to provider hosting and provider security.

For provider hosting, in Windows 2000 and Whistler Beta 1, all providers are loaded in-process to Windows Management service, which runs under the LocalSystem account. In Whistler Beta 2, the providers load into a provider subsystem. In general, hosting providers out-of-process guarantees that a faulting provider affects only the providers in the same host and hosting providers out-of-process cannot end the critical Windows Management process. The provider host's lifecycle is fully controlled by Windows Management. The latter automatically restarts the host if it exits for any reason. This effort increases WMI robustness and reliability for applications that rely on the key services that WMI provides.

For provider security, providers should use the NetworkService security account. This account is intended for services that have no need for extensive privileges, but have the need to remotely communicate with other systems. Using this account eliminates the potential risk that a corrupted or compromised provider could remove the entire computer (or domain, in the case of a domain controller). It also ensures that no privileged information is revealed to a user in case the provider does not correctly impersonate the client's context.

Event providers do not perform operations on behalf of individual subscribers; instead, event providers listen for occurrences or changes in event provider data sources and then start events. This means that event providers access their event sources while not impersonating anyone (they rely on the internal event system to perform the appropriate access checks before firing events).

Given these security requirements in Whistler, if you load any instance, class, or method provider into LocalSystemHost (by default or by explicitly setting the hosting mode) the subsystem generates a warning entry in the NTEventLog indicating that this might pose a security risk in the enterprise.

These issues will not be addressed in a future release.

Applies to users: administrators, OEMs

Applies to scenarios: improving technology

On computers running Whistler Personal, Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, WMI has tightened security for remote client connection to WMI as part of improving the security and performance for Whistler.

For example, in Whistler, WMI runs Svchost.exe, which requires higher security access to connect to WMI (RPC_C_AUTHN_LEVEL_PACKET). Specific remote access scenarios where programs are affected are as follows:

• Programs deployed on Windows 2000 and Whistler can use RPC_C_AUTHN_LEVEL_DEFAULT instead of CONNECT.
• Programs deployed on a broad range of operating systems (for example, Windows 95, Windows 98, Windows Millennium Edition, Windows NT 4.0, Windows 2000, and Whistler operating systems) that require remote access to Whistler can use CoQueryProxyBlanket(). Return DCOM security settings and use these parameters to set the security on the proxy using CoSetProxyBlanket().

These issues will not be addressed in a future release.

Applies to users: developers

Applies to scenarios: improving technology

On computers running Whistler Personal, Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, the Windows Management Instrumentation (WMI) property Win32_Processor.CurrentClockSpeed (and therefore user interface components that make use of it such as the Computer System Properties dialog box) reports incorrect values on Intel Itanium processors. This issue is caused by a problem in a kernel API where the information is being retrieved. This issue will be addressed in the future release.

Applies to users: administrators, OEMs

Applies to scenarios: improving user experience

On computers running Whistler Personal, Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, the system clock class is defined as:

<class Win32_CurrentTime { uint32 Year; uint32 Month; uint32 Day; uint32 DayOfWeek; uint32 WeekInMonth; uint32 Quarter; uint32 Hour; uint32 Minute; uint32 Second; [key] sint32 UTCOffset; };>

Currently, we can form queries for a specific point in time in the future. The basic form of a query is:

<select * from __InstanceModificationEvent>

where:

This query specifies a single point in time, irrespective of the time at which it is to be evaluated, at which an event should be generated. If the time specified is in the past at the time it is evaluated, then no event occurs. Queries are coded assuming universal time (UTC). All times returned in the __InstanceModificationEvent object represent the current system time in UTC at the time the event was generated.

The fundamental unit of time recognized by the time provider is seconds. This means, for example, if a query omits the seconds field, then when all supplied parameters (year, month, day, and so on) match the current time, an event will be generated every second that the current time matches the query. The same is true for minutes, hours, and so on. The field UTCOffset is not recognized for event queries. The event queries must be defined in Greenwich mean time (GMT). For instance queries, it represents the time zone offset from UTC time with UTC time itself in time zone UTCOffset = 0. For instance queries there exists one Win32_CurrentTime object for each time zone -12 far west to far east +13. Thus, a total of 26 instances exist. When queried, each instance represents current system time adjusted for that time zone.

The following issues will be addressed in a future release.

In order to be valid, a query must have each of the following properties:

These issues will be addressed in a future release.

Applies to users: administrators, developers, OEMs

On computers running Whistler Personal, Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, the WMI method Win32_Process.Create() might not function correctly due to a problem in the COM layer. This issue will be addressed in the next release.

Applies to users: developers

Applies to scenarios: improving technology

When upgrading your domain controller from Windows 2000 to Whistler Personal, Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, the first Windows Management Instrumentation Filter user interface is started. Attempts to save the WMI filter do not function correctly unless the user currently logged onto the computer has domain administrator privileges. The reason for this loss of functionality is that the Active Directory container required to store this WMI filter has not been created automatically during the upgrade.

To work around this issue, contact your local domain administrator to save the first WMI filter, which creates the container. This issue will not be encountered on a clean installation of Whistler.

Applies to users: administrators

Applies to scenarios: improving user experience

On computers running Whistler Personal, Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, the following storage issues apply to Removable Storage. These issues will be addressed in a future release.

Applies to scenarios: improving user experience

On computers running any version of Whistler, if a message appears and is confusing, too complex, or unreadable, please report your comments to the Windows Beta Web site at:

You should report your comments immediately to ensure your comments are received in a timely manner.

Applies to scenarios: improving user experience

On all versions of Whistler, error reporting does not receive notification when a system stops responding until Savedump.exe completes. If an administrator logs in before Savedump.exe completes, the administrator does not receive the option to report the error to Microsoft. To workaround this issue, log off from the administrator account and log in as an administrator again after Savedump.exe has completed. Use Windows Task Manager to determine when Savedump.exe has completed. This issue will be addressed in the next release.

Applies to users: administrators, OEMs

Applies to scenarios: improving user experience

The following Remote Assistance issues apply to Whistler Personal, Whistler Professional, Whistler Server, Whistler Advanced Server, and Whistler Datacenter Server.

For the Whistler Beta 2 release, users must have Microsoft Outlookâ Express installed on Itanium-based computers in order to use Remote Assistance. MSNâ Instant Messenger-based Remote Assistance is not supported. This issue will be addressed in a future release.

Applies to users: administrators

Applies to scenarios: improving user experience

When the expert controls the computer requesting assistance, the user can press ESC at any time to stop the expert control due to privacy or security reason. Because of strong security, any key combination which includes the ESC key sequence stops the expert control. This includes keys such as ALT+INS, which the system translates to CTRL+ESC. However, the expert can prompt to re-establish control immediately.

Applies to users: administrators

Applies to scenarios: improving user experience

When a request for Remote Assistance is sent, it contains the IP address of the computer making the request. This allows the expert's computer to connect back to the caller. If the IP address of the requesting computer is changed (such as by logging out and logging back in a dial-up account or by DHCP), then the expert's computer cannot make a connection since it only has the old IP address. This is mainly an issue when an e-mail for assistance is sent and the computer changes its IP address before the expert responds. If possible, the computer requesting assistance should try to keep the same IP address (for example, by not restarting) until the connection is made. If an IP address change is unavoidable, then simply cancel and resend the assistance request. You can do this easily by selecting the View Invitation Status link. Select the request that you'd like to resend, and then click the Resend button. This will send the expert a refreshed request with the new IP address.

Applies to users: administrators

Applies to scenarios: improving user experience

If the computer requesting or providing Remote Assistance is behind a firewall or network address translation (NAT) (not directly on the Internet), there might be issues with establishing connections. However, if the helper or expert and the person requesting assistance are in the same local network, then direct connections are supported.

Opening the RDP Port

For security reasons, firewalls might not allow inbound or outbound connections for Terminal Services (Remote Desktop Protocol on Port 3389). To work through a firewall, the network administrator can choose to open Port 3389 and allow Remote Assistance and Terminal Services over their firewall.

Using VPN to Assist

Alternately, the administrator can give the helper or expert outside the firewall a VPN logon account to gain access to the intranet. This is the recommended solution for managed intranets where some support services are outsourced to engineers who are outside the network. Once the engineer logs in on the VPN account, the engineer become part of the managed network and can directly provide Remote Assistance to computers on the intranet. VPN has the added advantage of providing more security, policy based privileges and auditing support.

Whistler Internet Connection Sharing

For the Whistler Beta 2 release, Internet Connection Sharing (ICS) works transparently for Remote Assistance. If your ICS server (host) computer uses Whistler or Windows Millennium Edition, then all operations should succeed without further configuration. If the ICS host computer uses other operating systems, or if a broadband connection is used that has more than one network connection, then any computer behind such a system can offer Remote Assistance, but cannot receive it.

Applies to users: administrators

Applies to scenarios: improving user experience

Remote Assistance connections need to transfer large amounts of screen information. LAN and DSL are ideal for fast screen transfer. For slower connections, such as dial-up modems, to improve the Remote Assistance experience, the following optimizations are strongly recommended on the computer of the person being assisted:

• Switch the Wallpaper off during assistance (required in dial-up; recommended for broadband).
• If connection is still slow, switch the display temporarily to use 256 colors (recommended for dial-up).
• If using 256 colors you can also switch the theme from "Whistler" to "Windows Classic."
• Finally, using a smaller display resolution (800x600) will also improve performance (optional).

Remote Assistance will automatically try to optimize your display settings during the session. The wallpaper will be turned off and 256 colors will be used for fastest performance. Settings will be restored once the session is disconnected.

Applies to users: administrators

Applies to scenarios: improving user experience

For computers requesting assistance that have multiple IP addresses, the helper's computer tries to call back to each reported IP until one succeeds or all fail.

For example, if you use a dial-up connection to connect to the Internet and then use VPN to connect to your computer, your computer has two IP addresses—one from the ISP and one on the LAN. When you request assistance, your request will carry both IP addresses (ISP address and LAN address).

If your helper or expert is on the LAN that you currently connected to by VPN, the helper can connect to your computer through the LAN. However, your helper might not receive a response from your computer because your Internet IP address (ISP provided) is temporarily inaccessible to all connections while you are on the LAN and using the VPN. If you disconnect from the VPN, your Internet address starts to respond to connections and the helper outside the LAN can connect to you.

Applies to users: administrators

Applies to scenarios: improving user experience

In order to offer Remote Assistance, the expert should have administrator privileges on the user's computer. Remote Assistance can be offered to users with computers running Whistler Professional, Whistler Server, Whistler Advance Server, and Whistler Datacenter Server. For information about how experts can offer Remote Assistance from a Whistler Professional computer, see Whistler Help and Support Services.

Applies to users: administrators

Applies to scenarios: improving user experience

If you need assistance, you can request Remote Assistance from multiple people. Any or all of them can help you, but you can connect to only one person at a time. Simultaneous connections from multiple helpers to a single user session are not supported.

If you are providing assistance, please help one person at a time. Supporting multiple people from the same session is not supported.

However, if several different users are using multiple Terminal Services sessions on one computer, then each user can be helped by a different expert simultaneously.

Applies to users: administrators

Applies to scenarios: improving user experience

To use Remote Assistance through e-mail, you need a client that supports the Simple Messaging Application Programming Interface (SMAPI). Outlook, Outlook Express, and many other popular e-mail programs are supported. However, if your default e-mail client does not support simple MAPI, Remote Assistance attempts to use Outlook Express and MSN Hotmailâ to send your invitation. To use other e-mail clients such as AOL first, save the invitation ticket to a local folder and then send it as an attachment in your preferred e-mail.

Applies to users: administrators

Applies to scenarios: improving user experience

Applies to users: administrators

Applies to scenarios: improving user experience

Applies to scenarios: improving technology, improving user experience

On computers running Whistler Personal, Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, over a slow link (for example, a 56 Kbps dial-up connection), Remote Desktop performance is slower than normal with the default Remote Desktop settings.

One possible workaround for this issue is to turn off the wallpaper on the Remote Desktop server computer. However, the user might wish to turn on the wallpaper while using the computer and turn off the wallpaper while working remotely over a slow link.

A better workaround for this issue is to change the color depth for the Remote Desktop connection to 256 colors by using the Terminal Services Client. This automatically turns off the wallpaper as well as causes the shell to change to the Windows Classic desktop theme for the duration of the remote connection. When the user logs back in directly to the console, the theme returns to the Whistler default theme.

Applies to users: administrators

Applies to scenarios: improving user experience

On computers running Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, you cannot control the operating system volume level using a Terminal Services session. The sound can be turned off completely, but the volume level control does not function. Applications with their own volume level control are not affected (For example, Sonique, WinAmp, Windows Mediaä  Player, and so on). This issue will be addressed in a future release.

Applies to users: administrators

Applies to scenarios: improving technology, improving user experience

The element name associated with these elements is also unavailable. This is done by design because removing the wallpaper and background improves network performance. This issue will be addressed in a future release.

Applies to scenarios: improving user experience

On computers running Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, the Web Client expiration date is January 15, 2002. The client does not function after the expiration date. This issue will be addressed in a future release.

Applies to users: administrators, developers, OEMs

Applies to scenarios: improving technology, improving user experience

Speech functionality in Office XP returns. However, all profile and training data accumulated on Windows 98 or Windows Millennium Edition is lost. This issue will be addressed in a future release.

Applies to scenarios: improving user experience

There is a known issue between the Whistler CD recording program and the Adaptec DirectCD recording program. If you run both programs on a computer running Whistler Personal or Whistler Professional, one of the programs might not function correctly.

Or, open the Properties dialog box, click the Recording tab, and then turn off the Whistler CD recording program. The Adaptec DirectCD recording program might then start functioning correctly as a result.

This issue will be addressed in a future release.

Applies to scenarios: improving user technology

On computers running Whistler Personal or Whistler Professional, you cannot install Adobe Postscript printer drivers. A message box titled "setup.exe - Entry Point Not Found" appears and the following message is displayed "The procedure entry point SUnMapLS_IP_EBP_32 could not be located in the dynamic link library KERNEL32.dll." There is no known workaround at this time. This issue will not be addressed in future release.

Applies to scenarios: improving user experience

On computers running Whistler Personal, Whistler Professional, or Whistler Advanced Server, users might experience problems using Adobe Photoshop 5.5 if the computer has an Intel Pentium 3 microprocessor. While using Photoshop 5.5 or 6.0, the system stops responding.

The electrical problem on the affected motherboards is triggered by computer operations that use the pathway (called a bus) between the processor and the random access memory (RAM) for an extended number of microseconds. The operating system or other programs can cause this problem; however, it often appears when using Photoshop because few other programs move memory as rapidly as Photoshop does.

Some Photoshop extensions optimize the way Photoshop moves data. Although removing or disabling these extensions can reduce the problem in some computers, this workaround is temporary because it slows the processing speed of Photoshop.

This issue occurs with Dell Optiplex GX1 computers and ASUS P2B-F and P3B-F motherboards and might also occur with other motherboards.

Note   If your computer is manufactured by Dell Computer Corporation, the computer might return the error, "Alert: Regulator Error."

There are three possible workarounds for this issue:

By using My Computer, move the MMXCore.8bx and FastCore.8bx files from the Program Files\Photoshop 5.5\Plug-Ins\Adobe Photoshop Only\Extensions folder to a location outside of the Adobe folder (for example, move them to the desktop).

Restart Photoshop.

Note   Perform this procedure if the computer has multiple processors. The MMXCore and FastCore plug-ins optimize data movement by Photoshop. After you move the extensions, Photoshop 5.5 performance slows noticeably.

Applies to scenarios: improving user experience

On computers running Whistler Personal, Whistler Professional, or Whistler Advanced Server, only antivirus programs written for the specific operating system run correctly. Antivirus drivers not written to run on the specific Whistler operating system might cause problems. Other issues might include a lack of real-time scanning for viruses or system vulnerability to virus attack. These problems range in severity from recoverable errors to loss of some or all of the data, to the computer becoming unusable. There is no workaround for this. This issue will not be addressed in future release.

Applies to users: administrators, developers, OEMs

Applies to scenarios: improving user experience

Applies to scenarios: improving user experience

Applies to scenarios: improving user experience

Citrix MetaFrame 1.8 is not supported on Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server. This issue will not be addressed in a future release. For support information, see the Citrix Web site at:

Web addresses can change, so you might not be able to connect to the Web site or sites mentioned here.

Applies to scenarios: improving user experience

Applies to scenarios: improving user experience

On computers running Whistler Personal or Whistler Professional, the following issue applies to Delphi 1.0

• On the Help menu, when you click Interactive Tutors, the following message appears:

"X Interactive Tutors are not available on systems running Windows NT."

After you click OK, the following messages appear:

"Application Error"

"Exception EUnhandledException in module TOOLHELP.DLL at 0001:0e2f."

"TOOLHELP.DLL caused a General protection fault at 0001:0e2f."

"Shutdown of Delphi is recommended."

The program closes. Restart the program. These messages will not appear again. This issue will not be addressed in a future release.

• After an upgrade from Windows 98 Special Edition to Whistler Personal or Whistler Professional, Delphi 1.0 does not start. To work around this issue, reinstall Delphi 1.0. This issue will not be addressed in a future release.

Applies to scenarios: improving user experience

Applies to scenarios: improving user experience

Applies to scenarios: improving user experience

"flpsetup"

"Unable to copy files from c:\Program Files\VisionLab\FaxLink\Fmfaxdrv.nt4 to"

"C:\WINNT\System32\Spool\DRIVERS\W32X86\Fmfaxdrv.dll due to system error 2."

These messages are followed by seven identical errors involving different file names, and then the following message appears:

"flpsetup"

"Setup failed - Unable to add monitor due to system error 126."

Applies to scenarios: improving user experience

Applies to scenarios: improving user experience

Applies to scenarios: improving user experience

Applies to scenarios: improving user experience

Applies to scenarios: improving user experience

The following issues apply to HostExplorer 6.2:

• After you upgrade from Windows 98 Second Edition to Whistler Personal or Whistler Professional, the Inetd configuration file cannot be saved. If you start Inetd Configuration by double-clicking the icon in the notification area, and then clicking Save or Reload, the following messages appear:

"INETD Error"

"Error opening configuration file"

To work around this issue, reinstall the program after the upgrade and ensure that only one Inetd.ini file created for Whistler Professional is on your system. It should be in the C:\Winsys32\Hummbird folder. When saved with the Control Panel extension tool supplied by the vendor during Setup and started from the notification area, the HostExplorer functions properly. You should delete any other copies of this file.

Applies to scenarios: improving user experience

After upgrading a IBM ThinkPad to Whistler Personal or Whistler Professional, the Battery Maximizer Gauge might impede performance of the Start menu and taskbar. This is currently under investigation and can be temporarily resolved by removing the following registry entry:

Applies to users: OEMs

Applies to scenarios: improving user experience

Applies to scenarios: improving user experience

On computers running Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, there is a new Group Policy setting called Disallow installation of printers using Kernel Mode drivers. This setting prevents the installation of printers using kernel-mode drivers and is located in the details pane under Computer Configuration/Administrative Templates/Printers. By default, the state of this Group Policy setting is Not configured. This prevents the installation of programs such as Lotus Millennium 9.5 Net-it Now Printer.

Applies to scenarios: improving user experience

Applies to scenarios: improving user experience

Applies to scenarios: improving user experience

Applies to scenarios: improving user experience

On computers running Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, when you attempt to create an Adobe Acrobat document in Lotus SmartSuite 9.5, an access violation might occur. To work around this issue, you must install Adobe Acrobat and not just Adobe Acrobat Reader. This issue will not be addressed in a future release

Applies to scenarios: improving user experience

Applies to scenarios: improving user experience

Applies to scenarios: improving user experience

Before you migrate to Whistler Personal or Whistler Professional, OmniPage 10 should be uninstalled or the program might not function correctly after the migration. After Whistler is installed, reinstalled OmniPage 10.

If the program is not functioning correctly, perform the following workaround.

This issue will not be addressed in a future release.

Applies to scenarios: improving user experience

Since the online games are running on a beta server to a restricted audience, you might experience delays in finding an opponent. This issue will be addressed in a future release.

Applies to scenarios: improving user experience

When installing PeopleSoft 7.56 on Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server in a dual-boot scenario with any version of Windows 2000, the operating systems must be installed to different partitions. If not, PeopleSoft 7.56 does not create a program group or icons on the Start menu. This issue will not be addressed in a future release.

Applies to scenarios: improving user experience

On computers running Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, the following issues apply to SAP R/3 4.0b, 4.5b, and 4.6b.

These issues will not be addressed in a future release.

Applies to scenarios: improving user experience

Application Center 2000

Whistler Server, Whistler Advanced Server, and Whistler Datacenter Server do not support Application Center 2000. This issue will be addressed in a future release.

Applies to users: administrators

Applies to scenarios: improving user experience

Exchange Server 5.5

Whistler Server, Whistler Advanced Server, and Whistler Datacenter Server do not support Exchange Server 5.5 Service Pack 4 and earlier versions. This issue will not be addressed in a future release.

Applies to users: administrators

Exchange 2000

Whistler Server, Whistler Advanced Server, and Whistler Datacenter Server do not support any version of Exchange 2000. This issue will be addressed in a future release. For more information about Exchange 2000, see the Microsoft Exchange Server Web site at:

Applies to users: administrators

Applies to scenarios: improving user experience

ISA Server 2000

Whistler Server, Whistler Advanced Server, and Whistler Datacenter Server do not support Internet Security and Acceleration (ISA) Server 2000. This issue will be addressed in a future release.

Applies to users: administrators

Applies to scenarios: improving user experience

Microsoft BizTalkä Server 2000

Whistler Server, Whistler Advanced Server, and Whistler Datacenter Server do not support BizTalk Server 2000. This issue will be addressed in a future release.

Applies to users: administrators

Applies to scenarios: improving user experience

Proxy Server 2.0

Whistler Server, Whistler Advanced Server, and Whistler Datacenter Server do not support Proxy Server 2.0. This issue will not be addressed in a future release.

Applies to users: administrators

Site Server 3.0

Whistler Server, Whistler Advanced Server, and Whistler Datacenter Server do not support Site Server 3.0 Service Pack 4 and earlier versions. This issue will not be addressed in a future release.

Applies to users: administrators

SNA Server 4.0

SNA Server 4.0 is not supported on Whistler Server, Whistler Advanced Server, and Whistler Datacenter Server. This issue will not be addressed in a future release.

Applies to users: administrators

Applies to scenarios: improving user experience

System Management Server 2.0

Whistler Server, Whistler Advanced Server, and Whistler Datacenter Server do not support Systems Management Server 2.0 Service Pack 2 and earlier versions. This issue will be addressed in a future release. For more information about Systems Management Server 2.0, see the Microsoft System Management Server Web site at:

Applies to users: administrators

Applies to scenarios: improving user experience

"-------------------------- Graphics Page Library --------------------------- Handle type doesn't match function's expectations sp~pagwf.dll D:\spw5src\pagew\Gps_doc.cpp(188) 8e000002 --------------------------- OK ---------------------------"

After this message, the program closes and any data previously entered is lost. To work around this issue, use SigmaPlot 2000 (v6.1). This issue will not be addressed in future release.

Applies to scenarios: improving user experience

After migrating to Whistler Personal or Whistler Professional on a Sony Vaio, the majority of Sony's proprietary programs might not function. This includes, but is not limited to, DVGate, Smart Capture, MovieShaker, JogDial, BatteryScope, PowerPanel, and Media Bar. This issue is presently under investigation.

Applies to scenarios: improving user experience

Applies to scenarios: improving user experience

Open File Option

Do not install the Open File Option of Veritas Backup Exec 8.5 on Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server. Installation of this option might cause a loss of functionality on your computer. For more information about support on the Open File Option, see the Veritas Web site at

This issue will not be addressed in a future release.

Applies to scenarios: improving user experience

On computers running Whistler Advanced Server or Whistler Datacenter Server, Visio 5.0 users share a common document directory. To work around this issue, after installing the program, run the Visio5.cmd script located in the systemroot\Application Compatibility Scripts\Install folder to provide each user with a unique document directory.

Note   Any Visio settings changed for one user apply to all Visio users.

Applies to users: administrators

Applies to scenarios: improving user experience

Applies to scenarios: improving user experience

Applies to scenarios: improving user experience

On computers running Whistler Advanced Server or Whistler Datacenter Server, multiple user support for Lotus SmartSuite 9.5 is not available. To work around this issue, run the Ssuite95.cmd script located in the systemroot\Application Compatibility Scripts\Install folder. This changes the default registry permissions necessary for non-administrator users so that they can run SmartSuite 9.5 (Millennium Edition). In addition, it adds the SS95usr.cmd script to UsrLogn2.cmd.

If you installed Lotus SmartSuite 9.5 on a computer running Windows NT Server 4.0, Terminal Server Edition and then upgraded to the Whistler Advanced Server Beta 2 release with Terminal Server, you should uninstall and reinstall Lotus SmartSuite 9.5. Then, to enable multiple user support for Lotus SmartSuite 9.5, run the Ssuite95.cmd script located in the systemroot\Application Compatibility Scripts\Install folder.

Note   The application compatibility scripts in the Whistler Beta 2 release do not require a SmartSuite node install for each user.

Applies to users: administrators

Applies to scenarios: improving user experience

On computers running Whistler Advanced Server or Whistler Datacenter Server, Lotus SmartSuite 9.0 ScreenCam must be turned off during installation or the installation does not successfully complete. This issue will be addressed in a future release.

Applies to users: administrators

Applies to scenarios: improving user experience

Office 97 has various program compatibility issues with Whistler Advanced Server. They include:

• Files that need permissions that are different from the defaults.
• Files that need to be moved to the user's home directory.
• Removal of the Find Fast option.

To correct these compatibility issues, after installing Office 97, run the Office97.cmd installation script located in the systemroot\Application Compatibility Scripts\Install folder.

The installation script also adds the Ofc97usr.cmd script located in the systemroot\Application Compatibility Scripts\Logon folder to UsrLogn2.cmd. This script ensures that the needed per-user directories and files have been configured.

The following issues will not be addressed by a future release. For specific Office 97 program compatibility issues, see the following sections.

Adding Users to Access 97 Workgroups

To add users to an Access workgroup on the Tools menu by using the Security command, in the workgroup information file, you must first change the permissions to Write. The default workgroup information file is System.mdw and is located in the systemroot\System32 folder. Once users have been added, you should change permissions back to Read.

Applies to users: administrators

Applies to scenarios: improving user experience

Creating Access 97 Workgroups

To create a new Access workgroup by using the Wrkgadm.exe file and to make Access 97 available to all the users within the workgroup, you need to change the security permissions for the groups Administrator and Everyone. To do this, in the new workgroup information file, change the security permissions to Read. Only administrators can create workgroup information files.

Applies to users: administrators

Applies to scenarios: improving user experience

Custom Dictionaries

The only per-user custom dictionary is the Custom.dic file created in the \Office97 subdirectory in the user's home directory. The list of custom dictionaries is not private for each user, and so other users can view any new custom dictionary that might be created by the user.

Applies to users: administrators

Applies to scenarios: improving user experience

Data Map Dictionary

The data map dictionary in Office 97 (Geodict.dct) is common to all users. If one user deletes a map, other users no longer can gain access to that map.

Applies to users: administrators

Applies to scenarios: improving user experience

Excel 97 Tools and Wizards

Some Excel wizards and tools do not support users using the Template Wizard.

Applies to users: administrators

Applies to scenarios: improving user experience

Microsoft Access 97 Spelling Options

Only administrators can modify the spelling options in Access 97 because the spelling options in Access 97 are common to all Access users.

Applies to users: administrators

Applies to scenarios: improving user experience

Microsoft Access 97 Tools and Wizards Workgroups

Some Access 97 wizards and tools do not support concurrent use, including Combo Box Wizard, Database Documenter Wizard, Field Builder, List Box Wizard, Lookup Wizard, Option Group Wizard, Switchboard Manager, Table Analyzer Wizard, and Table Wizard. In addition, the preferences for the wizards are common to all users. Database Documenter is not supported by servers using the NTFS file system and running in Secure mode. To use the Documenter database, users must have permission to modify the System.mdw file. To use Database Documenter, users must be granted Write permission in System.mdw located in the systemroot\System32 folder. In order for non-administrative users to be able to run the Access wizards (or Access Add-Ins in Excel) locate the following lines in the Office97.cmd file and delete Rem:

Rem If Exist "%O97INST%\Office\WZMAIN80.MDE" cacls "%O97INST%\Office\WZMAIN80.MDE" /E /P "Authenticated Users":C >NUL: 2>&1

Rem If Exist "%O97INST%\Office\WZTOOL80.MDE" cacls "%O97INST%\Office\WZTOOL80.MDE" /E /P "Authenticated Users":C >NUL: 2>&1

Applies to users: administrators

Applies to scenarios: improving user experience

Microsoft PowerPointâ  97 Conference Presentations

Only one person on a server can use the Presentation Conference command on the Tools menu. It is not possible for several people on a server to conference among themselves.

Applies to users: administrators

Applies to scenarios: improving user experience

Microsoft Word 97 Tools and Wizards

Some Word wizards and tools do not support concurrent use, including Clipart Preview.

Applies to users: administrators

Applies to scenarios: improving user experience

Outlook 97 Auto Signature

The Outlook 97 wizard uses the same profile for all users. A unique profile can be specified for each user using Mail and Fax. To do this, in Control Panel, double-click Mail and Fax.

Applies to users: administrators

Applies to scenarios: improving user experience

Outlook 97 Tools and Wizards

Some Outlook wizards and tools do not support concurrent use, including the Template Wizard.

Applies to users: administrators

Applies to scenarios: improving user experience

Tools and Wizards

Users should avoid enabling the Menu Animation component in Office 97. Enabling this component can severely affect system performance.

All of these Office 97 and Office 97 programs issues are applicable for the following users and scenarios.

Applies to users: administrators

Applies to scenarios: improving user experience

Visual Basic Editor Controls

Users without administrative rights cannot use or create additional controls in the toolbox. Only users with Write permission for the systemroot\System32 folder are able to perform this task.

Applies to users: administrators

Applies to scenarios: improving user experience

On computers running Whistler Advanced Server, Office 2000 cannot be installed using Terminal Services. To work around this issue, prior to installing Office 2000, you must install the Terminal Server Tools transform file from the Office Resource Kit. Then, install Office 2000 using that transform file.

change user /execute

For clarification, note the following example. Install the Office Resource Kit to its default location on the C drive. Then, insert the Office 2000 CD into the D drive. At the command line, type

Certain features of Office 2000 are purposely turned off during this transform installation.

• Only the still agent is available. Users cannot select a different agent.
• Since only an administrator can install Office 2000, Demand install and Detect and repair components are not supported under Terminal Services.

A specific compatibility issue that applies to Office 2000 programs is that the Help System Information function does not function correctly when running in Terminal Server mode. This issue will not be addressed in a future release.

Applies to users: administrators

Applies to scenarios: improving user experience

If you are migrating to Whistler Personal or Whistler Professional, the following issues involve the User State Migration Tool (USMT).

• User passwords are not migrated.
• If Always dial my default connection is selected, a message prompting you to dial the Internet appears. To work around this issue, do not dial the Internet. Continue through the migration.

These issues will not be addressed in a future release.

Applies to users: administrators

Microsoft Office 2000

Applies to users: administrators

Microsoft Word

The custom dictionary does not migrate and merge correctly. This issue will be addressed in a future release.

Applies to users: administrators

Outlook

If you are migrating to Whistler Personal or Whistler Professional, in Outlook:

• On the Tools menu, in Options, on the Preferences tab, some settings do not migrate correctly.
• Message rules do not migrate.

These issues will be addressed in a future release.

Applies to users: administrators

Outlook Express

If you are migrating to Whistler Personal or Whistler Professional, in Outlook Express:

• Migrating multiple times to Outlook Express can cause incorrect merging.
• Message rules do not migrate
• When applying the settings and files to your new Whistler system, you might be prompted to log off when the Setup Wizard finishes. This might cause an End Now dialog box to appear. To work around this issue, click Cancel, and the Setup Wizard continues.
• Files with extended (and foreign) characters in the name, might not migrate correctly.

These issues will be addressed in a future release.

Applies to users: administrators

Data partitions on basic disks that are converted to dynamic simple data volumes might be extended. On Windows 2000, the conversion retains all of the original partitions on the disk. On Whistler, the original partitions are converted to a single container partition. All data simple volumes can be extended.

Data partitions on dynamic disks can no longer be installation targets. You can install Whistler onto existing dynamic system or boot volumes or to any primary partition or extended partition on a basic disk.

Whistler includes a new diskpart command line for volume management. Anything that can be done with the Disk Management snap-in can be done with diskpart. However, commands that are not available to Whistler Personal and Professional are not blocked in diskpart. Running commands to create and break mirrors or RAID volumes on a Whistler Personal or Professional installation can cause system instability. Additionally, commands relating to dynamic disks might cause system instability on Personal.

Drive letters are assigned incrementally starting from C for all drive letters with the exception of network mapped drives, which start from Z and get assigned in reverse order (Z, Y, and so on). This is to help keep the namespace separate on computers, especially in Terminal Server environments.

These issues will not be addressed in future release.

Applies to users: administrators

Applies to scenarios: improving user experience, improving technology

Kodak 4800 Zoom Digital Camera

On computers running Whistler Personal, Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, the Kodak 4800 Zoom Digital Camera with Firmware version 1.0 will not be automatically recognized as a supported device until the firmware in the camera has been upgraded to 1.04 or later.

This issue will be addressed in a future release.

Applies to scenarios: improving user experience

Windows Movie Maker requires the following minimum system configuration:

The following devices have been preliminarily tested with Windows Movie Maker on computers running Whistler Personal or Whistler Professional:

• ATI All-In-Wonder (using the drivers that are included with the product).

• ADS Pyro Digital Video 1394
• OrangeMicro OrangeLink FireWire

• Telex M-560 Super-directional USB Digital Microphone

If you change the video line input in the Change Device dialog box, ATI All-In-Wonder analog video capture cards might not run correctly in Windows Movie Maker.

Applies to scenarios: improving user experience

Audio is not supported on some Acer TravelMate notebooks running Whistler Personal or Whistler Professional. There is no workaround for this.

Applies to scenarios: improving user experience

Alps touchpad drivers do not work on Whistler Personal, Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server after an upgrade or a clean install. To work around this issue, uninstall the drivers before setup and use the generic class drivers to get functionality. Beta drivers are available through Alps. This issue will be addressed in a future release.

Applies to users: OEMs

Applies to scenarios: improving user experience

Application Compatibility

All applications that have an application compatibility script, which was installed with the operating system, will require that the application compatibility script be run manually after restart.

On computers running Whistler Personal or Whistler Professional, the following audio hardware issues involve application compatibility.

Applies to scenarios: improving user experience

Creative Labs Live!Ware

If you installed Creative Labs Live!Ware 3.0 for Windows 2000 on computers running Whistler Personal, Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, the main volume slider does not function correctly. The hardware MIDI synthesizer does not play and the driver does not correctly display the volume controls for additional channels. If you choose the four-speaker setup, the operating system stops responding.

Applies to scenarios: improving user experience

Dell Laptops

On Dell laptops with Allegro/M3 designs running Whistler Personal or Whistler Professional, the audio does not function correctly when the laptop is docked. The mute buttons and volume buttons do not function correctly. The volume control does not work when playing audio from the docking station's audio output. This issue will be addressed in a future release.

Applies to scenarios: improving user experience

Loss of Audio When Returning from Hibernation or Standby

On computers running Whistler Personal or Whistler Professional, the following audio hardware issues involve the loss of audio when returning from certain power modes.

Applies to scenarios: improving user experience

Microsoft SideWinderâ Force Feedback Joystick

• Creative Sound Blaster Live.
• ESS Technology Solo-1.
• Turtle Beach Santa Cruz.

The joystick is functional except for the force feedback level.

Applies to scenarios: improving user experience

Microsoft Visual Studioâ  6.0 Enterprise Edition

On computers running Whistler Advanced Server or Whistler Datacenter Server, Visual Studio 6.0 sets up several default document settings that are specific to the user who installed the program. To give each user unique default directories, after completing the Visual Studio 6.0 installation, run the Msvs6.cmd script located in the systemroot\Application Compatibility Scripts\Install folder. Note the following issues:

• In Visual Basic 6.0, all users share a common default project directory.
• In Microsoft Visual FoxProâ , users cannot use the ActiveX catalog tools. Multiple users cannot use the Forms Wizard, Database Wizard, Label Wizard, Multimedia/Sound Player, or Setup Wizard simultaneously in Visual FoxPro. If one user creates a default macro set in Visual FoxPro, it applies to all users on the server.
• In Microsoft Visual C++â  6.0, quick macros do not support multiple users. Only one user at a time can record a quick macro and only the user that created the quick macro can run it. The default file name and directory for macro files (\Program Files\Microsoft Visual Studio\Common\Msdev98\Macros\MyMacros.dsm) is common for all users. To run Visual C++ 6.0 tools from a command prompt, users must run Vcvars32.bat located in the \Program Files\Microsoft Visual Studio\VC98\Bin\ folder.

These issues will be addressed in a following release.

Applies to users: administrators, developers

Applies to scenarios: improving user experience

Netscape Communicator 4.7x

On computers running Whistler Advanced Server or Whistler Datacenter Server, in Netscape Communicator 4.7x, the User Profile Manager can now create different user profiles for each user. When a user initially opens Netscape Communicator, the user is prompted to create his or her own profile or to copy an existing user profile. However, any user on the system can gain access to the user profiles.

After installing Netscape Communicator, run the Netcom40.cmd script located in the systemroot\Application Compatibility Scripts\Install folder. This sets up the root drive to point to the user profile directory for each user. For example, after the user runs Netcom40.cmd, the user profile drive (W:) is mapped to the C:\Documents and Settings\user name directory. Netcom40.cmd adds the Com40usr.cmd script located in the systemroot\Application Compatibility Scripts\Logon folder to UsrLogn2.cmd. This logon script sets the permissions on the user's Netscape Communicator profile directory so only that user can gain access to his or her profile directory.

The following issues still remain:

• The Netscape default user profile directory is always set to the Netscape program user directory (for example, \Program Files\Netscape\Users\Default). Each user should select a unique name (such as their user name) for the Netscape profile directory. If they select a name that already exists, Netscape Communicator displays a warning message. The user can still, however, select that directory. The user that originally created that directory is unable to run Netscape Communicator, and has to use the Netscape User Profile Manager to create a new profile to run Netscape Communicator. After Netscape Communicator is initially run, the permissions for each user's Netscape profile directory are set the next time the user logs on to the computer. The user must log off after initially running Netscape Communicator.
• The AOL Instant Messenger program that installs with Netscape Communicator 4.7x does not support multiple simultaneous users.
• If you installed Netscape Communicator 4.7x on a computer running Windows NT Server 4.0, Terminal Server Edition and then upgraded to Whistler Advanced Server or Whistler Datacenter Server with Terminal Services, Netscape Communicator might not function correctly. To work around this issue, you should uninstall and reinstall Netscape Communicator, and then run the Netcom40.cmd script.

Applies to users: administrators

Applies to scenarios: improving user experience

Toshiba Tecra Laptops Audio Playback

On Toshiba Tecra 8100 laptops running Whistler Personal or Whistler Professional, when running the laptop on battery power, the audio playback is uneven. To work around this issue, use the AC power cable as the power source for the computer.

Applies to scenarios: improving user experience

USB Speakers

On computers running Whistler Personal or Whistler Professional, the following audio hardware issues involve universal serial bus (USB) speakers.

Applies to scenarios: improving user experience

Volume Settings

Applies to scenarios: improving user experience

When you upgrade your computer from Windows 2000 to Whistler Personal or Whistler Professional with a Creative WebCam Go or WebCam Go Plus attached, leave the camera unplugged from the computer during Setup.

Applies to scenarios: improving user experience

When you install Digifep.sys-based Digi PCI multiport serial adapters on computers running Whistler Personal, Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, a Code 10 error message is reported and the device cannot start. The adapter is listed in the Multiport Serial class of Device Manager, but does not function correctly.

Applies to scenarios: improving user experience

Gateway computers running Whistler Personal, Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server that use 1 GHz AMD Athlon processors with BIOS 0AAVWB02 might display a Stop error or might not display all the accelerated graphics port (AGP) textures. To work around this issue, you must upgrade to BIOS 0AAVWB05 or a later version. This issue will be addressed in a future release. For more information on this BIOS, see the Gateway Web site at:

Applies to scenarios: improving user experience

Upgrading from a computer running Windows 95 or Windows 98 to Whistler Personal or Whistler Professional might cause your DVD player application to function incorrectly. This is due to a DVD decoder incompatibility between these operating systems, which often also affects the associated DVD player application.

To work around this issue, install a Windows 2000 or Whistler-compatible DVD solution after performing the upgrade. For more information on how to obtain the Whistler compatible DVD solution, refer to the upgrade report information that appears during Whistler Setup. If no information on how to obtain a Whistler-compatible DVD solution appears, see the online Help or your product documentation to obtain a Windows 2000 or Whistler-compatible DVD solution. This issue will be addressed in a future release.

Applies to scenarios: improving user experience

If you upgrade your computer from Windows NT 4.0 or Windows 2000 to Whistler Personal, Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server, Equinox multiport serial adapters might list the port numbers as 9999. This happens most often with an adapter configuration with more than 256 ports. To work around this issue, uninstall and then reinstall the adapters. This issue will be addressed in a future release.

Applies to scenarios: improving user experience

After you perform a clean installation of Whistler Personal or Whistler Professional on your computer, you cannot install the Logitech Driver Package version 5.3. A message appears stating that Logitech's QuickCam USB Cameras Installer is unable to locate a working USB port on the computer. To work around this issue, try either of the following:

Applies to scenarios: improving user experience

If you have ActiveSync 3.1 installed on a computer running Whistler Personal or Whistler Professional and if you transfer files by using Windows Media Player 8 to a portable media player, ActiveSync tries to connect to the portable media player as well. To work around this issue, close ActiveSync 3.1 and proceed with the file transfer using Windows Media Player 8. This issue will be addressed in a future release.

Applies to scenarios: improving user experience

Parallel port Compact Flash reader fails to function correctly if the user tries to hibernate/suspend a computer running Whistler Personal, Whistler Professional, Whistler Server, Whistler Advanced Server, or Whistler Datacenter Server when the Compact Flash reader is busy. To work around this issue, do not power-manage your computer while there are transfers in progress. This issue will be addressed in a future release.

Applies to scenarios: improving user experience

After you upgrade from the factory-preloaded Windows 98 Special Edition with OEM applications to Whistler Personal, you cannot uninstall Battery Scope by using Add or Remove Programs. Battery Scope does not function correctly in Whistler.

To work around this issue for either program, uninstall the program before performing the upgrade.

Applies to scenarios: improving user experience

On computers running Whistler Personal or Whistler Professional, the 3Com HomeConnect Camera does not function correctly using the currently available Windows 2000 drivers. This issue will be addressed in a future release.

Applies to scenarios: improving user experience

Applies to scenarios: improving user experience

ABIT VP6 Motherboard

On all versions of Whistler, if you connect a USB device to a computer using the ABIT VP6 motherboard, the computer might stop responding.

Applies to scenarios: improving user experience

On computers running Whistler Personal or Whistler Professional, if you change screen resolution or color depth while previewing or capturing video, the computer might stop responding. This issue will be addressed in a future release.

Applies to scenarios: improving user experience

Whistler Personal and Whistler Professional currently only include drivers for the following video capture devices:

Applies to scenarios: improving user experience

On computers running Whistler Personal or Whistler Professional, some custom video capture and video preview programs that many hardware vendors released with Windows 98 drivers for their USB, television, and analog capture devices might not function correctly. To work around this issue, contact your hardware vendor for a Windows 2000 version of the program.

Applies to scenarios: improving user experience

For the latest information about Windows 2000 compatible-device drivers and programs, see the camera manufacturers' Web site. These issues will be addressed in a future release.

Applies to scenarios: improving user experience

Installing the drivers for the Xircom REX 6000 MicroPDA with a USB docking station on a computer running Whistler Personal or Whistler Professional causes the computer to function incorrectly. There is no workaround for this.

Applies to scenarios: improving user experience

On computers running Whistler Server, the domain name is ignored for Basic authentication while logging on to a computer. When using Basic authentication, the logon process does not correctly validate the domain name and the user can log on to the computer using an unrecognized or unregistered domain name. In this case, the user name and password must still be valid and must be valid for the domains for which they are associated. This issue will be addressed in a future release.

Applies to users: administrators

Applies to users: administrators, OEMs

Applies to scenarios: improving user experience

The following issues apply to Windows Media Player 8 installed on computers running Whistler Personal or Whistler Professional. These issues will be addressed in a future release.

Backup Licenses

Before upgrading computers running Windows 98 or Windows 2000 to Whistler Personal or Whistler Professional, you must back up the Windows Media Player 8 licenses. After the upgrade is complete, you can use Windows Media Player 8 to restore the licenses.

Applies to scenarios: improving user experience

Creating Your Own CDs

Applies to scenarios: improving user experience

Downloading Album Art

Applies to scenarios: improving user experience

DVD Decoders

Applies to scenarios: improving user experience

DVD Playback

Applies to scenarios: improving user experience

Hardware Playback and Copying Issues

Applies to scenarios: improving user experience

Scratches and Pops in Copied Tracks

Applies to scenarios: improving user experience

Supported Portable Devices

Applies to scenarios: improving user experience

Troubleshooting Your Portable Device

On computers running Whistler Personal or Whistler Professional, occasionally audio errors can occur when you simultaneously play and copy tracks to your portable device. If you notice audio errors, avoid playing tracks while your computer is copying the tracks to your portable device.

If you encounter errors while playing tracks on your portable device, it might be the result of a bad copy of the track. Ensure that your storage card was properly formatted, and do not play tracks simultaneously when copying. If your portable device is properly formatted, try copying the track to your portable device again. Occasionally, a storage card might have a bad sector that causes errors while playing a track.

Applies to scenarios: improving user experience

Using RCA Lyra

On computers running Whistler Personal or Whistler Professional, to use Windows Media Player 8 with the RCA Lyra, you must install the RCA Lyra storage card reader software that came with your RCA Lyra. After the storage card reader is installed, two drives names, such as Lyra (F:) and F:, are shown in the drop-down list on the Music On Device tab. You must select Lyra (F:) to play the tracks you are copying to the RCA Lyra.

Applies to scenarios: improving user experience

Using the Internet

Applies to scenarios: improving user experience

Video Playback

Applies to scenarios: improving user experience

The following issues involve the feature Discovery and Control in Home Networking.

Applies to scenarios: improving user experience, improving technology

The Home Networking Components (Internet Connection Sharing, Internet Connection Firewall, Network Bridge) have been removed from Whistler Advanced Server and Whistler Datacenter Server. This issue will not be addressed in a future release.

Applies to users: administrators

Applies to scenarios: improving user experience, improving technology

The following issues involve the Home Networking Wizard.

Applies to scenarios: improving user experience

On computers running Whistler Personal or Whistler Professional, the FTP proxy currently does not allow connections to FTP servers that use a port other than Port 21. This issue will be addressed in a future release.

Applies to scenarios: improving user experience

http://www.microsoft.com/hiserver

For the 64-bit edition, DLC protocol is not available. This issue will be addressed in a future release.

• Support for AppleTalk networking protocol has been removed from Whistler Personal and Whistler Professional. Whistler Server continues to implement AppleTalk as part of Services for Macintosh (SFM). This issue will not be addressed in a future release.

Applies to users: administrators

Applies to scenarios: improving technology

On computers running Whistler Personal or Whistler Professional, drivers for the following modems might exhibit a dialing problem when using pulse dialing in Japan. This problem might occur in other countries that have public telephone networks with pulse dialing. If the computer is under heavy load during pulse dialing, the telephone network might misinterpret the pulses produced by the modem and cause the wrong telephone number to be dialed.

This issue might occur in the following modems:

• ACER Inc HCF 56K PCI Modem
• Aztech Systems MDP3858V-U Data Fax Modem
• Aztech Systems MDP3858-U Data Fax Modem
• Aztech Systems MDP3880-W(B) PCI Modem
• Aztech Systems MDP3900V-U Modem
• Aztech Systems MDP3880-W(U) PCI Modem
• Aztech Systems MP3930V-W(C) Data,Fax,Voice MiniPCI Modem
• Aztech Systems MDP3900V-W Modem
• Best Data Inc 56FW PCI V90 56K Modem
• CIS 5614 series Modem
• Compaq 56K V90 HCF MiniPCI Modem
• Compaq Global 56K V90 HCF MiniPCI Modem
• Conexant, Inc. HCF 56K PCI Modem
• Creative Modem Blaster Flash56 PCI DI5630
• Creative Modem Blaster DI5601
• Diamond Multimedia Systems Inc SupraExpress 56i PRO
• Digicom D-F-V V.90 DI3635
• ELSA MicroLink 56K PCI Modem
• GVC 1156IV+ International series V90 Modem
• IBM HCF 56K PCI Modem
• NEC Fax 56K Modem
• NEC Data+Fax 56K Modem
• Sony HCF 56K PCI Modem

This issue will be addressed in a future release.

Applies to users: OEMs

Applies to scenarios: improving user experience

On computers running Whistler Personal or Whistler Professional installed with 1394 cards, IP addresses change every five minutes. This might lead to network connectivity issues. Additionally, an error occurs if you type the following command at the command prompt

This issue will be addressed in a future release.

Applies to scenarios: improving user experience, improving technology

If you upgrade a computer running Windows 2000 that uses Routing and Remote Access service (RRAS) with a network address translator (NAT) to Whistler Server, FTP traffic cannot flow through the NAT. To work around this issue, turn off and then turn on RRAS with NAT. This issue will be addressed in a future release.

Applies to scenarios: improving user experience, improving technology

The following issues involve Universal Plug and Play devices.

Applies to scenarios: improving user experience

Cover Pages

Applies to scenarios: improving user experience

Missing Context-Sensitive Help in Fax Console

Applies to scenarios: improving user experience

Missing Notification Functionality

Notification functionality described in the documentation for Fax Service is not implemented on computers running Whistler Personal or Whistler Professional. This issue will be addressed in a future release.

Applies to scenarios: improving user experience

Non-Textual Content Cannot be Copied and Pasted into Outlook Fax Documents

If you are using Outlook 2000 on a computer running Whistler Personal or Whistler Professional, you cannot use Fax Service to send a fax that includes non-textual content, such as graphics and tables that have been copied and pasted into the fax document. To work around this issue, save the non-textual content to a file and attach it to the Outlook document.

Applies to scenarios: improving user experience

Reinstall a Modem if the Fax Printer is Deleted

When installing Fax on a Whistler Personal or Whistler Professional computer with a local fax device installed, a local fax printer is created automatically. If a fax device is added after Fax has been installed, a fax printer is created at that time.

If this fax printer is deleted for any reason, to work around this issue, recreate the fax printer by installing any modem. Even though you do not actually have to install a real modem, the process will recreate your local fax printer. This issue will be addressed in a future release.

Applies to scenarios: improving user experience

Sending a Fax from Outlook Using Both E-Mail Addresses and Fax Numbers

When using Fax Service on a computer running Whistler Personal or Whistler Professional to send a fax from Outlook 2000 with Exchange 2000 as the mail server, if the fax has both an e-mail address and a fax number, you receive a message stating that the e-mail cannot be sent because the e-mail address is incorrect. However, the fax message is submitted and sent successfully. This issue will be addressed in a future Exchange 2000 service pack.

Applies to scenarios: improving user experience

Sending a Fax with HTML Document Attachments from Outlook

Applies to scenarios: improving user experience

Support in Send Fax Wizard for Other Languages Besides the System Default Location Language

Applies to scenarios: improving user experience

Temporary Functionality

Applies to users: administrators

Applies to scenarios: improving user experience

Unsupported Modems

On a computer running Whistler Personal or Whistler Professional, Fax Service does not fully support the following modems: Aiwa PV-BF5606, Omron ME5614D, and Hucom-EX. This issue will be addressed in a future release.

Applies to users: administrators

Applies to scenarios: improving user experience

On computers running Whistler Server or Whistler Advanced Server, changes to relocated policies in the registry only propagate additions and not deletions. Group Policy objects added to the relocated registry policy are recognized and propagated to Active Directory directory service and are visible through remote administration on other computers. However, deletions are only recognized on the computer on which they were performed. They are not recognized or propagated to Active Directory and are not visible through remote administration.

In public key policy and software restriction policy settings, IGPEInformation copies the policy from Active Directory to a special place in the registry. It is edited there and when called, the PolicyChanged method writes the policy back to Active Directory. The expected behavior in a single domain controller domain is that the policy appears the same whether it is viewed on the domain controller or viewed remotely from a joined computer. When the policy is copied back to Active Directory as a result of a call to PolicyChanged, it appears that only additions to the policy are being copied back to Active Directory, but deletions are not.

To work around this issue, delete the extra request objects by using Group Policy on the domain controller itself. This issue will be addressed in a future release.

Applies to users: administrators

Certificate Server

Certificate Server 1.0 cannot be upgraded directly from Windows NT 4.0 to Whistler Server or Whistler Advanced Server. If you do so, your Certificate Server settings are not saved, and Certificate Server automatically uninstalls. To work around this issue and preserve all your Certificate Server settings, upgrade first to Windows 2000 and then upgrade to Whistler Server or Whistler Advanced Server. This issue will not be addressed in the future.

Applies to users: administrators

Upgrading a Certification Authority

Upgrading a certification authority (CA) to Whistler Server or Whistler Advanced Server might cause the upgraded Whistler CA to publish a delta certificate revocation list (CRL), but fail to publish a base CRL. To work around this issue, manually publish a base CRL. This issue will be addressed in a future release.

Applies to users: administrators

On English versions of all versions of Whistler, error reporting is only available in English. On localized versions of all versions of Whistler, error reporting is available in English and the localized language.

Applies to users: OEMs

Applies to scenarios: improving user experience

Permissions

The default permissions settings for Terminal Services in Whistler Advanced Server have changed from the Windows 2000 default. Computers running a clean installation of Whistler Advanced Server with Terminal Services turned on provide full compatibility with Whistler permissions settings by default unless specified otherwise during the operating system installation. This ensures that newly installed systems can operate under full Whistler security unless specifically directed otherwise. If a computer running Windows 2000 Terminal server is upgraded to Whistler Advanced Server, the existing compatibility settings are preserved.

A user cannot run some legacy programs under full Whistler permissions settings because they require Power Users permissions. At the time of Terminal Services installation, the administrator selects from two options: Full Security (permissions compatible with the Whistler Users group), or Windows NT 4.0 Compatible Security (permissions compatible with the Windows NT Server 4.0, Terminal Server Edition Users group). To work around this issue, use the Terminal Services Configuration tool to choose the Windows NT 4.0 Compatible Security option and increase compatibility with some older programs.

The exact behavior of the permissions compatible with the Windows NT Server 4.0 Terminal Server Users Permissions setting is also different in Whistler from what it was in Windows 2000. In Windows 2000, users can gain full access to registry information by selecting this option, just as they had in Windows NT 4.0. In Whistler, this option only provides permissions to those parts of the registry accessed by the program, thus providing greater security without compromising compatibility.

Applies to users: administrators

Applies to scenarios: improving user experience

If a terminal server cannot find a License Server within 90 days of the first connection made to it, it stops accepting connections. For the Beta 2 release of Whistler Advanced Server and Whistler Datacenter Server, this period has been extended to 180 days. This extension is for the beta release only and is meant to simplify test deployments.

Applies to users: administrators

Applies to scenarios: improving user experience

The first time a program compatibility script is used on a computer running Whistler Advanced Server, the script checks to see whether Rootdrv.cmd has been edited. Rootdrv.cmd is a script that maps a drive letter to the client's home directory. For example, if W:\ is specified as the drive letter to be used for mapping, then W:\ would be mapped to %homedrive%%homepath%. With this technique, you can specify what appears to be a shared path, such as W:\Mail\Mailbox.dat. Yet, the drive mapping causes each user to get a unique copy of the file in their home directory. This script starts Notepad and requires that you type a drive letter and then save and close the file. The program compatibility script then resumes. Rootdrv.cmd is run only if you have not already mapped a drive letter for use.

If you wish to change the drive letter later, open the Rootdrv2.cmd file in Notepad, edit the drive letter, and save the file. Rootdrv2.cmd is where Rootdrv.cmd stores the final drive mapping information. You also need to update the following registry key with the new drive letter.

Caution   Incorrectly editing the registry can severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.

Note   Logon scripts are not executed for users who are logged on until they log off and log back on. Many programs do not behave correctly when run before the logon script begins. For this reason, you should install programs when no users are logged on to the system.

When upgrading or adding components to an existing installation of a program covered by compatibility scripts, you should rerun the script. This issue will not be addressed in a future release.

Applies to users: administrators

Applies to scenarios: improving user experience

On computers running Whistler Advanced Server, Session Directory recovery for Terminal Services is not fully functional. As a result, if you stop and restart Session Directory Service, or if you change the cluster or Session Directory to which a Terminal server subscribes without restarting the Terminal server, the Session Directory Service does not function for any existing disconnected sessions. In such cases, the Session Directory Service works for any existing session created after the recovery, but does not redirect a client to an existing session on another server if the existing session was disconnected prior to recovery. This issue can occur if one or more of the following circumstances occur.

• The Session Directory Service does not function correctly or is stopped and then restarted, but the Terminal servers subscribing to that Session Directory Service are not restarted.
• One or more Terminal servers are reconfigured to a different cluster name without being restarted.
• One or more Terminal servers are reconfigured to join a different Session Directory Service without being restarted.
• Participation in the Session Directory Service is stopped and then restarted on one or more Terminal servers without restarting the server.

To work around this issue, users can manually connect to their disconnected sessions to avoid the loss of data that might result from restarting Terminal servers with existing disconnected sessions. To do this, use Terminal Services Administration or the command-line utility qwinsta to determine the server hosting the disconnected session, and then connect directly to that server. You need to supply users with the names or IP addresses of the individual Terminal servers in the cluster.

Applies to users: administrators

Applies to scenarios: improving user experience

If Terminal Services Advanced Client (TSAC) is installed on a computer running Advanced Server or Whistler Datacenter Server, and you do not uninstall TSAC before installing the Whistler version of the Terminal Services client on the computer, the Whistler client setup program does not function correctly. The message "File could not be copied over the network" appears and the Whistler version of the Terminal Services client is not installed, but TSAC is still functional. To work around this issue, uninstall TSAC.

Applies to users: administrators

Applies to scenarios: improving user experience

The 64-bit editions of Whistler do not support 16-bit editions of DOS, Windows, or OS/2 applications. This is significant to applications in which the Setup.exe file is a 16-bit dummy routine which checks the computer type and then starts the real 32-bit installation program that actually performs the installation. On computers running Whistler Professional or Whistler Advanced Server, certain 16-bit Setup programs do not run correctly and might affect other applications. These applications have their own proprietary Setup program.

The list of substitutions is stored in the registry in the following registry key:

This issue will not be addressed in a future release.

Applies to scenarios: improving user experience

On computers running Whistler Professional or Whistler Advanced Server, 32-bit file system drivers do not function correctly and must be ported to a 64-bit version. This issue will not be addressed in a future release.

Applies to scenarios: improving user experience

On computers running Whistler Professional or Whistler Advanced Server, the .dll file name extension for 32-bit applications that installs an InProcServer dynamic-link library (DLL) does not function correctly. This is a design criterion of WOW64 in which mixed 32-bit and 64-bit DLLs within the same process are not permitted.

WOW64 is the 32-bit emulator that starts and runs Win32-based applications on 64-bit editions of Whistler. It is intended to run 32-bit personal productivity applications needed by software developers and administrators.

Most commonly, these are shell extensions that are loaded by Internet Explorer, which is 64-bit. The 64-bit Windows Installer can install 32-bit Microsoft Installer-based applications on 64-bit Whistler. This issue will not be addressed in a future release.

Applies to scenarios: improving user experience

On computers running Whistler Professional or Whistler Advanced Server, the 64-bit kernel cannot load or run 32-bit drivers. All kernel-mode drivers must be ported to 64-bit native code. Also, WOW64 cannot transparently thunk (call) one critical API for device drivers. The API is NtDeviceIoControlFile() (also known as Win32 DeviceIoControl()). This API is highly polymorphic and depends entirely on the implementation of the kernel-mode driver being called. The 64-bit driver must identify that it might be called from a WOW64 process and that the input/output control (IOCTL) data buffers might contain data formatted using 32-bit data types. This issue will not be addressed in a future release.

Applies to scenarios: improving user experience

The 64-bit browser that is the installed with computers running the 64-bit editions of Whistler Professional or Whistler Advanced Server will not load 32-bit plug-ins. However, a 32-bit edition of Internet Explorer ships with 64-bit editions of Whistler.

This file is the 32-bit edition of Internet Explorer. Use this browser to visit Web sites which contain 32-bit plug-ins. This issue will not be addressed in a future release.

Applies to scenarios: improving user experience

For more information, contact the software vendor. This issue will not be addressed in a future release.

Applies to scenarios: improving user experience

32-bit server applications are not supported on Whistler Professional or Whistler Advanced Server. This issue will not be addressed in a future release.

Applies to scenarios: improving user experience

Applies to scenarios: improving user experience

Applies to scenarios: improving user experience

Applies to scenarios: improving user experience

Applies to scenarios: improving user experience

Applies to scenarios: improving user experience

Applies to scenarios: improving user experience

On computers running Whistler Professional or Whistler Advanced Server, when you restart your computer after the pcAnywhere 9.2 installation, the computer stops responding when the user logs on. Safe mode does not function correctly as well. This issue will not be addressed in a future release.

Applies to scenarios: improving user experience

On computers running Whistler Professional or Whistler Advanced Server, the Setup program that the PowerPoint 2000 Pack and Go uses is a 16-bit application. This issue will be addressed in a future release.

Applies to scenarios: improving user experience

On computers running Whistler Professional or Whistler Advanced Server, during Setup of VMware 2.03, you might receive the following message: "No Ethernet adapter cards were located on your system. This may be due to improper installation of an adapter. The network adapters on your system will be rescanned and any with an unspecified media type will be presented for use in bridge networking. Beware that Ethernet adapters can be used with bridged networking support. If you select a non-Ethernet adapter the service will not function correctly." This issue will not be addressed in a future release.

Applies to scenarios: improving user experience

On computers running Whistler Professional, Whistler Advanced Server, or Whistler Datacenter Server, using Folder Redirection in conjunction with an encrypted Offline File cache can cause the following issues:

These issues will be addressed in a future release.

Applies to users: administrators

Applies to scenarios: improving user experience

Master Boot Record

On computers running Whistler Advanced Server or Whistler Datacenter Server, cluster disks on a shared bus must be partitioned as master boot record (MBR) disks and not as globally unique identifier (GUID) partition table (GPT) disks. This issue will not be addressed in a future release.

If the cluster is installed with GPT shared disks, the cluster creates a failed disk resource. To work around this issue, delete the failed disk resource, convert the disk resources to MBR, and then add the MBR disk resources by using Cluster Administrator.

Applies to users: administrators, OEMs

QLogic Drivers

On computers running Whistler Advanced Server or Whistler Datacenter Server, QLogic 2100 and QLogic 2200 drivers are not supported on Windows Clustering configurations.

Applies to users: administrators, developers, OEMs

Applies to users: administrators, developers

This issue will be addressed in a future release.

Applies to scenarios: improving user experience, improving technology

System Sounds

On computers running Whistler Professional, all Whistler system sounds are played as "ding." This issue will be addressed in a future release.

Applies to scenarios: improving user experience

On computers running Whistler Professional or Whistler Advanced Server, because debugging tools are turned on and the current operating system code contains numerous breakpoints to catch bugs, it is relatively easy to cause the operating system to stop responding by setting illegal register values, executing illegal instructions, and so on. These actions might cause the operating system to stop at a kernel-mode breakpoint or cause the operating system to stop responding. These operating systems should not be deployed in environments where these actions might result in loss of data or in which unauthorized personnel can gain access to the computer.

To work around this issue, turn off the kernel debugger. You can do this by removing the proper start options in the Start Manager. This might reduce the probability of problems caused by these debugging tools. This issue will be addressed in a future release.

Applies to users: developers, OEMs

Applies to scenarios: improving technology

Computers running Whistler Professional, Whistler Advanced Server, or Whistler Datacenter Server support the Extensible Firmware Interface (EFI) specification version 1.02. This issue will not be addressed in a future release. Please treat specification noncompliance issues as bugs and report them to the Windows Beta Web site at:

Applies to users: administrators, OEMs

Applies to scenarios: improving technology

The Home Networking technologies (Internet Connection Sharing, Internet Connection Firewall, Network Bridge, Discovery and Control, Home Networking Wizard) are not available on Itanium-based systems. This issue will not be addressed in a future release.

Applies to scenarios: improving technology

Support for IPX/SPX networking protocol is not implemented in Whistler Professional, Whistler Advanced Server, or Whistler Datacenter Server. To work around this issue, use x86-based (32-bit) hardware for IPX/SPX functionality. This issue will not be addressed in a future release.

Applies to users: administrators

Applies to scenarios: improving user experience

On computers running Itanium-based versions of Whistler, you must install the operating system to the first data partition on the GPT disk. Failure to do so can result in an installation that will not start. This issue will be addressed in a future release.

Applies to users: administrators

Applies to scenarios: improving user experience

Microsoft virtual machine for Java (Microsoft VM) is no longer included with Whistler Itanium-based operating systems.

Applies to users: administrators, developers, OEMs

On computers running Whistler Professional, Whistler Advanced Server, or Whistler Datacenter Server, the following printers do not work in the 64-bit versions of Whistler:

This issue will be addressed in a future release.

Applies to scenarios: improving user experience

The 64-bit editions of Whistler Professional, Whistler Advanced Server, or Whistler Datacenter Server, do not support the Schlumberger smart card Cryptographic Service Provider (CSP) shipped with the product. These problems do not affect the 32-bit editions of Whistler. This issue will be addressed in a future release.

Applies to scenarios: improving user experience

On computers running Whistler Professional, Whistler Advanced Server, or Whistler Datacenter Server, when a 64-bit program does not function correctly, error reporting prompts the user to connect to the Internet even when there is a previously established active Internet connection. Error reporting fails to send a report.

Applies to users: OEMs