The following table illustrates the user accounts and where they are created when connecting a workgroup-based OPC or other DCOM client to a domain-based DeltaV computer (for example a DeltaV Remote Access Server (RAS), an OPC Server, a DeltaV Batch Historian, or DeltaV Batch Executive).
| Where the user is | Local User Account?
(not the DeltaVAdmin user account) |
Local DeltaVAdmin User Account? | Notes |
|---|---|---|---|
| Client side | YES | YES |
Whenever there is a local account on both sides, the passwords must match on both sides. Important For the DeltaVAdmin user account, all local DeltaVAdmin passwords must match the DeltaV DOMAIN account (that is, Domain\DeltaVAdmin). |
| DeltaV side
(That is, the DeltaV computer to which you are connecting.) |
YES
The local user must exist on the DeltaV ProfessionalPlus workstation. Note The local account on the client must match the domain account that is also a DeltaV user (a DeltaV database account) so that the local user will be granted the same DeltaV privileges as the domain user. |
NO |
Whenever there is a local account on both sides, the passwords must match on both sides. Important For the DeltaVAdmin user account, all local DeltaVAdmin passwords must match the DeltaV DOMAIN account (that is, Domain\DeltaVAdmin). |
Always configure the local DeltaVAdmin account to not allow local or remote login.
Use gpedit.msc under .
Add the local DeltaVAdmin account to the Deny log on locally and Deny log on through Remote Desktop Services policies.