Security: Video

The following procedure will allow you to create a self signed certificate to allow a trusted connection between a web browser and MVS.

SecureOS sends events from analytics to BVMS, which can be translated into alarms and/or stored into the logbook.

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.

The connection of 2N® Helios IP intercom to BVMS and Bosch Access Control System is possible thanks to the implementation of ONVIF and Wiegand protocols, which ensure mutual compatibility.

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.

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

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

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

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"/>

This article explains how to collect Video SDK Logs for VSDK based applications.

BVMS Version 10.0: please note that, currently, the export mechanisms provided in the BVMS Configuration Client do not export the user-data.

This article explains how to find the source (details of the workstation) and credentials that are used to attempt to login into BVMS (when the attempt has failed)

This article describes how you can upgrade a BVMS license to a higher version via Bosch Remote Portal. ( eg. from BVMS 11.0  to BVMS 11.1.x )

If the Host Type was set to other value than “Factory Default” for DSA E2800 and you want to integrate it with BVMS, the targets will most likely not be scannable and there will be no recordings at all.

This article explains how you can configure the iSCSI ports of your DSA E2800 dual or single controller and afterwards configure it in BVMS Configuration Client.

Prior to receiving any type of support, the customer needs to be informed that he/she must have a valid SMA (Software Maintenance Agreement)

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.

This article explains what is BVMS Operator Client and how this work with cameras in live view mode. 

Check this article and find out if you can add and see a BVMS 11 system running on a DIP in MVS webpage as unmanaged site