Реферат: Windows 2000 Essay Research Paper Microsoft Windows

? If you are using MTS 1.0, Component Services automatically replaces MTS. However, user-defined packages are lost, and you must re-create them.

? If you are using either MTS 1.0 or MTS 2.0 and you have installed the SDK option, the SDK files are removed. You may want to install the latest Component Services SDK, which is available with the Microsoft Platform SDK.

? If a Component Services application is marked as not changeable, the Comrepl.exe utility or the Iissync.exe utility does not properly replicate its identity. For this release, you must mark the application as changeable before initiating the replication. For additional information about Comrepl.exe, see the Component Services online documentation. For additional information about Iissync.exe, see the Internet Information Services (IIS) documentation. This will be addressed in a future release.

? When you re-install over a Component Services application that has been marked as not deletable, neither the Component Services snap-in nor the Component Services administrative interfaces return an error. However, the application is not updated. For this release, you must either mark the application as deletable or modify the installation code to check whether an application exists before installing it.

To download Component Services documentation and samples, see the Microsoft Platform SDK: COM Components Web site at:

http://www.microsoft.com/msdownload/platformsdk/com.htm

Upgrading MTS 2.0 Installations to

Windows 2000 with Component Services

When you upgrade a computer running Windows NT 4.0 with Windows NT 4.0 Option Pack, Windows 95 with Personal Web Server from the Windows NT 4.0 Option Pack, or Windows 98 with Personal Web Server to Windows 2000, Setup automatically migrates all existing MTS packages to Component Services applications.

Note

Before you use, import, or export the migrated packages, it is important to review the migration log file that is generated during the migration process even if the upgrade appears successful. If this migration fails or encounters a problem that is not fatal, a message appears and an event log entry or log file is generated that describes the reason for the failure.

As an alternate approach to migrating MTS 2.0 packages to Component Services, do the following:

1. Use the MTS 2.0 Package Export feature to export the MTS packages on the computer running Windows NT 4.0, Windows 95, or Windows 98. This export process produces a .pak file for each exported package and a collection of other files.

2. Perform a clean installation of Windows 2000, or delete the MTS packages and upgrade to Windows 2000.

3. Use the Application Install feature of the Component Services administrative tool to install the .pak files on a Windows 2000 computer.

Application Proxy Installation

If an application proxy (.msi file) for the same server application is re﷓exported, before you install the new application proxy, you must uninstall the earlier application proxy from the computer. Otherwise, both application proxies appear when you open Add/Remove Programs in Control Panel. Additionally, changes contained in the new application proxy may not be applied to the computer. No message or error log is generated. This will be addressed in a future release.

Upgrading from Component Services (Beta Version) with MSCS

If you are upgrading from a previous beta version of Windows 2000 on a Microsoft Cluster Server (MSCS) cluster with the Component Load Balancing (CLB) router enabled, you may have configured the cluster for use with the CLB service. You need to remove the earlier configurations to avoid unnecessary errors in the event log.

? To remove the earlier configurations

* At the command prompt, type:

comclust -r

Microsoft Distributed Transaction Coordinator

This section describes issues related to the MS DTC.

Performing Distributed Transactions with

Windows NT 3.51 and Windows NT 4.0

MS DTC uses a new protocol for performing distributed transactions on Windows 2000. As a result of this protocol change, a distributed transaction can no longer flow from a Windows 95, Windows 98, Windows NT 3.51, or Windows NT 4.0 computer to a Windows 2000 computer. However, a distributed transaction can flow from a Windows 2000 computer to any of these computers.

If you are running the Window NT 4.0 Option Pack, you can circumvent this limitation by installing either Windows NT 4.0 SP4 or SP5. If you are running Windows NT 4.0, you can also circumvent the problem by installing QFE 810, which is located at:

ftp://ftp.microsoft.com/bussys/distapps/MTS/Public-Fixes/usa/DTC/SvcPack/