Bosch Building Technologies

    cancel
    Showing results for 
    Search instead for 
    Did you mean: 

    Security: Video

    Sort by:
    ‎03-30-2020 02:50 PM
    Question How can I use "virtual" cameras to demonstrate BVMS? Answer Demonstrating a video surveillance system typically requires a couple of cameras. However, when you only have a couple of cameras, the screen can look boring and empty. Did you know you can use the video streaming gateway to pull in any online JPEG picture as a camera into BVMS? This makes your demonstration more interesting! Additionally, you can set-up your own webserver and host customer JPEG images yourself. You can find a warehouse example below, fully based on JPEG based static images. The attached document describes how to configure JPEG cameras.
    View full article
    ‎03-30-2020 11:46 AM
    Question My customers asks me to store the field of view of the cameras connected to BVMS. Is there an easy way to achieve this without opening every camera manually? Answer The embedded BVMS script engine makes this easy to achieve. The attached document explains how to achieve this and included an example script.
    View full article
    ‎03-30-2020 11:34 AM
    Question How does BVMS 10.0.1 (or newer) configure the firewall during the installation of the system? Answer The firewall configuration dialog is a fixed step in the setup process and will allow automatic configuration of all required firewall settings to run BVMS. The applied rules and settings can be found in the readable command script file "C:\Program Files\Bosch\VMS\bin\FirewallConfig.cmd". The firewall rules that have been applied with the setup cannot be reverted and must be manually changed/removed if required.
    View full article
    ‎01-14-2020 12:32 PM
    In many cases a minimum and maximum retention time needs to be defined in a video surveillance systems due to legal requirements. While the minimum retention time defines the time period for how long video recordings need to be stored, the maximum retention time defines after which period of time the recordings have to be deleted. Thus, the minimum retention time is going to influence the amount of storage needed. The higher the minimum retention time the more storage space is required. Hence, the storage space needs to be large enough to store the recordings for the minimum retention. For the maximum retention time this doesn’t have to be the case. Still users might be confused why recordings gaps might appear sort-of randomly, if the system does not have enough storage space to keep all recordings until the maximum retention time is reached. To understand what is going on we have to remember the principle of the VRM block assignment first. For each camera in the system the BOSCH Video Recording Manager (VRM) generates a list of recording blocks (LUNs) on which the camera can next record. Therefore, the VRM makes an estimation based on the data rate and the amount of data of each camera in the system (global optimization). Basically, the VRM predicts when which camera needs a new block and always lists the block which will be the oldest block at the time the camera needs to record on the next block. One could think of it as a “next oldest block” estimation done by the VRM. But the prediction of the VRM might differ from the reality (mainly because of variance in recording bitrate) and this can cause recording gaps if the storage space is not large enough to support the maximum retention time. Let’s have a closer look on the following two cases: Sufficient storage space for maximum retention time Insufficient storage space for maximum retention time Sufficient storage space for maximum retention time In case of sufficient storage space to fulfill the maximum retention time for every camera in the system no random recording gaps will appear, because the VRM will always assign a block containing recordings, which are older than the maximum retention time. Thus, for each camera the recording blocks will be kept until the maximum retention time is reached as illustrated in Figure 1. Figure 1: Enough storage space to cover the maximum retention time for each camera of the system Insufficient storage space for maximum retention time In case the system is designed such that the storage space is not large enough to store all recordings from all cameras until the maximum retention time is reached, the VRM will of course still do its estimation and predict the oldest recording block when a camera will ask for a new block. Assuming an ideal setup (with ideal network connection where each camera has the same data rate and all cameras record the same amount of video data simultaneously), the oldest block would always be assigned by the VRM. Hence, no recordings gaps should appear for recordings older than the minimum retention time, compare Figure 2. This is was most customers falsely assume or expect. Figure 2: Customer expectation of the system behaviour in case of insufficient storage space to cover the maximum retention time for each camera of the system However, in reality the stated assumptions do not apply. Network connection, data rate, amount of recorded video data, etc. varies. Thus, the “next oldest block” estimation of the VRM can differ from reality. Since each camera already got its block list from the VRM and records according to this block list, it can happen that not the truly oldest block is used and recording gaps appear as shown in Figure 3. Figure 3: System behaviour in case of insufficient storage space to cover the maximum retention time for each camera of the system How to avoid or minimize this effect To avoid this effect of random recording gaps simply add enough storage to your system. To get the best out of your system in terms of storage usage, the optimum would be to set the maximum retention time to storage limit, see Figure 4, but that is almost impossible to realize in practice. Figure 4: In principle a maximum retention time set to the storage limit would avoid random recording gaps Option 1 to minimize the effect in practice is to estimate the maximum retention time so that it will not exceed the storage limit of the system as illustrated in Figure 5. Figure 5: Maximum retention very close to the storage limit will minimize the random recording gaps Another less recommended option is to set a smaller time difference between the minimum and maximum retention time. But especially when the minimum retention time is shifted closer to the maximum retention time that introduces the risk that the VRM cannot free up storage space in case the minimum retention time is reached, which might result in a recording stop. Thus, we recommend to go for the first option. One last hint: Changing the retention time on a running system is not going to influence the retention time of already recorded blocks. but will of cousre only be applied to new recorded video footage. Hence, changing the retention time is no option for an immediate change of required storage.  
    View full article
    ‎11-19-2019 01:22 PM
    Symptoms The Activation Key provided from SLMS cannot be activated in BVMS. During the introduction of BVMS 10.0 the BVMS Lite16, 32, and 64 base licenses were not introduced and succeeded by BVMS Lite 10.0 (8 channel base package). Existing BVMS Lite customers might still want to upgrade to BVMS 10.0. Solution The LIF file attached to this article (in the zip archive) can be imported in BVMS Lite 10.0 installations using the license manager (the license manager can be found in the "Tools" menu of the BVMS Configuration Client). Once imported, BVMS Lite 16, 32, 64 systems that are covered under SMA can be upgraded.    
    View full article
    ‎10-30-2019 08:07 AM
    Symptoms During the introduction of BVMS 10.0 the BVMS Plus unmanaged site expansion licenses were not introduced, even though this functionality was announced to be available. Solution The LIF file attached to this article (in the zip archive) can be imported in BVMS Plus 10.0 installations using the license manager (the license manager can be found in the "Tools" menu of the BVMS Configuration Client). Once imported, the purchased licenses (MBV-XSITEPLU-100) can be activated.
    View full article
    100% helpful (2/2)
    ‎10-28-2019 08:43 PM
    BVMS Installer - Windows Pending Restart Message Issue:  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. BVMS Installer Pending Restart Message   Cause:  This is a known Windows specific problem when another (non-BVMS) installer does not properly manage its creation and deletion of the “PendingFileRenameOperations” registry key. The most common user created way for this key value to be left resident in the system is when an installation prompts for a restart, yet the system is not expeditiously restarted.     Resolution:  A. Restart the affected workstation B. If the issue still persists, delete the orphaned "PendingFileRenameOperations" registry key value Open a registry editor, such as Regedit.exe or Regedt32.exe.   Navigate to "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\" In the right navigation pane, right-click the "PendingFileRenameOperations" key value and select delete Close Registry Editor. Run the software Installer again as Administrator   Note:  This message is not a Bosch product failure message. This is a problem within windows and it's registry clean-up handling.  This is a Windows work around. 
    View full article
    100% helpful (1/1)
    ‎10-28-2019 03:38 PM
    BVMS Mobile Video Service - Creating a Self-Signed Certificate to establish a trusted connection Some sites may request or require that the connection to the Mobile Video Service is a trusted connection.  The following procedure will allow you to create a self signed certificate to allow a trusted connection between a web browser and MVS. -Navigate to the Microsoft Management Console Run command mmc.exe Go to File ---> Add/Remove Snap-in… Highlight Certificates and Add for Computer Account You should see certificates listed for Local Computer Save a copy of this console to the Desktop -Run Windows PowerShell ‘as administrator’ on the MVS Server Run the following commands in Windows Power Shell to create the self-signed certificate including the IP address of the MVS and the DNS name so both will work when accessing from a web browser. $todaydt = Get-Date $20years = $todaydt.AddYears(20) New-SelfSignedCertificate -DnsName "mvsIPaddress",”DNSname” -notafter $20years If creation was successful, you will see a thumbprint with a hash as well as the subject CN=ipaddress -Navigate back to your saved MMC console Find the newly created certificate under the Personal  ---> Certificates directory Copy the Certificate to Trusted Root Certification Authorities ---> Certificates directory -Navigate to the IIS Manager Highlight the server machine name on the top-left and then double-click Server Certificates Double-click the created certificate and verify that a private key corresponds to the certificate and that the certificate is OK under the Certification Path Expand the server machine name on the left to reveal the Sites Highlight BoschIVS Select Bindings… on the far right-hand side Edit the Binding for 443 Select the newly created certificate under the SSL certificate dropdown Select OK Click Yes that you want to change the binding Add… new binding Type: https Port: 444 Choose BoschVms in the SSL certificate dropdown Click OK -Navigate to the BVMS Config Client to edit the MVS URL Change the MVS URL to reflect port 444 Example:  https://mvsIPaddress:444/mvs Red X should go away Save/Activate  (BVMS will be bound on the new port and still be able to communicate with the MVS server -Open Internet Explorer (as administrator) and navigate to the MVS URL using the IP address or the DNS Name Continue to the site with the certificate error Click on the certificate error in the navigation bar Click View Certificates and then Install Certificate Install for the Local Machine Place certificate in the Trusted Root Certification Authorities store Click Finish and close out the browser Open IE again and navigate back to the MVS.  There should be no more error.   *The reason behind changing the port to 444 is to make browser access for basic users easier.  This way basic users only have to enter the IP address or DNS name and do not have to enter a special port in the URL.    
    View full article
    100% helpful (3/3)
    ‎10-25-2019 12:48 PM
    Possible Communication Issue between BVMS 8.0 Central Server and Video Recording Manager (VRM) 3.7x with BVMS 8.0 installed on different Servers. Problem Identification Communication can get interrupted and configuraiton might fail if the below desribed actions are not performed. If your system is affected or not is described here as follows: There can be authentication issues between the BVMS Central Server and the Video Recording Manager in case they are installed on different Servers. It is possible to see reports at the BVMS 8.x system alarms that VRM reports wrong version Please check in the VRM debug logging if the following logline indications can be found CONFIG;DEBUG;SENDING XPATH /SYSTEM/DEVICES/DEVICE as well as HAS NO CONFIGURED NODE, SET TO CONFIGURED CONFIG;INTERNAL;/SYSTEM/DEVICES CHANGED IN CONFIG. DEVICEID= [DEVICE IP]\0;SYSINFO;INTERNAL;LINE 1 HAS NO CONFIGURED NODE, SET TO CONFIGURED Solution In general please keep in mind, that it is strongly recommended to use VRM 3.71.00xx with BVMS 8.0. Do not use any older VRM version like 03.71.0022. The 03.71.0029 and Releaseletter is available at the BOSCH DownloadStore (status update 2018-10-26). https://downloadstore.boschsecurity.com/FILES/Setup_VRM_03.71.0029_win32.zip Release Letter: https://downloadstore.boschsecurity.com/FILES/Bosch_Releaseletter_VRM_3.71.0029.pdf At the VRM system / server, please check and ensure that the following Microsoft software packages are pre-installed: .NET framework 4.6.2 or higher Redistributables for Visual Studio 2015 In case one component is missing, please perform the following steps: Download the missing Microsoft components. Note: When using BVMS 8.0 the VRM is typically a 32-Bit VRM software. Therefore the 32-Bit Microsoft packages are needed. Component that was seen as missing is the >>   “Visual C++ Redistributable for Visual Studio 2015”            https://www.microsoft.com/en-US/download/details.aspx?id=4814 Please choose the 32-Bit version of that when using with 32-Bit VRM and the >>  .NET framework 4.6.2 or higher (NDP462-KB3151800-x86-x64-AllOS-ENU.exe)       https://www.microsoft.com/en-US/download/details.aspx?id=53344 Stop the VRM (rms.exe) service in Windows services  Install those components with Administrator rights at the VRM server Reboot the server after installation of the Microsoft components Check if the VRM service is running and if needed Re-Start the VRM (rms.exe) service Check that the combination of messages are not longer seen in the VRM debug logging The VRM package is enhanced and useres should no longer run into this issue with VRM 3.81 and newer versions. Please be aware that BVMS releases are tested with certain VRM verions. This still can offer to install a newer VRM than originally rolled-out in the BVMS overall installer. For all VRM versions 3.7x and below 3.81 it is needed to add this packages.
    View full article
    ‎09-19-2019 08:32 AM
    The attached document aims to provide concerned parties, such as customers, users, operators or consultants, with an overview of data privacy and protection related features of BVMS Person Identification. Moreover, this document describes how data, as processed during the Person Identification steps, can be classified. Finally, this document lists technical measures for data protection in the context of BVMS Person Identification.
    View full article
    ‎09-18-2019 09:17 AM
    As video surveillance use grows in commercial, government and private use cases, the need for low-cost storage at scale is growing rapidly. BVMS, Bosch cameras, HPE hardware and SUSE Enterprise Storage provide a platform that is an ideal target for recording these streams. There are numerous difficulties around storing unstructured video surveillance data at massive scale. Video surveillance data tends to be written only once or become stagnant over time. This stale data takes up valuable space on expensive block and file storage, and yet needs to be available in seconds. With this massive scale, the difficulty of keeping all the data safe and available is also growing. Many existing storage solutions are a challenge to manage and control at such scale. Management silos and user interface limitations make it harder to deploy new storage into business infrastructure. The solution is software-defined storage (SDS). This is a storage system that delivers a full suite of persistent storage services via an autonomous software stack that can run on an industry standard, commodity hardware platform. Bosch, Hewlett Packard Enterprise (HPE) and SUSE have partnered to deliver the benefits of SDS to the video surveillance industry. Using SUSE Enterprise Storage™ on HPE ProLiant DL and Apollo servers in a Bosch video surveillance environment simplifies the management of today’s volume of data, and provides the flexibility to scale for all enterprise storage needs. The full description can be found in the attached whitepaper.
    View full article
    100% helpful (1/1)
    ‎08-26-2019 01:03 PM
    Question How can I combine a ISS SecureOS Auto system (providing ANPR functionality) with a BVMS system? Answer The attached document describes the steps how to configure BVMS and the ISS SecureOS Auto system for achieving watchlist ANPR alarms and recorded ANPR detections into the BVMS logbook.  
    View full article
    ‎08-26-2019 08:34 AM
    The attached document describes how the GDPR impacts video surveillance systems and how BVMS can be configured to function in a GDPR compliant organization.
    View full article
    ‎08-02-2019 03:47 PM
    Question Does BVMS meet the requirements specified in IEC62676-1? Answer The attached document describes how a BVMS system meets the requirements specified by IEC62676-1.
    View full article
    100% helpful (2/2)
    ‎07-18-2019 07:50 AM
    Question Can I move the BVMS Logbook database to a separate Microsoft SQL Server to ease maintenance or increase the size of the Logbook? Answer The BVMS Logbook database can be moved to another SQL Server. The attched guide describes the steps that are necessary to migrate the database and describes how to confirm if the migration was successful.
    View full article
    100% helpful (1/1)
    ‎07-10-2019 12:25 PM
    VSC, Video Security App, Bosch Video Security App 3.0.1.75 fixes internet connection issue.
    View full article
    100% helpful (1/1)
    ‎03-26-2019 02:54 PM
    Question How can I migrate the full configuration (including server configuration and user settings) of a BVMS system from one server to another? (please note that, currently, the export mechanisms provided in the BVMS Configuration Client do not export the userdata. This is a known problem and being worked on. Until then this work-around should be applied). Answer Stop the BVMS Central Server service on the existing server from the Windows task manager or Services overview. Stop the BVMS Central Server service on the new server from the Windows task manager or Services overview. Copy the contents of the directory C:\programdata\Bosch\VMS\UserData on the existing server to the same directory on the new server (via the network or other media). Copy the "elements.bvms" file located in the directory C:\programdata\Bosch\VMS\ on the existing server to the same location on the new server (via the network or other media). Start the BVMS Central Server service on the new server from the Windows task manager or Services overview.
    View full article
    ‎03-17-2019 06:55 PM
    Question How can I find the source (details of the workstation) and credentials that are used to attempt to login into BVMS (when the attempt has failed)? Answer The username that is used to login is saved into the BVMS logbook and can be found by searching the logbook from the Operator Client (username of login is "blabla").   The details of the workstation (mainly the IP address) is logged into the BVMS client log files. These can be found on the workstations in the directory: C:\ProgramData\Bosch\VMS\Log (Hint: for log file analysis a lot of free / open source tools are available. Snaketail is one of these tools, and can be found here.) Open the BVMSClientLog.txt (there could be multiple files which are all related to a different timeframe) and search for the phrase "InvalidCredentialException". If an user has tried to login to the system the following log lines should be present in the log file: 2019-03-17 18:31:53,668 75516 [GUI Thread] INFO Bosch.Vms.Frontend.OpClient.Wcf.DataAccessServiceClient ConnectAndAuthenticate - Call failed with InvalidCredentialException 2019-03-17 18:31:53,670 75518 [GUI Thread] INFO Bosch.Vms.Frontend.OpClient.ServerManagement.CentralServerManager AuthenticateAtMainServer - Main-Server 192.168.20.190: WCF online authentication result is WrongUserOrPassword This needs to be checked for every workstation which runs the BVMS Operator Client.  
    View full article
    ‎01-17-2019 10:12 AM
     The Software "VIDOS" or "VIDSO-NVR" with the replay tool "Archive Player for VIDOS" are all rather outdated former software developments of BOSCH ST. We kindly request all our partners and customers in the need to get technical support on license transfers to get in contact with a local BOSCH team (e.g. Sales contact person). Level 2 Support / ASA organization can assist and help you to find a correct contact person as well, but a support ticket should and can no longer be created as license transfers are no longer offered for discontinued and outdated software. Status of Aug 3, 2018   In many countries, the VIDOS Software went end of live 2011. With this announcement, we inform about the discontinuation of the software maintenance and license transfers. Please be aware of the EOL status (End of life). EOL was rolled out globally in June 30, 2011 with some exceptions in North America. December 31, 2012 and later it was no longer possible to purchase the software. End of 2015 License management was restricted. Due to many other changes (Operating system limitations and not state of the art security support), it is anyhow no longer possible to use those software. BOSCH does offer for a long time other software generations and we offer migration support from commercial side to find software today that can meet the needs in projects. Since 2018-08-03, BOSCH Support can no longer offer license transfers for VIDOS and similar former Software packages. Following Type Number and SAP Number is included:   For more details you can check with the Technical Support for video products at BOSCH in your region.
    View full article
    ‎01-15-2019 05:10 PM
    In this article we cover the following basic questions: How to Factory Default a NetApp E-Seires unit by using BOSCH tools and NetApp WEB GUI? How to download the NetApp Support Bundle of a reachable online NetApp Storage Array   How to Factory Default a NetApp E-Series that you bought via BOSCH sales channel? Using the BOSCH Configuraiton Manager 6.00 or 6.01 the NetApp models E2600, E2700 and E2800 can be managed. Especially we recommend to use the BOSCH Configuration Manager version 06.01 when using a NetApp E2800 to have all models (also former models E2700 and E2600) supported. Also in the BOSCH Configuraiton Manager 6.01 the Basic configuration for the initial setup is helpful as well as the Factoury Default option and Clear option is available. Of cours the NetApp E2800 offers also a WebGUI by using the IP of the management port of a controller. The following screenshot made from the BOSCH Conmfiguration Manager shows the options available in the tab "Basic Configuration" when a NetApp E-Series (DSA E-Series) is already added to a VRM system in the Configuraiton Manager. The Button "Defaults" is used to trigger the "Reset Storage Array" mechanism of NetApp. At a E2800 all configuration is eliminated but the Management Port IP still remains to ensure that the WEB GUI of NetApp and the communiction of the BOSCH Configuraiton Manager can still work. How to download the NetApp Support Bundle of a reachable online NetApp Storage Array In the Tab "My Devices" of the Configuration Manager 6.01 and newer versions you can also now download the Support Bundle (collection of logfiles) from a NetApp E2800 stroage system. Select the NetApp E2800 in your device tree that is added to a VRM system and right-click on it. There you find "File Download" and "Maintenance Log..." - Choose that to download the NetApp Support Bundle.          
    View full article
    Top Contributors
    Icon--AD-black-48x48Icon--address-consumer-data-black-48x48Icon--appointment-black-48x48Icon--back-left-black-48x48Icon--calendar-black-48x48Icon--center-alignedIcon--Checkbox-checkIcon--clock-black-48x48Icon--close-black-48x48Icon--compare-black-48x48Icon--confirmation-black-48x48Icon--dealer-details-black-48x48Icon--delete-black-48x48Icon--delivery-black-48x48Icon--down-black-48x48Icon--download-black-48x48Ic-OverlayAlertIcon--externallink-black-48x48Icon-Filledforward-right_adjustedIcon--grid-view-black-48x48IC_gd_Check-Circle170821_Icons_Community170823_Bosch_Icons170823_Bosch_Icons170821_Icons_CommunityIC-logout170821_Icons_Community170825_Bosch_Icons170821_Icons_CommunityIC-shopping-cart2170821_Icons_CommunityIC-upIC_UserIcon--imageIcon--info-i-black-48x48Icon--left-alignedIcon--Less-minimize-black-48x48Icon-FilledIcon--List-Check-grennIcon--List-Check-blackIcon--List-Cross-blackIcon--list-view-mobile-black-48x48Icon--list-view-black-48x48Icon--More-Maximize-black-48x48Icon--my-product-black-48x48Icon--newsletter-black-48x48Icon--payment-black-48x48Icon--print-black-48x48Icon--promotion-black-48x48Icon--registration-black-48x48Icon--Reset-black-48x48Icon--right-alignedshare-circle1Icon--share-black-48x48Icon--shopping-bag-black-48x48Icon-shopping-cartIcon--start-play-black-48x48Icon--store-locator-black-48x48Ic-OverlayAlertIcon--summary-black-48x48tumblrIcon-FilledvineIc-OverlayAlertwhishlist