Considerations for the Independent DeltaV Domain Controller

The following must be considered when using the Independent DeltaV Domain Controller.

The Independent DeltaV Domain Controller:

must be configured using the setup application provided with the DeltaV media. The Independent DeltaV Domain Controller setup application will not proceed on a computer previously configured as a domain controller by some means other than with the Independent DeltaV Domain Controller setup application.
cannot be used in conjunction with DeltaV systems where any DeltaV node is also configured as a domain controller.
can only be used as a domain controller and cannot be used as a multi-purpose computer.
must use a firewall (physical or Windows) for all network connections.
must evaluate any non-domain trust/authentication activity on the external (non-ACN) network card and block (with a firewall) any non-essential communications (for example, NTP communication must be blocked).
can be a virtual machine using the appropriate DeltaV Virtual Studio blank operating system template for the supported operating system.

For a complete specification of the Independent DeltaV Domain Controller (along with Emerson part numbers for ordering), refer to the DeltaV Workstation and Server Hardware product data sheet.

It is strongly recommended to use the DeltaV Firewall IPD between the Independent DeltaV Domain Controller and the rest of the workstations on the DeltaV domain. The DeltaV Firewall IPD is documented in DeltaV Books Online as well as in the Emerson KBA NK-1600-0290.

Important

Other than the configuration changes outlined in KBA NK-1600-0290, do not change the firewall IPD configuration unless you are specifically instructed to do so by Emerson. Changing the configuration may adversely affect communications on the network.