Security: Video

This troubleshooting guide, will guide you through the recovery steps of a DIVAR IP 6000 or 7000, DIVAR IP 6000 R2 or 7000 R2, without video data loss

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

Do not upgrade the camera FW directly to 7.81. Otherwise, “error 13: device check failed” message will be displayed, and the FW will not be upgraded successfully.

The purpose of this article is to help you find the customer number and the material/ serial/ commercial type number of your Bosch device in different ways.

This article explains how you can change the IP address of a Bosch camera from its WEB GUI or by using Configuration Manager.

This article describes all the steps that will help you to create iSCSI Virtual Disk/LUNs after replacing an HDD on a DIVAR IP 5000 AIO.

This article explains you how and where you can get the logs of your camera. The system logs are extremely useful for troubleshooting recurring or obscure problems, as they provide a record of all work performed on the system and may shed light on hard-to-spot interactions between seemingly unrelated symptoms.  

The article explains the different types of licenses, the basic rules of the license activation and how to activate licenses for the BVMS system.

VSG is specifically designed to provide integration for 3rd party ONVIF, JPEG, RTSP, and legacy H.263 Bosch devices.

In this article, you will find such an automation process between Bosch Cameras and Advantech Adam I/O devices.

The pop-up dialog window message: "Setup has detected a pending restart.  Please reboot the system and rerun the installation"  appears when attempting to run the valid BVMS windows installer package.

MTU stands for "Maximum Transmission Unit." MSS stands for "Maximum Segment Size"

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!

Remote Portal's Remote Connect service allows connection to your devices through the Remote Portal with your client software, such as Video Security Client and Video Security App.

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 provides you the way you can set the VIDEOJET decoder 8000/ 7000 (VJD-8000/ VJD-7513) to factory default. Article requirements: VIDEOJET decoder 8000/ 7000 Keyboard monitor

It is possible to add ONVIF compliant cameras to Bosch Video Management System as live only devices or as VSG devices (then the cameras will also record). This article explains how to add an ONVIF camera as VSG device in full Bosch Video Management System (BVMS 10.1). We recommend using Bosch Workstations and Servers. They are fully tested and optimized for Bosch Video Management System.   Article requirements: BVMS installed ONVIF camera. Please refer to BVMS - ONVIF Device compatibility for additional information. PC/ Server/ Workstation

This article will guide you to setup a App password usage from your Google account which you can use the generated password for Bosch IP camera alarm email notification setup.

This article provides you with the available options, services and licenses in Bosch Remote Portal for Bosch IP cameras.

DIVAR IP units can be upgraded to BVMS 11.0. Starting with BVMS 11.0, the BVMS licensing scheme also applies to the DIVAR IP units. This document describes which units you can upgrade to BVMS 11.0 and which licenses you have to order for a DIVAR IP unit!