DOCUMENT:Q161274  17-MAR-1997  [vbwin]
TITLE   :HOWTO: Port a Remote OLE Application to DCOM
PRODUCT :Microsoft Visual Basic for Windows
PROD/VER:5.00
OPER/SYS:WINDOWS
KEYWORDS:kbenv kbusage vb5all vb5howto VBKBAutomation VBKBDCOM kbhowto

======================================================================
---------------------------------------------------------------------
The information in this article applies to:

 - Microsoft Visual Basic Enterprise Edition for Windows, version 5.0
---------------------------------------------------------------------

WARNING: ANY USE OF THE INFORMATION PROVIDED IN THIS ARTICLE IS AT YOUR
OWN RISK. Microsoft provides this information "as is" without warranty of
any kind, either express or implied, including but not limited to the
implied warranties of merchantability and/or fitness for a particular
purpose.

IMPORTANT: For more information on DCOM, please see the following article
in the Microsoft Knowledge Base:

   ARTICLE-ID: Q158508
   TITLE     : COM Security Frequently-Asked Questions

IMPORTANT: This article contains information about editing the registry.
Before you edit the registry, you should first make a backup copy of the
registry files, which are hidden files in the Windows folder. If you do
not have backup copies of the registry files, before you proceed please
see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q101229
   TITLE     : How To Restore Windows NT Over an Existing Installation

SUMMARY
=======

To port a Remote OLE application to DCOM, several modifications to the
client registry are required. This article describes the necessary
changes.

MORE INFORMATION
================

WARNING: Using the Registry Editor incorrectly can cause serious problems
that may require you to reinstall Windows NT. Microsoft cannot guarantee
that problems resulting from the incorrect use of the Registry Editor can
be solved. Use the Registry Editor at your own risk.

Follow these steps to change the registration of an out-of-process OLE
server manually from remote automation to DCOM:

1. Remove the LocalServer32 and InprocServer32 subkeys of the component’s
   CLSID key.

2. Change the client registry as follows:

   [HKEY_CLASSES_ROOT\CLSID\{ Put Component CSLID Here }]
   "AppID"="{ Put Component CSLID Here }"

   [HKEY_CLASSES_ROOT\APPID\{ Put Component CSLID Here }]
   ="Put Component App Name Here"

   [HKEY_CLASSES_ROOT\APPID\{ Put Component CSLID Here }]
   "RemoteServerName"="Put Remote Server name Here"

   [HKEY_CLASSES_ROOT\APPID\Put Component File Name Here]
   "APPID"="{ Put Component CSLID Here }"

3. Use the DCOMCNFG.EXE tool in the server's Windows NT 4.0 system32
   directory to specify access and launch permissions for the server.

NOTE: You won't need to run the Remote Automation Manager with DCOM.
======================================================================
Keywords            : kbenv kbusage vb5all vb5howto VBKBAutomation VBKBDCOM kbhowto
Technology          : kbole
Version             : 5.00
Platform            : WINDOWS
Issue type          : kbhowto

=============================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS
PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND.  MICROSOFT DISCLAIMS
ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  IN NO
EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR
ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF
MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.  SOME STATES DO NOT ALLOW THE EXCLUSION
OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES
SO THE FOREGOING LIMITATION MAY NOT APPLY.

Copyright Microsoft Corporation 1997.