Bosch Building Technologies

    cancel
    Showing results for 
    Search instead for 
    Did you mean: 

    Security: Video

    Sort by:
    ‎08-20-2020 09:08 AM
    Question What is the decoding performance of BVMS? How many cameras can I open on the screen before the systems is overloaded (and frames are being dropped)? Answer The BVMS client performance overview is attached to this article and shows, based on several workstation configurations and a specific BVMS version, how many cameras can be opened before the workstation is overloaded.
    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
    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
    Thursday
    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.5 BVMS 7.5 list of tested ONVIF cameras  BVMS 8.0 BVMS 8.0 List of tested ONVIF cameras  BVMS 9.0 BVMS 9.0 List of tested ONVIF cameras  BVMS 10.0 BVMS 10.0 List of tested ONVIF cameras  BVMS 10.0.1 BVMS 10.0.1 List of tested ONVIF cameras  BVMS 10.1 BVMS 10.1 List of tested ONVIF cameras    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.
    View full article
    ‎08-19-2020 08:21 AM
    Question How can I protect my security system, from an IT security perspective? Answer The attached document explains how the security system can be hardened. Additionally the BVMS - Network Design Guide includes best practices for desgning a secure network.  
    View full article
    ‎11-19-2019 12:41 PM
    Related Products: BVMS, application crash, memory dump This article lists the scenarios in which technical support normally request dump file from a BVMS system. It contains general guidelines how to create a dump file for BVMS system and provides links to more concrete articles, that correspond to particular issues and exact steps to create a dump. BVMS dumps are needed to troubleshoot the following types of issues: Application crashes – dump is expected to provide more information about the cause of the crash and its origin. Memory or handle leaks – dump is expected to point to their origins Deadlocks, freezes and hangs – dump is expected to point to their origins Recommended tool to create BVMS dumps. The recommended tool is Procdump. It is a command line tool which must be started from the command shell. Development provides couple of .bat files that start Procdump with predefined parameters and cover the most common dump creation cases. The tool as well as the set of .bat files are attached to this article: BVMS_DumpTools_V2.zip The batch file names follow a naming guideline: <Executable>_<Dump use case> , where <Executable> is one of: ConfigClient ConfigWizard OperatorClient ManagementServer ArchivePlayer ExceptionTest and <Dump use case> is one of SingleDump TwoDumps DumpOnException DumpOnHang ActivatePostmortemDebugging There are 3 possible error scenarios and corresponding dump creation methods: Dump creation for reproducible crashes that trigger Windows Error Reporting Run the affected application/service (Operator Client, Configuration Client or Management Server Service) Reproduce the steps that lead to the crash Leave the Windows crash dialog open Run the corresponding batch file for creating a single dump: *_SingleDump.bat. E.g. run OperatorClient_SingleDump.bat to create a single dump of the Operator Client process. Provide support with the resulting .dmp file a description of the steps to reproduce the problem ConfigCollection Note: attached you can find a configured example for this scenario and application Operator Client - BVMS_OC_dump_onException.zip Dump creation for reproducible memory or handle leaks Run the affected application/service (Operator Client, Configuration Client or Management Server Service) Run the corresponding batch file for creating two dumps: *_TwoDumps.bat. E.g. run OperatorClient_TwoDumps.bat to create two dumps of the Operator Client process. Note that by default, the delay between the two dumps is set to one hour (3600 seconds). Depending on the magnitude of the memory leak, you might want to increase/decrease the delay. To do that, edit file *_TwoDumps.bat: replace value "3600" by a value that fits your needs e.g. a value of "7200" will create two dumps with a delay of two hours. Reproduce the steps that lead to the memory leak. Wait until the second dump was created. Provide support with the resulting two .dmp files a description of the steps to reproduce the memory leak a ConfigCollection Dump creation for crashes/hangs/freezes that are hard to reproduce Deactivate the restarting option for Operator Client / Configuration Client: To deactivate the restarting option for Operator Client / Configuration Client: edit ..\Bosch\VMS\bin\ConfigClient.exe.config or ..\Bosch\VMS\bin\OperatorClient.exe.config. Navigate to section <appSettings> add a new entry <add key = "DisableExceptionHandling" value="TRUE" />. Run ActivatePostmortemDebugging.bat Run the affected application/service (Operator Client, Configuration Client or Management Server Service) As soon as the issue appears, check whether the dump was created. Provide support with the resulting .dmp file description of the steps to reproduce the crash ConfigCollection Note: attached you can find a configured example for this scenario and application Operator Client - BVMS_OC_dump_Just-In-Time-Debuger.zip
    View full article
    100% helpful (2/2)
    ‎01-11-2019 09:05 AM
    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. Once the BVMS Management Server is set-up, it creates a client installation package (mainly used for the auto-upgrade functionality). This client installation package is a lot smaller compared to the full installation package and is located on the BVMS Management Server (assuming the default installation directory is used): C:\Program Files\Bosch\VMS\Update In order to use the client installation package: copy all the files in this directory from the management server to the new workstation and start BVMS.msi (please note Setup.exe will trigger the auto update mechanism, which will not work as there are no existing components to be updated). The MSI will start the installation process and will allow you to select Operator Client, Configuration client and/or SDK. Please note: The correct version of the .NET framework will need to be installed manually before this procedure is used. This can be found in the zip file available in the product catalogue: “zip file extraction location”\ISSetupPrerequisites\Microsoft .NET Framework x.x.
    View full article
    100% helpful (1/1)
    ‎10-10-2018 03:42 PM
     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. The attached document describes how the integrity of software can be checked.
    View full article
    ‎10-21-2019 02:05 PM
    Related Products: BVMS, Operator Client This article describes the initial information needed to start troubleshooting Operator Client Crash. Needed information and logs from the customer: 1. Note down the events that lead to crash 2. Classify the crash reproducible crashes that trigger Windows Error Reporting crashes/hangs/freezes that are hard to reproduce, or take long before repeating 3. Provide the following logs: Dump file from the crash – refer to the following article ( https://community.boschsecurity.com/t5/Security-Video/How-To-create-BVMS-memory-dump/ta-p/7326 ) ConfigCollection from the machine where the crashing Operator Client is running.
    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
    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
    ‎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
    ‎03-29-2019 10:38 AM
    Related Products: BVMS SDK, Cameo SDK, BVMS  Overview: Analyzing BVMS systems interaction with BVMS SDK based application is a challenging task. One needs to determine if the issue is based on wrong implementation of the BVMS SDK functionality, wrong programming practices, functionality and runtime behavior of BVMS system with SDK functionality or BVMS SDK issues. In order to troubleshoot BVMS SDK or Cameo SDK application support needs the following information and logging. Please prove the following information to support. 1. Detailed description of the expected behavior of the SDK functionality. 2. Detailed description of the actual behavior of the SDK functionality. 3. 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? 4. SDK Interactions Do SDK components interact with remote Operator Clients? Do SDK components interact with the Operator Client UI? Do SDK components control devices? Do SDK components link to 3rdParty devices or applications? 5.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.)  Please provide source code and/or Log files The optimal approach is to provide both source code and logging for the problematic BVMS SDK application. If it is not possible to provide the code, we will start the troubleshooting process based only on the logging. 1.Source Code Provide a little sample application that illustrates the BVMS SDK issue and list the reproduction steps. 2.Logfiles Add log outputs to the SDK application functionality. The logs should illustrate which BVMS SDK functionality was called at which time. Provide the logs to support.   List of Typical Mistakes that are often seen when troubleshooting BVMS / Cameo SDK based applications Use of Thread. Sleep() in event handlers - Consequence: loss of events in customer SDK application. Implementations that are not thread safe - Consequence: unexpected SDK application effects Unintentional introduction of multithreading issues by using timers - Consequence: unexpected SDK application effects Application without "speed control" - Consequence: operator overload in case of high event frequency Lack of configuration change handling - Consequence: data inconsistencies in SDK application (access to no longer existing devices) Lack of traces/logging in SDK code - Consequence: not detected malfunctions and troubleshooting difficulties Lack of error tolerance in SDK code - Consequence: unhandled exceptions in SDK application / script Lack of exception handling - Consequence: SDK application crashes    
    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
    ‎09-03-2019 01:41 PM
    Dear users, have you ever wondered how to best transition from the Project Assistant to (B)VMS? This article aims at providing you a recommendation and the answer is quite simple: Use the Project Assistant to its full extent and once the cameras are connected to the target network, perform a network scan using the BVMS Configuration Client, to add the respective cameras to the system. The remaining fine-grained settings can then be tackled within BVMS.  For details, please check out the attached presentation. Let us know, if you have further questions and share your comments below. Best regards, Your Bosch Security App Team    
    View full article
    ‎04-01-2019 12:33 PM
    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. 1. Detailed description of the expected behavior of the SDK functionality. 2. Detailed description of the actual behavior of the SDK functionality. 3.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? 4.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? 5.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.)    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. Make sure that logging is implemented in the script and that logging is activated in the configuration. 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.  
    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
    ‎04-26-2019 11:03 AM
    Related Products: BVMS / MVS / VSDK Overview: On request from development to provide a dump file from MVS system please follow the steps in the solution section. Solution: Reproduce the issue Download the Microsoft debugger procdump (https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx). The procdump tool is also attaced to the article https://community.boschsecurity.com/t5/Security-Video/How-To-create-BVMS-memory-dump/ta-p/7326?advanced=false&collapse_discussion=true&filter=includeTkbs,location&include_tkbs=true&location=tkb-board:bt_community-tkb-video&q=dump&search_type=thread  When application is crashing, do not click any buttons on the appeared error window that will change the program state. Run the procdump.exe from the directory where you copied the tool with following command line (Start - cmd): procdump.exe –ma <name of the programm exe> <dump file name>.dmp In the case of MVS you need to do that for all 4 MVS services: - Bosch.MVS.SourceProvider.BVMS.Service.exe - Bosch.MVS.DataStorage.Service.exe - Bosch.MVS.SourceProvider.MobileCamera.Service.exe - Bosch.MVS.Transcoder.Service.exe
    View full article
    100% helpful (1/1)
    ‎08-20-2020 08:01 AM
    Compared to hardware, in which it is relatively easy to define an end-of-support concept based on the expected lifetime, software behaves totally different. In theory, when the environment does not change, software can still be running ten years after it has been installed. As new versions of the software are released regularly, it is important for customers to know what they can expect from Bosch Building Technologies when the software is purchased. This document describes how Bosch Building Technologies handles the life-cycle of the BVMS, BIS, AMS, and APE, and in which state a specific release can reside. Additionally this document lists the up-to-date situation for all of those software packages.
    View full article
    100% helpful (4/4)
    ‎10-02-2018 01:55 PM
    The BVMS Operator Cliet 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 works with BVMS 9.0 and newer. The username and password parameters are working from BVMS 5.0 onwards. The username and password are stored as cleartext in the target of the shortcut, which could be considered a security risk.
    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