Remote access

Connecting to a domain-based DeltaV computer from any workgroup-based computer

When connecting from a workgroup-based computer to a domain-based client, you must configure the user accounts appropriately. Two user accounts that must be configured are the client's logged on user and the DeltaVAdmin user account. This is because of requirements for DCOM authentications.

DCOM applies to any client in a workgroup that needs to access DeltaV data (such as any DeltaV historian or the Alarms and Events data) using OPC clients. For example, DCOM is used where you install OPC Remote on a client (for example, Batch Analytics). It is also required for any DeltaV engineering application run from a DeltaV Remote computer (or a Remote Remote computer where both levels are in workgroups).

The general rule is to configure
Note

The local user must exist on the DeltaV ProfessionalPlus workstation.

In addition, configure the following:
Important
The following rules must be adhered to when creating a local DeltaVAdmin account on ANY computer (DeltaV or non-DeltaV):
  • Always configure the local DeltaVAdmin account to not allow local or remote login.

    Use gpedit.msc under Local Computer Policy → Computer Configuration → Windows Settings → Security Settings → Local Policies → User Rights Assignment.

    Add the local DeltaVAdmin account to the Deny log on locally and Deny log on through Remote Desktop Services policies.

  • The DeltaVAdmin accounts must remain synchronized (that is, passwords must match) at all times.
  • When a DeltaV-side, local DeltaVAdmin account is required, only make it a member of the local DeltaV user group. Do not make it a member of any Administrator-level groups.

The tables in subsequent topics detail the user account configuration.