Bosch Building Technologies

    Security: Video

    Sort by:
    50% helpful (1/2)
    ‎09-06-2019 09:38 AM
    This troubleshooting guide, will guide you through the recovery steps of an DIP, without video data loss   General note:  Using a Bosch DIP system without video data disks is a non supported use case, its mandatory to equip the system with data disks to recover the system.     Step 1 - Preperation Download the attachment repair.zip and unzip the content Prepare an USB-stick, rename it to SCRIPT Copy the repair.txt extracted of the attachment on the USB-stick Insert the USB-stick into an USB-slot of your machine Insert the BOSCH r ecovery DVD into the DVD-drive   Step 2 - Create RAiD1  Boot the machine and enter the Intel RAiD MENU pressing  CTRL  +  I Navigate to CREATE RAiD VOLUME and hit enter Set RAiD level to RAiD1(Mirror), navigate to CREATE VOLUME and hit enter Exit the RAiD controller, navigate to EXIT and hit enter Reboot the machine (e.g. press CTRL + ALT + DEL)   Step 3 - System Recovery During the reboot, boot from DVD, press ENTER as the line will displayed In the System Management  Utility, click on CONSOLE Type into command line "diskpart.exe" hit enter Type into command line "list volume" hit enter and search for your USB-stick called SCRIPT, note down the assigned drive letter (LTR) End diskpart.exe by typing on the command line "exit" hit enter Type into the command line "diskpart.exe /s [YOUR_USB_DRIVE_LETTER]:\repair.txt" hit enter Wait until the script has been finished and CLOSE the console   Step 4 - System Recovery On the System Management Utililty click on  SYSTEM RECOVERY (back to factory default) NOTE: Do not select Initial Factory Setup, this will wipe all existing data! As  the recovery has been completed, click on OK to confirm and reboot Do not eject the DVD and follow the instructions on your screen to initialize the system. 
    View full article
    100% helpful (3/3)
    ‎03-27-2020 02:08 PM
    Symptoms Connectivity problems after DIVAR Mobile Viewer APP upgrade from v3.0.0 to the new v3.1.0 Diagnosis As result of a software bug in the APP problems in the connectivity  can occur in case the DIVAR hybrid/network is running firmware v3.0.0 or below. Running firmware v3.1.0 does not show the problem. This problem exists for both Android and IOS app platfoms Solution DIVAR Mobile Viewer app 3.1.1 for both Android and iOS have been released and are available on the stores. This version is compatible with previous DIVAR hybrid/network firmware v3.0.0 and 3.1.0   Additional info for DIVAR AN 3000/5000  For the DIVAR AN 3000/5000 we just learned that the DIVAR Mobile Viewer app v3.1.1. can consume more than one session per device. This typically happens when in the Live Preview the "Device List" (top right icon) is used to open all cameras simultaneously. This seems only to happen as a first action when you open the app. This can result is a failing connection showing the message “System is busy”. For the moment please apply these workarounds avoiding this connection problem: - Change the number of remote sessions allowed (default=4) in the DIVAR AN 3000/5000 configuration to 64 (Menu, Settings, Network, Max. connection) OR - Avoid the use of "Start Live Preview (16)" in "Device List" as an first action. By viewing one camera only as first action showed that new session consumption was prevented. In case of occurring connection problem: close and restart the DIVAR Mobile Viewer app. This problem seems not to occur when using Android or for accessing DIVAR network/hybrid.
    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
    2 weeks ago
    Upcoming with FW 7.10 and CM 6.20, Camera Trainer is a licensable Intelligent Video Analytics module that allows uses to define objects of intereste and train their own detectors for them based on examples of target objects and non-target objects. In contrast to the moving objects detected in general by IVA 7.10, Camera Trainer allows detection of both moving and non-moving objects, separates and immediately classifies them. Training can be done both on live video as well as on recordings available through the respective camera. The resulting detectors can be down- and uploaded for distribution to other cameras. Camera Trainer configuration should be done in Configuration Manager. The attached fact sheet lists the cameras that support Camera Trainer. The attached technical note describes in-depth what Camera Trainer is, how it works, what to use it for and what not, and how to configure it. The configuration is also shown in the following how-to videos: Note: After you license your Camera Trainer, reboot your device. Setup Camera Trainer Camera learning phase with recorded video   Configure Camera Trainer Task   Backup Camera Trainer Configuration - Method 1   Backup Camera Trainer Configuration - Method 2 Setup VCA Masking
    View full article
    100% helpful (3/3)
    ‎02-12-2020 10:10 AM
    The attached document describes the settings you must perform after having installed BIS and BVMS on the different computers. Ensure that the installations of BIS Server and BVMS Management Server were performed successfully on separate computers. Additionally you must have purchased and activated an OPC Server License for BVMS.   The document can be found in the attachments section on the bottom of the page or the right side of the page.  Please look for the attachment icon.
    View full article
    100% helpful (3/3)
    a month ago
    General Note: Newer NetApp controller firmware might be approved and qualified by BOSCH. This article only refers to a introduction in time of a 11.50 firmware generation.  (e.g. status 08/2020 there is an 11.60.2 qualified by BOSCH)  Details can always be found at the BOSCH product catalogue: https://commerce.boschsecurity.com/us/en/DSA-E-Series-E2800-60-bay/p/34919710859/  and https://resources-boschsecurity-cdn.azureedge.net/public/documents/DSA_E2800_Release_Note_enUS_79775057035.pdf Potential for Data Inconsistency Issues on E-Series Storage Systems With the controller firmware 11.50.1 and newer version an issues are fixed by NetApp, which enforce an immediate update of all E2800 iSCSI Storage Systems (their controllers). In July 2019 BOSCH announced the need to update from all former NetApp controller firmware 08.30.40.00 to newer versions. These newer versions should be certified and approved by BOSCH. In 2019 there was also an announcement by NetApp. All customers owning a NetApp storage system with valid warranty agreement and registered unit do have access to the public announcemnt of NetApp. This was announced by NetApp on their support websites (see https://mysupport.netapp.com/). Bosch approval 31st of January 2018  Bosch approval 7th of May 2019 Bosch approval  20th of September 2019 newer NetApp firmware versions: NetApp Firmware 08.30.40.00 no longer allowed for usage NetApp Firmware: 11.50.R1 no longer allowed for usage NetApp Firmware: 11.50.2 no longer allowed for usage BOSCH qualifies and approves new global NetAp frmware vversions for E2800 controllers. Please always use the latest approved NetApp global firmware where possible Please follow our BOSCH Knowledge Base and monitor for updates at this article for important news.  The BOSCH submodel ID 356 ensures that the NetApp system is optimized for 24/7 video recording. Products that were affected: All DSA E-Series (E2800 12-bay) and DSA E-Series (E2800 60-bay) Example product variants: DSA-N2E8X4-12AT Base unit 12x4TB High-performance and high-capacity storage system base unit with iSCSI disk arrays, single controller. DSA E2800, 12 x 4 TB HDD, Order number DSA-N2E8X4-12A DSA-N2C8X4-12AT Dual controller unit 12x4TB High-performance and high-capacity storage system base unit with iSCSI disk arrays, dual controller. DSA E2800, 12 x 4 TB HDD, Order number DSA-N2C8X4-12AT Note: There are other models with various HDD capacity (e.g. 8TB harddrives and larger) available For more details visit the BOSCH product website Summary of issue NetApp® has become aware of issues that could occur when an E-Series controller reboots at certain points during the evacuation of data from a drive that is performed as part of the sequence when a drive is being failed by the controller. As a result, there is a small possibility of data inconsistency on controllers running certain versions of E-Series SANtricity® OS controller software.   Issue Description First announced in 06/2019: The issues are possible on E-Series controllers running 8.30, 8.40, 11.30, 11.40, and 11.50 versions of E-Series SANtricity OS controller software. The overall probability of these issues occurring is very low, but RAID 1 volumes have a higher probability of encountering the issues than other RAID levels or NetApp Dynamic Disk Pools. These issues do not affect traditional RAID volume groups that have no global hot spare drives because drive evacuation does not occur in this configuration. For information about fixes in these releases, view the readme notes for each revision release. Workaround No workaround available. Controller Firmware update is needed. HDD Firmware update is not in relation to the descdribed issue here, but it is in general recommended to install the latest offered HDD firmware that is recommended by BOSCH and NetApp. The same applies for HDD firmware.   Solution: Update the NetApp Controller Firmware Upgrade E-Series SANtricity OS controller software to the latest applicable revision release for each platform as soon as possible. Please reach out to your local BOSCH technical team and BOSCH BT-SC/ETP-MKP team to ensure that the relevant NetApp Firmware has been approved to be usable for 24/7 video recording and replay use case. Even the global NetApp Firmware can be installed on BOSCH submodel ID 356 Where to get the Controller Firmware All customers with a full NetApp NOW support account and valid warranty on their system can download the controller firmware by using the own NetApp user account. The verison offered at the NetApp NOW platform should be certified and allowed by BOSCH for video use cases.  See also: https://community.boschsecurity.com/t5/Security-Video/TB-VS-date-2020-04-22-New-Firmware-11-50-3R1P3-is-available-for/ta-p/12778 In caase the download option is not offered to one of our customers, we kindly ask to make sure that the unit is registered on the company and that the NetApp NOW account belongs to the company that has registered the unit. In all other cases, please recout out to the BOSCH Support organisation or local Bosch Technical Support desk. A NetApp SANtricity firmware / controller firmware package for E2800 model can be downloaded from the NetApp NOW website.  Revisions can be found at https://mysupport.netapp.com/NOW/cgi-bin/software/ See also: https://mysupport.netapp.com/products/web/ECMLP2854621.html  Additional information is available at NetApp and accessible after user registration. First go to https://mysupport.netapp.com/ to register. Product Release Notes from NetApp:  https://mysupport.netapp.com/ecm/ecm_download_file/ECMLP2842060 NetApp Support Bulletin, please view the following URL:  https://kb.netapp.com/app/answers/answer_view/a_id/1086731 (As the URL can change any time by NetApp, search for the KB id 1086731) ----------------------------------------------------------------------------------------------------------------- Steps to update The E-Series SANtricity ® OS package includes data for simplex controller and duplex controller systems and the firmware file itself. NVSRAM File for for duplex. NVSRAM file for simplex and the controller firmware Download the latest SANtricity OS software files from the NetApp Support Site to your management client. From SANtricity System Manager, select Support > Upgrade Center . In the area labeled “SANtricity OS Software upgrade,” click NetApp Support . On the NetApp Support Site, click the Downloads tab, and then select Software . Locate E-Series/EF-Series SANtricity OS (Controller Firmware) . For the platform, select E2800 , and click Go! Select the version of SANtricity OS (Controller Firmware) you want to install, and click View & Download . Follow the online instructions to complete the file download. Attention: Risk of data loss or risk of damage to the storage array — Do not make changes to the storage array while the upgrade is occurring. Maintain power to the storage array.
    View full article
    100% helpful (1/1)
    ‎06-03-2020 11:33 AM
    Question BVMS Lite and BVMS Viewer are BVMS editions that you can download and activate free-of-charge. How can I set-up a basic (live and recorded video) BVMS system? Answer First, you need to download the software package, active the BVMS Lite license and install the software. This is described in this article: BVMS - Activating a license. Second, you need to prepare an iSCSI environment which is suitable for recording video. Any Windows Server based operating system will do. This is described in this article: BVMS - Configuring a Microsoft iSCSI target. Last, you need to add cameras to the system and start the recording. This is described in this youtube video: How to add a new camera using Configuration Client (BVMS). Now, have a look at the Operator Client quick guide and you're ready to go! Where can I get more information on advanced functionality? Once the software (configuration client or operator client) is running you can press F1 at any time to open the embedded software help! All of the advanced functionality BVMS offers is explained in the help files.
    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
    ‎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
    2 weeks ago
      Related Products: DIVAR IP 7000R2 and DIVAR IP 6000R2   CTN Description   DIP-6180-00N  DIVAR IP 6000 2U W/O HDD  DIP-6183-4HD  DIVAR IP 6000 2U 4X3TB  DIP-6183-8HD  DIVAR IP 6000 2U 8X3TB  DIP-6184-4HD  DIVAR IP 6000 2U 4X4TB  DIP-6184-8HD  DIVAR IP 6000 2U 8X4TB  DIP-61F0-00N  DIVAR IP 6000 3U W/O HDD  DIP-61F3-16HD  DIVAR IP 6000 3U 16X3TB  DIP-61F4-16HD  DIVAR IP 6000 3U 16X4TB  DIP-7180-00N  DIVAR IP 7000 2U W/O HDD (R2)  DIP-7183-4HD  DIVAR IP 7000 2U 4X3TB (R2)  DIP-7183-8HD  DIVAR IP 7000 2U 8X3TB (R2)  DIP-7184-4HD  DIVAR IP 7000 2U 8X3TB (R2)  DIP-7184-8HD  DIVAR IP 7000 2U 8X4TB (R2)  DIP-71F0-00N  DIVAR IP 7000 3U W/O HDD (R2)  DIP-71F3-16HD  DIVAR IP 7000 3U 16X3TB (R2)  DIP-6704-HD 4000GB HDD DIVAR IP 6000/7000      Overview: For recovery of DIVAR IP 6000 R2 or DIVAR IP 7000 R2 one should use only the DVD provided with the particular device. Do not use the DVD for recovery if you are not sure that it is the one delivered with the system. In case the DVD is lost or damaged request the respective ISO image from Bosch Technical Support.  Solution:  Request the ISO image from Bosch Technical Support:   Provide the Serial Number of the device Issue description: What is the reason for the recovery Why it is not possible to use the recovery DVD   Note: his document will guide you through the recovery steps of an DIP https://community.boschsecurity.com/t5/Security-Video/TSG-Rebuild-broken-OS-RAiD-on-DIVAR-IP-6000-DI...
    View full article
    100% helpful (2/2)
    ‎03-04-2020 03:40 PM
    Status February 25, 2017 BOSCH offers and confirms that since February 2017 the firmware version 3.180.05-1562 can be used with the LSI MegaRAID Controller. In case there are newer versions supported and recommended with BOSCH DIVAR IP this will be announced in cooperation with the Product Management. For DIVAR IP units (e.g. DIVAR IP 6000) BOSCH BT Security & Safety Systems offers an firmware update for the internal MegaRADI Controller. It could happen that in the Megaraid Software the user can see the following: potential non-optimal configuration due, PD commissioned as Emergency Spare error.   Here we provide the steps to update a DIVAR IP system: Using MegaRAID Storage Manager utility under OS   1) Open MSM, Right click on Supermicro MegaRAID controller to be updated and click Update Controller Firmware 2) Click Browse to search for new firmware   3) Select the new MegaRAID controller firmware 4) Click OK to continue   5) Check the “Confirm” box and click OK to continue   *** Wait for around 1~2 minutes to complete 6) Click OK once firmware update completed   7) Reboot the system and check firmware version in controller OPROM banner during boot. At the section Revision you can see version 3.180.05-1562   😎 Check firmware version using MSM in OS When selecting the "Supermicro SMC 2208 (Bus1, Dev 0) device you can see on the right the "Firmware Version" = 3.180.05-1562     The firmware *.rom filw is available via the following link - inside the ZIP file: https://downloadstore.boschsecurity.com/FILES/KnowledgeBase/MegaRAID_Ctrl_FW_update_DIVAR_IP_BOSCH.zip This Firmware Version is subject of change. Any new version must be announce by BOSCH PRM responsible for DIVAR IP via the BT-ST/ETP-MKP2 organisation and BOSCH support at BT-ASA here in the BOSCH Knowledge Base. 
    View full article
    100% helpful (2/2)
    ‎05-17-2019 04:46 PM
    Combined firmware package 6.60 – applicable to all platforms The Release Letter of the combined firmware package for all platforms 6.60.1321 provides information about the dependencies between firmware versions for a better understanding of the upgrade process of devices with older firmware. CCP4 and CPP6 devices: Due to an internal file system being introduced to CPP4 and CPP6 since firmware 6.10 and architectural changes thereof, a direct upgrade from firmware below version 6.10 to latest firmware is only possible via intermediate firmware 6.1x. CPP4 cameras with firmware versions below 6.10 need to upload this package twice. For example, when having firmware 5.92 on a CPP4 device, you need to load the CPP all common firmware file two times: >  First time this is loaded the device will be updated to the 6.11.0021 which is part of the common file. >  Second time you load the common firmware file, the update to 06.50.0128 will be performed. CPP6 cameras with firmware versions below 6.10 need to upload the separate firmware version 6.1x first to receive the latest firmware version. This means that intermediate firmware version 6.1x for CPP6 needs to be requested from your technical support. A support ticket to Level 3 team at MKP PRM group via the support ticket system is needed. In case we see a high demand for that a new combined firmware file might be created by PRM. Only after receiving and uploading firmware 6.1x, you can upload combined firmware package for all platforms 6.50.0620 or CPP6 specific firmware  6.50.0128.  CPP5 devices: This combined firmware cannot be applied to CPP5 products with firmware version older than 5.91. It is required to upgrade to intermediate firmware 5.91 first This means that intermediate firmware version 5.91 for CPP5 needs to be requested from your technical support. Only after receiving and uploading firmware 5.91, you can upload combined firmware package for all platforms e.g. 6.50.0620 or CPP5 specific firmware  6.30.0059. To find a combined firmware file in the downloadstore you can use the folowing URL syntax: https://downloadstore.boschsecurity.com/index.php?type=fw&filter=CPP or you use the CPP 6.50 combined file here: https://downloadstore.boschsecurity.com/FILES/KnowledgeBase/CPP_FW_6.50.0620.fw and Releaseletter of that combined firmware package: https://downloadstore.boschsecurity.com/FILES/KnowledgeBase/Bosch_Releaseletter_CPP_FW_6.50.0620.pdf Note: Upgrading from versions lower than 5.5x To upgrade to a newer firmware version using this combined firmware package, firmware versions before 5.5x require an intermediate update cycle using the respective platform firmware version mentioned above. Restrictions: This firmware and its included platform firmware builds are not applicable to MPEG-4 products. The final firmware version for VIP-X1600-XFM4 modules is FW 5.53. No newer firmware will be provided for these modules. Configuration Manager cannot upload this Combined Firmware file to VIP-X1600-XFM4 modules. Use the module’s web page instead for uploading; or use the separate firmware file. The final firmware version for CPP3 devices is FW 5.74. No newer firmware will be provided for these products. The Combined Firmware file does not load onto VG4 AUTODOME or AUTODOME Easy II via the browser when running a firmware version before 5.52.0017. The specific platform file should be used instead. (Note: In case any link might not work to the current DownloadStore, see attached a copy PDF of the Release Letter.) How to get and request a BOSCH Legacy Firmware: The procedure to request and get an legacy firmware that is no longer online in the web is as follows: Customers are kindly requested to reach out to the local BOSCH Support (L1 and L2 team). Bosch Level 2 will ask for the exact BOSCH Commercial Type Number (CTN). The local BOSCH team can check the Global End of service date. The project background (How many of these devices/cameras) need to be collected.  The relevant BOSCH Technical Support (e.g. Level 2) can explain and check if there is the chance to update the project and included management software in order to be able to use the latest BOSCH device firmware as the goal is to have a non-vulnerable product in productive environments. In case there is no newer firmware available (hardware was discontinued), a commercial hardware upsell can be recommended. In general all firmware that is not available on the product catalog, and for all firmware files that are ranked to have vulnerabilities, this need to be documented in a Technical Support case. In case legacy firmware is anyhow needed and requested by our customers, the Bosch Technical support will start an approval flow. The BOSCH Level 3 Technical Support will provide a form/document that must be signed by the installer/endcustomer. See an example PDF (empty) "Example_Aged_Software_Release_form.pdf" attached to this article. Such a form will be prepared by the BOSCH Level 3 Technical support team and provided to our customer/installer in order to confirm that legacy firmware is then used on the risk of the installer and customer (See text and legal note in the PDF). In the future BOSCH plan to introduce and setup a self-service portal for all customers to simplify this process. ___________________________________________________________________________ The above mentioned combined firmware 6.50 supports: CPP7.3 HD and UHD cameras update from FW 6.40 or newer to latest FW 6.50 CPP7 UHD cameras update from FW 6.30 or newer to latest FW 6.50 CPP6 UHD cameras update from FW 6.10 or newer to latest FW 6.50 CPP5 encoders update from FW 5.91 or newer to latest FW 6.30 CPP4 HD cameras update from FW < 6.10 to intermediate FW 6.11 update from FW 6.10 or newer to latest FW 6.50 CPP3 cameras and encoders update from FW 4.54.0026 or newer to latest FW 5.74 CPP-ENC VIP-X1600-XFM4 encoders: update from FW 4.2x or newer to latest FW 5.53 VJT XF and VJD-3000 update to latest FW 5.97 The combined firmware package includes the following build versions: CPP7.3 FW 6.50.0128 CPP7 H.264 6.50.0128 CPP6 H.264 6.50.0128 CPP5 H.264 6.30.0059 CPP4 H.264 6.50.0128 CPP4 H.264 6.11.0021 CPP3 H.264 5.74.0010 CPP-ENC H.264 5.97.0005 for VJT XF family, VJD-3000 and VJC-7000 CPP-ENC H.264 5.53.0004 for VIP X1600 XFM4 For detailed description please refer to the separate release letters. Customers can upload such combined firmware packages by using multi-select in the Configuration tool "BOSCH Configuration Manager" (currently available in version 06.01.0157 at the BOSCH DownloadStore or Product catalog > Video Software > Video Management Systems > Configuration Manager) When using the multi-select option in Configuration Manager, please make sure this combined firmware package for all platforms can be uploaded to all the devices selected and there are no additional requirements or intermediate steps needed for any of the devices in question. This article has status of 31st of October 2018 and changes in this procedure might be introduced. When changes are done, then this article will be updated. Therefore check this article from time to time.
    View full article
    100% helpful (2/2)
    ‎06-07-2018 06:30 PM
    The table below lists the firmware versions which are used in the BVMS 7.5 system test.
    View full article
    ‎05-29-2020 05:28 PM
    Dear community, The Project Assistant has been around for almost 2 years now and we are wondering how it has affected your way of working? The initial idea of the Project Assistant is nicely summarized in this video: Feel free to share you experiences and best practices with us - here in the community using the comment section below 🙂 Stay tuned and healthy Your Bosch Security App Team
    View full article
    100% helpful (1/1)
    ‎04-07-2020 01:28 PM
    With the VRM eXport Wizard 2.0 encrypted and unencrypted VRM recordings can be exported (VRM block export) from any video surveillance system based on Bosch Video Recording Manager (VRM) and exported recordings can be converted to mp4-files. Therefore, the VRM eXport Wizard 2.0 offers the following two options, compare also Figure 1: Export VRM recordings of cameras Convert already exported data to mp4-file Figure 1   Export VRM recordings To export recordings, no matter if encrypted or un-encrypted recordings, from a video surveillance system based on VRM, the user first needs to select and connect to the Bosch VRM system that contains the source video data the user wants to export. To optimize the data traffic, the user can further select the number of maximum sources exported in parallel and set the maximum bit rate used per source, see Figure 2. Figure 2 Note: To avoid any performance loss of the VRM system it is not recommended to run the VRM eXport Wizard on the same hardware as the VRM itself or any other system critical server (e. g. VRM server, BVMS MS, etc.). In the next step (Figure 3) the user selects the cameras and the time period that shall be included in the export. Additionally, the user can change the name of the export file and add a comment. Figure 3   Once the user is done with the camera selection, the export destination has to be selected in the "Select Type and Destination" window, see Figure 4. Here the user can choose between CIFS export, iSCSI export and export to a file system. Note: The tape export some users might know from previous older versions is no longer supported. Figure 4 Once the destination is selected, the export process can be started. The VRM export Wizard informs about the current status of the export process and tells the user when the export is completed, compare Figure 5. The exported blocks can now be found on the before choosen destination platform. Please note for mass exports, if the overall export time is longer than the respective retention time for a camera not all video data might be exported before being overwritten / deleted. As already mentioned above, this export procedure works for unencrypted as well as encrypted VRM recordings (encrypted and unencrypted VRM blocks). Unfortunately, for playback of the exported material we have to differentiate between encrypted and unencrypted exported recordings. For playback of unencrypted video data exported by the VRM eXport Wizard BVMS is the best choice, as the user can then also take advantage of the meta data like IVA information. For now, this is not possible for encrypted recordings, because the re-import of encrypted VRM block exports is not yet supported. Instead, the user has to take advantage of the new mp4 conversion functionality of the VRM eXport Wizard. Of course, the conversion also works for unencrypted recordings. Both cases are explained in the following. Convert already exported data to mp4 To convert VRM block exports to mp4 format the user has to choose the option "Convert already exported data to mp4-file", see Figure 6. Limitations: Max file size per MP4 file is 500 MiB Figure 6 How to convert unencrypted recordings to mp4? In the "Select exported data for conversion" screen the user can choose the source, in this case unencrypted recording blocks, and the output directory, where the mp4 files shall be saved to, Figure 7. To choose the exported VRM blocks, which shall be converted to mp4 format, the user has to  navigate to the corresponding camera folder and has to select the related BIN.file. This is illustrated in Figure 8. For unencrypted VRM blocks no further information is needed and conversion can be started by pressing the next button in the "Select exported data for conversion" screen. Figure 7 Figure 8 Similar to the export procedure the VRM eXport Wizard also shows the status of the conversion process. Once it is successfully finished, the screen will look like in Figure 9. Figure 9 How to convert encrypted recordings to mp4? The conversion of encrypted VRM blocks starts in the same way as the "unencrypted recordings" case above. However, in the "Select exported data for conversion" screen the user needs to add a valid redundancy key for encryption. Therefore, the checkbox "Source is encrypted" needs to be checked and the redundancy key (a .pfx file) needs to be selected and the password needs to be entered, as demonstrated in Figure 10 and Figure 11. Figure 10 Figure 11
    View full article
    ‎08-17-2018 07:36 AM
    Step by step instructions on how to successfully import video
    View full article
    ‎03-27-2020 11:52 AM
    Functionality for security operators
    View full article
    ‎01-22-2020 05:27 PM
    Dear all, please find the release information about Configuration Manager 7.00.0111. Configuration Manager 7.0 introduces a complete rework of the user interface, following the latest Bosch application style guide, with many improvements in readability, compactness and improved navigation for a better user experience. New Features User Interface Look-and-feel according to latest Bosch style guide, improvements on readability of form elements. Screen space optimization due to higher density of presented information, optionally vertical navigation bar. Scaling invariant user controls enable smooth support for high DPI screens. Avoiding horizontal scrolling by adaptive column reduction. New easy to use filters, supporting “Google”-like free text matching on various identifiers as well as down into device properties. VCA pages with new sub-navigation, larger video presentation for easier task setup, improved calibration and Camera Trainer pages, in-field editing, object filter page, and providing tooltips and direct links to help pages. Security Strong password demand during first start of the program. Working without password prompts extra warning pop-up and requires specific user action. Certificate creation now allows including usage. This enables fully automated batch certificate creation for larger sets of devices. The creation dialog shows the progress of key creation. Cameras Support for new AUTODOME IP 7000i and MIC IP 7100i with firmware 7.52, introducing changes and enhancements on picture settings and pre-position settings pages. Setting an alternate home position is now possible for applicable moving cameras. Support for new DINION and FLEXIDOME IP 3000i series with firmware 7.51. An RCP+ message and/or a SNMP trap from cameras, if time sync fails, can be configured. Storages Assignment option for CHAP password on DSA E series storages added. Password must be from 12 to 16 characters long. Decoders Playback permission is configurable for IP Matrix since decoder firmware 9.60. Changes Support for Bosch Video Client (BVC) and BVIP Lite Suite is excluded. The configuration backup of the Configuration Repository is now referring to the MAC address of a device instead of the IP address. Network scan is now also possible for IPv6 networks. Context menu and some configuration pages cleaned-up for decoders. Improved feedback on firmware upload status and errors. The character ‘+’ is not allowed anymore for camera passwords since it is also blocked in cameras from firmware 7.50 onwards. The image posting tab is moved from ‘Network’ to ‘Recording’, and a link to configure accounts was added. Secure crypto-coprocessor version is now displayed on camera’s compatibility tab. Note Configuration Manager 7.0 has excluded support for Bosch Video Client and BVIP Lite Suite. Installing it over an existing installation of a previous version will encrypt the database with strong encryption and thus render it unusable for the older software. Please refer to the release notes for details: https://downloadstore.boschsecurity.com/FILES/Bosch_Releaseletter_ConfigManager_7.00.0111.pdf The software package will be loaded into ST4 the next days and uploaded to the product catalogue with the next sync. It has already been uploaded to DownloadStore as well.
    View full article
    ‎11-05-2019 03:19 PM
    This article will guide you how to remedy invalid expansion licences on your Bosch Divar IP 5000 all in one.      Error indication Dispite that the registration of your additinal purchased licencens has been completed successfully. The licecens may become invalid  after a  following reboot. This behaivor is caused by switching the MAC address of your teaming interface. Solution In order to prevent such behavior or even to revoke your licences as they are already invalid, please perform the follwing steps:  Step 1 Download the attachment MacAddress.zip (2 KB) and provide it locally to your DIP all in one    Step 2 Unzip the archiv, it should extract two files (setMacAddress.cmd  / setMacAddress.vbs) please do not alter or move the files!   Step 3 Open the command promt (CMD) as adimistrator, e.g.  right-click on the windows button and click on Command Promt (Admin) Step 4 Run the "setMacAddress.cmd",  for this purpose navigate to the location where you have stored the unzipped files  and call   the "setMacAddress.cmd"  file      YOURPATH\setMacAddress.cmd  and hit enter    Step 5 Press the spacebar to continue, after the cursor is blinking again you can close the CMD   Step 6 Reboot your device, in order to complete the task.              
    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
    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