Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
VirtaMove Knowledge Center
/
COM+ and DCOM Requirements
Published Mar 02, 2022

    COM+ and DCOM Requirements

    The requirements for COM+ and DCOM are as follows.

    Requirement

    Description

    Registry key value Com+Enabled

    If the registry key value Com+Enabled in the HKLM\SOFTWARE\Microsoft\COM3 registry key is set to 0 (disabled) on the source machine, attempts to connect from the destination machine to the source machine and list COM+ applications on the source machine will result in an error.

    If Com+Enabled is disabled on the destination machine, it will not be possible to list COM+ applications on the destination machine or install COM+ applications on the destination machine, which means that containers that have COM+ application packages will fail to dock.

    Additionally, if RemoteAccessEnabled is disabled on the source machine, attempts to connect from the destination machine to the source machine and list COM+ applications on the source machine will result in an error.

    Membership in the Distributed COM Users Group

    The account used to perform the export (the account specified in the tether credentials) must be a member of the Distributed COM Users group on the source machine. Otherwise, the export will fail.

    Configure your firewall to allow DCOM connections

    You may need to configure your firewall to allow DCOM connections. For information, see:

    How to Configure the Firewall to Allow DCOM Connections

    AutoShareServer  and LocalAccountTokenFilterPolicy registry keys

    For less than Windows Server 2008

    The following key must be set to 1 or undefined:

    Local SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\AutoShareServer

    For Windows Server 2008 or higher

    The Remote Account must be the built-in Administrator (not just an Administrator), or the following key must be set to 1 on both the source and destination machine:

    SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\LocalAccountTokenFilterPolicy

    complusnetwork registry key

    For Windows Server 2003 Source Machines

    To ensure that VirtaMove can access COM/COM+ components related to your application, the Application Server Role must be installed and the following key must be enabled (set to 1) on the source server:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\OC Manager\Subcomponents\complusnetwork

    A reboot is not required after you change the value of this key.

    For Windows Server 2008 and Higher Source Machines

    For Windows Server 2008 and higher source machines, the complusnetwork key does not exist. However, port 135 must be open to allow VirtaMove access to COM/COM+ components. For more information, see: https://technet.microsoft.com/en-us/library/cc731967(v=ws.11).aspx.

    To enable the Com+Enabled registry key

    Enable the Com+Enabled key as follows:

    1. Start Registry Editor.

    2. Locate and click the following key in the registry: HKEY_LOCAL_MACHINE\Software\Microsoft\COM3

    3. Set the registry key value RemoteAccessEnabled to 1

    4. Set the registry key value Com+Enabled to 1.

    5. Quit Registry Editor.


    VirtaMove Documentation
    • VirtaMove Support Knowledge Base
      VirtaMove Support Knowledge Base
       This trigger is hidden
    Results will update as you type.
    • V-Migrate Documentation
      • 01. Managing Your VirtaMove Licensing
      • 02. Installation Guide
      • 03. Application Migration Guide
        • Environmental and Machine Requirements for Migration
          • Environmental and Machine Requirements
          • Understanding Audit
          • Comparing Firewall Rules
          • Comparing Group Policies between Source and Destination
          • COM+ and DCOM Requirements
        • Introduction to VirtaMove Application Migration
        • Activating Your VirtaMove License
        • Migrating an Application
        • Migrating an IIS Application
        • Using VirtaMove Source Monitor
        • Monitoring Migration
        • Running and Exercising Your Application
        • Dissolving Your Application
        • Advanced Application Migration
      • 04. Administration Guide
      • 05. CLI Guide
      • About VirtaMove V-Migrate Documentation
    • V-Maestro Documentation
    • VirtaLinux Documentation

      You‘re viewing this with anonymous access, so some content might be blocked.
      {"serverDuration": 9, "requestCorrelationId": "78524a75a2d547ecb69f2f820aea2d48"}