Security: Video

This article presents what web browsers are supported by Bosch IP cameras. Also, presents the tools to be used in replacement of Internet Explorer and MPEG-ActiveX.

This article contains the list of Security Advisories (SA) to inform you about identified security vulnerabilities in our product or service and proposed solutions.

In Bosch VMS it is possible to assign an LDAP user group to a Bosch VMS user group. This article describes why it is important to not assign the same LDAP user group to multiple Bosch VMS user groups.

The RCP documentation can be found in the Firmware .zip file on the product page.

Due to the product design, the configuration of the NIR-50850-MRP (IP IR Illuminator 5000 MRP) is done only in the web browser. Also, this article contains a short explanation about how to setup the NIR-50850-MRP (IP IR Illuminator 5000 MRP).

Find out from this article how many cameras can be opened before the workstation is overloaded.

By subscribing to a specific topic on the Knowledge Base, you ensure that you receive timely updates and relevant information.

If BVMS and VRM are installed on the same machine, it is needed to change the TCP Port of the VRM Monitor.

This article is a step-by-step guide about how to disable the Live and Playback page in VRM monitor version higher than 4.10.  

BVMS Operator Client has live issues (black image, the app closes by itself, pixelation of images, same camera shown in multiple cameos although it was only selected once, hibernation/power saving, part of the tree view seen in the Image Panes area). Follow this article and find out how you can check the basics for BVMS Operator Client live issues

“Server is not online” message is displayed when accessing BVMS Operator Client. After clicking OK, the Operator Client is opening in a loop and never stops. What should you do?

This article provides causes and solutions regarding Netapp E2800 periodically disconnections.

This article lists the scenarios in which technical support normally request dump file from a BVMS system.

Since VRM 4.10, we have reintroduced the Live & Replay pages in the VRM web GUI.

Bosch's Remote System Management service allows you to leverage the power of the Internet of Things (IoT) to provide secure, transparent, and cost-effective asset management throughout the lifecycle of a video system. This service enables end users, system integrators and installers to perform inventory and update management, as well as health monitoring tasks for an entire Bosch video system (DIVAR IP + BVMS + cameras) from one centralized Remote Portal platform.

With the new VRM eXport Wizard, we offer the possibility to use CLI commands to do exports without needing to open the application.

For VRM (Video Recording Manager) stand-alone Systems and Servers with VSG (Video Streaming Gateway) installed, it is strongly recommended to check for Microsoft OS updates before the VRM Master Installer is installed/updated.

This article provides the following solution regarding: Bosch CPP7.3 cameras: DHCP does not follow the standard protocol (FW v7.85.0016) Upgrade your camera to FW 7.86.0019 and perform a factory default (access Download Store here). The time effort to fix this in older FW will be planned for early March 2023.

This article contains a simplified and generalized example, that could be helpful in building a particular tailored script related to implementation of event receiver in BVMS SDK scriplet.

Related Products: BVMS SDK, BVMS    Overview: 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: Log Info Log Error Log Debug   Examples: [Scriptlet("59c4d66e-9395-4dcc-8d27-90dc2b7a00c4")] public void DemoLogger() { //use refence:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 MessageBox.Show("Hello World"); 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: Default: </appender> <appender name="ServerScriptLogAppender" type="Bosch.Vms.Shared.Logging.Imp.RollingFileAppender, Bosch.Vms.Shared.Logging.Imp"> <file value="%CommonApplicationData%\\Bosch\\VMS\\Log\\ServerScriptLog.txt"/>   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: Default: </appender> <appender name=“ClientScriptLogAppender" type="Bosch.Vms.Shared.Logging.Imp.RollingFileAppender, Bosch.Vms.Shared.Logging.Imp"> <file value="%CommonApplicationData%\\Bosch\\VMS\\Log\\ClientScriptLog.txt"/>