Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

PI Interface for OPC Alarms and Events

Installing the interface service manually

  • Last UpdatedOct 27, 2026
  • 2 minute read

Help for installing the interface as a service is available at any time with the command:

PIOPCAE.exe -help

Open a Windows command prompt window and change to the directory where the PIOPCAE.exe executable is located. Then, consult the following table to determine the appropriate service installation command.

Windows Service Installation Commands on a PI Interface Node or a PI Data Archive Node with Bufserv implemented

Manual service

PIOPCAE.exe -install -depend "tcpip bufserv"

Automatic service

PIOPCAE.exe -install -auto -depend "tcpip bufserv"

*Automatic service with service id

PIOPCAE.exe -serviceid X -install -auto -depend "tcpip bufserv"

Windows Service Installation Commands on a PI Interface Node or a PI Data Archive Node without Bufserv implemented

Manual service

PIOPCAE.exe -install -depend tcpip

Automatic service

PIOPCAE.exe -install -auto -depend tcpip

*Automatic service with service id

PIOPCAE.exe -serviceid X -install -auto -depend tcpip

* - When specifying service id, the user must include an id number. It is suggested that this number correspond to the interface id (/id) parameter found in the interface .bat file.

Check the Microsoft Windows Services control panel to verify that the service was added successfully. The services control panel can be used at any time to change the interface from an automatic service to a manual service or vice versa.

The service installation commands in this section create an interface service that runs under a low-privilege built-in account. On Windows 8.1 and Server 2012 and later, the service logs on as the service virtual account. For earlier versions of Windows, the service logs on as Network Service.

Note: For best security, we recommend running this interface service under an account with minimum privileges, such as a Windows service virtual account, the built-in Network Service account, or a non administrative account that you create.

The services control panel can change the account that the interface service runs under. Changing the account while the interface service is running does not take effect until the interface service is restarted.