Factorysoft Opc Client Install File

FactorySoft OPC Client Install — Step-by-step guide

This article walks through installing and configuring the FactorySoft OPC Client so you can connect to OPC servers, read/write tags, and troubleshoot common issues. Assumes Windows environment (FactorySoft products are typically Windows-based).

4.4 Completion

  • ✅ Uncheck View Release Notes (optional)
  • ✅ Check Launch FactorySoft OPC Client
  • Click Finish

1. Understanding the Landscape

Before clicking "Next" on any installer, it is vital to understand what the FactorySoft OPC Client actually does. factorysoft opc client install

The Architecture: The FactorySoft OPC Client is a "COM/DCOM" based application. It acts as a middleman. It connects to an OPC Server (the software that talks directly to the hardware, like RSLinx, Kepware, or Matrikon) and exposes that data to a client application (like a VB6 app, an Excel spreadsheet, or a custom HMI). FactorySoft OPC Client Install — Step-by-step guide This

Why you are installing it today: You likely are not installing this on a brand-new Windows 11 machine for a greenfield project. You are likely: ✅ Uncheck View Release Notes (optional) ✅ Check

  1. Reformatting a crashed Windows XP machine.
  2. Virtualizing a legacy workstation.
  3. Trying to get a 15-year-old Excel reporting macro to work on a newer OS.

3. Installation Steps (Concrete, actionable)

  1. Obtain installer: download the FactorySoft OPC Client installer executable (assume FactorySoft_OpClient_Setup.exe).
  2. Verify digital signature and hash (SHA-256) of the installer.
  3. Run installer as Administrator.
  4. Choose installation folder (default: C:\Program Files\FactorySoft\OPC Client).
  5. Select components: Core client, OPC Classic DCOM Helper, OPC UA module (if available), Documentation.
  6. During install, allow the installer to configure required Windows Firewall rules or note ports to open:
    • OPC Classic (DCOM/RPC): dynamic ports; open TCP 135 and configure RPC range (e.g., 50000–51000) if server-side firewall present.
    • OPC UA: default TCP 4840 (or configured port).
  7. Post-install configuration wizard: specify OPC server endpoint (hostname/IP), authentication credentials, and tag subscription parameters (sampling interval, deadband).
  8. Configure DCOM settings for OPC Classic (on both client and server machines):
    • Run dcomcnfg → Component Services → Computers → My Computer → Properties → COM Security: set limits/launch permissions for the service account.
    • Set default authentication level to Connect/Packet Privacy as required.
  9. Import/accept OPC UA server certificates into the Client’s certificate store if using OPC UA.
  10. Start the client service/agent and verify connectivity using built-in OPC Server Browser.

8. Security Considerations

  • Use OPC UA with TLS and certificates where available.
  • Restrict network access with firewalls and VPNs.
  • Apply least-privilege accounts for services.
  • Keep software and OS patched.
  • Secure local storage of credentials; prefer Windows Credential Manager or encrypted stores.

RELATED ARTICLESMORE FROM AUTHOR