The latest version of GuardPointPro is available for download
Notes on installation can be viewed here
Update policy for this version
The main GuardPointPro application requires a dongle with minimum version 3.00.0xx or higher.
In case there are no version details at all or if the version on the dongle is less than 3.00.0xx, the license should be updated.
If running this version with a dongle that has not the required version, GuardPointPro
will give an error to the user and would close the application right after.
Default setting values
When installing this version for the first time, the following settings are set in the GuardPointPro.ini file in order to optimize the system:
- LogSelectTopLines = 25
- MaxCardholders = 8900 instead of 44000
- ImportDBAPISynchronous = 0
When updating an existing system, the current settings will not be overwritten.
Thus, if necessary, those parameters must be set manually.
In the previous version (3.3.051), when updating an existing system, the MaxCardholders option was overwritten with the value 44000.
This caused some Accesses to be denied on installations having 4-door controllers that do not support NumBadge value >32512 or 128K RAM controllers that do not support NumBadge value >8934. Now, this value is not overwritten.
If you have used the previous version (3.3.051), please update the MaxCardholders option
Note that on Workstations, the MaxCardholders value is taken from the Server GuardPointPro.ini file.
• A new INI option, ‘ImportDBAPISynchronous’, allows to choose if wanting the DBAPI
“ImportOneCardHolderXML” command synchronous or asynchronous. The synchronous way guarantees the download order of the commands whereas the asynchronous way allows to download the cards immediately, independently of the general queue of the commands. Note that in the previous versions, this command was asynchronous by default.
• The “re-sending card definition after ‘denied’ event” option downloads the relevant cardholder
definitions to the relevant controllers automatically upon a denied accesses with the denied
reason “Access group”. This option allows to make sure that the cardholders have been correctly downloaded. In the previous versions, this command was not downloaded immediately, if a cardholder import via DBAPI was in progress. If a denied access happened, the "Resend on deny" feature adds the download command to the queue and the command was not sent later. From this version, the “Resend on deny” commands have priority and they are downloaded immediately, even during an import.
• Great improvement in import speed when importing batches of cardholders by using the DBAPI
“ImportOneCardHolderXML” command. The system uses the batch size defined by the
“QueueMsgTOP” INI option to import cardholders by groups and no more one by one. In comparison, in the previous versions, it took 24min to update 3k cardholders by DBAPI. With
this version, it takes 6min only.
Note that for optimum speed, it is necessary to have the following settings in the INI file:
- ImportOptimized = 1
- ClearAddressInAllCtlOnNewBadge = 0
• In the previous versions, when using the DBAPI “ImportOneCardHolderXML” command to
import cardholders with the SecComService module, the delete commands were written in the
‘ComSync’ table one by one for each controller. On installations having a lot of controllers, this
caused the import to be slow. Now, when the delete commands should be sent to more than 3
controllers at the same time, the delete commands are written in the ‘ComSync’ table with the
mention "All Networks" per cardholder, allowing to save time.
Note that for having this feature, it is necessary to have the following settings in the INI file:
- ImportOptimized=1 or ImportDBAPISynchronous=1
• A new INI option, ‘LogSelectTopLines’, allows to continue to display events on the event log
screen of the server application during cardholders import process via DBAPI. By default, it reads
25 lines from the Log table at each iteration and writes them on the screen.
• In the previous versions, when the database server was not reachable during a cardholder
import via DBAPI, the import was stopped and GuardPointPro did not resume the import after the
database reconnection. Now, in such case, once the SQL server is reachable again, GuardPointPro
resumes the cardholder import.
A cloud database is a database that typically runs on a cloud computing platform. It is possible to install the GuardPoinPro database on a cloud platform. For this solution, we have made the following improvements:
• In the previous versions, when the GuardPoinPro database was on a cloud platform or if the
database server was far from the GuardPoinPro station, GuardPoinPro startup took too much time.
We saw that if the database has lots of events (we tested a database of 62 million of events),
when using the ‘EventsfromDB’ INI option, the SQL query to display the last event took too
much time. To optimize this time, we have replaced the “SELECT *” query by the “SELECT TOP
1” query. After this change, the startup took 3.25min instead of 7.45min.
• In addition, we saw that GuardPoinPro took too much time at startup during the ‘init Input memory’step. After changing the SQL query type, from ‘Server side’ to ‘Client side’, we saw a speed improvement of 20% on the Workstation startup duration.
• The logon/logoff duration has been improved also. In the previous versions, when the database
was located on an ‘Microsoft Azure’ server, LogOff took 37sec and LogOn 38sec. Now, after
optimization, LogOff takes 6sec and LogOn 6sec.
• The opening time of the Cardholder screen has been optimized. In the previous versions, when
the database was located on an ‘Microsoft Azure’ server, it took about 24sec to open this screen
from a Workstation. With this version, this operation takes 5sec.
• The speed for removing a card and allocating a card in the Cardholder screen has been
optimized also for cloud databases. In the previous versions, when the database was located on
an ‘Microsoft Azure’ server, it took 10sec to remove a card and 24sec to allocate a card. After
optimization, it takes 5sec to remove a card and 16sec to allocate a card.
• The T&A report generation time and the filter lists in the T&A wizard reports screen have been
optimized also for cloud databases.
There was a bug that deletes the NVR definition and its cameras automatically after deleting a camera from the Camera screen. This has been fixed now.
Galaxy & SecComService
When using Galaxy panels with the SecComService module, if one of the Galaxy service was down, when the SecComService was starting, all the controllers with the type ‘Galaxy’ or ‘MOBILE’ were automatically set as not active once the SecComService has started.
This has been fixed in the ‘ServiceCom.exe’ version 220.127.116.11.
'Network Door Open' action & SecComService
The 'Network Door Open' action to open all the doors by a Global reflex, was not working with the
SecComService module. Now, it has been fixed.