TRITECH SOFTWARE SYSTEMS -2015 - Laserfiche WebLink

Home Browse Search

Chapter 3 - System Components B. As with any network/system change, it is a good practice to install the software initially on a limited number of computers and then monitor for performance or any other anomalies that were not occurring prior to the installation of the software. Monitor for a one to two week period of time. If everything appears to be fine, deploy on the rest of your system and monitor for problems. 20.3.3 SCHEDULED VIRUS PROTECTION RECOMMENDATIONS 1. Definition files should be updated before the scheduled scans are started. 2. Nightly scans should be configured so that they do not interfere with normal call activity or the nightly maintenance routines (i.e. Backups, etc.). 3. All TriTech folders and files can be scanned during a scheduled virus protection scan. This includes the Inform CAD file structure on the File Server, and the TriTech folder and all of its subfolders on business servers and workstations, the Inform CAD file structure on Mobile Servers, and the Inform RMS file stricture on Law RMS Servers and Workstations. As noted in the general recommendations network and/or mapped drives should not be scanned. Do not scan the Inform CAD Q: (network drive) from a workstation.) 4. As noted in the Platform Specific Recommendations, Microsoft and EMC require files to be excluded from any virus scanning to protect against data corruption. a. UNDER NO CIRCUMSTANCES should the SQL Server's "Data" directory ever be scanned. Configure your virus scan activities to exclude this directory, which on a typical SQL Server installation will be the "\Program Files\Microsoft SQL Server\MSSQL\Data" directory. Disabling the scanning of the SQL Server "Data" files by type is also acceptable, they can be identified by having one of the following file extensions-*.mdf, .ndf, and *.ldf. The full Microsoft guidelines for configuring SQL Server with Virus Protection software can be found at: http://sgpporL.microsoft.comlkb/309422. b. EMC recommends that the RepliStor "C:\Documents and Settings\All users\Application Data\Legato Replistor Data" be excluded from active and scheduled scans. Refer to the RepliStor Administration Guide for additional information. 5. Expect performance impacts during the scan. 6. Stagger scans across the system so that performance impacts will be dispersed. 7. Notify users about the scan and expected performance impacts. 20.3.4 ACTIVE SCANNING RECOMMENDATIONS 1. When implementing on -access scanning, it should be done in a conservative mariner. Heuristics should NOT be used. Typically, the default configuration will have heuristics disabled. 2. Perform active scanning at the Network level where vulnerability of a virus infection is most likely, this is generally where access to or from an outside source is possible such as an E-mail server or an Internet server. 3. As noted in the Platform Specific Recommendations, Microsoft and EMC require files to be excluded from any virus scanning to protect against data corruption. a. UNDER NO CIRCUMSTANCES should the SQL Server's "Data" directory ever be scanned. Configure your virus scar activities to exclude this directory, which on a typical SQL Server installation will be the "C:\Program Files\Microsoft SQL Server\MSSQL\Data", D:\\MSSQL\DATA and L:\MSSQL\Logs directories. Disabling the scanning of the SQL Server "Data" files by type is also acceptable, they can be identified by having one of the following file extensions -*.md f .ndf, and *.Idf. The full Microsoft guidelines for configuring SQL Server with virus protection software can be found at: http://supportanierosoft.com/kb/309422 8 The contents of this material are confidential and proprietary to TriTech Software Systems, Inc. and may not be reproduced, 3 published or disclosed to others without the prior written consent of TriTech Software Systems, Inc. ©2015 TriTech Software Systems