About marioverhaeg

Possible causes and solution(s)   Causes   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".   Solution   The SNMP services need to be installed manually. This can be done  by opening the new "Settings App“: Click “Apps” Apps&Features Manage optional Features Install SNMP It can also be done using Powershell: DISM /online /Add-Capability /CapabilityName:SNMP.Client~~~~0.0.1.0       Other useful KB articles related to SNMP: What should you know about SNMP and Bosch cameras SNMP support? How to activate the SNMP and configure sending SNMP traps from Bosch cameras? How to send SNMP v3 requests to Bosch cameras? How to send SNMP v1 requests to Bosch cameras? How to change SNMP Community string for Bosch cameras? On which occasion does DIVAR recorder send the SNMP trap HDD_STATUS_CHANGE? ... View more

Question   Is the BVMS software installation file reliable and secure (Safe software delivery)?   Answer   Software delivery Bosch software is distributed via the Bosch website, but can also be re-distributed by Bosch partners. It is important for the system-installer to check if the installation file he or she has received, matches exactly with the output of the engineering process. There are several risks that, in the distribution path, changes are made to the installation file. Keyloggers or other spyware could be added to the installation, or in theory video surveillance footage could be routed to external resources.   1 Risks The digital distribution path of the software installation file looks as follows: 1. Installation (zip) file is generated as output of the engineering process. The sources are fully protected and there no to little risk of modifications of the installation file in this phase. 2. Installation file is uploaded to the Bosch Security Systems website. The installation file is distributed within Bosch Security Systems without external exposure. There is no to little risk of modification of the installation file in this phase. 3. The installation file is downloaded from the Bosch Security Systems website to a "distributor". The installation file is distributed over the internet. Due to the point-to-point connection there is little to medium risk of modification of the installation file in this phase. 4. The installation file is distributed from the distributor to the system-installer. The installation file is temporarily stored. Depending on the accessibility of the this temporary storage there is a medium (internal) to high (public) risk of modification of the installation file in this phase. 5. The installation file is downloaded from the Bosch Security Systems website to a system-installer. The installation file is distributed over the internet. Due to the point-to-point connection there is little to medium risk of modification of the installation file in this phase.   2 Solution Downloading the installation file from the website directly does not guarantee the software is delivered as it has been generated by the engineering team. This section explains what concepts are used to check the installation file.   2.1 Checksum and Hashes Based on a hash, or checksum, the integrity of information can be verified. A hash algorithm is used to generate a fixed length key which relates directly to a unique word, or in this case, an installation file. Hashing is a one way function, there is no way to go back from the hashed value to the original value.   As a result, every time the word "Fox" is inserted into the hash function, the output will be exactly the same (DFCD3454). Using the installation file as an example, the same concept is applied: when the file is processed, a hash value is calculated. When the file is modified, the calculated hash value will also change. When the original (stored) hash value and the calculated, current, hash value, are compared, they will not match. This will mean the original installation file is modified.   3 Verifying the download This section describes how to verify if the installation file matches the expected output. The 7ZIP, open source, file compression utility includes the functionality to check the integrity of a file. Download 7ZIP Open the software installation zip, which can be downloaded from the Bosch Security Systems website, in 7ZIP. Click "File", "CRC", "*". The results can be compared with the checksum displayed on the Bosch download store, and relates to the "SHA1 checksum for data".   3.1 BVMS 7.5 As an example: the result for the BVMS 7.5 installation file (Software_Setup_7.5.0.432_all_28203530379.zip) is displayed below. --------------------------- 7-Zip --------------------------- Folders: 36 Files: 201 Size: 2903784133 bytes (2769 MB) CRC32 checksum for data: 43CB44A5 CRC32 checksum for data and names: 827EAA3F CRC64 checksum for data: 248DED357F75E492 CRC64 checksum for data and names: 9CA3603E1BD6A7E9 SHA256 checksum for data: 660C90899D1078D86CD5C52ED9D8777DAB2923D998CA3E389F94B03E5C82787B SHA256 checksum for data and names: FE59F07FCF2318A9E390633C98308E2608FE6B5103DE55C752B56FB08C2AA737 SHA1 checksum for data: E35D7879667B0675C0DEDFBCC607261B2438D20A SHA1 checksum for data and names: 83F6022D2B576340E7E11B6BFEE5D5A2AB085BB8 BLAKE2sp checksum for data: 5BF1499C2C0DA25253928C16BC643AC6DA978C03D1D8BE79042BF7FE4E41AB0D BLAKE2sp checksum for data and names: 0E6D7C02601E3F9F7B329EBC2413D6AEB9C040835BABAB1804C0C4FFFEC65B64 --------------------------- OK --------------------------- ... View more

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.   Step-by-step guide   1. AD Explorer AD explorer is a tool created by Microsoft (previously sysinternals) which allows system administrators to browse an Active Directory environment. https://docs.microsoft.com/en-us/sysinternals/downloads/adexplorer   2. Login Login to AD Explorer by using an administrator account. 3. Selecting the right DN Select the organizational unit which contains the user-group which you want BVMS to associate with. Open its properties (right-click) and copy the Distinguished Name (DN) of the organizational unit. The image below takes the general "Users" folder. The Active Directory Users and Computers overview on the domain controller looks like shown below (this is the default configuration, no additional users or groups are added). It is recommended to create a specific BVMS usergroup (the example below uses a group within the "Users" organizational unit: "BVMSgroup"). A user was added to the BVMSgroup, as shown below. 4. Command-line Experienced users could also use the command-line to retrieve the Distinguished Name of a specific user or group. dsquery user -name <known user name> dsquery group -name <known group name>   BVMS configuration 1. Configuration The LDAP basis for user and LDAP basis for group equal the Distinguished name of section 1.2. Section 3 of this document describe how to apply filters (this is especially convenient for bigger LDAP environments). The username and password of the Proxy User should relate to an administrative account of the domain. ⓘ Note Writing filters (for user and for group members) is outside of the scope of this document. More information can be found in the Microsoft Windows Dev Center.   2. Test LDAP connection The Test button within the Proxy User section tests the connection to the LDAP server. Check the username, password, LDAP Server (IP address or DNS name) settings if a connection errors appears. Firewalls or other network components could block this connection as well. 3. Test user Close the pop-up window and save the LDAP settings by closing the LDAP Server Settings dialogue with the OK button.   4. Associate LDAP group with BVMS group Once the "Test User" has succeeded, the LDAP server can be searched for groups. Once the groups are listed, the BVMS user group needs to be associated with the LDAP group. ... View more

From BVMS 10.0 onwards BVMS is an ONVIF Profile S conformant client. Cameras which are listed as Profile S compliant product on the ONVIF website are supported based on the ONVIF Profile S functionality. In the table below you can find an overview of the tested and supported ONVIF cameras for BVMS.   Version List of tested cameras BVMS 7.0 BVMS 7.0 - List of tested ONVIF devices.xlsx BVMS 7.5 BVMS 7.5 - List of tested ONVIF devices   BVMS 8.0 BVMS 8.0 - ONVIF device compatibility list   BVMS 9.0 BVMS 9.0 - VSG 6.45.8 ONVIF Device compatibility list   BVMS 9.0 BVMS 9.0 - VSG 6.45.8 OMF files.zip BVMS 10.0 BVMS 10.0 - VSG 7.0.2 - List of tested ONVIF cameras   BVMS 10.0.1 BVMS 10.0.1 - ONVIF Device Compatibility BVMS 10.1 BVMS 10.1 - ONVIF Device Compatibility BVMS 11.1.1 BVMS 11.1.1 - List of tested ONVIF devices BVMS 12.0.1 BVMS 12.0.1 - List of tested ONVIF devices   The table below shows in which situation a specific camera can be connected to BVMS and is supported. BVMS version BVMS 9.0 and older BVMS 10.0 and newer ONVIF Profile S compliant camera Yes Yes Yes Yes BVMS tested camera Yes No Yes No           Supported camera Yes No Yes Yes   For BVMS version 10.0 and above, please make sure to go through these steps: Please check the List of tested cameras. If the device is not listed in the List of tested cameras, then please check here and make sure that your device is ONVIF Profile S compliant. If your camera is not listed in the tested cameras and is not listed on the ONVIF website as Profile S conformant, we cannot help you when you have an issue with this device. You should approach the device manufacturer to certify the device as ONVIF Profile S conformant. For example, if you have an Axis camera, M1004 model, please fill in your product details in the Application Type, Profile(s), Manufacturer and the Product Name fields, under the Product Search option, and press on the “Search” button: 3. If your device is ONVIF profile S compliant you can contact Bosch Central Technical Support and request assistance. Additional information: Cameras listed as tested are owned by Bosch and issues can be fully investigated by Bosch. Cameras not listed as tested are not owned by Bosch. Solving issues might take longer as it requires collaboration with the camera vendor. Bosch support teams might need to refer to the camera manufacturer’s support line to help fixing the issue. We consider the firmware listed on the ONVIF website as the minimum firmware version of a camera. Please let us know if you run into issues with newer firmware versions so that we can investigate those accordingly. If the problem is a firmware regression, we might need to refer you to the camera manufacturer for support.    Note For the latest info in relation to BVMS version 12 or above, please contact the Central Technical Support team: Bosch VIDEO Security Systems request and Central Technical Support Team ... View more

Question   Can BVMS Operator Client be automatically authenticated using parameterized start-up?   Answer   BVMS - Automatic login of Operator Client: The BVMS Operator Client can be automatically logged in by using parameterized startup. For this, a new shortcut to the OperatorClient.exe needs to be created, and the target of the shortcut needs to be adjusted. The text between ** needs to be adjusted to the specific situation. "*BVMS installation directory*\bin\OperatorClient.exe" /user="*username*" /password="*password*" /connection="*ip_address*" For example: "C:\Program Files\BOSCH\VMS\bin\OperatorClient.exe" /user="Admin" /password="password123" /connection="192.168.20.120" The connection parameter (/connection="*ip_address*") is optional. The username and password parameters are working from BVMS 5.0 onwards.   ⚠️Warning The username and password are stored as cleartext in the target of the shortcut, which could be considered a security risk. ... View more