Security: Video

Starting with BVMS v10.0, you can leverage VRM Encryption Technology.

White cameo in BVMS Operator Client or "device failed" message may be caused by the NVIDIA graphic card driver that might not be compatible.

The MBV-MBase is the license that allows you to extend the SMA in Remote Portal. You receive this license when you place an order to Order Desk for SMA extension and it must be activated in the Remote Portal and on the server like any other license.

The connection of 2N® Helios IP intercom to BVMS and Bosch Access Control System is possible thanks to the implementation of ONVIF and Wiegand protocols, which ensure mutual compatibility.

This article answers the question:  Is there a search limit of results in BVMS Operator Client Logbook for collecting license plate data?

If you would like to exclude certain Events and Alarms from being written in the BVMS logbook you do have the option to exclude such information.  

You can lock the control of a PTZ camera for other users. A user with a higher priority can take over the control and lock the camera control. A timeout can be configured for this explicit PTZ locking. If you only take over the control without manually locking it before, the control is locked for the user with lower priority for 5 seconds.

Have a look at this article and learn how to fix the Add Scriptlet button which does not become active. It stays grayed out. Same happens with ClientScript and ServerScript.

If replacing a defective camera, the camera must be the same IP address as the defective device, and it cannot contain a GUID from a different VRM.

This behavior is mentioned in the release notes and as a workaround you can separate the cameras into different groups. For example, if you have cameras in 2 different locations, it would be actually better to separate the cameras in 2 groups. But please be informed that by doing so, you will not be allowed to view them all together.

You should only subscribe directly to this article (Option 1) or to the software_release_notification label (Option 2) and you will receive a notification in your inbox every time when a new Software version is released and added to the lists within this article.

Glutton (German: Vielfraß) defines and prevents a camera or multi-channel encoder from mounting and consuming  a large number of  blocks in a very short time.

This behavior occurs when you have requested the SMA extension and you didn't upload the Activation file in the BVMS Configuration Client.

Find out from this article the steps that should be considered for a planned shutting down and powering up of your BVMS system

This document is specifically for DIP-71xx as it's the DIP which supports certain versions of BVMS (regular BVMS installer) and must be updated in a certain order. The document details how to upgrade from BVMS v8 to BVMS v12.0.1.

This document is specifically for DIP-73xx as it's the only DIP with Software Center. The document details how to upgrade all the way from BVMS 10.1 with Software Center and to BVMS 12.1 with System Manager 2.3 

The validity of the SMA date should cover the BVMS version release date you wish to upgrade to. Otherwise, the upgrade will not work and you will get the message "It is not possible to upgrade the software of this System Info file to a newer version". Also, please note that this message could occur in case you are trying to upgrade your BVMS and it is on the latest available version released.

This article provides causes and solutions regarding  the date and time indication inside the Image Panes  which are not visible in BVMS Operator Client.  

OPC server is installed on the BVMS server OPC client software is installed (the client used in this article is Softing OPC Toolbox Demo Client), and the user can connect to OPC server that is running on BVMS server, but the user cannot send any command from 3rd party OPC client to BVMS system, for example changing the status of virtual inputs. There are no events coming from OPC to BVMS and the OPC client is not present in the list for third party integrations with BVMS

Log4j 1.2.17 is not actively used or called by the SQL Server or by the BVMS. This means that the vulnerabilities are not exploitable unless you install some additional components that refer to the vulnerable component. Therefore, there is no risk of exploitation within the SQL Server or BVMS environment.