Data Bases • Custom Term Papers • Free Term Papers • Free Research Papers • Free Essays • Free Book Reports • Plagiarism? Links • Top 100 Term Paper Sites • Top 25 Essay Sites • Top 50 Essay Sites • Search 97,000 Papers @ DirectEssays.com • Search 101,000 Papers @ ExampleEssays.com • Search 90,000 Papers @ MegaEssays.com Free Essays • Term Paper Sites • Chuck III's Free Essays • Free College Essays • TermPaperSites.com • My Term Papers • Get Free Essays • Essay World • Planet Papers

Search Lots of Essays Back to Subjects - Technology winxp winxp 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. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. Whistler Beta 1 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.  2000 Microsoft Corporation. All rights reserved. Microsoft, MS-DOS, Windows, Windows NT, Active Directory, ActiveX, DirectX, MSN, Outlook, PowerPoint, Visio, Visual Basic, Visual C++, Visual FoxPro, Visual Studio, and Windows Media are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. Issues for Itanium-based Versions Only Welcome to the Beta 1 release notes for Microsoft Whistler Personal, Whistler Professional, Whistler Advanced Server, Whistler Professional for Intel Itanium systems, and Whistler Advanced 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. There are several release notes files on your Beta 1 compact disc (CD): • Read1st.txt (important preinstallation information, located in the Whistler CD root directory) • Setup text file series located in the Setuptxt folder on your Whistler CD • Readme Notes (compatibility and postinstallation notes, located on your Desktop) • Featguid.doc (what's new in this release, located in the Whistler CD root directory) 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. Applies to: general users, administrators, developers, specialists Outlook 2000 Service Release 1 - File Types On computers running Whistler Personal and Whistler Professional, when opening an attachment in Outlook 2000 Service Release 1 (SR-1) that does not have a recognized file type, instructions for registering the file type appear. The instructions are not correct. 1. On the desktop, double-click My Computer. 2. On the Tools menu, click Folder Options. 3. On the File Types tab, click New. 4. In the File Extension text box, type the attachment file type. 5. To register the file type, click OK. Applies to: general users, administrators On computers running Whistler Advanced Server, performing a restore of the System State using Ntbackup.exe and the default restore options results in an authoritative restore of the SYSVOL data. This restored SYSVOL data overwrites any changes to SYSVOL data that have been made since the backup and could adversely affect Group Policy. To work around this issue, run the nonauth_sysvol_wrdaround.ini file using Regini.exe, which sets the correct registration key value so that the SYSVOL data is restored non-authoritatively. This key must be set after the restore has finished but before the Ntbackup.exe application has closed. This is because Backup commits the merged (restored plus current) registry when it closes and any changes made after that are ignored. If you have missed this window, unplug any netcards as a precaution, restart in DS Restore Safe Mode again, and then repeat the restoration using Ntbackup.exe. After you have set the registry key at the appropriate time, you can close Ntbackup.exe and restart in normal mode. You can ensure that the restoration of the Sysvol data was non-authoritative by checking the Sysvol root folder after the computer starts in normal mode again. By default, the root Sysvol folder is located at windirSysvol. Instead of seeing a Policies and Scripts folder at windirSysvolDomain, you should see a folder titled NtFrs_PreExisting___See_EventLog. This folder contains the restored Sysvol data and indicates that a non-authoritative restore of the SYSVOL was performed. If you have disconnected the netcards for this domain controller, you can now reconnect them and domain controller will resynchronize all the current SYSVOL data from a partner domain controller. HKEY_LOCAL_MACHINESystemCurrentControlSetServicesNtFrsParametersBackup/RestoreProcess at StartupBurFlags It should have the value 0D2, but by default only has 00. Group Policy Microsoft Management Console Snap-in The Group Policy Microsoft Management Console (MMC) snap-in cannot connect to a remote computer when NetBIOS is disabled instead of TCP/IP. This issue will be addressed in a future release. The following Group Policy issues apply to computers running Whistler Professional or Whistler Advanced Server. These issues will be addressed in a future release. Resultant Set of Policy - Delegation Support Delegation support does not operate correctly for Resultant Set of Policy cross domains. In the Resultant Set of Policy snap-in, the messages displayed by the incorrect property page for folder redirection are not the same as those in the event log. Startup and Logon scripts do not run if the client computer is also the server hosting the scripts. The following issues apply to software deployment. • If the software installation cannot deploy a program, a message appears stating that it cannot extract deployment information from the package. This can occur if the program was deployed locally to your computer and if you are not logged on as a local administrator. To work around this issue, use a computer that does not deploy that program. • Add or Remove Programs might not list any programs even though programs are deployed on that computer. • If a roaming user logs on to a different computer right after a Group Policy object (GPO) containing the program has been removed from scope, the program is not uninstalled. • If you publish a program as a required upgrade to another program, and mark it as not visible in Add or Remove Programs, the old version of the program is still visible in Add or Remove Programs. • While roaming between x86-based and Itanium-based computers, when returning to an Itanium-based computer after having visited an x86-based computer, the Itanium-based programs might become uninstalled. • In Resultant Set of Policy Planning Mode, if access to a program is modified on the access control list by using Software Installation and this causes a user to be denied access to the program, the Resultant Set of Policy planning view still displays the program as being available to the user. • If a program has an optional upgrade, the Resultant Set of Policy user interface does not correctly display that the program is available to the user. • The Resultant Set of Policy user interface is missing items in context-sensitive Help. On computers running Whistler Professional and Whistler Advanced Server, when using Group Policy to manage Terminal Services settings, the Group Policy object named Limit users to one remote session is not yet functional. This Group Policy object is located in the console tree under Local Computer Policy, under Computer Configuration, under Administrative Templates, and in the Terminal Services folder. This will be addressed in a future release. Windows Management Instrumentation Filters Windows Management Instrumentation (WMI) filters do not operate correctly when applied to a Group Policy object (GPO) that is linked across domains. On computers running Whistler Professional or Whistler Advanced Server, Poledit.exe is not yet fully functional. If you need to deploy System Policy from a server running Whistler, then obtain a copy of Poledit.exe from the Windows 2000 Server CD and use that version of Poledit.exe to create a policy file to deploy System Policy. This issue will be addressed in a future release. For more information about deploying System Policy, visit the Microsoft Windows 2000 technical library at the Microsoft Web site at: http://www.microsoft.com/windows2000/library/ Logging on to or Logging off from Terminal Server When a user encounters a profile error while trying to log on to or log off from a Terminal server, no message is displayed to the user. The correct message is written to the program's event log. On computers running Whistler Personal, Whistler Professional, or Whistler Advanced Server, the Temp directory has the Read Only attribute selected, which might cause application installations to function incorrectly. To work around this issue, if you encounter installation problems, manually clear the Read Only attribute from the Temp directory before installing an application. Applies to: general users, administrators On computers running Whistler Professional or Whistler Advanced Server, you cannot administer Windows 2000 COM+ from the Component Services administrative tool. This issue will be addressed in a future release. Message Queuing supports sending messages to queues on the Internet and Intranet by introducing a URL-style format name DIRECT=HTTP://sitenamemsmqqueuename Note the mandatory msmq component in the name. In this Beta 1 release, name components must be separated by a backward slash rather than a forward slash. This will be addressed in a future release. For Message Queuing to support Internet and intranet messaging using the URL-style of queue naming, the Internet Information Services (IIS) component must be installed and properly configured. When upgrading a computer running Windows 2000 or Windows NT 4.0 to Whistler Professional or Whistler Advanced Server, Message Queuing does not install or configure IIS with the Message Queuing extension. The Message Queuing Internet Messagingis therefore disabled. This will be addressed in a future release. Important Message Queuing and IIS services must be installed before extension configuration. To configure the Message Queuing IIS extension 1. Create a %windir%System32MsmqWeb folder for the Message Queuing IISapplication. 2. On the desktop, right-click My Computer, and then click Manage. 3. Double-click Services and Applications. 4. Double-click Internet Information Services. 5. Right-click Default Web Site, point to New, and then click Virtual Directory. The Virtual Directory Creation Wizard opens. Click Next. 8. In the Directory text box, type the full path to the Web directory that was created in Step 1 (typically C:WindowsSystem32MsmqWeb). 10. On the Access Permissions page, clear all check boxes, and then select Execute. 11. Click Next, and then click Finish. 12. Right-click the created MSMQ virtual directory, click Properties, and then click Create. 13. On the Virtual Directory tab, clear the Log visits check box. 15. In the Application Configuration dialog box, click Add, and then click the Mappings tab. 16. In the Add/Edit Application Extension Mapping dialog box, in the Executable text box, type the full path to Mqise.dll (typically C:WindowsSystem32Mqise.dll). 17. In the Extension text box, type: 18. Select Limit to, and in the adjacent text box, type: 19. Click OK three times to close all the open dialog boxes. The Message Queuing IIS extension is created. In this Beta 1 release, message destination, response, or administrative format names can address multiple queues. The information about the multiple queues for any of these format names does not reach an Internet destination, but only the first queue. For example, an acknowledgment generated at the destination is sent only to the first queue on the admin format name. This will be addressed in future release. Applies to: administrators, developers, specialists The following Message Queuing issues apply to Whistler Professional, and Whistler Advanced Server. Message Queuing also supports sending messages to distribution lists (DL) hosted in the Active Directory as objects in the group class. Usage and format are similar to that of Public Queues: DL=GUID. Furthermore, a quote-enclosed list of comma-delimited destinations, in various formats, can be constructed for the destination parameter of a send (For example, "DIRECT=OS:ComputerQueue,PUBLIC=GUID,DL=GUID"). This method is referred to as Multiple Queue Format. 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 MMC snap-ins. The following issues apply to Whistler Professional, and Whistler Advanced Server. • Messages cannot be sent to a distribution list in an explicit domain using the format DL=GUID@domain. This will be addressed in a future release. • Authenticated messages cannot be sent to multiple format names. Only the message to the first format name is signed, and an acknowledgment with an invalid signature is returned. This will be addressed in a future release. Applies to: administrators, developers, specialists 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. Message Queuing does not support the Internetwork Packet Exchange (IPX) network protocol. Applies to: administrators, developers, specialists 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. This feature is not currently functional. It will be addressed in a future release. • Distribution lists only work within domain boundaries (where no access to a global catalog is required). This will be addressed in a future release. Applies to: administrators, developers, specialists Message Queuing Support for Earlier Versions Message Queuing configured as Dependent Client 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 Client, Dependent Client, and Routing Server, as long as they are not in an MSMQ 1.0 domain. MSMQ 1.0 domains cannot be upgraded to Whistler. This will be addressed in a future release. Message Queuing does not function with MSMQ 1.0 Controller Server (on Windows NT 4.0). This will be addressed in a future release. To work around this issue, you can try one of two suggested approaches: • Create a new Message Queuing Enterprise by using a Windows 2000 or Whistler domain controller. Message Queuing does not require MSMQ server to be installed on the domain controller Or, migrate the MSMQ 1.0 Controller Server (primary enterprise controller, primary site controllers, and backup site controllers) to Windows 2000. Clients using earlier versions can access to Active Directory using the new Message Queuing Directory Service. This service is only required for the mentioned functionality and can be safely stopped if not needed without affecting other Message Queuing functionality. Applies to: administrators, developers, specialists In MSMQ 1.0 and MSMQ 2.0, the Triggers interface is an add-on module and is delivered in the operating system Software Development Kit. For the Whistler Beta 1 release, the Message Queuing Triggers interface is incorporated into the core product and delivered on the Whistler CD. The Message Queuing Triggers interface is not supported in a Whistler cluster. This will be addressed in a future release. Applies to: administrators, developers, specialists Message Queuing COM does not support Multiple Queue Format addressing through the MSMQQueueInfo.FormatName property. To utilize Multiple Queue Format addressing, use the new object MSMQDestination introduced in Whistler. To work around this issue, set MSMQDestination.FormatName to a multiple-queue format name and pass the object to MSMQMessage.Send. You can optionally call MSMQDestination.Open before passing it to MSMQMessage.Send. Applies to: administrators, developers, specialists 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. Queue aliases are not supported within distribution lists. This will be addressed in a future release. Applies to: administrators, developers, specialists Enabling a Message Queuing on a Domain Controller Message Queuing Server running on a Whistler domain controller provides support for a Message Queuing dependent client. To enable a Message Queuing Server on a Whistler domain controller 2. To open the Component Services snap-in, click Start, point to Programs, point to Administrative Tools, and then click Component Services. 3. In the console tree, click Component Services. 4. On the toolbar, click Configure Microsoft DTC. 5. In the MSDTC dialog box, click Stop, and then click Security Configuration. 6. In the Security Configuration dialog box, select the Network DTC Access check box, and then the Network Transactions check box, and then click OK. 7. In the MSDTC dialog box, click Start to restart MS DTC, and then click OK. Applies to: administrators, developers, specialists In this Beta 1 release, the Message Queuing resource on a virtual server in a server cluster cannot connect to the Microsoft Distributed Transaction Coordinator (MS DTC) resource in the cluster by default. For this reason, the Message Queuing resource does not come online until the MS DTC cluster resource is configured to accept such a connection. 1. If a local quorum resource is present in the target group, delete it. Ensure that the Physical Disk resource is the quorum resource in the cluster. 2. Create an MS DTC cluster resource. 3. Open the Component Services snap-in. 4. In the console tree, double-click Component Services, and then double-click Computers. 6. On the toolbar, click Configure Microsoft DTC. 7. In the MSDTC dialog box, click Security Configuration. 8. Under DTC logon account, in the Account text box, type: 10. In the MSDTC dialog box, stop and restart the DTC by clicking Stop and then Start. 12. In the Security Configuration dialog box, select the Network DTC Access check box, and then the Network Clients check box, and then click OK. 13. In the MSDTC dialog box, stop and restart the DTC by clicking Stop and then Start, and then click OK. 14. Close the Component Services snap-in. The following issue applies to computers running Whistler Advanced Server in a server cluster configuration. In this release, the HTTP protocol is not supported on either the nodes or virtual servers of a server cluster. During Message Queuing setup on a node, the following message might appear. "Unable to create application for MSMQ IIS extension /LM/W3Svc/1/Root/MSMQ. To work around this issue, you can configure HTTP support for Message Queuing manually as detailed elsewhere in these Release Notes, but it might not function correctly. Applies to: administrators, developers, specialists To open Help for Message Queuing, locate and open the file Msmq.chm in the windirHelp folder (typically C:WindowsHelpMsmq.chm). In a future release, you will be able to open Help by using the Start menu. Applies to: general users, administrators, developers, specialists Message Queuing on Whistler Personal is not supported. If you run MSMQ 1.0 on Windows 95, Windows 98, or Windows Millennium Edition, upgrade to Whistler Professional in order to continue to use Message Queuing. Applies to: administrators, developers, specialists Microsoft Distributed Transaction Coordinator The following issues apply to Microsoft Distributed Transaction Coordinator (MS DTC). On computers running the Cluster services on Whistler Professional or Whistler Advanced Server, if MS DTC clients select the Use Network Name option in the 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. On computers running Whistler Professional or Whistler Advanced Server, MS DTC does not support rolling upgrades on the Cluster services clusters. 2. Upgrade MS DTC on all nodes in the cluster. On computers running Whistler Professional or Whistler Advanced Server, the following issues apply to COM+ partitions. Administration of Base Application Partition To administer programs in the base program partition, you must be a global administrator. An administrator of any partition can modify roles and role memberships of any program in any partition. The only exception is the role memberships on the system program. If users are given reader access to any partition, then they have reader access to all partitions. Also, an administrator of any partition has reader access to all partitions. The debugging of Visual Basic (VB) programs that are in a partition is not supported at this time. To work around this issue, for VB program development, debug and test the program in the base program partition. After development is complete, move the program to another partition. In releases prior to Window 2000, the registry key HKEY_LOCAL_MACHINESOFTWAREMicrosoftTransaction ServerLocal ComputerMy Computer specified which Oracle client libraries should be used by COM+ to communicate with Oracle. On computers running Whistler Professional or Whistler Advanced Server, the registry key HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSDTCMTxOCI specifies which Oracle client libraries should be used by COM+ to communicate with Oracle. For more information, visit online product support at the Microsoft Web site at: http://search.support.microsoft.com/ Component Services Administrative Tool 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 Microsoft 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. On computers running Whistler Professional or Whistler Advanced Server, administrators cannot access the MS DTC property sheet by clicking Properties on 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. MS DTC does not support MSCS 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. On computers running Whistler Professional or Whistler Advanced Server, by using MS DTC you can disable certain features such as Transaction Internet Protocol (TIP), 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 NetworkService 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 disabled on all installations. In addition, on domain controllers, XA and Network Transactions are also disabled. These features are important because the administrator needs to enable features before existing client software is supported. If you have a single-node cluster and the MS DTC log is on the local quorum disk on computers running Whistler Professional or Whistler Advanced Server, the MS DTC resource might not come online. • Run the MS DTC service as LocalSystem. Or, delete the log file in winntSystem32MsDTCMsdtc.log. Active Directory Setup/Install (DCPROMO) At least one domain controller in an existing Windows 2000 Active Directory forest must be upgraded to Whistler before any new Whistler domain controllers can be added to the forest. This is necessary in order to upgrade the schema of the forest to a Whistler-compatible schema. If you attempt to add a Whistler domain controller as a new domain controller, new tree root domain domain controller, or new child domain domain controller to an existing forest without upgrading at least one Windows 2000 domain controller first, you receive the following message:"The following error occurred. A schema validation check failed. If this is a mismatch, please upgrade your build. This occurs because a schema mismatch is detected between the source and the build used during a replica install. The replica cannot be installed." Domain Controller Locator - Global Catalog 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. I. If there is a domain controller in the same site where the renamed domain controller resides, then: 1. Set a lower priority in the service location (SRV) records registered by a renamed domain controller by using Registry Editor and setting the REG_DWORD value LdapSrvPriority under HKEY_LOCAL_MACHINE/SYSTEM/CCS/Services/Netlogon/Parameters to the value greater than that used by other domain controllers in the domain (or if the renamed domain controller is a global catalog, then also greater than that used by other global catalogs in the forest). If the value is not specified on some domain controllers/ global catalogs, then they register SRV records using the default value of Priority = 0. 2. After Active Directory replicates the updated Service Principal Name value to other domain controllers in the domain and global catalogs in the forest, set the REG_DWORD value LdapSrvPriority under HKEY_LOCAL_MACHINE/SYSTEM/CCS/Services/Netlogon/Parameters to the previous value. If the previous value was not specified, then delete the value from the registry. II. If there is no domain controller in the same site where the renamed domain controller resides, then 1. To pause Netlogon on the renamed domain controller, at the command prompt, type: 2. Ensure that new Service Principal Name value corresponding to the new computer name of the domain controller replicates to all the domain controllers in the same domain and all the global catalogs in the forest (Note: SPN values do not propagate immediately to the replica domain controllers and global catalogs because of the Active Directory replication latency). 3. To resume Netlogon, at the command prompt, type: Caution While Netlogon is paused, the domain controller is not discoverable by other devices as the domain controller for the domain. It also does not pass through the NTLM authentication requests directed to other domains. Domain Controller Locator - Group Policies for Netlogon On computers running Whistler Advanced Server, all of the Netlogon Group Policies that are in the Group Policy Edit UI do not function correctly. To work around this issue, continue using corresponding registry values to configure Netlogon parameters. This issue will be addressed in a future release. The Beta 1 release for Whistler Personal, Whistler Professional, and Whistler Advanced Server contains new Help topics as well as Help topics from Windows 2000. Many of the new topics have not yet been edited or reviewed for technical accuracy. Due to product changes, legacy topics might no longer be accurate. The Help topics are preliminary and subject to change. As this product progresses through the development cycle, various functions might change and specific components or functionality might be added or removed. Documentation of a particular component or function in this Beta 1 release does not guarantee that this particular component or function will be included in the final version of the product. Applies to: general users, administrators, developers, specialists The online documentation for Whistler contains references to Whistler Professional, 64-Bit Edition and Whistler Advanced Server, 64-Bit Edition. These references should read Whistler Professional for Intel Itanium systems and Whistler Advanced Server for Intel Itanium systems. This issue will be addressed in a future release. Applies to: general users, administrators, developers, specialists On computers running the Beta 1 release for Whistler Professional for Intel Itanium systems and Whistler Advanced Server for Intel Itanium systems, neither Backup, Restore, nor Automated System Recovery (ASR) function. Removing only one piece of media from a library backup might result in a loss of data. If you remove the first piece of media from a spanned save set and then open Removable Storage Managementand select Delete Media From System on any of the other elements of that save set, all remaining media belonging to that save set will be erased. When backing up to an 8 mm AME (advanced metal evaporated) tape on an Exabyte 220 changer, Backup displays a message reading "Write file mark." To workaround this issue, upgrade the firmware to version 6.4.3. If you attempt to restore files to a Microsoft Exchange Server, the exchange service must be running Otherwise, no options will appear. Only members of the Administrators group can back up or restore anything other than data volumes, including the system volume or System State. Applies to: general users, administrators Automated System Recovery (ASR) supports only basic disks in this Whistler Beta 1release. To manually restore a complete system from tape, you must first complete a minimal installation of Windows 2000 in the same directory as the previous installation. If the directory or drive is different, the system restore will not function. On an unformatted disk, the initial installation must be into the default directory. If the previous installation was not made to the Winnt directory, perform a second minimal installation in that location. If there is one installation already on the disk, indicate whether you want to overwrite the current installation or install to an alternate location. Applies to: general users, administrators Dynamic disks on Itanium-based systems are limited to data disks only. System/boot disks must be basic. Both MBR and GPT disks may be dynamic. Data partitions on basic disks that are converted to dynamic simple data volumes may 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 may be extended. Data partitions on dynamic disks can no longer be installation targets. You can install Whistler to 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. Whistler does not support legacy Windows NT 4.0 Ftdisk volume sets. If you are running Windows 2000, you must convert all Ftdisk volume sets to dynamic volumes before upgrading. If you are running Windows NT 4.0, you should break any mirrors and backup all data on stripe, RAID5, or extended volume sets before upgrading. Ftdisk sets may not be accessible after the upgrade. The Logical Drive snap-in has been removed from Whistler. To manage local disks, use Disk Management. To manage file shares, use the Shared Folders snap-in. ATI Rage 3 Driver Does Not Enter Standby On computers running Whistler Personal, Whistler Professional, or Whistler Advanced Server, the driver for ATI Rage 3-based hardware cannot go into the power management mode Suspend-to-Ram state (S3). A message appears stating that the driver cannot go into standby operation. Hardware affected includes the ATI Rage Mobility M/P, the ATI Rage LT Pro, and the ATI Rage XL. This issue will be addressed in a future release. Applies to: general users, administrators, specialists Limited Support for Matrox Four Port Display Adapters On computers running Whistler Personal, Whistler Professional, or Whistler Advanced Server, Matrox display adapters with four ports display video only on the primary VGA port. All other ports on the adapter do not function correctly. This issue will be addressed in a future release. Applies to: general users, administrators, specialists VGA Driver Does Not Support Power Management If there is no driver for the installed display adapter on computers running Whistler Personal, Whistler Professional, or Whistler Advanced Server, the adapter uses the default VGA driver, which does not support power management. To work around this issue, the user should install a driver for the display adapter that does support power management and restart the computer. This issue will be addressed in a future release. Applies to: general users, administrators, specialists On computers running Whistler Personal, Whistler Professional, or Whistler Advanced Server, after performing a Disable/Enable or Remove/Refresh operation on a 1394 host controller in Device Manager, the user is prompted to restart the computer. This prompt is an error, and no restart is necessary. To work around this issue, cancel the restart prompt to resume normal operations. This issue will be addressed in a future release. On computers running Whistler Personal, Whistler Professional, or Whistler Advanced Server, remote wake does not function for USB input devices. This issue will be addressed in a future release. The driver file E1000nt5.sys has compatibility problems with Intel Gigabit and Compaq Gigabit network interface cards (NIC). Computers running Whistler Personal, Whistler Professional, or Whistler Advanced Server and using Intel and Compaq Gigabit adapters might encounter devices that are disabled. Upon restart, they might not function correctly. This will be addressed in a future release. Applies to: general users, administrators On computers running Whistler Personal, Whistler Professional, or Whistler Advanced Server, system hibernation is enabled by default. Hibernation requires disk space that matches your system's memory configuration. If you don't plan to use hibernate, you can recover this disk space by disabling the hiberation feature. To work around this issue, follow the procedure below. 1. In Control Panel, in the Simple Control Panel view, click Performance and Maintenance. 3. On the Hibernate tab, clear Enable hibernate support. When detecting or loading the mini-port drivers on some RAID controller models, computers running Whistler Personal, Whistler Professional, or Whistler Advanced Server require a full Plug and Play compatible ID match for Vendor ID, Device ID, Sub-Vendor ID, and Subsystem ID in Txtsetup.sif and Scsi.inf to be detected and configured with the drivers sold with the product. This might cause some controllers or chip sets that were detected as compatible in Windows NT 4.0 or Windows 2000 to not be detected and configured by Whistler. To work around this issue, the user must contact the vendor for an updated driver and the Txtsetup.oem files for these undetected chip sets. To load the updated driver file and Txtsetup.oem files 1. Insert the Whistler Beta 1 CD into the computer's CD-ROM drive. 2. Restart or turn on the computer. Your computer should start using the Whistler Setup CD. 3. After the message "Setup is inspecting your computer's hardware configuration" is displayed, the screen turns blue and displays "Press F6 if you need to install a third-party SCSI or RAID driver". Press F6. 4. To specify an additional device, press S. 5. Insert the diskette containing the updated driver file and Txtsetup.oem files you received from the vendor. To continue Whistler Setup, follow the instructions that appear. This issue will be addressed in a future release. Applies to: general users, administrators, specialists USBReady, a program that tests whether or not your system has functional USB ports, does not function on computers running Whistler Personal, Whistler Professional, or Whistler Advanced Server. Please refer to your product documentation to confirm that the USB controller is enabled in the basic input/output system (BIOS), or look under "Universal Serial Bus Controllers" in Device Manager to determine whether your USB controller is operating correctly. On computers running Whistler Personal, Whistler Professional, or Whistler Advanced Server, if the maximum power requirement of the USB port is exceeded, users might not receive a warning message. Users do receive warning messages for exceeding bandwidth on the USB device. This issue will be addressed in a future release. Applies to: general users, administrators Active Directory Installation Wizard On computers running Whistler Professional, the W3SVC (WWW) and SMTP services do not always restart after the Active Directory Installation Wizard runs. The event log on the domain controller states that the Internet Information Services Administrator Service (IISADMIN) service stopped responding during startup. This issue occurs only after you run the Active Directory Installation Wizard, restart IISADMIN, and then promote or demote a domain controller. • Restart Internet Information Services (IIS) by running the IIS snap-in. This issue will be addressed in a future release. On computers running Whistler Professional or Whistler Advanced Server, valid client certificates fail after Internet Information Services (IIS) is configured to require them. Because the Verisign root certificate (or any intermediate) does not contain a certification revocation list (CRL) distribution point, an IIS nonvalid message appears. To work around this issue, manually install the CRLs in the registry under HKEY_LOCAL_MACHINE for Intermediate Certification AuthoritiesCertificate Revocation List. This issue will be addressed in a future release. Applies to: administrators, developers When upgrading from Windows 95, Windows 98 or Windows 2000 to Whistler Professional or Whistler Advanced Server, Internet Information Services (IIS) is installed by default. To work around this issue, you can remove IIS by using Add or Remove Programs in Control Panel. This issue will be addressed in a future release. On computers running Whistler Advanced Server, Network News Transfer Protocol (NNTP) posting does not function using the default settings. To work around this issue, you must give the Everyone group permission to write to the InetpubNNTPfile directory. This will be addressed in a future release. On computers running Whistler Professional and Whistler Advanced Server, Iissync.exe, a command-line utility for replicating the metabase and other configuration settings from one server node to others, does not function properly. There is no workaround for this issue. This will be addressed in a future release. On computers running Whistler Professional or Whistler Advanced Server, the Secure Sockets Layer (SSL) certificate cannot import valid files in Personal Information Exchange (.pfx) format. When programmatically creating and importing a .pfx file to be used for SSL certificate installation, IIS does not properly access the file. var objScriptUtil = new ActiveXObject( "MSUtil.ScriptUtil"); var objCert = new ActiveXObject( "CertObj.IISCertObj" ); strPfx = objScriptUtil.ContentDir + "ssl.pfx"; WScript.Echo("Importing " + strPfx + " in Default Web Site" ); objCert.Import( strPfx, "1", "ssl" ); There is no workaround for this issue. It will be addressed in a future release. Applies to: administrators, developers The following home networking issues apply to computers running Whistler Personal, Whistler Professional, or Whistler Advanced Server. You cannot enable a personal firewall or Internet connection sharing (ICS) for a custom dial-up connection, such as those provided by Connection Manager (CM), Microsoft Network, America Online and some other third party dialers. These connections do not display a Sharing or Personal Firewall tab. ICS does not have the level of application compatibility support for games and applications that is provided in Windows Millennium Edition. For the Whistler Beta 1 release, the level of application compatibility for applications used by ICS computers is equal to that of Windows 2000. Automatic dialing only functions when a user with administrative rights is locally logged on to the ICS host. Name resolution for hosts on the local network is not implemented for computers running Whistler, so the level of functionality is the same as Windows 2000 ICS, but less than Windows Millennium Edition ICS. Clients that rely on DNS for name resolution on the local network cannot perform name resolution. This might also lead to the ICS host dialing out to the Internet. To work around this issue, use the client's IP address when attempting to access file and printer shares. Users cannot bridge network traffic between IEEE 802.11 wireless adapters and other networks. This will be addressed in a future release. Users that bridge IEEE1394 devices with another network cannot see beyond their local subnet. For example, users see computers on the bridged network, but cannot browse the Internet if they are bridged behind an ICS host. This will be addressed in a future release. Personal Firewall -Clients Using an ICS host When an ICS host has the Personal Firewall enabled (as recommended), DirectPlay games do not work through the ICS host for client computers. To work around this issue, the ICS host should not enable the Personal Firewall. If your computer has the Personal Firewall enabled, Internet Control Message Protocol (ICMP) message types 3, 4, 5, 8, 10, 11, 12, 13, 17 are blocked. This means, for example, you cannot ping your computer from the Internet. This will be addressed in a future release. ICS host settings are not be preserved when upgrading an ICS computer from Windows 98 Special Edition, Windows Millennium Edition or Windows 2000 to Whistler. Users need to manually enable and configure ICS after the upgrade. Computers running Whistler Personal, Whistler Professional, or Whistler Advanced Server implement adapter speed sensitive route metrics that allow the computers to select the fastest available adapter for network communications. As a result, default metrics are in the 10–50 range, depending on the adapter speed. Windows 2000 and earlier versions of Windows used the default metric of 1. Applies to: administrators, developers On computers running Whistler Personal, Whistler Professional, or Whistler Advanced Server, Internet Protocol version 6 (IPv6) support is available for use by software developers and for experimental deployment. For more information about Ipv6 Technology, visit the MSDN Online SDKs page at the Microsoft Web site at: http://msdn.microsoft.com/downloads/sdks/platform/ Applies to: administrators, developers When upgrading from any Windows operating system to Whistler Personal, Whistler Professional, or Whistler Advanced Server, the following networking protocols are removed: NetBEUI, AppleTalk (except server), and Data Link Control (DLC). These protocols implement non-Internet technologies and are no longer supported by Windows. • For DLC mainframe communication, install DLC protocol from the Host Integration Server 2000 CD. • For peer-to-peer and client/server networking, install TCP/IP protocol. • For network printing, enable TCP/IP printing on printers and servers. Applies to: administrators, developers The following issues apply to computers running Whistler Personal, Whistler Professional, or Whistler Advanced Server. Applies to: general users, administrators, developers New Connection Manager Administration Kit Wizard Features • The Connection Manager Administration Kit Wizard offers the option of including automatic proxy configuration in a service profile. • The Connection Manager Administration Kit Wizard offers the option of including routing table updates in a service profile that enables "split tunneling". • The Advanced Customization dialog box gives an administrator the option of editing .cms and .cmp files while building the service profile. New Connection Manager Client Features • Client-side log files for a connection can be created, viewed, and cleared by a user. • Client use of terminal windows during connection is supported for all Windows platforms except Windows 2000. • The Connection Manager client features the ability to define, save and apply "favorite" location properties and dialing rules as defined by the user. • The Connection Manager client supports the Callback feature. • Server/client authentication displays a Retry dialog box when the server rejects a connection because of a mistyped user name or password. Applies to: general users, administrators, developers • The remote access client supports the Point-to-Point Protocol (PPP) over Ethernet protocol for broadband connections. There is no server support for this protocol. • After a successful connection, the remote access client can cache the dial-in credentials that are used to access resources on the remote network. • After a successful connection, the remote access client issues DHCP-inform requests to obtain the DNS domain name of the network to which it is connected and to obtain routing information for that network. Applies to: general users, administrators, developers The Routing and Remote Access service now includes an Internet NetBIOS Over TCP/IP (NBT) gateway, which means remote access clients can access intranet resources by name without requiring a WINS or DNS server on the intranet. Applies to: general users, administrators, developers • The Switch User feature in Whistler Personal does not close any VPN or dial-in connections made by the previous user. All users have the same access allowed by that Remote Access service connection. For additional security, users should close connections after use. • Support for the NetBEUI protocol has been permanently deleted. • Support for the IPX protocol has been permanently deleted for Itanium-based systems. Applies to: general users, administrators, developers • The routing interface that sends packets in IP tunneled mode (IP-in-IP interface) is no longer supported. • NBT cannot be disabled for dial-up PPP connections. To limit the traffic that enables a dial-on-demand link, set IP demand-dial filtering on Ports 137, 138, and 139. Applies to: general users, administrators, developers On computers running Whistler Advanced Server, after forming a cluster on the first node, if a user attempts to add all remaining nodes in one additional step, then the cluster is not formed correctly. To work around this issue, add each remaining node into the cluster one at a time. This will be addressed in a future release. Applies to: administrators, developers, specialists Automated System Recovery (ASR) for cluster backup and restore is not supported in Whistler Advanced Server. This will be addressed in a future release. Applies to: general users, administrators, developers, specialists No program should be installed into the cluster group on computers running Whistler Advanced Server. There is a new resource in the cluster group called local quorum. To work around this issue, if a user wants to install SQL Server or any other program on the quorum disk, then the quorum disk needs to be moved out of the cluster group. Applies to: administrators, developers, specialists On computers running Whistler Advanced Server, if a user is logged on as the local computer administrator and attempts to create a new cluster, the user might receive the following message: "The selected domain could not be located." The message is generated because the domain could not authenticate the local user and not because the domain could not be located. The message does not reflect the nature of the problem. To work around this issue, the user must be logged on with a domain account in order to create a cluster. This will be addressed in a future release. Applies to: administrators, specialists On computers running Whistler Advanced Server, when the Cluster service is deleted from a node and then a subsequent attempt is made to re-form a cluster on that same node, a user might receive a message indicating that the service has been marked for deletion. This is a timing related issue between the service that is deleting cluster service and the service that is adding it. You should wait until the original delete request is completed. This will be addressed in a future release. On computers running Whistler Advanced Server, no quorum disk is selected if the shared storage bus is configured so that the last disk configured has two NTFS partitions that are each smaller than the partitions for the previous disks. This will be addressed in a future release. Applies to: administrators, developers, specialists SQL Server 2000 does not install on Whistler Advanced Server clusters if Terminal server is installed in application mode. If a user selects Terminal server during Whistler installation on a cluster, then SQL Server 2000 Setup might not function correctly. To work around this issue, do not select Terminal server from the installation choices during the Whistler setup process. If Terminal server is not selected, it is installed by default in remote administration mode (instead of application mode) and SQL Server 2000 setup functions correctly. This will be addressed in a future release of SQL Server. Applies to: administrators, specialists Windows Management Instrumentation provider for Cluster services is not supported in Whistler Advanced Server. This will be addressed in a future release. Applies to: general users, administrators, developers, specialists The following Remote Assistance issues apply to Whistler Personal, Whistler Professional, and Whistler Advanced Server. Remote Assistance connections might need to transfer your screen or file information. This transfer is limited by the bandwidth of the connection. Slower connections, such as those used by dial-up modems of 56 kilobits per second or less, can still use Remote Assistance, except when the desktop changes very often due to animated images, audio and visual movies, and so on. In these cases, there is far more data transfer and it takes significantly longer, degrading the response times correspondingly. When a request for Remote Assistance is sent, it contains the IP address of the computer from which it originates. This information allows the receiving computer to establish a connection to its caller. If the IP address of the requesting computer is changed (such as in a dial-up account or by DHCP), then the receiving computer cannot make a connection. The original computer should therefore keep the same IP address (for example, by not restarting) until the connection is made. Should an IP address change be unavoidable, then cancel the old request and send a new one. If the computer requesting Remote Assistance is behind a firewall, direct connection between computers might sometimes fail. The firewall might not allow the inbound connection for Terminal Services (by using Remote Desktop Protocol on Port 3389). Remote Assistance relies on the Terminal Services connection to function and is thus disabled. Connections to peers inside the same firewall (such as in a corporate intranet), however, are functional. Similarly, computers accessing help through the Internet can accept connections as long as they are not behind network address translation or firewall protection. To work around a firewall, the network administrator might choose to open Port 3389 and allow Remote Assistance and Terminal Services over their firewall. Alternatively, the administrator can give the party outside the firewall a limited privilege VPN login account into the intranet. This is the recommended solution for managed intranets where some support services are outsourced to engineers who are not on the same network. Once the engineers log on using the VPN account, they become part of the managed network and can directly provide Remote Assistance to computers on the intranet. Only one computer on an Internet connection sharing server can receive Remote Assistance from outside the local subnet. To change your configuration to accept Remote Assistance 1. In Control Panel, click Network and Internet Connections. 2. Click Network Connections, right-click Dial-up Connection, and then click Properties. 3. On the Properties page for the Dial-up Connection dialog box, on the Sharing tab, select Enable Internet Connection Sharing for This Connection. 4. Click the Settings button, click Services, and then click Add. 5. In the Internet Connection Sharing Service dialog box, perform the following procedure: a. In the Name of service text box, type: b. In the Service Port number text box, type: d. In the Name or address of server computer on private network text box, type: For the Whistler Beta 1 release, users must have Outlook installed on an Itanium-based computer in order to use Remote Assistance. This issue will be addressed in a future release. Applies to: general users, administrators Simple Messaging Application Programming Interface Remote Assistance requires an e-mail client that supports the simple Messaging Application Programming Interface (MAPI). Outlook, Outlook Express, and most 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 to send your invitation. Applies to: general users, administrators On computers running Whistler with a connection to the Internet (for example, a persistent connection such as DSL or cable modem), perform the following steps. 1. In Control Panel, open Network Connections. 2. Right-click on the connection, select Properties, and click the Personal Firewall tab. 3. Click the check box to enable the firewall, and then click OK. This will be handled by default in a future release. Computers with file sharing enabled on folders should disable File Sharing on Internet connections. 1. In Control Panel, open Network Connections. 2. Right-click Connection to the Internet, and then select Properties. 3. Clear File and Printer Sharing, and then click OK. This will be handled by default in a future release. On computers running Whistler Personal, Whistler Professional, or Whistler Advanced Server, the Everyone group no longer includes Anonymous users by default. This change reduces the number of network resources available by default to anonymous users and simplifies how network administrator control access by anonymous users. It is easier for administrators to configure a secure system because: • The default access control lists on earlier versions of Windows that granted the Everyone group access to resources and potentially exposed them to attack does not grant this access to Anonymous users after the computer is upgraded to Whistler. • Anonymous users cannot be accidentally granted access to resources as in the past when administrators did not realize that Anonymous users were in the Everyone group. This change impacts Anonymous users attempting to access resources hosted on computers running Whistler. When a Windows 2000 system is upgraded to Whistler, resources with access control lists that grant access to Everyone (and not explicitly to Anonymous Logon) are no longer available to Anonymous users after the upgrade. In most cases, this is an appropriate restriction on anonymous access. However, to support some pre-existing programs, you might need to permit anonymous access. In that case, you should explicitly add the Anonymous Logon security group to the access control lists on the specific resources. In some situations, it might be difficult or impossible to: • Determine which resource on the computer running Whistler must grant anonymous access. • Modify the permissions on all the necessary resources. In these rare situations, you might need to include the Anonymous Logon security group in the Everyone security group on the computer running Whistler. To support this, Whistler introduces a new registry value, EveryoneIncludesAnonymous, which is used to switch between the default Whistler (the Everyone security group does not include the Anonymous Logon security group) and the Windows 2000 behavior (the Everyone security group includes the Anonymous Logon security group). The EveryoneIncludesAnonymous registry value can be set through the "Let Everyone permissions apply to anonymous users" local security setting. The security setting can be set to either Enabled or Disabled (default). To set the EveryoneIncludesAnonymous registry value using local security settings 1. Click Start, point to Programs, point to Administrative Tools, and then click either Local Security Policy or Domain Security Policy (on domain controllers only). 2. In Security Settings, double-click Local Policies, and then click Security Options. 3. Right-click Let Everyone permissions apply to anonymous users, and then click Properties. 4. To allow anonymous users to be members of the Everyone security group, click Enabled or, to prevent the inclusion of the Everyone security group security identifier in the anonymous user's access token, (the Whistler default), click Disabled. Applies to: administrators, developers Auditing Based Named Objects Causes Networking Failure The following registry value must NOT be enabled on computers running Whistler Personal, Whistler Professional, or Whistler Advanced Server. HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlLsaAuditBaseObjects Setting this registry value to 1 renders the TCPIP networking stack inoperable. The "Audit the access of global system objects" security setting can be configured both locally and remotely in the Group Policy snap-in. This Group Policy setting is located in the console tree under Computer Configuration, under Windows Settings, under Security Settings, under Local Policies, and in the Security Options folder. This security setting is listed in the details pane. If this setting is enabled (registry value set to 1) and deployed in Group Policy, then computers that receive the enabled setting and then are restarted cannot access the network. To work around this issue, the registry value should be set to 0 locally. Note This setting is disabled by default on a clean installation and is not enabled by any of the predefined security configuration manager templates. Applies to: general users, administrators, developers, specialists On computers running Whistler Advanced Server or on computers upgraded from Windows 2000 to Whistler Advanced Server, Certification Authority Security and Auditing does not allow security access to be denied in the Access Control List. This will be addressed in a future release. On computers running Whistler Advanced Server, when the Archive Key flag is set in the enrollment template, the policy module denies the certificate request. To work around this issue, on the Web enrollment page, confirm that the Archive key check box is selected. This is the default value. The following message might appear when connecting to a Web site through a Secure Sockets Layer (SSL) certificate. "The name on the security certificate does not match the name of the site." A certificate name constraint failure defined by the site administrator might cause this message. This will be addressed in a future release. After the certification authority (CA) database is restored on computers running Whistler Advanced Server, the CA might not be able to issue certificates, and instead displays a message that revocation is unknown or offline. There are three possible workarounds for this issue: • Publish a new base Certificate Revocation List (CRL) and delta CRL from the newly restored CA. • When restoring the CA, manually copy the CA database into the default database location before the CA starts for the first time. • Wait the allotted amount of time until a new base CRL and delta CRL are published automatically. On computers running Whistler Advanced Server, Certificate Services auditing events do not contain the correct descriptions. The event text includes the message "The description for Event ID number cannot be found." This will be addressed in a future release. On computers running Whistler Advanced Server, the Certutil -dspublish command utility does not publish cross certificates to the appropriate location. The certificates need to be explicitly appended to the following location: ldap:///CN=AIA,CN=Public Key Services,CN=Services,%s?crossCertificatePair, cACertificate?one?objectCategory=certificationAuthority This will be addressed in a future release. On computers running Whistler Personal, Whistler Professional, or Whistler Advanced Server, some local security settings cannot be modified using Local Security Settings. Specifically, policies such as Message text for users attempting to log on and LAN Manager authentication level that correspond to registry values are currently undefined on the computer and cannot be modified using Local Security Settings. In the console tree, the policies are located under Computer Configuration, under Windows Settings, under Security Settings, under Local Policies, and in the Security Options folder. The security settings are listed in the details pane. To work around this issue, use the Security Templates and Security Configuration and Analysis snap-ins to configure these security settings. Once the registry values are defined, they can be configured using Local Security Settings. This issue will be addressed in a future release. On computers running Whistler Advanced Server, name constraints fail when an e-mail name is added at the beginning of the Subject name field of a certificate. To work around this issue, do not add the e-mail name to the Subject name of a certificate. Use the e-mail name in the Altsubject name field of a certificate. On computers running Whistler Advanced Server, the certification authority (CA) rejects requests made after performing qualified subordination using a cross certification authority certificate request that uses Certificate Management protocol using Cryptographic Message Syntax (CMS). This protocol is also known as CMC. • Use a PKCS #10 request instead of a CMC request Or, add the enrollment agent extended key usage in the cross certification authority certificate template OID_ENROLLMENT_AGENT (1.3.6.1.4.1.311.20.2.1). Use the Microsoft Management Console (MMC) Certificate Templates snap-in to edit this template. On computers running Whistler Personal, Whistler Professional, or Whistler Advanced Server, Domain, Security Policy and Domain Controller Security Policy Administrative tools do not bring up the corresponding default domain and default domain controller Group Policy objects (GPO). To work around this issue, open the Active Directory Users and Computers snap-in, right-click the domain or domain controller's organizational unit, click Properties, and then on the Group Policy tab, edit the associated GPOs. This issue will be addressed in a future release. On computers running Whistler Personal, Whistler Professional, or Whistler Advanced Server, because of a problem in the RPC connection, Windows Management Instrumentation (WMI) remote access between non-English and English Whistler Beta 1 computers will result in an access violation. This issue will be addressed in a future release. The IWbemServicesEx APIs found in the public IDL are not supported in Beta 1 and will be removed in future releases. Applies to: administrators, developers, specialists Included in this Beta 1 release are three new command line tools to improve server manageability. These command line tools are located in the windirSystem32 directory. Whistler Server will have additional command line tools in future beta versions, but the following new tools are currently available in this Beta 1 release: • Service controller (Sc.exe) tool - this tool can manage, start, stop, pause, and diagnose Win32 services. • New printer management VBScript tools: there are seven new VBScript-based tools (*.vbs) in the System32 directory that the user can use for detailed management of print drivers, print servers, print queues, and print jobs on Whistler servers. • New Shutdown.exe tool: provides for scripted control of the shutdown and restart process for servers. This new version supports the Reboot Reason Collector application programming interfaces to document why a computer was shut down or restarted. To view the usage help for these tools • Type the tool name, and then type: Applies to: administrators, developers Lotus SmartSuite 9.5 (Millennium Edition) On computers running Whistler Advanced 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 systemrootApplication Compatibility ScriptsInstall 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 1 release with Terminal Services, 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 systemrootApplication Compatibility ScriptsInstall folder. Note The application compatibility scripts in the Whistler Beta 1 release do not require a SmartSuite node install for each user. Applies to: general users, administrators Microsoft Office 97 and Office 97 Programs Office 97 has various program compatibility issues with Whistler Advanced Server. They include: • Files that need permissions different from the defaults. • Files that need to be moved to the user’s home directory. To correct these compatibility issues, after installing Office 97, run the Office97.cmd installation script located in the systemrootApplication Compatibility ScriptsInstall folder. The installation script also adds the Ofc97usr.cmd script located in the systemrootApplication Compatibility ScriptsLogon folder to UsrLogn2.cmd. This script ensures that the needed per-user directories and files have been configured. Specific compatibility issues that apply to the following Office 97 programs are: Only administrators can modify the spelling options in Access 97 because the spelling options in Access 97 are common to all Access users. Access 97 Tools and Wizards Workgroups Some Microsoft Access 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 on 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 systemrootSystem32 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%OfficeWZLIB80.MDE" cacls "%O97INST%OfficeWZLIB80.MDE" /E /P "Authenticated Users":C *NUL: 2*&1 Rem If Exist "%O97INST%OfficeWZMAIN80.MDE" cacls "%O97INST%OfficeWZMAIN80.MDE" /E /P "Authenticated Users":C *NUL: 2*&1 Rem If Exist "%O97INST%OfficeWZTOOL80.MDE" cacls "%O97INST%OfficeWZTOOL80.MDE" /E /P "Authenticated Users":C *NUL: 2*&1 Adding Users to Microsoft 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 permissions to Write. The default workgroup information file is System.mdw and is located in the systemrootSystem32 folder. Once users have been added, you should change permissions back to Read. To create a new Access workgroup 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. 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. The data map dictionary (Geodict.dct) is common to all users. If one user deletes a map, other users no longer can gain access to that map. Microsoft Excel 97 Tools and Wizards Some Microsoft Excel wizards and tools do not support users using the Template Wizard. Microsoft Outlook 97 Tools and Wizards Some Microsoft Outlook wizards and tools do not support concurrent use, including the Template Wizard. 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. Microsoft Visual Basic Editor Controls Users without administrative rights cannot use or create additional controls in the toolbox. Only users with Write permission for the systemrootSystem32 folder are able to perform this task. Some Microsoft Word wizards and tools do not support concurrent use, including Clipart Preview. 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. Users should avoid enabling the Menu Animation component in Office 97. Enabling this component can severely affect system performance. Applies to: general users, administrators Microsoft Office 2000 and Office 2000 Programs 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. To install Office 2000 by using Terminal Services using the command line 3. Install the Terminal Server Tools from the Office Resource Kit. 4. To install the desired Office components with the transform file, at the command line, type: Office 2000 pathSetup TRANSFORMS=”Office Resource Kit pathTermSrvr.mst” where TermSrvr.mst is the transform file. 5. If you manually switched to Install mode, switch back to Execute mode after the installation. To do this, at the command line, type: 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: D:Setup.exe TRANSFORMS="C:Program FilesORKToolsToolBoxToolsTerminal Server ToolsTermSrvr.MST" Certain features of Office 2000 are purposely disabled 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. Microsoft Visual Studio 6.0 Enterprise Edition On computers running Whistler Advanced Server, Visual Studio 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 systemrootApplication Compatibility ScriptsInstall folder. • In Visual Basic 6.0, all users share a common default project directory for Microsoft Visual Basic 6.0 (which is part of the Microsoft Visual Studio Enterprise Edition). • In Microsoft Visual FoxPro, users cannot use the ActiveX catalog tools. Multiple users cannot use the Forms Wizard, Database Wizard, Label Wizard, or Multimedia/Sound Player, or Setup Wizard in Visual FoxPro simultaneously, and the default macro set in Visual FoxPro is common to all users. If one user sets a default macro set, it applies to all users on the server. • 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 FilesMicrosoft Visual StudioCommonMsdev98MacrosMyMacros.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 FilesMicrosoft Visual StudioVC98Bin folder. 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 systemrootApplication Compatibility ScriptsInstall 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 Settingsuser name directory. Netcom40.cmd adds the Com40usr.cmd script located in the systemrootApplication Compatibility ScriptsLogon 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 Netscape default user profile directory is always set to the Netscape program user directory (for example, Program FilesNetscapeUsersDefault). 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 the Whistler Advanced Server Beta 1 release with Terminal Services, you should uninstall and reinstall Netscape Communicator, and then run the Netcom40.cmd script. On computers running Whistler Advanced 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 systemrootApplication Compatibility ScriptsInstall folder to provide each user with a unique document directory. Note Any Visio settings changed for one user apply to all Visio users. On computers running Whistler Advanced Server, Terminal Services (TS) only supports 8-bit color for a TS session even though VMware uses 15-bit color or higher. For more information, visit the VMware 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: general users, administrators Terminal Services connection capabilities are now built into Whistler Personal, Whistler Professional, or Whistler Advanced Server. The Remote Desktop Connection program is the improved Terminal Services client and can be used to create any Terminal Services-enabled connection. You can use Remote Desktop Connection to connect to a server for remote administration, to a Terminal server, or to the Remote Desktop of a computer running Whistler Professional. 1. Click Start, point to Programs, point to Accessories, point to Communications, and then click Remote Desktop Connection. 2. Follow the instructions that appear. Applies to: general users, administrators Remote Desktop must be enabled on the computer running Whistler Professional before anyone can connect remotely. This ensures that users in a secure environment do not allow unintentional connections. 1. In Control Panel, double-click System, and then click the Remote tab. 2. Select Allow users to connect remotely to this computer. 3. Grant users permissions to connect remotely to the computer by adding them to the Remote Desktop users list. Members of the Administrators group for the computer can connect by default. Applies to: general users, administrators 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 1 release of Whistler Advanced Server, this period has been extended to 180 days. This extension is for the beta release only, and is meant to simplify test deployments. The Whistler Advanced Server multilingual capabilities enable Terminal Services to operate in several languages at once, providing each user with their language preference. Supporting this feature requires global application compatibility scripts, which often contain localized file names. When such a file name contains characters not in the server's default code page, the characters are not displayed properly at the command prompt. To prevent this, the administrator must set the appropriate code page to display, based on the program names, prior to running the compatibility script. where nnn specifies the required code page. Permissions for Application Compatibility 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 enabled 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 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: administrators, specialists On computers running Whistler Personal, Whistler Professional, or Whistler Advanced Server, within a Terminal Services session, the client LPT1 port is mapped to LPT51 (an offset of 50) on the server. Any additional LPT ports are mapped with the same offset (an offset of 50) in order not to interfere with the server's local LPT ports. This default mapping can be changed by running Chgport.exe. Changing the default port mapping might be necessary, for example, if the program running on the server is hard-coded to use LPT1. In this case, the client LPT1 must be mapped to the server LPT1 instead of the default LPT51. This causes any device connected to the server's local LPT1 port to become unavailable to programs running within the context of the remote Terminal Services user's session. Applies to: general users, administrators 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:MailMailbox.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. HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersion 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 there are no users 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. Terminal Services Remote Administration capabilities are now permanently available in Whistler Advanced Server. There is no need to install or enable this functionality; simply use any Terminal Services Client or the built-in Whistler Remote Desktop Connection client. By default, Administrators have remote access permissions that might be changed if desired. Terminal Services in Whistler now provides two different kinds of access to the server desktop for remote administration. As with Windows 2000, a user can create a remote session on the server, independent of the server console session. Up to two such sessions can be created concurrently, though it is advisable to ensure that only a single administrator use the computer at one time. In addition, by using Whistler, an administrator can connect remotely to the server console. When the user does so, the console is locked at the physical device. To end the remote console session and provide console activity back to the physical server, simply enter the user credentials at the console. Administrators can gain access to the remote console using the Remote Desktop Microsoft Management Console (MMC) snap-in. You can also create a remote console connection by running the Whistler Remote Desktop Connection client from a command line using the Mstsc.exe file with the /console switch enabled. Terminal Services in Whistler Advanced Server introduces the Remote Desktop Users group, a new mechanism for granting users remote access to a computer for administration, Remote Desktop connection, or program sharing on a terminal server. Remote Desktop Users is a Built-In group that can be administered by means of a policy. Placing a user or group into Remote Desktop Users gives that user the ability to remotely connect to a computer. The user does not need to be given local logon privileges, as in earlier versions of Terminal Services. Local users do not need to be given separate remote access permissions. By default, the Remote Desktop Users group includes the same entries as the User group, and, in addition, new users added to the Users group are automatically added to Remote Desktop Users. If there are no special configurations set in the Permissions through Terminal Server Configuration, these permissions are also granted. Any users added to the Permissions tab are automatically included in Remote Desktop Users on upgrade. The Permissions tab in Terminal Services Configuration can still be used to add specific users, just as in Windows 2000, or to set particular permissions for users. However, users must be granted the Remote Interactive Logon right to be able create a remote Terminal Services connection. This right can be given to any user or group using the Security policy editor, by running the Secpol.msc file, or by simply adding that user or group to the Remote Desktop Users group. If you have multiple connections to your Terminal server and wish to configure user permissions differently for each NIC, use a combination of the Remote Desktop Users group and the Permissions tab (or Windows Management Instrumentation Permissions functionality) to provide this. Typically, remove Remote Desktop Users from all configurations, add all the users or user groups who should have access to the computer to Remote Desktop Users, and add the particular users or groups who should have access through a particular NIC into that permission set. 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 disabled and then re-enabled 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. This issue will be addressed in a future release. If Terminal Services Advanced Client (TSAC) is installed on a computer running Whistler Personal, Whistler Professional, or Whistler Advanced 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. This will be addressed in a future release. Applies to: general users, administrators In the Whistler Personal, Whistler Professional, or Whistler Advanced Server Control Panel, the Accessibility Options item and the Accessibility Wizard cannot turn High Contrast on or off. This issue will be addressed in a future release. The Acer PowerKey, which allows user to select different power configurations, does not function correctly on Whistler Personal and Whistler Professional. There is no workaround for this. It will be addressed in a future release. After an upgrade from Windows Millennium Edition to Whistler Professional, when the computer is running ActiveSync, a synchronization error appears during connection to the Internet. • Delete the partnership and create a new one. When you delete the original partnership, its program settings are lost. Or, use My Computer to copy all the folders from C:WINDOWSApplicationDataMicrosoftActiveSyncProfiles to C:Documents and SettingsUser NameApplication DataMicrosoftActiveSyncProfiles. Updated drivers for the Adaptec CD-Recording Plug-In are available for Whistler Personal and Whistler Professional. The driver files that need to be updated are CDR4_2K.SYS and CDRALW2K.SYS. These can be obtained from Adaptec. For more information about drivers, visit the Adaptec Web Site at: http://www.adaptec.com/support/advisor/cdrupdates/ Web addresses can change, so you might not be able to connect to the Web site or sites mentioned here. Applies to: general users, administrators On computers running Whistler Personal or Whistler Professional, a Stop error occurs when the computer is shut down or restarted with the Udfreadr.sys file installed. This file might be installed with Adaptec UDF Reader. • Shut down and restart the computer. Or, delete the Udfreadr.sys file before or after the upgrade to Whistler. Applies to: general users, specialists On computers running Whistler Personal or Whistler Professional, America Online version 6.0 (AOL 6.0) might not function correctly. For more information about updates, visit the AOL Web site at: Web addresses can change, so you might not be able to connect to the Web site or sites mentioned here. On computers upgraded from Windows 98 or Windows 98 Second Edition to Whistler Professional, the toolbar buttons (Save, New, Duplicate, and so on) do not display correctly. To work around this issue, switch to another window, and then switch back to the original window. The toolbar buttons then display correctly. Applies to: general users, administrators, developers On computers upgraded from Windows 95 or Windows 98 to Whistler Personal or Whistler Professional, programs that require an Advanced SCSI Programming Interface (ASPI) layer to run might not function correctly. The following messages might appear: "The dynamic link library wnaspi32.dll could not be found in the specified path;" Or, "The file named 'wnaspi32.dll' could not be loaded." This issue is known to affect the following programs: Intervideo WinDVD 2000 2.1; Sony OpenMG Jukebox 1.3E; Sony Media Bar 3.2; and Adaptec Easy CD Creator 3.5b and 3.5c. This issue might affect other programs and is under investigation. To work around this issue, reinstall the affected program after the upgrade. Applies to: general users, specialists On computers upgraded from Windows 98 Special Edition or Windows Millennium Edition to Whistler Personal or Whistler Professional, users cannot start BaySwap 1.1. Currently, there is no workaround for this. This issue will be addressed in a future release. Applies to: general users, specialists On computers running Whistler Personal or Whistler Professional, BlackIce Defender versions 1.19.18LE, 1.9.6, and 2.1.cn do not fully install. The computer might randomly restart, or a Stop error might occur. You cannot reinstall or uninstall BlackIce Defender after restarting your computer because there are signatures of the install process embedded into the registry entries and temp files. No files appear to be copied into the program folder. There is no workaround for this. For the latest BlackIce Defender updates, visit the Network ICE Web site at: http://www.networkice.com/html/blackice_defender.html Web addresses can change, so you might be unable to connect to the Web site or sites mentioned here. On computers running Whistler Personal or Whistler Professional, Business Map Pro 2.02 might not start. This results in a General Protection Fault error. 1. In Control Panel, click Appearance and Themes. 2. Click Change the computer's theme. 3. On the Themes tab, in the Theme box, click Windows Default, and then click OK. On computers running Whistler Professional, the following issues apply to Calypso 3.1: • In the New Mailbox Wizard, closing the Mailbox Properties dialog box causes an access violation, and the program ends. • During Mailbox configuration, entering the new Mailbox name and password, and then clicking the Desktop Properties button cause an access violation, and the program ends. Applies to: general users, administrators On computers running Whistler Professional, quitting Carbon Copy Access Edition 5.5 while Carbon Copy service (Ccsrvc.exe) is running causes an access violation. Applies to: general users, administrators Citrix MetaFrame 1.8 is not supported on Whistler Advanced Server. For future support information, visit 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: administrators, specialists On computers running Whistler Professional, starting CodeWarrior 5.0 by using the icon placed on the desktop by the CodeWarrior Setup program causes a message to appear stating that the shortcut is missing. 1. Click Start, and then point to More Programs. On computers running Whistler Professional, CodeWright 6.0 reports low disk space if the following conditions are true: • The temp folder is a long path (as it is on Whistler by default). • The program is started from a command line using Cmd.exe or in any other environment where long file names in environment variables are converted to a short path. To work around this issue, start the program from the Start menu. Applies to: administrators, developers Compaq Computers - 16-Bit Subsystem Error On some Compaq computer models running Whistler Personal or Whistler Professional, programs might produce the following message: An application has attempted to directly access the hard disk, which cannot be supported. This may cause the application to function incorrectly. This is known to happen when running Microsoft Works 4.5, IomegaWare 2.2.1, Compaq Support, LivePix 2.0, Videogram Player 1.16, and Videogram Creator 1.20. • Delete or rename the Drvsize.exe file in the C:CpqsTools folder. Or, to ensure that the program runs without any errors, when the message appears, click Ignore. Compaq Diagnostic Tools for Windows 95 or Windows 98 Compaq Diagnostic Tools for Windows 95 or Windows 98 are not compatible with Whistler Personal and Whistler Professional and do not function correctly. There is no workaround for this. On computers running Whistler Personal or Whistler Professional, Compaq Easy Access Buttons on the keyboard cannot be programmed. There is no workaround for this. On computers running Whistler Professional, the following issues apply to CoolCat 4.01. • Clicking the Files tab in CoolCat 4.01 causes the characters to display incorrectly. There is no workaround for this. • Users receive the following error while installing CoolCat 4.01: "Service Pack Required You cannot install this VB5 application without the latest service pack first being installed onto this computer. Please install the latest service and rerun the installation." This message does not affect the performance of the program. Applies to: general users, administrators, developers On computers upgraded from Windows 98 Special Edition to Whistler Professional, a message appears when Conversa Web 3.1.0.7 is started that states that the program is "unable to listen for voice commands" There is no workaround for this. Applies to: general users, administrators On computers upgraded from Windows 2000 to Whistler Professional or Whistler Personal, when restarting the computer for the last time, a Stop error occurs. • Uninstall Cosession Remote32 prior to the upgrade. Or, after the upgrade, restart the computer in safe mode and uninstall the program. Applies to: general users, specialists On computers running Whistler Professional, the following issues apply to Crystal Reports Professional 8.0: • After upgrading from Windows 98 Second Edition to Whistler Professional, the program cannot be installed. A Windows Installer message prompts you to insert the program CD. After the CD is inserted, the Scr.msi file still cannot be found. • When User A creates and saves a file and logs off as an administrator, and then logs on as a different administrator (User B), the program prompts you to insert the program CD to configure Windows. After the CD is inserted, Windows Installer cannot continue. Applies to: general users, administrators, developers In Whistler Professional, the following issues apply 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: "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. • During the installation of Delphi 1.0, the program stops responding at the initial setup screen. To work around this issue, in Task Manager, click the Applications tab, and then click Delphi. Click End Task, click Delphi again, and then repeatedly click End Task until the program installation begins. • After an upgrade from Windows 98 Special Edition to Whistler Professional, Delphi 1.0 does not start. To work around this issue, reinstall Delphi 1.0. Applies to: administrators, developers When you open a new project by using the Windows and Button settings in Professional style, the Object Inspector window only partially displays. To work around this issue, to view the entire window, change the Windows and Button settings to Windows Classic style. Applies to: administrators, developers On computers upgraded from Windows 98 Second Edition to Whistler Professional, DHTMLMenu Builder 2 does not run. To work around this issue, reinstall the program. Applies to: administrators, developers After the upgrade from Windows 98 Second Edition to Whistler Professional, DropChute Professional 3.0 cannot start. A message appears stating that the program was designed for Windows 95 or Windows 98. There is no workaround for this. Applies to: administrators, developers In Whistler Professional, during the installation of Exceed 6.1 and 6.2, tuning the X server causes an access violation to occur. This prevents the program from installing properly. To work around this issue, before installing this program, change the Windows and Button settings to Windows Classic style. In Whistler Professional, clicking Start, pointing to Programs, and then clicking Exceed 6.2 causes an access violation. The program does not run. There is no workaround for this. When running Setup for Extra Bundle for TCP/IP 6.6 on computers running Whistler Professional, users are prompted to select a product to install from a list box. Because the list box is empty (no text is visible), users cannot select the item to install. To work around this issue, to install the full product (default selection), press ENTER. Applies to: general users, administrators After an upgrade from Windows 98 Second Edition to Whistler Professional and when Fax 2000 3.0 is started, the following messages appear: "fax2000.exe - Entry Point Not Found." "The procedure entry point MapSLFix could not be located in the dynamic link library KERNEL32.dll." The program does not run, and there is no workaround for this. Applies to: general users, administrators Near the end of the installation of FaxLink 1.4, when the program starts to install a print driver, the following messages appear: "Unable to copy files from c:Program FilesVisionLabFaxLinkFmfaxdrv.nt4 to" "C:WINNTSystem32SpoolDRIVERSW32X86Fmfaxdrv.dll due to system error 2." These messages are followed by seven identical errors involving different file names, and then the following message appears: "Setup failed - Unable to add monitor due to system error 126." Applies to: general users, administrators In Whistler Professional, when the Setup.exe file for FrameMaker 4.0 is run, the following message appears: "Application Error: not enough space for environment" To work around this issue, run Setup.exe a second time. Applies to: administrators, developers In Whistler Professional, the user cannot install Adobe PostScript Printer Drivers. A message box appears with the following message: "The procedure entry point SUnMapLS_IP_EBP_32 could not be located in the dynamic link library KERNEL32.dll." Applies to: general users, administrators If you install GoBack 2.1d (and possibly all earlier versions) on computers running Windows 95 or Windows 98 and then upgrade to Whistler Personal or Whistler Professional, the Whistler upgrade process stops responding during the first restart. To work around this issue, uninstall GoBack 2.1 before starting the Whistler upgrade procedure and then reinstall the program after the upgrade is complete. Applies to: general users, specialists The Help window is only partially displayed for the Tables; Frames; Lists; Forms; Script; CFML Tag Editors. To work around this issue, change the display settings to Windows Classic. Applies to: general users, administrators The following issues apply to HostExplorer 6.2: • After you upgrade from Windows 98 Second Edition to 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: 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:Winsys32Hummbird 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. • On computers running Whistler Professional, Toolbar buttons on Hummingbird Neighborhood or FTP Explorer are not painted after switching Themes from Professional Style to Windows Classic Style. To work around this issue, restart the programs after switching to the Windows Classic style theme. Applies to: general users, administrators On computers upgraded from Windows 98 Special Edition to Whistler Professional, an access violation occurs when the user starts the program. There is no workaround for this. Applies to: general users, administrators In Whistler Professional, when starting HTML Editor 8.0 from the Start menu, the toolbar is displayed incorrectly and the title bar is missing. There is no workaround for this. Applies to: general users, administrators, developers On computers upgraded from Windows 98 Special Edition to Whistler Personal or Whistler Professional, Intel SpeedStep 1.1 is uninstalled. To work around this issue, reinstall Intel SpeedStep 1.1. Applies to: general users, specialists On computers running Whistler Personal or Whistler Professional, when you open Internet communications programs (for example, chat, news readers, browsers, plug-ins, and so on), the programs cannot connect to the Internet. To work around this issue, connect to the Internet manually or through your Internet service provider (ISP), and then run the Internet program. 2. In Control Panel, click Network and Internet Connections. 4. To connect to the Internet, double-click any existing Internet connection. 5. If no connections appear, click Make New Connection. 6. Follow the instructions that appear. To connect to the Internet by using an ISP such as AOL, Prodigy, MSN, or WorldNet, you can double-click the desktop shortcut icon provided by the ISP. This issue is currently being investigated. In Whistler Professional, while installing Java Workshop 2.0 using the 30-day trial license, the following message appears: "Sorry, the product version is too old." Applies to: administrators, developers After you upgrade from Windows 98 Second Edition to Whistler Professional, JAWS cannot be started. A JAWS for Windows message states that the display driver is not properly installed, and the program does not start. There is no workaround for this. Applies to: general users, administrators On computers running Whistler Advanced Server, there is a new Group Policy setting called Disallow installation of printers using Kernel Mode drivers that prevents the installation of printers using kernel-mode drivers. This setting can be located in the console tree, under Computer Configuration, under Administrative Templates, in the Printers folder. The setting is listed in the details pane. 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. 1. Right-click Disallow installation of printers using Kernel Mode drivers setting, and select Disabled. Applies to: general users, administrators After you install LapLink 2 and restart Whistler Professional, a fatal system error occurs. This error also occurs when during the upgrade from Windows 98 Second Edition to Whistler Professional. There is no workaround for this. Applies to: general users, administrators All versions of Liquid Audio Five are incompatible with Whistler Personal and Whistler Professional. The following issues involve making upgrades to Whistler Beta 1. Before running Windows Setup, you must uninstall Liquid Audio. There are currently no other workarounds available. After upgrading from Windows 95 or Windows 98 to Whistler Beta 1, Liquid Audio Five does not function correctly and cannot be installed after the upgrade. You cannot install Whistler Beta 1 because Liquid Audio Five causes Whistler Setup to function incorrectly. 2. To remove the reference to the driver in the registry: a. Click Start, and then click Run. Type regedit, and then click OK. b. From the console tree, click My Computer, click HKEY_LOCAL_MACHINE, click System, click Current Control Set, click Control, and then click Class. c. Double-click the folder labeled {4D36E965-E325-11CE-BFC1-08002BE10318}. 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. To make a backup copy, click the folder labeled {4D36E965-E325-11CE-BFC1-08002BE10318} and from the File menu, click Export. d. In the details pane, find LowerFilters where the Data column reads ainctl2k. e. Right-click LowerFilters, and then click Delete. a. Click Start, and then click Run, and then type: Rename %windir%system32driversainctl2k.sys *.bak 4. You are now ready to install the latest Whistler Beta release. On computers running Whistler Personal or Whistler Professional, when you start Logitech MouseWare, the Microsoft Mouse program starts instead. There is no workaround for this. This issue will be addressed in a future release. Applies to: general users, specialists The following issues apply to Lotus Notes and Domino R5 5.0.3 running on Whistler Advanced Server. • After changing the Welcome page in Lotus Notes R5, Internet Explorer opens multiple pages. The Nlnotes.exe file stops responding because of common code found on some Web sites (for example, the Lycos Web site and the AOL Web site). To work around this issue, do not change the Welcome page from the default Lotus selection. If the problem persists, uninstall and then reinstall Lotus Notes R5. • After an express upgrade on a computer running Windows 2000 to Whistler Advanced Server, Internet Information Services (IIS) claims port 80 and Lotus Domino R5 Server does not start. To work around this issue, uninstall IIS after the upgrade or perform a manual upgrade. These issues will be addressed in a future release. Applies to: administrators, specialists On computers running Whistler Advanced 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. Applies to: general users, administrators On computers running Whistler Professional, if you start Mastering Web Site Fundamentals 1.0, the following message appears: "Internet launches will require a recent version of Internet Explorer (version 3.0 or greater)." When you use Mastering Web Site Fundamentals 1.0 to connect to the Internet, Internet Explorer 5.5 is not detected. To work around this issue, use Internet Explorer 5.5 to connect to the Internet. Microsoft Exchange Server 5.0 - Exchange Client 5.0 The following issues apply to Exchange Client 5.0: • After an upgrade from Windows 98 to Whistler Professional, the Exchange Server 5.0 splash screen appears for a moment, but the program does not run. When you click the Mail icon in Control Panel, the following message appears: You need more memory or system resources. Close some windows and try again." • Users cannot start Exchange Client 5.0 on computers running Whistler Professional after a clean installation. Instead, the following message appears: You need more memory or system resources. Close some windows and try again." Applies to: general users, administrators Applications without an autorun feature and with image files in the root directory of the CD might generate the mixed content window. The mixed content window allows images on a CD to be viewed in a slideshow viewer. This feature was meant to be used with photo CDs but is currently affecting application CDs as well. If an application generates this window, it will do so every time the application CD is inserted into the drive. • To open the root directory of the CD, select Open a folder so I can view the files, and then click OK. This procedure does not stop the mixed content window from opening the next time you insert the CD. The application should run normally whether the mixed content window appears or not. NFS Maestro Client 6.1 and 6.2 cannot be installed on computers running Whistler Professional. During the installation, the following message appears: "This package can only be installed on Windows NT version between 4.0 and 5.0 inclusive." In the message, click OK, and Setup ends. Applies to: general users, administrators Office 2000 Service Release 1 - Shortcut Bar If the Office Shortcut Bar is used on computers running Windows 98 or Windows Millennium Edition and upgraded to Whistler Personal or Whistler Professional, two Office Shortcut Bars appear the first time the system is started after the upgrade. This does not affect the functionality. To work around this issue, restart the system. Only one Office Shortcut Bar appears. On a multiuser computer running Whistler Professional, users who did not install Palm Desktop 3.0 as an administrator cannot use the program. Applies to: general users, administrators When installing PeopleSoft 7.56 on Whistler Advanced 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. Applies to: administrators, specialists 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 Adobe Photoshop 5.5, 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 may also occur with other motherboards. Note If the computer manufacturer is Dell Computer Corporation, the computer might return the error, "Alert: Regulator Error." There are three possible workarounds to this issue: • Contact the motherboard or computer manufacturer for assistance resolving this issue, which occurs because of an electrical problem on some motherboards. 2. In Microsoft Windows Explorer, move the Extensions folder from Program FilesAdobePhotoshop 5.5Plug-InsAdobe Photoshop Only to a location outside of the Adobe folder (for example, move it to the desktop). Note Perform this procedure if the computer has only one processor. Moving the Extensions folder disables the extensions in the folder that optimize data movement by Photoshop. After you move the extensions, Photoshop 5.5 performance slows noticeably. 2. Using My Computer, move the MMXCore.8bx and FastCore.8bx files from the Program FilesPhotoshop 5.5Plug-InsAdobe Photoshop OnlyExtensions folder to a location outside of the Adobe folder (for example, move them to the desktop). 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: general users, administrators, developers, specialists In Whistler Professional, during the installation of ProComm Plus 3.0, the Setup program stops responding at the initial Setup screen. There is no workaround for this. Applies to: general users, administrators On computers running Whistler Personal or Whistler Professional, when closing QuarkXPress 4.1, the Shutdown Windows dialog box appears. This dialog box reappears in a loop regardless of the user's action. 1. In Control Panel, click Appearance and Themes. 2. Click Change the computer's theme. 3. On the Themes tab, in the Theme box, click Windows Default, and then click OK. RoboHELP Office 7.0 and RoboHELP Office 2000 On multiuser computers running Whistler Professional, users who did not install RoboHELP Office 7.0 or RoboHELP Office 2000 as an administrator cannot use the program. The following message is displayed: The RoboHELP template C:Documents and SettingsUserBApplication DataMicrosoftTemplatesRoboHELP.dot cannot be located. Until the user reinstalls the program, the user cannot open the RoboHELP.dot template and cannot create RoboHELP projects. Applies to: administrators, developers The following issues apply to SAP R/3 4.0b, 4.5b, and 4.6b running on Whistler Advanced Server. • While installing SAP R/3 4.0b on Whistler Advanced Server using a network file share as the CD file source location, the final export CD is not copied during setup. To work around this issue, copy the CD locally before beginning the installation. • If you use Microsoft Management Console (MMC) to stop SAP services, six minutes elapse before SAPMMC detects that the Msg_server.exe process stopped. These issues will be addressed in a future release. Applies to: administrators, specialists Server programs supported on Windows 2000 should run with very few functional issues on Whistler Advanced Server. As with all Beta products, there is no guarantee that every program runs correctly. If you experience any issues with Server programs supported on Windows 2000, please send details to appfix@microsoft.com. Applies to: administrators, specialists On computers running Whistler Professional, after establishing a 5250 session in SmarTerm 9.0a, the program quits after you press any key on the keyboard. The following messages appear: "SmarTerm Office - [IBM 5250 display session 1]: STOFFICE.exe - Application Error" "The instruction at "0x65f51ac8" referenced memory at "0x00000001". The memory could not be "written"." "Click on OK to terminate the program" "Click on CANCEL to debug the program" Applies to: general users, administrators On computers running Whistler Personal, the SoftQuad HoTMetaL Site Maker Database is missing from the More Programs menu and HoTMetaL 2.0 Readme and SoftQuad HoTMetaL 2.0 are missing from the SoftQuad HoTMetaL 2.0 menu. However, in Add or Remove Programs, SoftQuad HoTMetaL Pro 6.0 and SoftQuad HoTMetaL Site Maker Database are both installed. To work around this issue, use the Start menu shortcuts to start the program. If you perform an upgrade on computers running Windows 95 or Windows 98 to Whistler Personal or Whistler Professional, some Sony proprietary programs might produce one of the following messages: "This application runs only on Sony Vaio series. Code=(25)" Or "This application runs only on Sony Vaio series. Code=(15)" The following applications are known to be affected: DVGate, Media Bar, Picture Gear, Smart Connect Monitor, Smart Capture, Smart Label, Picture Toy, Movie Shaker, and Visual Flow. This issue might affect other applications and is currently under investigation. For more information about specific Sony Vaio programs, visit the Sony Computing 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: general users, specialists SQL 7.0 - Data Transformation Services When running SQL 7.0 Service Pack 1 on a computer running Whistler Advanced Server, Data Transformation Services (DTS) packages stop responding. For more information, visit online product support at the Microsoft Web site at: http://search.support.microsoft.com/ This issue will be addressed in the SQL 7.0 Service Pack 3 release. Applies to: administrators, developers SQL 7.0 - Registering Server Applications When running SQL 7.0 on Whistler Advanced Server, registering server applications might cause SQL 7.0 to stop responding. This only occurs when running SQL on very large domains. This issue will be addressed in the SQL 7.0 Service Pack 3 release. Applies to: administrators, specialists On computers running Whistl