Geschrieben am 10. Dezember 2007 Keine Kommentare
Version 1.10.00.0000 of Panda GateDefender Integra incorporates a new anti-spam engine that notably improves performance and spam detection in real time.
The new system uses algorithms that calculate a unique set of identifiers for each message (Advanced Message Fingerprinting) and a global network made up of 180 million users sharing information. The system can process over 3,000 million messages every day in 160 countries and updates its knowledge base every 45 seconds. Also, it uses a local cache that ensures service continuity even if server connection is lost.
How to apply the upgrade
Version 1.10.00.0000 of Panda GateDefender Integra is available in the following formats:
- DVD, available from the Downloads area of the website.
Check how to download the latest version of Panda GateDefender Integra.
- On-demand upgrade from the GateDefender Integra console.
From the administration console, select Update, System software upgrade and click the New available version tab.
NOTE: Once Panda GateDefender Integra is upgraded, check the version by clicking the View version details button in the Current versions section.
Version 1.10.00.0000 of the Panda GateDefender Integra system software (firmware) also upgrades the rest of the modules to the following versions:
- Anti-malware engine version: 220.127.116.11
- Anti-spam engine version: Cloudmark 3045.1.0.29
- Web filtering version: 0.00.04.1392
- IPSec module version: 2.4.5
- IPS module version: 18.104.22.168
ISO Download via http://pandatechnik.de/144
- DVD, available from the Downloads area of the website.
Panda AdminSecure Administration Server
- Processor: Pentium III 800 MHz. The processor requirements may increase as the size of the network increases. For large networks (more than 500 computers), it is advisable to have a dedicated computer.
- Memory: 256 MB of RAM, although around 1 GB is recommended for large networks.
- Operating system:
- Windows NT4 SP
- Windows NT4 Terminal Server
- Windows 2000
- Windows Server 2000 SBS
- Windows XP
- Windows Server 2003 Enterprise Edition
- Windows Server 2003 SBS
- Windows 2003 R2
- Windows XP 64 bits
- Windows Server 64 bits
- Windows Vista 32 bits
In Windows NT4 SP6 Windows Installer 2.0 must be installed.
- Applications: Internet Explorer 5.5
The main objective of this FAQ is to detail the process of generating an installation package with an updated PAV.SIG file.
This process is suitable for companies with slow communication lines as it would prevent them from collapsing when the protection ( Panda Security for Desktops, Panda Security for File Servers etc…) is installed.
Installation of the package with an updated pav.sig:
From the console, go to Tools–> Updates and repositories–> Packages.
Select the protection you wish to install , for example, Panda Security for Desktops, and click on Generate Installer…
The package contains three files:
In the case of Panda Security for Desktops, the files are:
AVTC.EXE, CRC.DAT and CONFAVTC.INI
Edit the *.INI file.
Add the following line to the file:
Save the changes.
Copy an updated PAV.SIG file ( either from the SIGNATURE folder or from the download area at the Website ) in the same directory where the three installation files are located.
Copy the four resulting files in the machine where the protection is going to be installed and run the *.EXE file.
In the case of Panda Security for Desktops, the file to execute is AVTC.EXE.
The name of the configuration files vary depending on which protection is going to be installed:
Panda Security for Desktops (Windows NT-2000-XP) confAVTC.ini
Panda Security for File Servers (Novell NetWare) confAVNW.ini
Panda Security for File Servers (Windows NT-2000-2003) confAVNT.ini
One of the essential components of the AdminSecure architecture is the Database. When installing AdminSecure you can choose between different data engines:
- MSDE 2000: Free Microsoft data engine (AdminSecure, AdminSecure 2006, AdminSecure 2007)
- Microsoft SQL Server 7 or 2000 (AdminSecure, AdminSecure 2006,AdminSecure 2007)
- Microsoft SQL Server 2005 and SQL Express 2005 (AdminSecure 2006, AdminSecure 2007).
The typical installation will always use MSDE as the data engine. If an SQL server database already exists in the network, it is advisable to use it for the following reasons:
- It offers the user additional functions, such as including our database in the periodic backup copies so that they can be restored if necessary.
- MSDE has a series of disadvantages compared to SQL, which are particularly significant in corporate environments.
It supports multiple connections, but from 5 connections onwards, the computer´s performance may degrade or slow down, due to the monitoring process performed on the system by the workload governor.
- Maximum size of the database: 2 GB
- Maximum RAM supported: 2 GB RAM
- Does not support machines with more than two processors.
If the database in MSDE has more than 5 concurrent batches of queries, an log file is generated in the database log. This log is located in:
C:\Program files\Microsoft SQL Server\MSSQL$PADMINISTRATOR\LOG
And will contain lines like the following:
2004-01-23 09:45:23.96 spid11 This SQL Server has been optimized for 8 concurrent queries. This limit has been exceeded by 2 queries and performance may be adversely affected.
2004-01-23 10:09:16.11 spid10 This SQL Server has been optimized for 8 concurrent queries. This limit has been exceeded by 1 queries and performance may be adversely affected.
2004-01-23 10:10:16.27 spid5 This SQL Server has been optimized for 8 concurrent queries. This limit has been exceeded by 1 queries and performance may be adversely affected.
When this happens, the query is not lost, but it is queued, and therefore, the functionality of the application is not reduced. However, bear in mind that this will greatly reduce the performance of the computer on which the database is installed.
Companies that do not have an SQL Server need to decide whether to perform an installation based on MSDE or to install an SQL server to house the database. The following factors must be considered when taking this decision:
- The capacity of the computer on which the database will be stored.
- Whether the computer will be dedicated exclusively to the database or not.
- The number of computers whose antivirus protection will be managed through AdminSecure.
- Frequency of the self-diagnosis and data collection jobs.
- Number of virus detected warnings generated in the computers protected by the antivirus.
Based on these factors, a series of hypothetical situations in which to perform each type of installation can be established:
- Small and medium-sized networks with a low number of virus warnings could work with either an MSDE database or an SQL Server.
- As the number of computers to be managed and the number of viruses detected increase, it is advisable to use an SQL server. In these networks, MSDE could work correctly but concurrent query errors would be generated in the database log and the performance of the computer on which it is installed will be slightly degraded.
- In large networks, with more than 300 computers and many virus warnings, it is highly advisable to use SQL Server 7, 2000 or 2005 (SQL 2005 included) to house the AdminSecure database. These networks could work with an MSDE database but the low performance of this engine could affect the smooth functioning of the console.
- In general, the following guidelines must be considered for all types of networks:
- Installing the database in a different computer from the one with the repository installed will allow the computer to work more smoothly. Therefore, in networks with a large number of computers, it is advisable to install an additional repository, which the majority of the computers will connect to.
- Install AdminSecure and the database in a computer that easily meets the minimum requirements.
- Increase the intervals for communicating with the workstations. You can do this through the AdminSecure console in Tools > Options > General > Advanced settings.
It is important to highlight that, if after installing AdminSecure using MSDE as the database, you decide to migrate to an SQL server in order to improve performance, you do not need to completely uninstall the product.
There are two basic methods for checking if low performance is a result of the 5 concurrent workload “throttle” on the database engine:
- Check the database logs.
- Use the DBCC command, which is available with all editions of SQL Server and especially useful in MSDE situations. Four parameters can be used with the DBCC CONCURRENCYVIOLATION command, which are DISPLAY, RESET, STARTLOG and STOPLOG.
The following link contains more information about the features and restrictions about MSDE and additional details of the DBCC command: