Register AVEVA Historian servers

When you install AVEVA Historian, it registers the local machine as a Historian server. If you want to administer remote Historian servers, you must first register them within the console. When you register a server, you are giving the Operations Control Management Console a logical name and login IDs to connect to both:

• The AVEVA Historian Configuration Manager.

• The Microsoft SQL Server database.

You can register and administer multiple historians from within a single instance of the console. When registering a server, a list of your previously registered servers is available for selection.

To be able to administer the Historian (for example, start and stop the server), you must provide a Windows security login that has administrative rights on the AVEVA Historian computer. You also must be logged in as a Historian administrator, with the aaAdministrators database role enabled. If you are using the console remotely for the AVEVA Historian, you do not need to be an administrator on the computer on which you are using the console on.

If you do not supply the login when you register the server, you are prompted to supply it when you attempt to execute an administrative command. If the login you supply does not have administrative permissions, the Management Console is set to read-only mode.

The SQL Server login you use must have the "aaAdministrators" database role to make changes to the Historian system configuration, as it is stored in the Runtime database. By default, Windows accounts that are members of the local Windows "aaAdministrator" group are assigned this role. If you do not log in with the SQL Server administrative permissions, functionality is restricted. You must have aaPowerUsers capability enabled to make tag-level changes.

All registration information associated with a particular server name is stored in the Windows registry on the computer running the Operations Control Management Console, not in the console file (.MSC). In addition, all registration information is stored according to the current user. This has the following implications:

• If you register the same Historian in multiple console files (.MSC), and you then edit the status or configuration for the Historian in one .MSC file, the status and configuration is reflected in the other .MSC files in which that Historian appears.

• If you copy a saved .MSC file from one computer to another, the registration properties for a particular Historian are not copied with the .MSC file.

• The same Historian can have different registration properties for each user who logs on to the Operations Control Management Console computer, even though all users may be using the same .MSC file.

  Important: In 2022, Microsoft is releasing a phased update to address a security issue with DCOM on Windows. After the third phase of this update is applied, administering remote Historian servers will no longer be possible using the Operations Control Management Console. Instead, you can administer remote Historian servers by first connecting with the remote desktop software of your choice, and then using the Operations Control Management Console on the remote server.

  For more up-to-date information about the vulnerability, and a timetable for its phased release, see https://msrc.Microsoft.com/update-guide/vulnerability/CVE-2021-26414.