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.
he Project Assistant offers two ways of importing existing project data:
Option 1) Importing a .bpassist file, which was exported from the app at some point and which contains all information and data ever created/entered inside the app for that specific project. Simply select the "Project Assistant" mode >> click "continue" >> and press "import".
Option 2) Importing from a tab-separated text file. This option may be useful, if you have existing project data, e.g. in an Excel spreadsheet, which you want to transfer into the Project Assistant for further use.
This article deals with option 2 and explains the steps potentially needed before you can refer to the steps explained in the following Youtube video ("Import from file").
The museum mode of Intelligent and Essential Video Analytics is an optimized tracking mode to detect whenever someone tries to reach towards and touch a valuable asset like a museum exhibit.
It can also be used in any other application where approaching a sterile zone from a more crowded environment shall be detected.
Time is everything: meetings, public transportation, religion, transactions: the whole world is working because the concept of “time” exists. Within a security (or any other) system this is not different: recording schedules, logging, authorizations, encryption keys, timelines, all of these concepts can exist because of time.
As a result, time can either make or break a system: problems can appear only due to a time difference of a couple of seconds between two system components.
This article describes how time services can be configured in a BVMS version ≤ 10.1 environment.
For BVMS version ≥ 11.0 please refer to the following article:
Where can you configure NTP server for cameras/encoders in BVMS≥11?
Time: what is the challenge?
Each device has its own internal clock, which is based on a hardware mechanism. This mechanism acts like a watch: try to put two watches together and synchronize them on the millisecond. A security system consists out of more than two devices, it can consist of thousands of devices.
Synchronizing the time of all these devices by hand is a very time consuming task. Additionally, due to small differences in electronic components, devices can have deviations from one another.
These deviations cannot be detected by the human eye, but can result in considerable time differences when a device is running for months.
The Network Time Protocol (NTP) was created to solve these challenges. The Network Time Protocol is a network-based protocol for clock synchronization between system components. The protocol utilizes a standard IP network to communicate and can maintain a time difference (considering a local area network) of less than one millisecond between components. The Network Time Protocol is a standard protocol and documented in RFC 5905.
The operation and configuration of the Network Time Protocol are complex: a hierarchical architecture needs to be set-up including several layers of systems which are able to run the Network Time Protocol. To reduce complexity the Simple Network Time Protocol (SNTP) was created. The Simple Network Time Protocol is mainly used when less accuracy (deviations of 1-2 seconds are acceptable).
Windows Time Service
The Bosch Video Management System is running on Microsoft Windows Server operating systems. Windows includes an internal time service, which is explained on Microsoft Technet:
“The Windows Time service, also known as W32Time, synchronizes the date and time for all computers running in an AD DS domain. Time synchronization is critical for the proper operation of many Windows services and line-of-business applications. The Windows Time service uses the Network Time Protocol (NTP) to synchronize computer clocks on the network so that an accurate clock value, or time stamp, can be assigned to network validation and resource access requests. The service integrates NTP and time providers, making it a reliable and scalable time service for enterprise administrators.
The W32Time service is not a full-featured NTP solution that meets time-sensitive application needs and is not supported by Microsoft as such. For more information, see Microsoft Knowledge Base article 939322,Support boundary to configure the Windows Time service for high-accuracy environments (http://go.microsoft.com/fwlink/?LinkID=179459).”
Source: Windows Time Service Technical Reference - Microsoft Technet
The Windows Time service is based on the Simple Network Time Protocol.
The Network Time Protocol requires a very complex infrastructure, which impacts the total installation and configuration effort of the system. The Simple Network Time Protocol (also used for the Windows Time Service) reduces the complexity, but at the same time also reduces the accuracy.
For most security applications the Simple Network Time Protocol provides sufficient accuracy. Bosch recommends to use the Windows Time service, based on the Simple Network Time Protocol, as basis for time synchronization in a security network. This article provides best-practices on how to configure the Bosch Video Management System and related components in a time synchronization environment based the Windows Time service.
Alternatively, the Network Time Protocol can be used whenever it is already existing inside an infrastructure or when event accuracy with a deviation less than one second is required. Due to the complexity of the infrastructure Bosch does not make any recommendations related to the Network Time Protocol.
Management server configuration
A. Operating system configuration
This section also applies for the Video Recording Manager and Mobile Video Service when these are not running on the management server.
Microsoft has prepared a lot of documentation related to time configuration Go to the Microsoft Support: How to configure an authoritative time server in Windows Server page and scroll down to the section “Configuring the Windows Time service to use an external time source”. Click the download button under the “Here’s an easy fix” section.
Figure: Download the Microsoft Windows Time service configuration utility
The utility will configure external time servers. To select these, browse to http://pool.ntp.org and select two servers which are related to the geographical location of the system, for example “de.pool.ntp.org” and “nl.pool.ntp.org”, referring to Germany and the Netherlands. Another (local or external) (S)NTP server can also be chosen.
Start the Microsoft configuration utility and configure it as indicated and shown in the figure below.
Administrative access is required to run the utility.
Figure: Pool.ntp.org locations
Figure: Windows Time service configuration
Alternatively the configuration can be done from the command-line, using the command shown below.
net stop w32time w32tm /config /syncfromflags :manual /manualpeerlist : "nl.pool.ntp.org, de.pool.ntp.org" net start w32time
The configuration can be verified by starting the Windows Command prompt and issuing the command “w32tm /query / status”, as shown in the figure below. Notice the time source, this should point towards the configured servers.
Figure: verifying configuration
It can take up to one minute before the correct time source is displayed.
When there is a problem, the configured (S)NTP server can be tested by issuing the “w32tm /stripchart /computer:de.pool.ntp.org”, which should result in the output displayed in the figure below.
Figure: test the (S)NTP service
When an unexpected result is returned, it is recommended to check access to the specific (S)NTP server. A firewall might prevent the communication between the (S)NTP server and the management server.
B. BVMS Management Server configuration
BVMS automatically points devices to its own time-server. This can be changed by editing the BvmsCenterlServer.exe.config file, located in C:\Program Files\Bosch\VMS\bin\. Find the key "TimeServerIPAddress" and adjust the value, as shown in the example below (192.168.0.1).
<!-- Ip address of the time server for VRM/NVR encoders(defaults to the Central-Server IP if not set) . --> < add key = "TimeServerIPAddress" value = "192.168.0.1" />
C. Workstation configuration
The Bosch Video Management System Operator client runs on a Windows workstation. When the workstation and server are part of the same Microsoft Active Directory service domain, no manual time synchronization needs to be configured.
Figure: workstation configuration, "192.168.0.200" needs to be replaced by the IP address or Fully Qualified Domain Name of the management server.
When the Bosch Video Management System workstation and management Server are not joined in a domain, or into the same domain, the workstation(s) need to be manually configured to use the management server as a time server. To achieve this, the description above can be used. Instead of using the pool.ntp.org as a server, the management server is now entered.
D. Camera configuration
If a camera is connected to a BVMS system the time server will be automatically configured.
This article guides you through the process of installing the BVMS Logbook Health Checker. The Bosch VMS Logbook Health Checker is a tool that is capable of fixing the overflow of the Bosch VMS Logbook database before it occurs.
This article will guide you how to remedy invalid expansion licenses on your Bosch Divar IP 5000 all in one. Error indication
Despite that the registration of your additional purchased licenses has been completed successfully. The licenses may become invalid after a following reboot. This behavior is caused by switching the MAC address of your teaming interface.
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?
No. It is not possible to disable the time synchronization function of BVMS.
It is only possible to configure a single time server per BVMS system to be used as time source for the VRM encoders.
You can check the article below, if needed:
How to configure time services in a BVMS environment?
Please refer to the following link:
If you have for e.g. a SNC-EM642R camera and you want to find out which device packs you need for your entire solution, follow the steps below:
The unit can receive the time signal from a time server using various time server protocols and then use it to set the internal clock. The device polls the time signal automatically once every minute.
To check the NTP connection from the camera please follow the below steps:
If you have configured an out of the box system and once the configuration was done you wasn’t able to access the BVRAdmin account, this article will help you to find a solution.
Access to BVRAdmin account is required to perform administrative tasks on the operating system.
This requires the following steps:
It only depends on the version of BVMS you have.
If you have BVMS 7.5, certain cameras with a certain FW have been tested and are supported.
If you have BVMS 8.0, certain cameras with a certain FW have been tested and are supported.
For BVMS versions of 9.0 or lower, only tested cameras must be added, otherwise we cannot support new setup.
On DIP 3000 you can only upgrade to BVMS 8.0.
The version of Windows installed on it does not support older versions of BVMS, it is not compatible.
Recommended to use BVMS 8.0, the largest version supported on that unit.
You need to make sure that those cameras are on the list of tested devices of the version you have.
Regarding the ONVIF Compatibility of the cameras, please see the following Bosch Knowledge Base article:
DIVAR IP 3000 and DIVAR IP 7000 video management appliances come pre-loaded with the latest available BVMS version from factory.
In order to make use of new VMS features and to attach most current devices, it may be required to perform a software upgrade, when a new BVMS version is available.
In this article it is explained how to do the initial system setup and how you can upgrade the BVMS installation to a newer version on a DIVAR IP 3000 or DIVAR IP 7000 video management appliance.
Initial system setup
Second revision DIVAR IP 7000 systems (DIP-71xx-xxx) allow for Appliance BVMS Installer packages to be imported directly during initial system setup. The following steps have to be performed in order to import a custom Appliance BVMS Installer package on a second revision DIVAR IP 7000 video management appliance:
- Download and unzip the Appliance BVMS Installer archive from http://www.boschsecurity.com - Copy the files Bosch_Appliance_BVMS_Installer_xx.xx.xxxx.exe and Setup-x.x.x.xxx.zip to a folder named “BoschAppliance” on a USB drive - Connect the USB drive to the DIVAR IP 7000 system during initial setup - Proceed with the system setup until the software selection screen is shown - Select the Appliance BVMS Installer version that shall be installed on the system
The following steps have to be performed in order to upgrade an existing BVMS installation on a DIVAR IP 3000 or DIVAR IP 7000 video management appliance: - Download and unzip the Appliance BVMS Installer archive from http://www.boschsecurity.com - Copy the content to a USB drive - When the BVMS default screen is shown, press CTRL + ALT + DEL - Hold down the SHIFT key while clicking Switch User (not Log off) - Log in as BVRAdmin - Transfer the folder that contains the files Bosch_Appliance_BVMS_Installer_xx.xx.xxxx.exe and Setup-x.x.x.xxx.zip from the USB drive to the BVRAdmin desktop - Double click Bosch_Appliance_BVMS_Installer_xx.xx.xxxx.exe inside the transferred folder. - Wait until the BVMS setup screen appears and select the upgrade option - Follow the installation procedure without changing any settings
Notes: - The system may request a reboot and re-login during the installation or upgrade procedure. - The upgrade procedure can alternatively be performed via Remote Desktop connection. - The software upgrade requires a system reboot which results in a short (~ 5 min) recording gap.
Please note that the latest information about the Appliance BVMS Installer for DIVAR IP 3000 and DIVAR IP 7000 can be found in the Release Notes on the product page, under Downloads menu > Literature > Release notes
Intelligent Insights makes use of Bosch cameras’ built-in Video Analytics to interpret video images and collect metadata from cameras. This metadata is collected, aggregated, and displayed using a series of pre-defined widgets within a user defined dashboard to visualize the data. Read on to learn how to add these widgets to the Bosch Video Management System (BVMS) for monitoring.
The Intelligent Insights widgets can be visualized in BVMS Operator Client. In this article we are going to show you how to add a widget to Bosch Video Management System (BVMS).
1. Access the Use cases menu and select the use case to add to BVMS.
In this example we’ll use the “Crowd detection graph”
2. Click the "Copy link" button
3. Next, access the BVMS Configuration Client and select Maps and Structure > Click Manage Resources
4. Click URL > Add a resource name and paste the URL copied from Intelligent Insights > Replace the text "localhost" with the IP address of the Intelligent Insights machine and click OK > OK
5. Click Add Document
6. Select the URL and click OK. The URL should appear under the Logical Tree
7. Click Save and Activate configuration
8. Next, access the BVMS Operator Client and select the tile where you want the widget to be displayed. Double click the widget to assign it
9. After signing in to Intelligent Insights, the widget will be visualized in the tile
YouTube video Learn more about Intelligent Insights
Central Support Team may ask you to provide them with the log files and configuration file of Intelligent Insights.
This article explains you how and where you can get them.
Intelligent Insights log files:
In the Log settings section you can select the log level that should be saved.
Note: Do not change the log level from Intelligent Insights unless requested by tech support.
The system logs of Intelligent Insights can be found at the path:
You can zip the Log folder and send it to Tech Support, when requested.
If you cannot see the "ProgramData" folder, please unhide the folder by clicking: Options > View > select "Show hidden files, folders, and drivers" option > OK > The folder will be displayed in path C:\
Intelligent Insights configuration file:
You can export the system configuration file from Intelligent Insight platform.
1. Open Intelligent Insights and login using the Admin credentials
2. Go to System > Export and import
3. Under "Export system configuration" type in the Admin password and click Export
4. Select the location where the file will be exported and click save
⚠️ WARNING: Do not upgrade the camera firmware directly to 7.81.
If you do this, “error 13: device check failed” message will be displayed, and the firmware will not be upgraded successfully.
1. Please make sure that the following steps are appropriate for your case, which means that the firmware version of your camera is 6.32.
The current version of the camera firmware can be checked in the web GUI from Configuration > Service > System Overview:
✅ Try to use the combined firmware package for all platforms, which can be downloaded from the following link.
Useful in case the combined firmware package is not available anymore:
Where you can find the intermediate firmware version when upgrading CPP4 cameras?
To upgrade to a newer firmware version using this combined firmware package, products may require to have this firmware file uploaded multiple times until the intended firmware version is installed.
Since intermediate firmware versions might have vulnerabilities that are fixed in later versions, it is advised to always install up to the most recent version.
In this case, where the camera has firmware version 6.32, you should apply this firmware twice.
The first time it will be upgraded to 6.50 and the second time to 7.10.
After the first upgrade, check the current version and then apply again until you get the desired version.
See also the Release letter:
2. After downloading the firmware package, go to Configuration > Service > Maintenance
3. Search for the file and upload it to proceed with the upgrade