Skip to main content
Waters

Can any antivirus software be used with MassLynx? - WKB8718

Article number: 8718

ENVIRONMENT

  • MassLynx 4.1
  • MassLynx 4.2
  • Symantec
  • Antivirus
  • FireEye

ANSWER

MassLynx operation with Symantec Endpoint Protection antivirus software is supported. Which version of Symantec was tested with each MassLynx version is described in the MassLynx release notes.

This does not indicate that any comprehensive testing is done with this antivirus software specifically. It indicates that MassLynx tested on Windows machines running a specific version of Symantec antivirus software has not shown any issues.

However, when antivirus software is configured to run automatically, it has occasionally interfered with MassLynx.

Therefore, Waters recommends the following:

  • Full virus scans should be scheduled for times when MassLynx is not in use.
  • Exclude C:/MassLynx,  C:/Program Files (x86)/Waters Instruments folders, and any other MassLynx related folders from real-time scanning.
  • Create an exclusion for .RAW files.
  • Disable Heuristic AV software  and Network Threat Protection (if using Symantec Endpoint Protection).
  • Disable real-time, automatic updates. Only download and install antivirus updates (including definitions updates) when not acquiring data.

It is the customer's responsibility to evaluate compatibility and, if needed, find alternative solutions if the proposed software conflicts with MassLynx.
 

ADDITIONAL INFORMATION

Recommendations for configuring antivirus software other than Symantec.

The following information is intended only as a framework that customer's IT specialist can use when evaluating MassLynx compatablity of antivirus software other than Symantec. This does not imply other antivirus software is supported with MassLynx.

  1. For Symantec we recommend users turn off Network Threat Protection, which is effectively a firewall. Also turn off the equivalent function in your antimalware software.
  2. Exclude .raw files from scans
  3. Exclude the following folders from scans (which of these is applicable depends on the software purchased)
    • C:\MassLynx\
    • C:\Program Files (x86)\Waters Instruments\
    • Locations of all MassLynx projects and raw data.
    • C:\PLGS3.0.3\ (or other version of PLGS as appropriate)
    • C:\Program Files (x86)\Nonlinear Dynamics\
    • C:\Program Files\Waters\ (this includes the DynamX installation folder)
    • C:\BiopharmaLynx1.3.x\
    • C:\Driftscope\
    • C:\MSeDataviewer\
    • The locations of all PLGS3 databases, including C:\ProgramData\Waters\
  4. Schedule antivirus scans so that they do not run when data is being acquired and/or processed.
  5. Schedule antimalware updates (including definitions updates) so that they are not downloaded or installed while data is being acquired or processed. Ideally, either turn software updates off, or configure them so that they alert the user to download and install manually rather than automatically.
  6. Firewalls.

    • Make sure all firewalls are disabled on the instrument LAN, including both the Windows firewall and any proprietary firewall included in the security software installed. Note that in some security software the firewall has a different name, for example Network Threat Protection in Symantec is effectively a firewall.

    • The Windows PC firewall can occasionally be re-enabled by windows updates, so after every Windows update the firewall should be checked to ensure it is still disabled.

    • If there are other firewall restrictions on the customer's network it may be necessary to configure the firewall to allow all MassLynx associated processes through, and also java processes (PLGS and BPL are java based), if data is being read / written across the network.

  7. The advice on when to schedule updates also applies to Windows updates and other software updates

  8. User Account Controls should be set to the lowest setting during software installation. Higher UAC settings can effectively restrict the permissions of the Administrator account to those of a standard user account. This can cause problems installing software and / or configuring ACQUITY modules.

Not able to find a solution? Click here to request help.