| Reference information | |
|---|---|
| Project page | COM Classes and Typelibs |
| Related topics | Working with attribute panes |
A DCOM Server object represents a DCOM server registration or unregistration. It is used to specify the configuration options of one or more distributed COM classes that are hosted by a single executable. The applicable COM classes refer back to the DCOM server through their AppID attribute.
Registration or unregistration of a DCOM server is controlled by its component and any COM classes that specify its AppID. The details differ somewhat between Tarma Installer and Windows Installer.
| Situation | Tarma Installer | Windows Installer |
|---|---|---|
| Not linked to a component | The DCOM server is registered if at least one COM Class with its AppID is registered. |
The DCOM server is registered if at least one COM Class with its AppID is registered. The DCOM servers's own component, if any, is ignored. |
| Linked to a component | The DCOM server is registered if its component is installed. |
The Tarma Installer approach allows you to register a DCOM server either implicitly, if one of its dependents is registered, or explicitly, for example if it doesn't have any dependents. See COM Classes and Typelibs for more information.
This pane contains the following attributes and options.
| Attribute | Description | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| AppID | Enter the GUID (Globally Unique IDentifier) of the DCOM server the distributed COM classes. | ||||||||||||||||
| Display name |
Enter the user-visible name of the DCOM server.
|
||||||||||||||||
| Surrogate .exe |
Name of the DLL surrogate process, used for disambiguation of the surrogate process name specified by DLL surrogate. This option only has effect on Windows Server 2003 and later, and is used as the first parameter (lpApplicationName) of the CreateProcess function call that the DCOM subsystem uses internally to start the DLL surrogate proces that you specify through DLL surrogate.
|
||||||||||||||||
| DLL surrogate | Enter the file name or full path to the executable that provides the surrogate process for a DLL-based DCOM server, or leave blank for a system-supplied surrogate executable (if required). | ||||||||||||||||
| Local service | Enter the name of the service if the distributed COM class is implemented and installed as a service rather than (or in addition to) a regular executable program, or leave empty for a non-service implementation. | ||||||||||||||||
| Parameters |
Enter any start-up parameters for the Local service service; these will be used when the service is started by the DCOM subsystem. |
||||||||||||||||
| Remote server | Enter the name of the network server on which the COM class objects must run if no COSERVERINFO information is specified during object activation, or leave empty for no preference. | ||||||||||||||||
| Endpoints |
Enter the TCP port number(s) to be used by the DCOM server for communication, or leave empty to let the DCOM subsystem assign port numbers dynamically. The Endpoints field must use the following format: ncacn_ip_tcp,0,port where port is the TCP port number to use between 1024 and 65535.
|
||||||||||||||||
| Authentication |
Select the required authentixation level from the drop-down list. The following choices are available:
|
||||||||||||||||
| Activate at storage | Check this box to instantiate COM objects on the same machine as the persistent state from which they are initialized; clear it not to force this behavior. | ||||||||||||||||
| Trust level |
Select the desired trust level for the DCOM server. This option only has effect on Windows XP and later. The following choices are available:
|
||||||||||||||||
| Run As |
Enter the user account name under which the COM class must run when activated; leave empty to use the default DCOM user account. The Run As name must have one of the following formats:
|