Bosch has been providing 2 types of VRM packages: a 32bit and a 64bit version. Since VRM 3.82 we are only offering the 64bit version.
As all of our released DIVAP IP units started off as 32bit VRM which includes a Transcoder service.
BVMS Mobile Video Service - Creating a Self-Signed Certificate to establish a trusted connection
Some sites may request or require that the connection to the Mobile Video Service is a trusted connection. The following procedure will allow you to create a self signed certificate to allow a trusted connection between a web browser and MVS.
-Navigate to the Microsoft Management Console
Run command mmc.exe
Go to File ---> Add/Remove Snap-in…
Highlight Certificates and Add for Computer Account
You should see certificates listed for Local Computer
Save a copy of this console to the Desktop
-Run Windows PowerShell ‘as administrator’ on the MVS Server
Run the following commands in Windows Power Shell to create the self-signed certificate including the IP address of the MVS and the DNS name so both will work when accessing from a web browser.
$todaydt = Get-Date
$20years = $todaydt.AddYears(20)
New-SelfSignedCertificate -DnsName "mvsIPaddress",”DNSname” -notafter $20years
If creation was successful, you will see a thumbprint with a hash as well as the subject CN=ipaddress
-Navigate back to your saved MMC console
Find the newly created certificate under the Personal ---> Certificates directory
Copy the Certificate to Trusted Root Certification Authorities ---> Certificates directory
-Navigate to the IIS Manager
Highlight the server machine name on the top-left and then double-click Server Certificates
Double-click the created certificate and verify that a private key corresponds to the certificate and that the certificate is OK under the Certification Path
Expand the server machine name on the left to reveal the Sites
Select Bindings… on the far right-hand side
Edit the Binding for 443
Select the newly created certificate under the SSL certificate dropdown
Click Yes that you want to change the binding
Add… new binding
Choose BoschVms in the SSL certificate dropdown
-Navigate to the BVMS Config Client to edit the MVS URL
Change the MVS URL to reflect port 444
Red X should go away
Save/Activate (BVMS will be bound on the new port and still be able to communicate with the MVS server
-Open Internet Explorer (as administrator) and navigate to the MVS URL using the IP address or the DNS Name
Continue to the site with the certificate error
Click on the certificate error in the navigation bar
Click View Certificates and then Install Certificate
Install for the Local Machine
Place certificate in the Trusted Root Certification Authorities store
Click Finish and close out the browser
Open IE again and navigate back to the MVS. There should be no more error.
*The reason behind changing the port to 444 is to make browser access for basic users easier. This way basic users only have to enter the IP address or DNS name and do not have to enter a special port in the URL.
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.
Workstations, Z4G4, Microsoft License
Is it possible to Activate Windows 10 by phone for Bosch Workstations?
With introduction of Windows 10, Microsoft disable the phone license activation for Bosch Workstations.
Please perform online activation over internet.
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.
Bosch Video Client
How do I backup the complete BVC configuration in Windows 7?
If BVC was installed whilst logged into Windows as the Administrator, go to the following folder:
C:\Users\Administrator\AppData\Roaming\Bosch\Vidos. Copy the conf folder. This folder contains the BVC configuration.
Note : Backup configuration only applicable to the specific BVC version during configuration restore.
What is the decoding performance of BVMS? How many cameras can I open on the screen before the systems is overloaded (and frames are being dropped)?
The BVMS client performance overview is attached to this article and shows, based on several workstation configurations and a specific BVMS version, how many cameras can be opened before the workstation is overloaded.
Related Products: BVMS SDK, BVMS
BVMS Scriptlets can be debugged via logging to a logger file or messaging to the Operator workstation.
This article describes how to enable BVMS Scriplet logging.
You can log to the Server Script log or the Client Script log. Logs are default send to C:\ProgramData\Bosch\VMS\Log
1.Creating Log files
ClientScriptLogger – automatically created
Creates file “ClientScriptLog.txt”
ServerScriptLogger - automatically created
Creates file “ServerScriptLog.txt”
2.Log information to the log files
There are 3 methods to log information:
public void DemoLogger()
Logger.Info("Hello World script started");
Logger.Error("Hello World script started");
Logger.Debug("Hello World script started"); // Not writing to ClientScriptLog.txt !
3.Logging Location - C:\ProgramData\Bosch\VMS\Log. The logs are automatically collected by the BVMS Configuration Collection Tool.
4.Changing the location of the BVMS Scriplet Logging.
Server Scripts :
Logging Directory can be found in the file:
C:\Program Files (x86)\Bosch\VMS\AppData\Server\CentralServer\BvmsLogCfg.xml
and is defined by the ServerScriptLogAppender path:
<appender name="ServerScriptLogAppender" type="Bosch.Vms.Shared.Logging.Imp.RollingFileAppender, Bosch.Vms.Shared.Logging.Imp">
Client Scripts :
Logging Directory can be found in the file:
C:\Program Files (x86)\Bosch\VMS\AppData\Client\OpClient\ApplicationWiring\Nvr\LogCfg.xml
and is defined by the ClientScriptLogAppender path:
<appender name=“ClientScriptLogAppender" type="Bosch.Vms.Shared.Logging.Imp.RollingFileAppender, Bosch.Vms.Shared.Logging.Imp">
How can I migrate the full configuration (including server configuration and user settings) of a BVMS system from one server to another?
(please note that, currently, the export mechanisms provided in the BVMS Configuration Client do not export the userdata. This is a known problem and being worked on. Until then this work-around should be applied).
Stop the BVMS Central Server service on the existing server from the Windows task manager or Services overview.
Stop the BVMS Central Server service on the new server from the Windows task manager or Services overview.
Copy the contents of the directory C:\programdata\Bosch\VMS\UserData on the existing server to the same directory on the new server (via the network or other media).
Copy the "elements.bvms" file located in the directory C:\programdata\Bosch\VMS\ on the existing server to the same location on the new server (via the network or other media).
Start the BVMS Central Server service on the new server from the Windows task manager or Services overview.
Related Products: Video Analytics for Firmware 6.60 and above
This article covers traffic monitoring of Bosch Video Analytics with How to Videos (one already available and one in planning)
Default scenario of wrong way detection
Learn how to use the default scenario of wrong way detection: A predefined scenario that can be used to detect an object that is traveling the wrong way.
Default scenario traffic incidents
This predefined scenario is designed to detect common traffic incidents on roads:
Wrong way – triggers an alarm if object travels in wrong direction
Pedestrian – triggers an alarm if pedestrian is on the road
Slow vehicle – triggers an alarm if vehicle moves slower then predefined speed.
Stopped vehicle – triggers an alarm when vehicle is stopped longer than predefined time span.
Dropped object – Triggers and alarm if an object is dropped on the road
This how to video shows in detail how to use the predefined tasks Wrong way, Slow vehicle and Stopped vehicle.
Note: If needed you can get additional how to information on camera calibration.
Relates to: IP Storage/PC HW - DIVAR IP 6000 R2 and DIVAR IP 7000 R2
Both DIVAR IP units running the BIOS from American Megatrends Inc. (A.M.I)
There are PRE BOOT or POST BOOT beeps.
Please see the following Acoustic Error Codes.
BOSCH offers and confirms that since February 2017 the firmware version 3.180.05-1562 can be used with the LSI MegaRAID Controller. In case there are newer versions supported and recommended with BOSCH DIVAR IP this will be announced in cooperation with the Product Management.
For DIVAR IP units (e.g. DIVAR IP 6000) BOSCH BT Security & Safety Systems offers an firmware update for the internal MegaRADI Controller.
It could happen that in the Megaraid Software the user can see the following: potential non-optimal configuration due, PD commissioned as Emergency Spare error.
In this article we cover the following basic questions:
How to Factory Default a NetApp E-Series unit by using BOSCH tools and NetApp WEB GUI?
How to download the NetApp Support Bundle of a reachable online NetApp Storage Array
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.