Device Imaging Component and DCOM
12/14/2011
For better reliability and fault isolation, you can configure the device imaging component to run outside the Device Manager 2011 server by using Distributed COM (DCOM). The device imaging component must be registered on the Device Manager 2011 server and the server that hosts the device imaging component.
Important
To unregister or reconfigure the device imaging component, you must unregister the component on both the Device Manager 2011 server and the server that the device imaging component is on. You must then restart the Device Imaging service.
You can use the same device imaging components as local in-process COM and remote out-of-process DllSurrogate DCOM. This section contains procedures for configuring the device imaging component for remote out-of-process DCOM using DllSurrogate.
To set up DCOM, you must add several GUIDs to the Windows Registry subkeys. The following table describes the GUIDs you will need for the procedures in this section:
- Device imaging component GUID. This GUID is defined by the device manufacturer.
- Plug-in TypeLib GUID = {BE27CD75-D857-4C19-A784-6624AAC498FB}. This GUID is fixed and cannot be changed.
- AppID GUID. This GUID is defined by the IT administrator who deploys the device imaging component.
Note
For 64-bit editions of the operating systems, use the registry keys under Wow6432Node instead.
In This Section
- Configuring DCOM on the Server Running Device Manager 2011
Information about how to configure DCOM on the same server as Device Manager 2011.
- Configuring DCOM on the Remote Server
Information about how to configure DCOM on a remote server.
- Adding User COM Permissions
Information about how to add user COM permissions.