Configure the Windows service

To ensure that PI Interface for OPC DA restarts when the interface node is restarted, configure it as a Windows service.

Note: As a security defense, AVEVA recommends running the interface service under an account with minimum privileges, such as a Windows built-in service virtual account, the built-in Network Service account, or a non-administrative account that you create. For more information about security, see Best practices.

Use PI ICU to install the interface as a service.

1. Launch PI ICU and select the Service tab.

2. Set the fields as described in the following table.

   Field	Description
   Service name	Descriptive name for the interface service.
   ID	Numeric ID of the interface instance. Must be unique for each instance.
   Display name	The service name displayed in the Windows Services control panel. The default display name is the service name with a PI- prefix. You can override the default. To ensure that AVEVA-related services are sorted together in the Services control panel, retain the PI- prefix.
   Log on as	The Windows user account associated with the service. The user must have DCOM permissions configured on the OPC server. Set password expiration to Never.
   Password	Password, if any, for the preceding user.
   Dependencies	Any services that the interface depends on. The only dependency is the TCP/IP service, which is pre-configured. If buffering is enabled, you are prompted to create a dependency on the buffering service.
   Startup type	Specifies whether the interface service starts automatically when the interface node is restarted. Generally, interface services are set to start automatically.

3. To create the service, select Create.

4. To start the service, select the button.