This section shows you how to update Genetec Patroller™ on your in-vehicle computer.
Before you begin
- Read the following Release Notes for any known issues and other information about
the release:
- AutoVu™ SharpOS Release Notes
- Genetec Patroller™ Release Notes
- Security Center Release Notes
- As a best practice, ensure that all license plate reads are offloaded.
- Close Patroller and Genetec Patroller™ Config Tool.
- If Patroller is installed or updated by users who aren’t logged in as Windows administrators, you must ensure that these users have access rights to the Patroller installation folder. Note that the name of the folder changes with each major release.
- If you’re running a 32-bit version of SQL Server on a 64-bit operating system, uninstall the 32-bit version of SQL Server and install the version packaged with the Patroller installer. This is necessary so that the system can enable FILESTREAM.
What you should know
- Security Center communicates with Patrollers using port 18731. As a result, previous Patroller versions already connected to the deprecated port 8731 appear under the ALPR Manager in a yellow warning state. Patroller continues to function and can send reads to Security Center as usual. To return the Patrollers to a normal state, update them to the latest Patroller release.
- Your configuration settings are carried over from the previous version.
- Following the update, the system might request permission to update the database schema and restart Patroller.
Procedure
Results
The Patroller update is complete.
After you finish
- After updating Patroller to version 7.0 or later, all existing Patrollers and any
new ones you add must be registered with Security Center. For more information,
see Sending live events from Patroller to Security
Center.NOTE: The Security Center user must have the Register Patroller privilege. For more information, see Assigning privileges to users.
-
If you use encrypted Live transfer for offloading
from Patroller, upgrading to Security Center 5.13.2.0 or later requires you to manually
replace the
OffloadPublicKey.xmlfile on the Patroller computer. For more information, see Configuring a public key for encryption of offload data. - If you didn’t allow the setup program to create firewall rules, open the default Patroller ports.
- Update Plate Reader on the mobile Sharp units (described in a separate document). For more information, contact your Genetec™ representative.
- The following Patroller settings are reset to their factory defaults after updating:
- Patroller window behavior
- The Patroller window’s initial size, position, and state (normal, minimized, maximized) are reset. You re-size and re-position the window manually, and you configure the window’s state from the User interface section in Genetec Patroller Config Tool.
- Map rotation behavior
- The option to have the Patroller icon or the map rotate with vehicle movement is reset. You can configure this setting from Patroller’s Options tab.
- Main window display
- The option to display the map or the vehicle’s context image in the Patroller main window is reset. You can configure this setting by clicking the thumbnail map or image in the Patroller information panel.
- Initial GPS position
- The Patroller’s initial GPS position is reset. This will automatically be adjusted as the Patroller vehicle starts moving.
- MLPI Selection type
- (Mobile License Plate Inventory only) The way you patrol a parking facility in MLPI is reset. You can choose between Route or Configuration when selecting a parking facility in Patroller.
- Genetec Patroller location display
- How Patroller displays the vehicle’s current location is reset. You can tap the address in the notification bar at the top of the Patroller window to toggle between displaying the reverse-geocoded address or GPS coordinates.
- You can refer to your old Patroller configuration files to update the current Patroller settings. The files are located on the in-vehicle computer at the default location C:\Program Files\Genetec AutoVu X.Y\MobileClient\OldConfigFiles. The configuration files from the earlier versions remain in their original directory.
- If you’re using maps, you need to install and configure BeNomad maps because MapInfo is no longer supported.