Install PI Vision

When you install AVEVA PI Vision for the first time, the AVEVA PI Vision database must be created. Therefore, the user performing the installation (through the installation program, administration web site or by using the Go.ps1 script) must have the appropriate privileges, which you can typically obtain from your organization's database administrator. The privileges that you need vary depending on if you are using on-premises SQL Server, Azure SQL Database, or Amazon RDS for SQL Server. To check the privileges that you need, refer to Required SQL permissions.

Note: AVEVA PI Vision is automatically configured to read PI AF Identities (used for controlling access to AVEVA PI Vision displays) from the PI AF server that is marked as the Default AF Server at the time of installation for AVEVA PI Vision. To change this setting to another PI AF server, see Select an authentication mode and identity AF server.

Make sure you have met the prerequisites listed in Pre-install checklist.

Follow the steps in this procedure to install AVEVA PI Vision for the first time.

1. Log on to the application server with a user account that belongs to the local Administrators group.

2. Right-click the AVEVA PI Vision setup executable and select Run as Administrator to launch the installation wizard.

   The installer displays a list of software components that are required by AVEVA PI Vision. Some components might already be present.

3. Review the list of software components and select OK to proceed with the installation.

   Select Next as you progress through the prompts.

4. Run the AVEVA PI Vision installation wizard, which prompts you to specify:

   • A destination folder for AVEVA PI Vision. We strongly recommend that all PI components are installed in the same root folder. For example, Program Files\PIPC.

   • A website name where AVEVA PI Vision will be installed. Select the name of a dedicated website where no other applications are installed.

   • An account type for the account to run the application pools that access the SQL server, as well as the Data Archive, and PI AF servers if in the security settings you plan to select the Use Windows identity of the IIS application pools authentication option for the Connection to PI Data archive and AF Servers (this is optional if using OpenID Connect only, but required if using Windows authentication). Select Default to use the ApplicationPoolIdentity account, or select Custom and enter the username and password for the account. To change the account after installation, see Configure PI Vision application pools to use the PI Vision service account.

   Note: If installing PI Vision on a server that is on a domain, we strongly recommend that you create a domain account for the AVEVA PI Vision service. If you use the machine account (the default), then all the applications running on the application server computer will have the same access as the AVEVA PI Vision service to the SQL server, as well as the Data Archive, and PI AF servers if you plan to select the Use Windows identity of the IIS application pools authentication option for the Connection to PI Data archive and AF Servers. Using the machine account is a security risk. At a minimum, consider removing some or all of the other applications running on this computer. For more information, see Create a service account and set up permissions.

   The AVEVA PI Vision installation wizard creates the following items:

   • The pre-populated Windows groups on the application server: PI Vision Admins, PI Vision Users, and PI Vision Utility Users.

   • The AVEVA PI Vision Administration website

   • The AVEVA PI Vision website, plus the application pools: PIVisionServiceAppPool, PIVisionAdminAppPool, and PIVisionUtilityAppPool