0% found this document useful (0 votes)
36 views2 pages

AVEVA System Platform 2020 Antivirus Exclusions

Uploaded by

mayursinh.parmar
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
36 views2 pages

AVEVA System Platform 2020 Antivirus Exclusions

Uploaded by

mayursinh.parmar
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Doc Type Tech Notes

Doc Id TN000032662

Legacy Doc Id TN10567

Publish Date 2/3/2021

AVEVA System Platform 2020 (formerly Wonderware) AntiVirus exclusions

PROBLEM

Title

AVEVA System Platform 2020 (formerly Wonderware) AntiVirus exclusions

SOLUTION

Summary

Configure your antivirus software to prevent the files and directories listed below from being scanned.

Important Note: The paths listed here may be different, based on your installation. If you are using AVEVA Historian, formerly Wonderware,
ensure you exclude any folder that contains history blocks.

Action

ArchestrA folder exclusions:

C:\ProgramData\ArchestrA\ and all subfolders


C:\Program Files\Common Files\ArchestrA\
C:\Program Files (x86)\ArchestrA\
C:\Program Files (x86)\Common Files\ArchestrA\
C:\Program Files (x86)\FactorySuite\ (The FactorySuite directory may not exist in newer installations)
C:\Program Files (x86)\Wonderware\
C:\Program Files (x86)\AVEVA\
C:\ProgramData\Wonderware\
C:\Users\Public\Wonderware\
C:\InSQL\Data\ (The InSQL folder may not exist in newer installations)
C:\Historian\Data\

History Store Forward directory:

C:\Users\All Users\ArchestrA\ (default location)

Checkpoint directory location default location:

C:\Program Files (x86)\ArchestrA\Framework\bin\

InTouch HMI Application folder path:

C:\Users\Public\Wonderware\InTouchApplications (default folder path), select an application folder path while an InTouch HMI application is
created.

Licensing folder and file paths:

C:\ProgramData\AVEVA\Licensing
C:\ProgramData\FNEServer
C:\Userprofile\.avevalic file
Note: The avevalic file will not be available by default. This file will be created by the user, to acquire the License from particular Part
Number.

Terms of Use| Privacy Policy


© 2021 AVEVA Group plc and its [Link] rights reserved.
SMC Logger Storage file path:

C:\ProgramData\ArchestrA\LogFiles\
C:\Documents and Settings\All Users\Application data\Archestra\LogFiles\

Windows Temp folder exclusion:

Exclude these files from the C:\Windows\Temp folder:

*.aFDX

SQL Server Database exclusion:

Exclude the files in the SQL Server database location:

C:\Program Files (x86)\Microsoft SQL Server\[Link]\MSSQL\DATA\ (will vary by SQL Server version)

Exclude SQL Server database files within this directory with below listed types:

.mdf
.ldf

You can also exclude these file types (optional):

*.idx
*.pdx

Supporting Information

Exclude the files in the lowest level subfolder of the listed directories in this section. Antivirus exclusions should not be recursive and should only
apply to the lowest listed subfolder in the specified folder path.

Note: System Platform 2020 is only supported on x64 Operating Systems and SQL Server. A 64-bit operating system and SQL Server versions
are now required for all System Platform core products:

Application Server
AVEVA OMI (formerly InTouch OMI)
AVEVA InTouch HMI (formerly Wonderware), and
AVEVA InTouch HMI (formerly Wonderware).

Running in a 64-bit environment provides a common environment for all products, and ensures that you get the best performance from your System
Platform installation.

Related information: TN2865 Antivirus Exclusions for System Platform 2017

Terms of Use| Privacy Policy


© 2021 AVEVA Group plc and its [Link] rights reserved.

Common questions

Powered by AI

Excluding specific files, like *.aFDX, within the Windows Temp folder from antivirus scans is important for AVEVA System Platform 2020's operation since temporary files can include processes vital for real-time operations. Scanning these files can lead to unnecessary latencies and interruptions, hence excluding them is essential for seamless system functionality .

AVEVA System Platform 2020 ensures compatibility with antivirus exclusion practices for SQL Server databases by recommending exclusions tailored to both system and SQL Server requirements. This involves excluding crucial database files within the C:\Program Files (x86)\Microsoft SQL Server\MSSQL.MSSQLSERVER\MSSQL\DATA\ directory, accommodating varying versions of SQL Server and aligning system performance without sacrifice due to antivirus restrictions, thereby safeguarding database integrity .

Excluding the SMC Logger Storage file path from antivirus scans is significant because this directory, located at C:\ProgramData\ArchestrA\LogFiles\, contains log files critical for monitoring and troubleshooting the system. Scanning could alter or interfere with log file integrity, thereby impairing the system’s ability to produce accurate logs needed for diagnostics and performance analysis .

Excluding specific file types such as .mdf and .ldf from antivirus scans within the SQL Server database location helps maintain uninterrupted database operations. These files are essential for database functionality and performance; continuous scanning can significantly slow down access and lead to potential corruption or data loss, thus compromising the system's reliability .

Configuring antivirus exclusions for specific directories in AVEVA System Platform 2020 is recommended to prevent the antivirus software from scanning important files and directories that could interfere with the proper operation of the platform. This includes preventing performance issues and ensuring that critical data files such as those associated with the historian and SQL databases remain uninfluenced by antivirus scans, which could otherwise lead to corruption or loss of crucial operational data .

AVEVA System Platform 2020 requires a 64-bit operating system to ensure optimal performance across its core products such as Application Server, AVEVA OMI, and AVEVA InTouch HMI. This mandatory shift to 64-bit systems builds upon the platform's latest performance and compatibility improvements over its precursors, facilitating a unified environment for system operations .

The avevalic file plays a critical role in managing the licenses for AVEVA System Platform 2020 by being used to acquire the license associated with specific Part Numbers. It might not be available by default because it is created by the user as part of the licensing process, indicating that the file handling is contingent on user-driven license acquisition activities .

The antivirus exclusions for AVEVA System Platform 2020 emphasize the transition to a fully 64-bit environment, reinforcing the necessity for running on x64 Operating Systems and SQL Server versions, unlike in 2017 where 32-bit components may have still been in use. This update implies a broader compatibility requirement for modern core products like Application Server and AVEVA OMI, thus possibly introducing more sophisticated directory structures that require careful exclusion to avoid performance hindrances .

For the AVEVA Historian component, it is essential to exclude directories containing history blocks from being scanned by the antivirus. The key directories specified include the History Store Forward directory located at C:\Users\All Users\ArchestrA\ and the data directory at C:\Historian\Data\. Excluding these folders helps maintain historian functionality efficiently .

Exempting the ABServer and FactorySuite directories from antivirus scans is crucial because these directories often house application server core files and components essential for system operations. The exclusion means reduced interference from antivirus activities, which might otherwise delay or destabilize real-time data processing and application control. These measures optimize system performance while preserving the integrity of essential processes within FactorySuite-based applications .

You might also like