Security: Video

Follow the steps from this article if you want to configure your camera to detect motion and then send the event to the server, to start recording. This guide helps you set this option only for nights and weekends. It is important that you find the best possible motion detection settings for the camera in order to avoid unnecessary recordings or notifications.

Have a look at this article and learn what you should check when your cameras do not record and when going to VSG and recording, it stands that 'ANR not configured' or 'No more blocks available'

Monitor Group gives operators flexible control over the content of a video wall or allows them to let the system take over this control automatically based on pre-defined scenarios. This article describes how to create a Monitor Group on a decoder VJD 7xxx/ 8xxx in BVMS Configuration Client

Follow this article and find out how to store a snapshot of all cameras automatically from the Operator Client

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

What should you do if you tried to drag an drop the device to the cameo window from BVMS Operator Client and instead having the video, it displays the logical tree?

The calculation of the storage capacity is done in different way in Configuration Client and VRM Monitor. Check this article and find useful details!

Short intro and related topics: This article will review the settings required to configure Windows as a NTP time server. Note: If you are running VRM and have the Time Server enabled, you must disable the Time Server before performing the following. Article requirements: Windows Server 2016/ Windows 10

This article explains step by step how to play exported recording files from VRM eXporter Wizard in BVMS Export Player.

This article describes the considerations that need to be taken into account when designing a video surveillance system that is suitable for person identification. 

The following steps have to be performed in order to use an updated software installation package on a DIVAR IP all-in-one 7000 3rd generation video management appliance.

The USB driver has a different letter than E:\ and DIVAR IP Software Center seems to look only in this root, in fact it doesn't find the new software.

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.

This article explains how to playback the SD card recordings in Operator Client from a camera added as Local Storage in BVMS Lite 10.1

Follow the steps from this article when an error message appears on your DIVAR IP 5000 AIO during license activation process

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

This article shows how to check if particular non Bosch camera is supported in BVMS.

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.

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

Starting with BVMS 10.0, ONVIF encoder events can be retrieved from VSG or ONVIF encoder directly. Additionally to ONVIF profile S, BVMS 10.0 supports ONVIF profile T.