Security: Video

The attached document provides more insights into the system configuration regarding the BVMS - Operator collaboration with Slack

The choice of the tool depends on the way the camera and recording are managed.

This article describes the absolute minimum information we need in order to start analyzing and optimizing Video Analytics performance

This article provides a step by step description of how to create certificates and configure their distribution in the large systems. 

The modern and easy to use Bosch Video Security Client version 3.2 provides you new features. Check out this article and find what's new!

Find out from this article if there are restrictions of VRM Configuration utility pre-installed on DLA

Find out from this article how to configure a singe mode VIF on NetApp array. For example if we have 2 (or more) physical interfaces, how to connect them to different network segments and, if one of the segments fails, the second network interface to step in automatically?

BP+ (Baseline Profile +) is available in any of the new ARM based chipset encoders, like the VIP-X1 XF.  BP+ is needed for compatibility with Divar and hardware decoders, for example, theVIP XD decoder.

Place the script from this article in the alarm task editor and save it.

The initial idea of the Project Assistant is nicely summarized in the video from this article

Check this article and see what's new in Project Assistant version 1.4.0

In order to quickly offer a technical solution or to provide a professional advice for the next analysis steps, the technical support specialists need to get some general and basic information. Ticket content should always be in English and provided in a well summarized and structured way in order to be able to provide a quick and appropriate feedback. Not following the guideline will impact the processing time of the ticket. Related Products: BVMS Operator Client Overview: This article describes the initial steps one can take for troubleshooting BVMS display issues (during live view or playback). It also summarizes what initial information and logs are needed for support in order to start the issue investigation.   General Information   SMA validity How to retrieve the Hardware ID for BVMS and check the Software Maintenance Agreement (SMA) status? BVMS stand alone or appliance Detailed problem description Check and eventually update the version of your Graphic Card driver. During BVMS system tests there were documented cases of display issues related with out of date Graphic card divers. ❗ It is important that the Graphic Card driver of the client is up to date. Find the supported version of the Graphic Card driver in the corresponding to your BVMS version Release Notes (https://downloadstore.boschsecurity.com), in the section Hardware drivers.   Symptom specific Information   Problem Description   Is the issue dependent on camera type/ FW? Are all the devices in the system affected? Is the issue existent for all BVMS Operator Clients in the system? Is the issue existent for hardware decoders, for camera Web Interface or other display Clients? Is the recording, the playback or are both affected?   Logging Information   BVMS ConfigCollector logs keeping the following conditions: From the machine that shows the issue VSDK logging – please follow the steps from the article: How to collect Video SDK log files  VRM logs (in case VRM runs on the same machine like the BVMS MS, then BVMS ConfigCollector logs from the server) for VRM version 3.82 and onwards use VRM Monitor. The following articles will help you out:   How to access VRM monitor from BVMS Configuration Client? How to collect VRM logs with VRM Monitor (v3.82/ v3.83)? Screenshot of the Dashboard of the VRM for VRM version till 3.81 - contact support to receive BVIP Log collector tool and use it to collect VRM logs Movie showing the display artefacts can be helpful

This article describes how Streamlining works and how it can be finetuned.

Time is everything: meetings, public transportation, religion, transactions: the whole world is working because the concept of “time” exists. Within a security (or any other) system this is not different: recording schedules, logging, authorizations, encryption keys, timelines, all of these concepts can exist because of time. As a result, time can either make or break a system: problems can appear only due to a time difference of a couple of seconds between two system components. This article describes how time services can be configured in a BVMS version ≤ 10.1 environment. For BVMS  version ≥ 11.0 please refer to the following article:  Where can you configure NTP server for cameras/encoders in BVMS≥11? Time: what is the challenge? Each device has its own internal clock, which is based on a hardware mechanism. This mechanism acts like a watch: try to put two watches together and synchronize them on the millisecond. A security system consists out of more than two devices, it can consist of thousands of devices. Synchronizing the time of all these devices by hand is a very time consuming task. Additionally, due to small differences in electronic components, devices can have deviations from one another. These deviations cannot be detected by the human eye, but can result in considerable time differences when a device is running for months. Synchronizing time The Network Time Protocol (NTP) was created to solve these challenges. The Network Time Protocol is a network-based protocol for clock synchronization between system components. The protocol utilizes a standard IP network to communicate and can maintain a time difference (considering a local area network) of less than one millisecond between components. The Network Time Protocol is a standard protocol and documented in RFC 5905. The operation and configuration of the Network Time Protocol are complex: a hierarchical architecture needs to be set-up including several layers of systems which are able to run the Network Time Protocol. To reduce complexity the Simple Network Time Protocol (SNTP) was  created. The Simple Network Time Protocol is mainly used when less accuracy (deviations of 1-2 seconds are acceptable). Windows Time Service The Bosch Video Management System is running on Microsoft Windows Server operating systems. Windows includes an internal time service, which is explained on Microsoft Technet: “The Windows Time service, also known as W32Time, synchronizes the date and time for all computers running in an AD DS domain. Time synchronization is critical for the proper operation of many Windows services and line-of-business applications. The Windows Time service uses the Network Time Protocol (NTP) to synchronize computer clocks on the network so that an accurate clock value, or time stamp, can be assigned to network validation and resource access requests. The service integrates NTP and time providers, making it a reliable and scalable time service for enterprise administrators. The W32Time service is not a full-featured NTP solution that meets time-sensitive application needs and is not supported by Microsoft as such. For more information, see Microsoft Knowledge Base article 939322,Support boundary to configure the Windows Time service for high-accuracy environments (http://go.microsoft.com/fwlink/?LinkID=179459).” Source: Windows Time Service Technical Reference - Microsoft Technet The Windows Time service is based on the Simple Network Time Protocol. Summary The Network Time Protocol requires a very complex infrastructure, which impacts the total installation and configuration effort of the system. The Simple Network Time Protocol (also used for the Windows Time Service) reduces the complexity, but at the same time also reduces the accuracy. For most security applications the Simple Network Time Protocol provides sufficient accuracy. Bosch recommends to use the Windows Time service, based on the Simple Network Time Protocol, as basis for time synchronization in a security network. This article provides best-practices on how to configure the Bosch Video Management System and related components in a time synchronization environment based the Windows Time service. Alternatively, the Network Time Protocol can be used whenever it is already existing inside an infrastructure or when event accuracy with a deviation less than one second is required. Due to the complexity of the infrastructure Bosch does not make any recommendations related to the Network Time Protocol.     Step-by-step guide   Management server configuration   A. Operating system configuration This section also applies for the Video Recording Manager and Mobile Video Service when these are not running on the management server. Microsoft has prepared a lot of documentation related to time configuration Go to the Microsoft Support: How to configure an authoritative time server in Windows Server page and scroll down to the section “Configuring the Windows Time service to use an external time source”. Click the download button under the “Here’s an easy fix” section. Figure: Download the Microsoft Windows Time service configuration utility   The utility will configure external time servers. To select these, browse to http://pool.ntp.org and select two servers which are related to the geographical location of the system, for example “de.pool.ntp.org” and “nl.pool.ntp.org”, referring to Germany and the Netherlands. Another (local or external) (S)NTP server can also be chosen.   Start the Microsoft configuration utility and configure it as indicated and shown in the figure below. Administrative access is required to run the utility. Figure: Pool.ntp.org locations   Figure: Windows Time service configuration   Alternatively the configuration can be done from the command-line, using the command shown below. net stop w32time w32tm  /config   /syncfromflags :manual  /manualpeerlist : "nl.pool.ntp.org, de.pool.ntp.org" net start w32time The configuration can be verified by starting the Windows Command prompt and issuing the command “w32tm /query / status”, as shown in the figure below. Notice the time source, this should point towards the configured servers. Figure: verifying configuration   It can take up to one minute before the correct time source is displayed. When there is a problem, the configured (S)NTP server can be tested by issuing the “w32tm /stripchart /computer:de.pool.ntp.org”, which should result in the output displayed in the figure below. Figure: test the (S)NTP service   When an unexpected result is returned, it is recommended to check access to the specific (S)NTP server. A firewall might prevent the communication between the (S)NTP server and the management server.   B. BVMS Management Server configuration BVMS automatically points devices to its own time-server. This can be changed by editing the BvmsCenterlServer.exe.config file, located in C:\Program Files\Bosch\VMS\bin\. Find the key "TimeServerIPAddress" and adjust the value, as shown in the example below (192.168.0.1). <!-- Ip address of the time server for VRM/NVR encoders(defaults to the Central-Server IP if not set). --> < add   key = "TimeServerIPAddress"   value = "192.168.0.1"   />     C. Workstation configuration The Bosch Video Management System Operator client runs on a Windows workstation. When the workstation and server are part of the same Microsoft Active Directory service domain, no manual time synchronization needs to be configured. Figure: workstation configuration, "192.168.0.200" needs to be replaced by the IP address or Fully Qualified Domain Name of the management server.   When the Bosch Video Management System workstation and management Server are not joined in a domain, or into the same domain, the workstation(s) need to be manually configured to use the management server as a time server. To achieve this, the description above can be used. Instead of using the pool.ntp.org as a server, the management server is now entered.   D. Camera configuration If a camera is connected to a BVMS system the time server will be automatically configured.

This article contains documents attached which describes the installation package for BVMS. Operating system support of the specific BVMS version is listed in the BVMS release notes.

The attached manual provides information for Mobile Video Service (MVS) within Bosch Video Management System. You can find:  - how to configure the router and Internet Information Service (IIS) - how to add MVS to BVMS - user guide - some troubleshooting tips   This document can also be found online here.

This article describes the different components that Bosch Video Management System offers to to establish a connection between Bosch Video Management System and a 3rd party management system. This description helps you in writing your own commands for controlling Bosch VMS from inside your management system.   

In order to quickly offer a technical solution or to provide a professional advice for the next analysis steps, the technical support specialists need to get some general and basic information. Ticket content should always be in English and provided in a well summarized and structured way in order to be able to provide a quick and appropriate feedback. Not following the guideline will impact the processing time of the ticket.

This article contains the LIF fie which will help you to activate the Activation Key from SLMS for BVMS Lite v10.0

This is a step-by-step guide about how to collect BMC logs (RAID & IPMI Event Logs, System, Audit & Video Logs) of DIP AIO 7000 gen4.