In Bosch VMS it is possible to assign an LDAP user group to a Bosch VMS user group. This article describes why it is important to not assign the same LDAP user group to multiple Bosch VMS user groups.
When logging on to Bosch VMS Operator Client as LDAP user, the granted user permissions and user rights are not as expected.
Examples: - When logging on as LDAP user, the permissions and rights of user group "A" are granted although the permissions and rights for user group "B" were expected. - When logging on as LDAP user, the permissions and rights of Enterprise group "A" are granted although the permissions and rights for user group "B" were expected.
Make sure that every Bosch VMS user group has an exclusively dedicated LDAP user group to avoid that unexpected user permissions and rights are granted.
Unexpected user permissions and user rights for LDAP users are most probably caused by invalid Bosch VMS user group settings. When setting the same LDAP user group for two different Bosch VMS user groups "A" and "B", the LDAP user will get the permissions and rights of one of the user groups, for example user group "A". This result might be unexpected if the expected behavior was that the logged on LDAP user gets the permissions and rights of user group "B". Note: When setting the same LDAP user group for a local Bosch VMS user group "A" and an Enterprise user group "B", the granted user permissions and user rights will always be the user permissions and user rights of Enterprise user group "B". In this case, the user permissions and user rights of user group "A" will never apply when logging on as LDAP user.
... View more
Related Products Allegiant LTC 8100 LTC 8200 LTC 8300 LTC 8500 LTC 8600 LTC 8800 LTC 8900 TC 8301 TC8500 TC8600 TC8700 TC8800 Issue Need to see cameras from remote Allegiant across the network. Solution Connect Allegiant to the VIP X1 XF as per attached drawing and connect VIA Internet Explorer to the VIP X1XF set in Allegiant mode(TC8X00).
... View more
Bosch VMS version 1.x, 2.x and 3.x
After more than 2147483647 events are written to the Logbook, overflow exceptions occur. After the first occurence of an overflow exception, Bosch VMS will stop writing events to the Logbook. In case of an overflow exception, the following message appears in the alarm list of the Operator Client:
The tool BVMS Logbook Health Checker should be used for preventing or fixing Logbook overflow exceptions. The tool should be installed by the Bosch Support group. Functionality of the BVMS Logbook Health Checker
The BVMS Logbook Health Checker checks the Logbook database for potential IDENTITY overflows on all database tables. If an overflow situation already occurred, or the occurrence of an IDENTITY overflow is imminent, the BVMS Logbook Health Checker corrects all affected IDENTITY values.
The Logbook health check begins one hour after starting the BVMS Logbook Health Checker service and is repeated every night at 00:00 a.m.
Installation of the BVMS Logbook Health Checker 1. Log on as local administrator to the Bosch VMS Central Server computer. 2. No part of Bosch VMS must be stopped or shut down. Especially the SQL-Server with the Logbook database must be running and the Logbook must be up. 3. Start the "BVMS Logbook Health Checker.msi" setup. Important hint: On Windows 7 computers, the setup must be started as administrator. The installation starts with the „Preparing to install“ dialog. After a short time the „welcome“ screen appears. Click "Next >" to proceed. If the BVMS Logbook Health Checker is installed on a Bosch VMS bigger or equal to version 2.3.0, the system-configured connection string is displayed readonly. Click "Next >" to proceed. If the BVMS Logbook Health Checker is installed on a Bosch VMS smaller than version 2.3.0, a default Logbook connection string is displayed. The Logbook connection string can be changed to reflect the system recommendation. In most cases, the default connection string should be correct and there is no need to change it. Click "Next >" to proceed. The next dialog prepares the Logbook connection string test. Click next to proceed. If the test result is that the Logbook database is up-to-date, then the following dialog will appear. In this case there is no need to install BVMS Logbook Health Checker. Click "Cancel". If the Logbook must be installed, the following dialog apears. Click "Next >". Accept the license agreement and click "Next >". In the next dialog, click "Install" to install the BVMS Logbook Health Checker. After accepting install, the progress dialog is shown. After the installation the last dialog is displayed. Click "Finish".
Deinstallation of the BVMS Logbook Health Checker
On the Bosch VMS system where the BVMS Logbook Health Checker is installed, start Control Panel > Add or remove Programs. There should be a BVMS Logbook Health Checker entry. Click "Change" to remove the BVMS Logbook Health Checker. If the setup determines that the service is needed, a warning message will be displayed. Notes
After installing the BVMS Logbook Health Checker, the Logbook database will be checked and corrected one hour after the first start. If the Bosch VMS was upgraded to version 126.96.36.199, there is no need to leave BVMS Logbook Health Checker installed on the system, so deinstall this tool.
... View more
Related Products Bosch Recording Station (BRS) version 8.9 and later Question I cannot configure UDP tunneling on BRS. Network cards are grayed out. Answer Under certain circumstances BRS NetLimiter may become not registered. The network cards are not shown in Configuration > Security and Network > Network settings. In that case, register BRS NetLimiter manually: 1. Close BRS application 2. Control Panel > System and Security > Administrative Tools > Services > Bosch Networking Service a) Set "Startup Type" to "disabled" b) Stop service c) In a console window with administrative rights, enter "C:\Program Files\Bosch\Recording Station\NetLimiterServer" /service d) Set "Startup Type" to "Automatic" e) Start service 3. Start BRS application
... View more