Step 1.2.1. Configure Registry Settings for Off-node Clients

Important: This procedure is supported for the CIMPLICITY OPC client. Third party OPC clients may require different settings.

This step only needs to be performed if the OPC client application is installed on a computer node other than the one on which CIMPLICITY and the OPC Server is installed.

Remote OPC client applications (i.e. client applications that run on a computer node other than the one running the GagePort Mitutoyo OPC Server) do have to have the GagePort Mitutoyo software installed on the remote machine in order to access the GagePort Mitutoyo OPC Server.

  1. Log onto the remote (client) node using an account with administrator privileges.

  2. Install the GagePort Mitutoyo OPC Server on the client node.

  3. Using the DCOMCNFG utility, select the Applications tab and double click the application labeled GagePort Mitutoyo OPC Server.

  4. Select the Identity tab.

  5. Check This user:

  6. Enter a User and Password that the OPC Server node can authenticate.

  7. Click OK.

Result: A client application on the remote node should now be able to reference the GagePort Mitutoyo Server (given that DCOM security issues have been addressed).

The ProgID of the OPC Server is GagePort Mitutoyo OPC Server and the CLSID is {BFBC14F0-1A51-11d5-9AD5-0050042953A6}.


The OPC GagePort server will take on the identity, privileges and permissions of the user account when activated by an OPC client. The chosen user account (either The interactive user or This user) must be authenticated on a remote OPC client node in order for some OPC interactions to occur (e.g. subscription notifications).

You must have identical user accounts with identical passwords on the OPC server and remote node, in order for the remote node to connect with the server.

More information

About DCOM security.

Step 1.2. Set up the GagePort OPC client.