The Bosch VRM Monitor page does not open correctly, but instead displays an Error.
Any Replay client requesting video from the Bosch Video Recording Manager service, only receives the Time-Line but the video is alway Black.
Bosch VRM by default uses Ports 80 & 443.
In most cases the problem is caused by another web server (e.g. IIS) that is installed on the same machine and is also making use of the default web ports 80 & 443.
Bosch Video Recording Manager (VRM)
Bosch Video Managment System (BVMS)
Bosch Video Client (BVC)
Bosch Video Security Client (VSC)
Any Replay Client/ Managment System which accesses recorded video data via HTTP/HTTPS
Disable any of the other web services or change the default Ports they are using.
... View more
With the VRM eXport Wizard 2.0 encrypted and unencrypted VRM recordings can be exported (VRM block export) from any video surveillance system based on Bosch Video Recording Manager (VRM) and exported recordings can be converted to mp4-files. Therefore, the VRM eXport Wizard 2.0 offers the following two options, compare also Figure 1:
Export VRM recordings of cameras
Convert already exported data to mp4-file
Export VRM recordings
To export recordings, no matter if encrypted or un-encrypted recordings, from a video surveillance system based on VRM, the user first needs to select and connect to the Bosch VRM system that contains the source video data the user wants to export. To optimize the data traffic, the user can further select the number of maximum sources exported in parallel and set the maximum bit rate used per source, see Figure 2.
Note: To avoid any performance loss of the VRM system it is not recommended to run the VRM eXport Wizard on the same hardware as the VRM itself or any other system critical server (e. g. VRM server, BVMS MS, etc.).
In the next step (Figure 3) the user selects the cameras and the time period that shall be included in the export. Additionally, the user can change the name of the export file and add a comment.
Once the user is done with the camera selection, the export destination has to be selected in the "Select Type and Destination" window, see Figure 4. Here the user can choose between CIFS export, iSCSI export and export to a file system.
Note: The tape export some users might know from previous older versions is no longer supported.
Once the destination is selected, the export process can be started. The VRM export Wizard informs about the current status of the export process and tells the user when the export is completed, compare Figure 5. The exported blocks can now be found on the before choosen destination platform.
Please note for mass exports, if the overall export time is longer than the respective retention time for a camera not all video data might be exported before being overwritten / deleted.
As already mentioned above, this export procedure works for unencrypted as well as encrypted VRM recordings (encrypted and unencrypted VRM blocks).
Unfortunately, for playback of the exported material we have to differentiate between encrypted and unencrypted exported recordings. For playback of unencrypted video data exported by the VRM eXport Wizard BVMS is the best choice, as the user can then also take advantage of the meta data like IVA information. For now, this is not possible for encrypted recordings, because the re-import of encrypted VRM block exports is not yet supported. Instead, the user has to take advantage of the new mp4 conversion functionality of the VRM eXport Wizard. Of course, the conversion also works for unencrypted recordings. Both cases are explained in the following.
Convert already exported data to mp4
To convert VRM block exports to mp4 format the user has to choose the option "Convert already exported data to mp4-file", see Figure 6.
Max file size per MP4 file is 500 MiB
How to convert unencrypted recordings to mp4?
In the "Select exported data for conversion" screen the user can choose the source, in this case unencrypted recording blocks, and the output directory, where the mp4 files shall be saved to, Figure 7. To choose the exported VRM blocks, which shall be converted to mp4 format, the user has to navigate to the corresponding camera folder and has to select the related BIN.file. This is illustrated in Figure 8. For unencrypted VRM blocks no further information is needed and conversion can be started by pressing the next button in the "Select exported data for conversion" screen.
Similar to the export procedure the VRM eXport Wizard also shows the status of the conversion process. Once it is successfully finished, the screen will look like in Figure 9.
How to convert encrypted recordings to mp4?
The conversion of encrypted VRM blocks starts in the same way as the "unencrypted recordings" case above. However, in the "Select exported data for conversion" screen the user needs to add a valid redundancy key for encryption. Therefore, the checkbox "Source is encrypted" needs to be checked and the redundancy key (a .pfx file) needs to be selected and the password needs to be entered, as demonstrated in Figure 10 and Figure 11.
... View more
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.
If you do not use the Start.exe included in the VRM Master Installer, you will not be offered the oppertunity to also upgarde the Transcoder. Just running the Setup_VRM_Service_<version>.exe found in the <Install\Bosch> folder, will cause the Transcoder service to stop functioning!
This includes if the upgarde is done via BVMS installer.
Since BVMS 10.0, VRM 3.82 "64bit" was implemented.
Due to the fact that BVMS does not manage the transcoder, it was not installed.
Also see Firewall settings: HowTo Configure Windows Firewall Rules, includes PS script to adjust the VRM 64bit and Transcoder rules.
Download the appropriate VRM version from our Downloadstore
Run the Start.exe
Deselect all components and choose only the Transcoder Service
Click on "Install"
To confirm that the Transcoder is fully functional, open your browser and navigate to the VRM Monitor:
Log in with you Credentials
... View more
When using Configuration Manager, each device has a status icon.
The method below shows you how to generate an updated certificate for Bosch IP Camera's and VRM Servers
Here we are talking about Certificates, the Icon is colored Yellow with an exclamation mark.
Using the mouse over Tooltip, the device is saying exactly what is wrong with the certificate connection.
VRM on a DIVAR IP 5000:
Right click on the device to Show Certificates, if you wish to view them.
We can see that there are multiple things wrong.
The Cert is not Trusted
Cert Name mismatch.
First is inconsistent date:
All IP devices and PC’s must be synchronized on Date time page (group General)
Second is invalid certificate
First quick look on certificate requirement level, navigate to Preferences -> Configuration Manager -> Access -> Security:
The certificate must just be valid - self signed certificate matching host name/IP address will be sufficient.
We need to generate a new certificate on Certificate page.
Clicking "Generate certificate" button:
should open a certificate creation dialog - most important options are matching common name and matching validity time.
After the certificate is created correct usage must be set as shown below:
IP Camera Certificate
To apply changes VRM must be restarted.
If certificate requirement is higher, then a validatable chain of certification must be used (This would be setup by a System Integrator or IT Administrator):
Trusted - the signing entity CA (e.g. VeriSign) must be trusted on target PC
Issued by this CA - There is a Micro CA setup on this PC.
... View more
The Bosch Video Client is a 32bit application, CFM 5.50 and newer are 64bit applictions. 32bit applications can only R/W 32bit files (where as 64bit applications can R/W to both 32 & 64bit files), so in order for BVC to access the CFM database, this database also needs to be 32bit.
If you need to configure newer devices with newer FW, you will need to install the relavant CFM version (e.g. CPP 7.3 Camera with FW 7.10.xxxx would require min CFM 6.20.xxxx), by installing the new CFM this will upgrade the original database to 64bit.
Leading to an issue that BVC can not open the database!
Reinstall CFM <5.5.x once more which will cause the database to be migrated back to 32bit.
Strong database encryption must not be activated, otherwise BVC will fail to start.
... View more