Security: Video

Related Products: BVMS / MVS / VSDK Overview: On request from development to provide a dump file from MVS system please follow the steps in the solution section.   Step-by-step guide   Reproduce the issue Download the Microsoft debugger procdump (https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx). The procdump tool is also attaced to the article :How To create BVMS memory dump?  When application is crashing, do not click any buttons on the appeared error window that will change the program state. Run the procdump.exe from the directory where you copied the tool with following command line (Start - cmd): procdump.exe –ma <name of the programm exe> <dump file name>.dmp   In the case of MVS you need to do that for all 4 MVS services: - Bosch.MVS.SourceProvider.BVMS.Service.exe - Bosch.MVS.DataStorage.Service.exe - Bosch.MVS.SourceProvider.MobileCamera.Service.exe - Bosch.MVS.Transcoder.Service.exe

The Windows Storage Server operating system of DIVAR IP all - in - one 7 000  is  installed on a two SSD drives in redundant (mirrored) configuration. Health status of  the mirrored OS drives can be monitored using a tool called Virtual RAID on CPU  (formerly known as Rapid Storage Technology). Installation and configuration steps  are described below. Step-by-step guide   1. Installation: Download  the setup  from  here Copy the content to a USB drive When the BVMS default screen is shown, press CTRL + ALT + DEL Hold down the SHIFT key while clicking Log off Log in as BVRAdmin Transfer the IATA_CD.exe from the USB drive to the BVRAdmin desktop Double click  the  IATA_CD.exe executable Follow the installation procedure  as shown in the screen shots     2. Email notification: Note: The E-mail notification feature is based on SMTP access without authentication. It is strongly suggested to use this functionality only with a dedicated server in the local network, which is specifically configured for this purpose and doesn’t handle any critical data.

Related Products: Video Analytics for Firmware 6.60 and above Technical Note on Intrusion Detection The technical Note  attached to this article contains detailed technical description of Intrusion Detection, set up guidance for different usage scenarios and best practices. It is useful to get in depth knowledge about Intrusion detection or to find the answer of frequently asked questions.   Intrusion detection without calibration Learn how to use the default scenario - Intrusion detection no camera calibration: A predefined scenario that can be used to detect intruders in small areas and controlled environments Intrusion detection one field   Learn how to use the default scenario - Intrusion detection one field: A predefined scenario that can be used to detect intruders in small areas. Intrusion detection two fields   Learn how to use the default scenario - Intrusion detection two fields: A predefined scenario that can be used to detect intruders in large outdoor areas.  Note: If needed you can get additional how to information on camera calibration.

Upcoming with FW 7.10 and CM 6.20, Camera Trainer is a licensable Intelligent Video Analytics module that allows uses to define objects of intereste and train their own detectors for them based on examples of target objects and non-target objects. In contrast to the moving objects detected in general by IVA 7.10, Camera Trainer allows detection of both moving and non-moving objects, separates and immediately classifies them. Training can be done both on live video as well as on recordings available through the respective camera. The resulting detectors can be down- and uploaded for distribution to other cameras.

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.  

This Video should help you to understand, what calibration means, why and when to calibrate the cameras.

 Related Products: Video Analytics for Firmware 6.60 and above This article describes how to count with Bosch Video Analytics with How to Video and a Technical Note on the topic. View the video to get initial idea how to set up the feature, short explanations on the prerequisites and an example configuration.    For in depth description of the feature counting please check the attached Technical Note. It provides background information and technical details and can support you to configure and optimize a particular counting scenario.  How to Video: People counting default scenario Learn how to configure the default scenario - People counting: A predefined scenario that can be used to count people that are crossing a specified / specific line.   Technical Note on Counting The attached document describes in depth the count feature of Video Analytics. It explains how to plan the camera perspective and best practices for camera view, the set up for the scenario people counting and the options to access the counter data.   Note: If needed you can get additional how to information on camera calibration.

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

⚠️  CAUTION! If a computer on which VRM Server is starte d is simultaneously accessed by multiple  Configuration Manager programs, this can result  in an inconsistent VR M configuration. Ensure  that different people do not make chang es to the configuration at the same time.   Step-by-step guide Open one browser and type in the IP address of the VRM server you are pulling the log from. This will take you to the VRM Monitor web page. Log in with the VRM credentials (default user name is srvadmin); by default, there is no password   3.82 version: Go to Monitoring > System > Logbook The Export  Log bock page allows you to export all or only selected system  log s as a .zip file. Export system  log s Select the desired export  log book options. Export as ZIP  – Click to create a .ZIP file with selected   log  files, for example to send them to the Central  Technical Support Team.   3.83 version: Please note that the interface for VRM v3.83 has changed on the log collection. Therefore, the VRM log collection will be done by accessing Monitoring > System > Export Logbook Export system  log s Select the desired export  log book options. Export as ZIP  – Click to create a .ZIP file with selected   log  files, for example to send them to the Central  Technical Support Team. You can also collect the device maintenance logs from the VRM monitor (for VRM 3.50 or newer) Open the   VRM monitor   and log in with the VRM credentials Go to   Monitoring->   Devices   -> click on the   download icon   next to the camera

  Related Products: VRM, Genetec Security Center Overview: It is possible to use VRM free of charge (no extra VRM license is required) within Genetec Security Center. Genetec is sending encrypted secret to the VRM server with the number of the licensed channels. When VRM receives and validates this, it can be used for that number of channels for 24 h. A periodic license update is send by Genetec, so the VRM licensing is guaranteed as long as it is used with Genetec Security Center. Default settings, if not extra configuration is needed or done. -License for 1000 Cameras - License update is done every hour   How to license more than 1000 cameras or change the license update period for VRM within Genetec Security Center: Open the Config Tool and Launch a Video Task Select the Archiver Go to the Resource Tab and click on Extensions From the Tab Installed extensions select Bosch. In the Tab VRM add a new VRM and/or select already configured VRM. Click on Advanced settings and add the following parameters If you need to license the system with more than the default 1000 licenses – create the parameter with Name VrmLicenseRequestCount and as value put the required number of licenses. The parameter name is case sensitive If you need to change the duration of the period between each license request (there is always one license request when the archiver starts) – create the parameter with Name VrmLicenseRequestPeriod. The duration of the period is in milliseconds. The default value is one hour. If the value is set to 0, the license request are disabled. The parameter name is case sensitive     Press Enter to confirm the entry and then Close Press Apply and then OK. At the webpage of the VRM one can check if the number of licenses is changed.                    

Follow the steps from this article and find out how you can integrate the Bosch USB Keyboard "KBD Universal XF" with Bosch Video Client (BVC).   Driver installation is required on the workstation where the KBD Universal XF Keyboard is connected Driver can be download from the official Bosch Security and Safety Systems page. Navigate to Products > Video System > Switching System and Keyboards > Keyboards >   KBD Universal XF   > Downloads > Software Operational Check When connecting the KBD Universal XF Keyboard to a workstation, the LEDs will blink once. This indicates that the keyboard is detected by the workstation

The   Clear   button on the   Configuration Manager   is designed to clear the codes that are self-generated by the IP firmware or the Configuration Manager itself. Follow the steps below, if you want the "Clear" button from Configuration Manager to able to erase the Alarm task script that are self created by users themselves.   Step-by-step guide   When you create your alarm task script, add it within an opening quotes which then the   Clear   button will be able to erase all those codes within the quotes. Alternatively, create your own quotes within your script by following the below rules. In the  Below example,   //{{MyScript_start   is inserted before any script and   //}}Myscript_end   is inserted at the end of the script. By doing this, the   Clear   button will now be able to recognize and detect the manual scripts created by user and erase them.   Example: //{{Myscript_start ControlCode auxon1:={Operation(AuxOn)Number(1)}; if(Motion(1))then auxon1; //r1_o1 //}}Myscript_end

This article shows how to configure Input Alarm and later search for them in the Event search using Web Interface. There are only 3 different search parameters for Event type search, which are "All", "Motion" and "Alarm". Once can search for any alarms during the set time period and channel and in this way indirectly to filter for Input Alarm (if only Input Alarm triggers Recording for a particular channel). It is not possible to directly narrow the search for particular Alarm type (ex. Input alarm).

Related Products: Configuration Manager 7.00 and above. This article shows how to use recorded video in Configuration Manager in order to calibrate a camera and to configure a task.  

This article provides you the solution when the MIC IP starlight 7100i camera wiper stops on the screen. Furthermore, you will learn how to perform a physical reset of the camera.

What happens when you upgrade the SW of your Management Server form e.g. BVMS 10.0 to BVMS 10.1 and you have not prepared a BVMS 10.1 activation key beforehand? => The System will be unlicensed and Operator Client will not be able to connect to the MS as long the new BVMS 10.1 activation key is not provided to the system via Config-Client. Therefore,   performing the steps from this article is absolutely necessary.

This guide is meant to explain how to enable the appropriate debug commands for logging during random reboot situations, and which logging to collect for troubleshooting, as in general there are multiple triggers that can cause a device to reboot. The information gathered will help to analyze the root cause.  Please make sure that all of the logs collected cover the same time period.

Related Products: BVMS, application crash, memory dump This article lists the scenarios in which technical support normally request dump file from a BVMS system. It contains general guidelines how to create a dump file for BVMS system and provides links to more concrete articles, that correspond to particular issues and exact steps to create a dump. BVMS dumps are needed to troubleshoot the following types of issues: Application crashes – dump is expected to provide more information about the cause of the crash and its origin. Memory or handle leaks – dump is expected to point to their origins Deadlocks, freezes and hangs – dump is expected to point to their origins Recommended tool to create BVMS dumps. The recommended tool is Procdump. It is a command line tool which must be started from the command shell. Development provides couple of .bat files that start Procdump with predefined parameters and cover the most common dump creation cases. The tool as well as the set of .bat files are attached to this article: BVMS_DumpTools_V2.zip The batch file names follow a naming guideline: <Executable>_<Dump use case> , where <Executable> is one of: ConfigClient ConfigWizard OperatorClient ManagementServer ArchivePlayer ExceptionTest and <Dump use case> is one of SingleDump TwoDumps DumpOnException DumpOnHang ActivatePostmortemDebugging There are 3 possible error scenarios and corresponding dump creation methods: Dump creation for reproducible crashes that trigger Windows Error Reporting Run the affected application/service (Operator Client, Configuration Client or Management Server Service) Reproduce the steps that lead to the crash Leave the Windows crash dialog open Run the corresponding batch file for creating a single dump: *_SingleDump.bat. E.g. run OperatorClient_SingleDump.bat to create a single dump of the Operator Client process. Provide support with the resulting .dmp file a description of the steps to reproduce the problem ConfigCollection Note: attached you can find a configured example for this scenario and application Operator Client - BVMS_OC_dump_onException.zip Dump creation for reproducible memory or handle leaks Run the affected application/service (Operator Client, Configuration Client or Management Server Service) Run the corresponding batch file for creating two dumps: *_TwoDumps.bat. E.g. run OperatorClient_TwoDumps.bat to create two dumps of the Operator Client process. Note that by default, the delay between the two dumps is set to one hour (3600 seconds). Depending on the magnitude of the memory leak, you might want to increase/decrease the delay. To do that, edit file *_TwoDumps.bat: replace value "3600" by a value that fits your needs e.g. a value of "7200" will create two dumps with a delay of two hours. Reproduce the steps that lead to the memory leak. Wait until the second dump was created. Provide support with the resulting two .dmp files a description of the steps to reproduce the memory leak a ConfigCollection Dump creation for crashes/hangs/freezes that are hard to reproduce Deactivate the restarting option for Operator Client / Configuration Client: To deactivate the restarting option for Operator Client / Configuration Client: edit ..\Bosch\VMS\bin\ConfigClient.exe.config or ..\Bosch\VMS\bin\OperatorClient.exe.config. Navigate to section <appSettings> add a new entry <add key = "DisableExceptionHandling" value="TRUE" />. Run ActivatePostmortemDebugging.bat Run the affected application/service (Operator Client, Configuration Client or Management Server Service) As soon as the issue appears, check whether the dump was created. Provide support with the resulting .dmp file description of the steps to reproduce the crash ConfigCollection Note: attached you can find a configured example for this scenario and application Operator Client - BVMS_OC_dump_Just-In-Time-Debuger.zip

This information  may be requested by Central Support Team, as the bundle file is useful for troubleshooting the improper behavior of the unit. This method provides the steps for collecting the NetApp DSA E2800 support bundle.

This article  provides an overview of Operator Client (BVMS 10.0.1) for most used functionality for security operators and incidental users.