? If a Component Services application is marked as not changeable, the Comrepl.exe utility or the Iissync.exe utility does not properly replicate its identity. For this release, you must mark the application as changeable before initiating the replication. For additional information about Comrepl.exe, see the Component Services online documentation. For additional information about Iissync.exe, see the Internet Information Services (IIS) documentation. This will be addressed in a future release.
? When you re-install over a Component Services application that has been marked as not deletable, neither the Component Services snap-in nor the Component Services administrative interfaces return an error. However, the application is not updated. For this release, you must either mark the application as deletable or modify the installation code to check whether an application exists before installing it.
To download Component Services documentation and samples, see the Microsoft Platform SDK: COM Components Web site at:
http://www.microsoft.com/msdownload/platformsdk/com.htm
Upgrading MTS 2.0 Installations to
Windows 2000 with Component Services
When you upgrade a computer running Windows NT 4.0 with Windows NT 4.0 Option Pack, Windows 95 with Personal Web Server from the Windows NT 4.0 Option Pack, or Windows 98 with Personal Web Server to Windows 2000, Setup automatically migrates all existing MTS packages to Component Services applications.
Note
Before you use, import, or export the migrated packages, it is important to review the migration log file that is generated during the migration process even if the upgrade appears successful. If this migration fails or encounters a problem that is not fatal, a message appears and an event log entry or log file is generated that describes the reason for the failure.
As an alternate approach to migrating MTS 2.0 packages to Component Services, do the following:
1. Use the MTS 2.0 Package Export feature to export the MTS packages on the computer running Windows NT 4.0, Windows 95, or Windows 98. This export process produces a .pak file for each exported package and a collection of other files.
2. Perform a clean installation of Windows 2000, or delete the MTS packages and upgrade to Windows 2000.
3. Use the Application Install feature of the Component Services administrative tool to install the .pak files on a Windows 2000 computer.
Application Proxy Installation
If an application proxy (.msi file) for the same server application is reexported, before you install the new application proxy, you must uninstall the earlier application proxy from the computer. Otherwise, both application proxies appear when you open Add/Remove Programs in Control Panel. Additionally, changes contained in the new application proxy may not be applied to the computer. No message or error log is generated. This will be addressed in a future release.
Upgrading from Component Services (Beta Version) with MSCS
If you are upgrading from a previous beta version of Windows 2000 on a Microsoft Cluster Server (MSCS) cluster with the Component Load Balancing (CLB) router enabled, you may have configured the cluster for use with the CLB service. You need to remove the earlier configurations to avoid unnecessary errors in the event log.
? To remove the earlier configurations
* At the command prompt, type:
comclust -r
Microsoft Distributed Transaction Coordinator
This section describes issues related to the MS DTC.
Performing Distributed Transactions with
Windows NT 3.51 and Windows NT 4.0
MS DTC uses a new protocol for performing distributed transactions on Windows 2000. As a result of this protocol change, a distributed transaction can no longer flow from a Windows 95, Windows 98, Windows NT 3.51, or Windows NT 4.0 computer to a Windows 2000 computer. However, a distributed transaction can flow from a Windows 2000 computer to any of these computers.
If you are running the Window NT 4.0 Option Pack, you can circumvent this limitation by installing either Windows NT 4.0 SP4 or SP5. If you are running Windows NT 4.0, you can also circumvent the problem by installing QFE 810, which is located at:
ftp://ftp.microsoft.com/bussys/distapps/MTS/Public-Fixes/usa/DTC/SvcPack/
No patch is available for Windows 95, Windows 98, or Windows NT 3.51.
Reinstalling MS DTC After Installing Microsoft SQL Server™
Whenever you install SQL Server 6.5, SQL Server 7.0, or any SQL Server 6.5 or SQL Server 7.0 SP release, you must reinstall MS DTC. This reinstallation is necessary because SQL Server Setup installs an obsolete version of MS DTC that is incompatible with Component Services on Windows 2000.
? To reinstall MS DTC on a non-clustered system
1. Stop the MS DTC service. Also stop any services that depend on MS DTC, including Component Services, Microsoft SQL Server, Microsoft Message Queuing, and Microsoft COMTI.
2. Execute the Dtcsetup.exe program, which is located in the System32 folder.
3. Restart any services that depend on MS DTC.
? To reinstall MS DTC on a cluster with an existing MS DTC cluster
1. Use the MSCS Cluster Administrator to stop the MS DTC cluster resource. Also stop any services that depend on MS DTC, including Component Services, Microsoft SQL Server, Microsoft Message Queuing, and Microsoft COMTI.
2. Execute the Dtcsetup.exe program, which is located in the System32 folder, on the node that controls the MS DTC cluster resource. When you are prompted to install MS DTC on the other nodes in the cluster, run Dtcsetup.exe on those nodes.
Do not restart any system until MS DTC Setup has been successfully run on all systems in the cluster.
3. Restart all systems and also any services that depend upon MS DTC.
MS DTC Does Not Support
Rolling Upgrades on MSCS Clusters
MS DTC does not support rolling upgrades on MSCS clusters. When you install MS DTC on a cluster, you must do the following:
1. Stop MS DTC.
2. Upgrade MS DTC on all nodes in the cluster.
3. Restart MS DTC.
These steps are necessary because MS DTC maintains a single MS DTC log file for the entire cluster, and the new information has been added to the MS DTC log file for the Windows 2000 release.
In-Memory Database
After evaluating customer feedback from the Microsoft Windows 2000 Beta Program, Microsoft has determined that the In-Memory Database (IMDB) does not completely address the needs of most customer scenarios. The IMDB does not support query processing or stored procedures, and it requires customers to implement a different database access method.
The Transactional Shared Property Manager (TSPM), which was built on top of IMDB, has also been removed from Windows 2000. However, the Shared Property Manager technology that was initially released with MTS in Windows NT 4.0 is still available with Component Services in Windows 2000.
For additional information about IMDB, see the “What Happened to IMDB?” topic on the MSDN Web site at:
http://msdn.microsoft.com/library/techart/whatimdb.htm
Removing COMTI Components with Component Services and Windows 2000
COMTI is a component of SNA Server 4.0 and later. When you remove a COMTI component from a Component Services application, it does not disappear from the COMTI Remote Environment pane. However, the component is removed from the COM+ Application Components pane. Although this produces an inconsistent display, you can deploy a new component with the same Class ID without causing an error.
Microsoft Data Access Components
Microsoft Data Access Components (MDAC) is automatically installed with Windows 2000. To obtain the most current information about MDAC 2.5 and known MDAC issues, see the MDAC release notes, which are installed at:
*system drive*:\Program Files\Common files\System\ADO
\MDACReadme.htm
For more information about MDAC, see the Microsoft Universal Data Access Web site at:
http://www.microsoft.com/data/
Internet Services
The following section describes Windows 2000 issues related to Internet services features.
Internet Information Services
To obtain the most recent information about installation, documentation, and other known IIS issues, type the following link into the address bar of your browser (or click Start, click Run, and type the link):
file:\%systemroot%\Help\Iishelp\Iis\Htm\Core\Readme.htm
where %systemroot% is your Windows 2000 installation path, including drive and directory (for example, C:\Winnt).
IIS is not installed by default on Windows 2000 Professional. If you cannot view the IIS release notes from the link above, you need to install IIS by using Add/Remove Programs in Control Panel.
Client Certificate Is Not Trusted or Is Invalid
A problem in the certificate trusts list (CTL) may cause the following 403.16 message to display for valid certificates:
“Client certificate untrusted or invalid”
As a workaround, install a copy of the root certificate from the Trusted Root Certification Authorities to the Intermediate Certification Authorities store for the Local computer. This will be addressed in a future release.
Cannot Change Anonymous Account
IIS 5.0 restricts changes to the Windows 2000 user account for anonymous authentications that are made below the service level and that contain an “IUSR_” account prefix. This restriction ensures proper functioning of the IUSR_computername account, which should not be altered in any way. If you require multiple anonymous authentication accounts, create new accounts that do not contain the “IUSR_” account prefix, assign account permissions to log on locally, and then add the accounts to the Guest User group.
Microsoft Windows 2000 Server Media™ Services
The following sections provide information and describe issues that affect Windows Media Services, an optional component of Windows 2000.
Logging Multicast and Unicast Client Information in Netscape Navigator
Netscape Navigator 3.04 may fail to obtain the Uniform Resource Locator (URL) of the Web page that contains the embedded client. This prevents the client information—the URL value of the cs(Referrer) field—from being properly logged when you use Netscape Navigator 3.04.
Using Windows Media Services Components and Microsoft Site Server with the Membership Authentication Plug-In
A known “boot race” problem exists when you use Windows Media Services components with Microsoft Site Server version 3.0 and you have enabled the Site Server Membership Authentication plug-in. This plug-in does not load when Windows Media Services starts, and clients cannot connect to Windows Media Services.
When this problem occurs, the Windows 2000 Server Event Log service does not log the error. To verify the failure, use Windows Media Administrator to connect to Windows Media Services. Windows Media Administrator messages appear, indicating that the plug-in has not started and prompting you to restart the Windows Media Unicast service.
As a workaround, restart the Windows Media Unicast service.
HTTP Streaming Can Cause Errors
After enabling Hypertext Transfer Protocol (HTTP) streaming in the Windows Media Administrator, you must restart your computer. Otherwise, the Windows Media Services Event Log fills up with error events.
Storage Notes
The following sections describe Windows 2000 issues related to storage.
Offline Folders
Do not use the Offline Folders feature with Distributed File System (DFS) volumes or shares.
File Systems
After you convert a FAT file system to NTFS, all files and folders are set with the following Access Control List (ACL):
? Administrators Full Control (not inherited)
? System Full Control (not inherited)
? Everyone Full Control (inheritable)
You can fix the inheritance settings at the root of the volume in Microsoft Explorer.
? To fix the inheritance settings at the root of the volume in Microsoft Explorer
1. In Microsoft Explorer, right-click the root directory, and then click Properties.
2. On the Security tab, click Advanced.
3. Double-click the Administrators entry.
4. On the Permission Entry page, change Apply onto: to This folder, subfolders and files.
5. Double-click the System entry.
6. On the Permission Entry page, change Apply onto: to This folder, subfolders and files.
7. Click OK.
Logical Disk Manager
This section describes known issues that apply to the Logical Disk Manager.
Disks That Are Members of FaultTolerant Sets (Mirror or RAID5)
If you upgrade from a previous version of Windows 2000, a disk that is a member of a fault-tolerant set (mirror or RAID5) may become orphaned during graphical user interface (GUI)mode Setup. No data is lost. You can use the Disk Administrator MMC snap-in to rebuild the disk.
? To use the Disk Administrator MMC snap-in to rebuild the disk
1. Start the Disk Administrator MMC snap-in.
2. For a mirror disk, click Resynchronize Mirror, or for a RAID5 disk, click Regenerate Parity.
The redundant information for the volume is rebuilt.
Creating Logical Drives Within Extended Partitions on Basic Disks
If you are upgrading from Windows NT 4.0 to Windows 2000 and you attempt to create logical drives within extended partitions on basic disks, a drive geometry translation error may cause the Logical Disk Manager to display the following message:
“Parameter is incorrect.”
This may also occur with raw installations on disks with no signatures. No workaround is available at this time.
Converting System or Boot Volumes from Basic to Dynamic
You should convert system or boot volumes from basic to dynamic independent of any other volume conversion. In particular, before you attempt to import disks from another computer, restart your computer.
Mirroring Combined SystemBoot Volumes on Systems with OEM Partitions
Mirroring combined systemboot volumes on systems with Original Equipment Manufacturer (OEM) partitions may require extra care. Whenever you mirror your system or boot partition, you should verify that the system starts from both the original and newly created mirrored partitions. On systems with OEM partitions, complete the following steps:
1. Ensure that the target disk for the mirror is basic.
2. Create a basic partition equal to the size of the OEM partition.
3. Convert the disk to dynamic.
4. Mirror the systemboot volume.
Backup
This section describes known issues that apply to Windows 2000 Backup.
Backup of Remote Storage Files by Legacy Backup Applications
Legacy backup applications include Windows NT 4.0 and earlier versions of Backup, and also any third-party backup applications that do not ship with Windows 2000 and do not recognize remote storage files. When using legacy backup applications to back-up remote storage files which are migrated to tape, Remote Storage opens by default the files with the FILE_OPEN_NO_RECALL option and streams the migrated data from tape directly to the backup application. On a volume with large quantities of remote storage files, this may tie up the server for long periods of time as it reads the data from tape and streams it to the backup application. Also, the legacy backup client may take an extended period of time to completely backup the volume.
If you do not need to backup the data in the remote storage files using the legacy backup application, you can skip these files. On the server containing the remote storage files, if a registry value of type REG_DWORD: exists and is set to a non-zero value for the HKEY_LOCAL_MACHINE \System\CurrentControlSet\
Services\RsFilter\Parameters\SkipFilesForLegacyBackup registry key, the remote storage files are skipped by the legacy backup application. By default this value is not present in the registry. Therefore, you must add this to the registry to skip the backup of remote storage files by the legacy backup application.
Caution
Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.
? To skip the backup of remote storage files
* Cut and paste the following text into a .reg file, and load it into the registry by using regedit.exe:
REGEDIT4
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RSFilter\Parameters]
“SkipFilesForLegacyBackup”=dword:00000001
Restoring the IIS Metabase While the IIS Administration Service Is Running
The IIS Administration Service does not hold open the metabase file. Therefore, if you restore the metabase file while the IIS Administration Service is running, the file is overwritten by the copy in memory when the service shuts down. Then, when you restart the computer, the IIS-managed services do not work.
As a workaround, before restoring the IIS metabase, stop the IIS Administration Service and all the other IIS-managed services. If you do not have the IIS Administration Service installed when you restore the IIS metabase, no action is required.
Restoring the System State from a Backup Set