BVMS Version 10.0: please note that the export mechanisms provided in the BVMS Configuration Client might not export the user-data. Check this article for more details!
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.
License expansions missing after upgrade to BVMS 11 in Remote Portal. Only 1 x MBV-XCHANPLU license activated instead of 16 x MBV-XCHANPLU. What to do?
This article describes how to configure a generic Microsoft Windows Server (2012 R2, 2016 or 2019) based server to serve as an iSCSI target for a Bosch video surveillance environment.
SCSI (Small Computer System Interface) is most commonly used for the communication between computers and peripheral devices, such as hard drives.
iSCSI enables devices to use SCSI over a network interface, therefore it makes a lot of sense for cameras to use iSCSI to record video.
The camera is a small computer that needs a (network) connection to a "hard drive" to store video footage. In other systems this job is performed by the network video recorder (NVR).
There might be problems when you are trying to use the Forensic search function for FLEXIDOME Multi 7000i cameras (FW 8.71.0066) after upgrading from BVMS 10.1 to BVMS 11.1.1.65.
The message is saying that “Forensic search must be configured for this workstation”
Starting with BVMS 12.2, new OpenID Connect (OIDC) login options have been introduced. When closing the Operator Client, the user can decide to completely log off or stay logged-in.
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
This article describes the different components that Bosch Video Management System offers to to establish a connection between Bosch Video Management System and a 3rd party management system.
This description helps you in writing your own commands for controlling Bosch VMS from inside your management system.
In this scenario, an alarm button is connected to the Adam unit and when this input is activated (close or open), a full screen camera image shows on the display. The display is always logged in the Operator Client for live camera view on the DIVAR IP 7000 AIO.
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.
This article explains how to use the settings as per the devices current configured capabilities if you just added a device to BVMS, you get the possible stream options as per a “Config table” known to BVMS.
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.
In the Logbook, you can search for particular events, alarms, devices, and strings of events. You have the possibility to save the BVMS Operator Client alarm logbook, before accepting and clearing it.
Starting with BVMS version 12.0, the Privacy overlay feature was introduced. This feature can be configured to blur objects of type Person, based on a powerful Bosch Artificial Intelligence (AI) function
