BVMS Lite and BVMS Viewer are BVMS editions that you can download and activate free-of-charge.
How can I set-up a basic (live and recorded video) BVMS system?
First, you need to download the software package, active the BVMS Lite license and install the software. This is described in this article: BVMS - Activating a license.
Second, you need to prepare an iSCSI environment which is suitable for recording video. Any Windows Server based operating system will do. This is described in this article: BVMS - Configuring a Microsoft iSCSI target.
Last, you need to add cameras to the system and start the recording. This is described in this youtube video: How to add a new camera using Configuration Client (BVMS).
Now, have a look at the Operator Client quick guide and you're ready to go!
Where can I get more information on advanced functionality?
Once the software (configuration client or operator client) is running you can press F1 at any time to open the embedded software help! All of the advanced functionality BVMS offers is explained in the help files.
How can I combine a ISS SecureOS Auto system (providing ANPR functionality) with a BVMS system?
The attached document describes the steps how to configure BVMS and the ISS SecureOS Auto system for achieving watchlist ANPR alarms and recorded ANPR detections into the BVMS logbook.
The BVMS Logbook database can be moved to another SQL Server.
This article describes the steps that are necessary to migrate the database and describes how to confirm if the migration was successful.
BVMS is using Microsoft SQL Server Express to store its logbook. Based on the information provided by Microsoft (Compare SQL Server 2017 editions), SQL Server Express is limited to a 10GB database size.
This could be insufficient for larger installations or installations that require a very long logbook retention time. Additionally, some organizations have a dedicated SQL server environment which should be utilized by all applications. The BVMS Logbook database can be moved to another SQL Server. This guide describes the steps that are necessary to migrate the database and describes how to confirm if the migration was successful.
The entire BVMS installation package, available on the downloadstore, contains the client as well as the server components. When a BVMS client needs to be deployed, all of this data (over 2.5GB) needs to be copied to the target workstation, which can be quite a challenge in some environments.
In August 2018 (10-08-2018) the VRM version 03.71.0029 was released.
The Video Recording Manager 03.71.0029 is fully supported with BVMS 8.0 and Product Management of BVMS and VRM recommend to use this VRM version instead of the former Release version of VRM 03.70.0056.
Changes / Bug Fixes:
One of the main bugfix reasons to use VRM 03.71.0029 is a fix in regards to correct display and replay of recorded clips in continous and alarm recording mode. This fix is listed on page 2 of hte attached Relase Letter.
For Troubleshooting and support reasons it is essential to double-check a reported gap in recording and to analyze on Level 2 and Level 3 support side what circoumstanced could lead to a video gap. See in the following chapter what kind of data a trained BOSCH partner, Installer or Video expert should provide to the BOSCH Technical Support to advise on next steps. The data described here below can and should be collected before the software VRM is changed and updated to a latger version. Note: Video Recording Manager version 03.71.0029 is not the latest available version of VRM, but in combination with other 3rd party implemantation or usage of special BOSCH VMS software version (e.g. BVMS 8.0) this VRM version 03.71.0029 may be required.
VRM logging to collect for in depth expert troubleshooting
In certain situations and troubleshooting scenarios extended logfiles might be required. The BOSCH Level 1 and BOSCH Level 2 team will assist all users on how to collect these data and cooperate with the BOSCH Level 3 Support where needed.
Backup the configuration of BVMS and VRM (BVMS elements and VRM config.xml file)
Enable debug logging of the VRM Depending on the used Configuraiton Software the debug logging need to be enabled to get an extended logging informaiton. In case a gap in recording happened in the past it is anyhow helpful to enable the debug logging for a defined time for future incidents. To analyze the already occured video recording gap the available VRM logging must be collected.
Depending on 32-Bit or 64-Bit version of the VRM software, the loggings are found in the "primary" or "secondary" sub-directory structure. Surch for ...\Bosch\Video Recording Manager\VRM Server folder at your VRM server to find a similar directory view like shown in the screenshot here below:
Inside the directory "log" the standard logging data of the VRM are found and need to bre collected. In addition to the standard logfiles of the relevant day, the debug logging from a defined time period need to be provided in case debug logging was enabled prior to an incident.
Here the "debug" logfiles are found: The debug loggins are saved in a special directory "debug".
The Spanhistory logging does provide details of the storage usage. It describes which internal "storage block" was used. It describes the IP of the target, the LUN and the block used for a recording. The Spanhistory of the day where the recording was done and shows issues (e.g. the video reocriding gap), the related spanhistory logfiles is required.
As seen in an earlier screenshot above the VRM configuration file is found in the directory: ...\Bosch\Video Recording Manager\VRM Server\primaryAll versions of the config.xml need to be provided to the Technical Support.
Until some years ago, new released cameras, encoders, domes and decoders that were introduced into market after a BVMS release could not be connected to an existing BVMS version because these cameras where not known to the BVMS.
In the BVMS 4.5.1, a new concept was introduced.
This concept treats Bosch video encoders and decoders as generic devices, and automatically recognizes specific device functionality (for example the number of streams, relays and inputs).
Based on this information, unknown device is added to the system and can be used by the operator.
The attached document provides a detailed description of this functionality.
You can find it in the Configuration Client > Main window > Settings menu > Remote Access Settings... command > Show Port Mapping... button > Port Mapping Table dialog box
Port Mapping Table dialog box displays the port mapping for the IP addresses of the configured devices in your BVMS.
You can find here the private and public ports that are in use in the BVMS system.
All local ports that must be open on the computer where the server is installed or on the router/ level 3 switch that is connected to the server can be found in Help section (F1) from Configuration Client or you can see some useful examples, Q&A and specific cases in the following Knowledge Base article:
Which are the ports that must be open within a LAN for all BVMS components?
When scanning a QR or Data Matrix code on a label using the Project Assistant app, it can happen that you get an error message that the MAC address cannot be found (1) or that only part of the address is correctly extracted (2).
First of all, there are different types of labels:
product labels (on the device)
box labels (on the outside of the box/packaging)
installer / UX labels (inside the box /packaging)
Symptom (1) can only happen when scanning a product label because some QR or Data Matrix codes do not contain a MAC address, depending on the product, even though the MAC address is available in plain text right next to the code.
The box and installer label codes, however, always contain the MAC address information.
Symptom (2) can happen when scanning certain installer labels due to legacy formatting.
We have further standardized the labels so that the symptoms mentioned above will be resolved. There will be a transition period, however. As an alternative for symptom 1, you will have smooth experience when preferably scanning the box label. If you encounter symptom 2, we ask you to enter the MAC address manually or use the December 2018 release of the Project Assistant (version 1.2)
PS: For full transparancy on QR code / Data Matrix content and/or troubleshooting purposes, you can use conventional code scanning apps available in the resepective app stores.
Bosch software is distributed via the Bosch website, but can also be re-distributed by Bosch partners. It is important for the system-installer to check if the installation file he or she has received, matches exactly with the output of the engineering process. There are several risks that, in the distribution path, changes are made to the installation file. Keyloggers or other spyware could be added to the installation, or in theory video surveillance footage could be routed to external resources.
The attached document describes how the integrity of software can be checked.
Communication can get interrupted and configuraiton might fail if the below desribed actions are not performed. If your system is affected or not is described here as follows:
There can be authentication issues between the BVMS Central Server and the Video Recording Manager in case they are installed on different Servers.
It is possible to see reports at the BVMS 8.x system alarms that VRM reports wrong version
Please check in the VRM debug logging if the following logline indications can be found
This article summarizes the BVMS design details, and serves as a guide to planning a BVMS system with Bosch cameras and storage. It focuses on BVMS combined with the VRM.
The BVMS 11.0 release notes can be found on the Bosch Security Systems website. This article lists the valid design specifications for BVMS 11.0.
The attached documents should help you to make the upgrade process as smooth as possible. The upgrade itself is not restricted to BVMS software only. The supported software and firmware versions can be found in the release notes of the related BVMS version.
Video Recording Manger v4.00.0070 does not allow anyone not configured in VRM, only as an admin (using Configuration Manager), to log into the VRM Monitor page. BVMS users are no longer able to login and a message is displayed that they require administrative rights. Even new BVMS users created in the default Admin group do NOT have access any longer.
For example, login to VRM Monitor is no longer possible for user type “live”
Live and Replay function was removed from VRM v3.83.0021 for ‘srvadmin’ user. All other BVMS created users are able to login to VRM Monitor and see live and replay video without the ability to restriction this function.
If you have an earlier version of VRM, lower than v4.00.0070 and you would like to restrict the login option to VRM Monitor for other users than admin, you need to upgrade the VRM to the latest version.
Important Note: Downgrade from version 4.00 to an earlier version is not possible.
⚠️ Please be aware that VRM 3.82 or higher is available as 64 bit version only (no 32 bit version available). When upgrading from a VRM 32 bit version to a 64 bit version SSL certificates will be removed and have to be added manually to the system.
Exception: self-signed certificates will be replaced automatically.
o For proper installation certain prerequisites e.g. latest Windows updates are required. For further information please refer to the knowledge base article.
Download: Software (Video Recording Manger 4.00.0070 (64-bit))
Please check the System Requirements section from Release Letter Video Recording Manager v.4.00.0070 (64-bit)
A transfer of the license from the Bosch Software License Manager System (SLMS) to the Bosch Remote Portal is required for every BVMS system to be upgraded from 10.1 to 11.0
Starting with BVMS 11.0 the license activation will be done via the Bosch Remote Portal.
To upgrade an existing system, the BVMS licenses need to be migrated from the old licensing system, Bosch Software License Manager System (SLMS), to the new licensing system available in Bosch Remote Portal.
This article describes the steps that need to be followed when upgrading a system to BVMS 11.0.
Prerequisites for upgrading a system to BVMS 11.0:
Existing license activated in SLMS
Valid Software Assurance (SMA) PRO
Valid account on Bosch Remote Portal
❗ ❗ ❗ IMPORTANT
In BVMS 10.x the computer signature is the link to the license in the SLMS
When upgrading to 11.x the computer signature becomes obsolete and the new Remote Portal tool no longer takes it into consideration
The software Order ID is transferred in the background from SLMS to the Remote Portal
This allows the activation of BVMS 11.x in the Remote Portal using the new identifiers for the Management Server Hardware called System Fingerprint, contained in the System Info file.
One of the reason why UPnP (Universal Plug and Play) is enabled in our devices is because ONVIF uses this to scan the ONVIF device in the network. If you don’t need to scan ONVIF devices in the network using ONVIF method, you can switch of the SSDP Discovery Service.
SSDP protocol can discover Plug & Play devices, with uPnP (Universal Plug and Play).
SSDP uses unicast and multicast address (126.96.36.199).
SSDP is HTTP like protocol and work with NOTIFY and M-SEARCH methods.
"188.8.131.52 " is Bosch Multicast discovery address. When you block this address you cannot scan devices via multicast