Migrating MTS Packages, COM Objects, and COM+ Applications
Applies To: Windows Server 2003, Windows Server 2003 with SP1
In addition to installing any software that you installed earlier in the migration process, there can be MTS packages, COM objects, and COM+ applications that need to be migrated. Table 6.5 lists the tasks that you need to complete to migrate MTS packages, COM objects, and COM+ application from earlier version of Windows.
Table 6.5 Migrating MTS Packages, COM Objects, and COM+ Applications
| Source Server | Target Server | Migration Tasks |
|---|---|---|
MTS packages on Windows NT 4.0 Server |
COM+ applications |
Convert the MTS package to a COM+ application. |
COM objects |
COM objects |
Copy COM object files (.dll or .exe) from the source server to the target sever and register the COM object by running the regsrv32 command. |
COM+ applications on Windows 2000 Server |
COM+ applications |
Create the COM+ application on the target server and use the same configuration on the target server that existed on the source server. |
For more information about migrating MTS packages, COM objects, and COM+ applications to Windows Server 2003, see the following articles: COM: Delivering on the Promises of Component Technology, and Microsoft .NET/COM Migration and Interoperability.
An example of registering a COM object that is running on the source server is CDONTS. If you decide to not modify your code to us CDOSYS instead of CDONTS, you must copy the Cdonts.dll file from the source server to the target server and then register Cdonts.dll with Windows Server2003. For more information about how to migrate CDONTS, see Migrate CDONTS.