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)
The BVMS Project Checklist is an Excel-based tool which makes it easier to design a BVMS system.
This article describes how to use the project checklist.
Pick the attachment you need, depending on the version of BVMS you have
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.
The attached manual provides information for Mobile Video Service (MVS) within Bosch Video Management System.
You can find: - how to configure the router and Internet Information Service (IIS) - how to add MVS to BVMS - user guide - some troubleshooting tips
This document can also be found online here.
Trying out the BVMS Lite is easy!
Download BVMS Lite from the Download Area and use the quick installation guide to set-up the system.
BVMS Lite contains
8 video channels
1 intrusion panel and can be used without a time limit.
BVMS Lite can be expanded to 42 channels using license extensions.
A step-by-step instruction on how to install the BVMS Lite demo license can be found to this page.
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.
In terms of license activation process and compared to other versions of BVMS (<v11.0), the Bosch Remote Portal replaces the Bosch Software License Manager System (SLMS), starting with BVMS v11.0.
A new user registration is required in Bosch Remote Portal and the mandatory information for license activation is the System Info file (generated in the Configuration Client) and the Software order ID (received from the Bosch order desk by e-mail → ordering remains unchanged: still utilizes the Bosch Order Desk)
The remote portal will then provide a "Activation file" which includes all activation details. It needs to be uploaded to the newly installed BVMS system.
The activation process defines the start date of the software maintenance agreement (SMA - software assurance) period.
The end date is shown on the License manager of the BVMS Configuration Client after activation
NEW: Software version-less ordering process: Ordering a BVMS Base or Expansion licenses is not software dependent anymore starting with BVMS 11.0 upwards. During license activation only "non End of Life" (EOL) versions are assigned to the license.
Follow this article and find out the steps that need to be performed when activating a new BVMS 11.0 license.
With BVMS 11.0, new licensing system was introduced.
Attached document describes how to migrate existing activated BVMS licenses from the Bosch Software License Manager System (SLMS) licensing system to the new Bosch Remote Portal licensing.
Starting with BVMS 11.0, the standard BVMS licensing scheme also applies to the DIVAR IP units.
Attached document describes how the upgrade process to BVMS 11.0 looks like and what kind of licenses are needed for a DIVAR IP unit!
Do you have any doubts, regarding BVMS licensing?
Attached whitepaper might serve as comprehensive source of knowledge for BVMS licensing topics, like:
BVMS product editions and license types
License activation process
Assurance PRO ordering process
Managing your licenses in Remote Portal
and much more!
In order to quickly offer a technical solution or to provide a professional advice for the next analysis steps, the technical support specialists need to get some general and basic information.
Ticket content should always be in English and provided in a well summarized and structured way in order to be able to provide a quick and appropriate feedback.
Not following the guideline will impact the processing time of the ticket.
Related Products: BVMS SDK, BVMS
Analyzing BVMS systems with SDK components is a challenging task, because the functionality and the runtime behavior of those systems are harder to determine than for a BVMS systems without SDK functionality.
In order to troubleshoot BVMS systems with SDK components support needs the following information and logging.
Please prove the following information to support:
Symptom specific Information
How to retrieve the Hardware ID for BVMS and check the Software Maintenance Agreement (SMA) status?
BVMS stand alone or appliance
Detailed description of the expected behavior of the SDK functionality.
Detailed description of the actual behavior of the SDK functionality.
What type is the standalone SDK application (based on ClientSDK, ServerSDK, or CameoSDK) and on which machine is it running?
Are there additionally client scripts, server scripts or workstation startup scripts?
Do SDK components interact with remote Operator Clients?
Do SDK components interact with the Operator Client UI?
Do SDK components control devices?
How often are client scripts triggered?
How often are scripts triggered by BVMS event?
Which shared resources are accessed by SDK actions? (Dome cameras, AMG, Operator Client UI)
Do SDK components interact with an unreliable environment? (Unstable network, offline devices, offline PCs, etc.)
Do SDK components properly handle offline situations? (offline devices, configuration changes, etc.)
Please provide the Scriplet and/or Log files
The optimal approach is to provide both the scriplet and logging.
ClientScript logfiles: can be found in the ConfigCollection of Operator Client machines.
ServerScript logfiles: can be found in the ConfigColletion of Management Server machines.
Make sure that logging is implemented in the script and that logging is activated in the configuration.
Intelligent Insights is a standalone product. The system can run as a standalone system and be accessed by operators via the web browser or the widgets can be integrated in a BVMS operator client.
The software can be downloaded from the product page here.
Operating system: Windows 10 Enterprise 1809; Windows 10 Pro 1909; Windows 10 Pro for Workstation 1909; Windows Server 2016 1607
CPU: Intel Core i7 4770 3.4 GHz (up to 3.9 GHz); Support of CPU virtualization
RAM: Minimum 16 GB
Network card: 1000Base-T
Free disk space: Minimum 50 GB
We recommend having minimum 15% freedisk space.
Supported Web browser: Microsoft Edge, Google Chrome, MozillaFirefox
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
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.
An attachment is added to this article for each BVMS version. Currently the upgrade guides for BVMS 8.0 and 9.0 are attached to this article. From BVMS 10.0 onwards a description on how to migrate systems has been included as well.
Compared to hardware, in which it is relatively easy to define an end-of-support concept based on the expected lifetime, software behaves totally different. In theory, when the environment does not change, software can still be running ten years after it has been installed. As new versions of the software are released regularly, it is important for customers to know what they can expect from Bosch Building Technologies when the software is purchased. This document describes how Bosch Building Technologies handles the life-cycle of the BVMS, BIS, AMS, and APE, and in which state a specific release can reside. Additionally this document lists the up-to-date situation for all of those software packages.