Security: Video

  What does mean the clock symbol showed in the Operator Client Logical tree?

When using the BVMS 9.0 installer on a Windows 10 "October 2018 update" machine (Build 1809) the SNMP services cannot be installed. Microsoft has changed the way the SNMP services are installed in Windows 10 "October 2018 update".

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 provides you with information related to the Windows Firewall, how to access, configure and adjust it.

This article explains how BVMS can be configured to connect to an LDAP (or Microsoft Active Directory) and use it as a base for user authentication.   BVMS is able to function in a (Windows) domain-controlled environment. The BVMS (and related) services run under the local system account. If another (domain-controlled) account is used to run these services, their permissions level should be the same as the local system account. It is recommended to add the Windows server to the domain first (as a domain member), before installing the BVMS software. The BVMS configuration is independent from the domain configuration, however, crucial changes in the domain could break the connection between the BVMS system and the LDAP authentication mechanism.

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.

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 SDK, BVMS    Overview: Analyzing BVMS systems with SDK components is a challenging task, because the functionality and the runtime behavior of those systems are harder to determine than for a BVMS systems without SDK functionality. In order to troubleshoot BVMS systems with SDK components support needs the following information and logging. Please prove the following information to support:   Symptom specific Information   Problem Description SMA validity How to retrieve the Hardware ID for BVMS and check the Software Maintenance Agreement (SMA) status? BVMS stand alone or appliance Detailed description of the expected behavior of the SDK functionality. Detailed description of the actual behavior of the SDK functionality.   SDK Components What type is the standalone SDK application (based on ClientSDK, ServerSDK, or CameoSDK) and on which machine is it running? Are there additionally client scripts, server scripts or workstation startup scripts?   SDK Interactions Do SDK components interact with remote Operator Clients? Do SDK components interact with the Operator Client UI? Do SDK components control devices? How often are client scripts triggered? How often are scripts triggered by BVMS event?   Environment Which shared resources are accessed by SDK actions? (Dome cameras, AMG, Operator Client UI) Do SDK components interact with an unreliable environment? (Unstable network, offline devices, offline PCs, etc.) Do SDK components properly handle offline situations? (offline devices, configuration changes, etc.)    Logging Information Please provide the Scriplet and/or Log files The optimal approach is to provide both the scriplet and logging. ClientScript logfiles: can be found in the ConfigCollection of Operator Client machines. ServerScript logfiles: can be found in the ConfigColletion of Management Server machines.   Make sure that logging is implemented in the script and that logging is activated in the configuration.  

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

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 This article describes the initial information needed to start troubleshooting Operator Client Crash.   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   Symptom specific Information Problem Description   Note down the events that lead to crash Classify the crash reproducible crashes that trigger Windows Error Reporting crashes/ hangs/ freezes that are hard to reproduce, or take long before repeating   Logging Information   Dump file from the crash – refer to the following article How To create BVMS memory dump?  ConfigCollection from the machine where the crashing Operator Client is running.

Question Why I cannot see my camera in the Logical Tree from Operator Client? Answer Please make sure that you have done all the steps below accordingly. Normally, to be able to view a camera in the Operator Client, you need to: Go to the Maps and Structure tab from Configuration Client. Drag and drop the camera in question from the Device Tree to the Logical Tree. Save and Activate the changes. This step is very important because otherwise, you will not be able to see the changes in Operator Client, even though the first 2 steps were carried out in Configuration Client.

This article explains how to find and calculate the specific size of BVMS logs on your server when the log starts to overwrite your own data.

Various overlays in the video image provide important status information. But what does mean the blinking play button near the yellow exclamation icon?

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

This article helps you to solve the situation where the "No Config" error message appears when you try to authenticate in Operator Client. This error can be persistent, no matter what central server you attempt to login to and no matter what user account or credentials you are trying to use. This means that you have a corrupt cache .dat file on your system. Follow the steps from this article if you attempt to login into BVMS Operator Client and encounter the message below and you want to fix it: "Please enter your credentials... No config..."

When working with previous versions of BVMS, remote connectivity was cumbersome due to the amount of port mapping that needed to be configured. BVMS 7.5 provides a new method of remote connectivity utilizing Secure Shell (SSH) Tunnelling. SSH Tunnelling constructs an encrypted tunnel established by an SSH protocol/socket connection. This encrypted tunnel can provide transport to both encrypted and un-encrypted traffic. The Bosch SSH implementation also utilizes Omni-Path protocol, which is a high performance low latency communications protocol developed by Intel. Key management The BVMS SSH service generates a private and public key when it is started for the first time. Both keys are saved in an encrypted file. When the BVMS SSH service restarts this file is detected and the private key is read.   Step-by-step guide   1.Configuration   A. Installation There is little to no configuration required for this feature to function. The SSH Service must be installed and running. If deploying a BVMS Pro system, insure the SSH Service is part of the installation process. Recording Appliances that ship with BVMS 7.5 should have the service pre-installed. Check your “Services”. If the service has not been installed, the install package can be run from the BVMS 7.5 downloadable install package. If working with a DIVAR IP Recording Appliance, the appliance “Installer Package” must be used.   B. Port mapping entry The primary configuration step is to configure one (1) port forwarding for the BVMS Central Server to utilize port 5322 for both internal and external connections. This is the only port mapping entry that needs to be made for the entire system. The image below shows a sample configuration.   2. Operation   A. Login with the Operator Client After the basic configuration is done, logging in via Operator Client is very intuitive: From the log menu, select the “Connection” drop down menu, then Select <New…> You will be prompted to enter an IP address or DNS host name. You will also notice a cheat guide below the entry menu that will assist with address entry. Addressing must be in the following format: ssh://IP or servername:5322. In the example we used: ssh://49.49.49.49:5322. After entering a properly formatted address, enter a valid user name and password. SSH users MUST have a password associated with their BVMS account. User accounts without a password cannot log in utilizing an SSH Connection.   B. Verification After connection is established via an SSH Tunnel, all communications between the BVMS Server (192.168.1.19) and a remote client (49.49.49.48) are encrypted. Below is a Wireshark Capture taken from the BVMS Server after a connection is established. C. Changing the SSH port Locate the SSH service configuration file in "C:\Program Files\Bosch\BVMS\bin" Open the configuration file and find the section below. Edit the value of the BvmsSshServicePort (the port should be unused) and restart the system.