Darshan,
For DCOM to work with PCo and Kepware, you have 2 options to configure the user access:
1. Allow full DCOM access for domain users that are members of the server Administrators group, EVERYONE, SYSTEM and NETWORK, and allow PCo and Kepware services to run under LocalSystem account (some network admins will not allow this as it opens potential network security holes)
2. Define named users or named Domain Group permissions for DCOM.
2.1. Use the named user or users that are members of the named Domain Group for the following:
- named user for Kepware server_runtime service
- named user for PCo Agent Instances
- administrative user to log into to PCo remote Desktop
Avoid hosting PCo and remote OPC Servers on different Domains or on Workgroups -- should always be in the same Domain.
I strongly recommend that you migrate to Kepware V5 and investigate using the Kepware OPC UA interface along with PCo OPC UA Agent where you are going to have remote OPC Server requirements, and avoid the DCOM issues altogether.
Installing Kepware on PCo server, or PCo on the Kepware server will remove any DCOM configuration requirements.
Regards, Steve
