Security: Video

VSC, Video Security App, Bosch Video Security App 3.0.1.75 fixes internet connection issue.

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.

Microsoft Event Logging, when an error occurs, the system administrator or Integrator must determine what caused the error. The operator can then use the event log to help determine what conditions caused the error and identify the context in which it occurred. Starting Event Viewer The procedure for starting Event Viewer depends on your starting point, e.g. windows key + R type in ”eventvwr.msc” hit enter. Selecting Computers With the decent administrative access, you can select any computer in your network to view that Microsoft system event logs. To select computers in Event Viewer: In the top of the console tree, right-click Event Viewer (local), and then click Connect to another computer. Enter FQDN/NetBIOS name or browser to the regarding machine Adjusting Event Viewer Settings In the console tree, right-click the appropriate log file, and then click Properties. Click the General tab. Saving Event Logs In the console tree, right-click the appropriate log file, and then click Save Log File As. Navigate to the subfolder in which you want to save the file, type a name for the file, click the file type, and then click Save. Clearing Event Logs In the console tree, right-click the appropriate log file, and then click clear all Events. You are prompted for whether you want to save the log to a file before clearing it. Click “Yes” to save a log and clear all events. If you click No, the log is not saved, but all events are cleared from the selected Event log. If you click Cancel, the request to clear the log is canceled. Viewing Event Details In the console tree, right-click the appropriate log file. A list of events in the log file is displayed in the details pane of Event Viewer. Click a specific event in the details pane to display the Event Properties dialog box and details about the event. Filtering Events In the console tree, right-click the appropriate log file, and then click Properties. Click the Filter tab. Type the appropriate information that you would like to filter. Finding Events In the console tree, right-click the appropriate log file. On the View menu, click Find. Type the appropriate information that you would like to find in the dialog box, and then click Find Next.   Event Types: Event type Description Error An event that indicates a significant problem such as loss of data or loss of functionality. For example, if a service fails to load during startup, an Error event is logged. Warning An event that is not necessarily significant, but may indicate a possible future problem. For example, when disk space is low, a Warning event is logged. If an application can recover from an event without loss of functionality or data, it can generally classify the event as a Warning event. Information An event that describes the successful operation of an application, driver, or service. For example, when a network driver loads successfully, it may be appropriate to log an Information event. Note that it is generally inappropriate for a desktop application to log an event each time it starts. Success Audit An event that records an audited security access attempt that is successful. For example, a user's successful attempt to log on to the system is logged as a Success Audit event. Failure Audit An event that records an audited security access attempt that fails. For example, if a user tries to access a network drive and fails, the attempt is logged as a Failure Audit event.   The events themselves are what we’re trying to see, of course, and their usefulness can range from really specific and obvious things that you can fix easily to the totally undefined messages that don’t make any sense and you can’t find any information on your preferred search engine. example: The regular fields on the display contain: Log Name – while in older versions of Windows everything got dumped into the Application or System log, in the more modern editions there are dozens or hundreds of different logs to choose from. Each Windows component will most likely have its own log. Source – this is the name of the software that generates the log event. The name usually doesn’t directly match with a filename, of course, but it is a representation of which component did it. Event ID – the all-important Event ID can actually be a little confusing. If you were to Google for “event ID 122” that you see in the next screenshot, you wouldn’t end up with very useful information unless you also include the Source, or application name. This is because every application can define their own unique Event IDs. Level – This tells you how severe the event is – Information just tells you that something has changed or a component has started, or something has completed. Warning tells you that something might be going wrong, but it isn’t all that important yet. Error tells you that something happened that shouldn’t have happened, but isn’t always the end of the world. Critical, on the other hand, means something is broken somewhere, and the component that triggered this event has probably crashed. User – this field tells you whether it was a system component or your user account that was running the process that caused the error. This can be helpful when looking through things. OpCode – this field theoretically tells you what activity the application or component was doing when the event was triggered. In practice, however, it will almost always say “Info” and is pretty useless. Computer – on your home desktop, this will usually just be your PC’s name, but in the IT world, you can actually forward events from one computer or server to another computer. You can also connect Event Viewer to another PC or server. Task Category – this field is not always used, but it ends up basically being an informational field that tells you a bit more information about the event. Keywords – this field is not usually used, and generally contains useless information. As a rule of thumb (common way of doing), you should try searching by the general description, or the Event ID and the source, or a combination of those values. Just remember that the Event ID is unique for each application. So there is a lot of overlap and you can’t just search for “Event ID 122” only. This is because users might find the list is too large and too general, your specific search aspect might not fit your issue.

Question  What's new in version 1.2? Answer Next to general stability improvements and bug fixes, version 1.2 of the Project Assistant introduces the following new features: Support of Flexidome IP 8000i Wi-Fi camera with regard to wireless commissioning .txt file import now supports tags to be somewhere in the column header, e.g. “IP address [ip]”, where for version 1.1 only the [ip] tag was allowed in the column header exclusively Software sealing support for cameras with firmware 6.60+ Extended report information Related News Project Assistant project file import functionality in Configuration Manager 6.10 Bosch portable camera installation tool is available and can be used in combination with the Project Assistant (check out the corresponding how-to video in this community)   PS: For detailed information, please refer to the release letter attached.

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.

In all VRM installation packages the required .NET framework package is included in the VRM installation routine. As Microsoft Operating Systems are expected to get and have the latest security updates applied before installing any new software component like VRM (Video Recording Manger) or VSG (Video Streaming Gateway), the installer will successfully finish the installation routine. The same is valid for BOSCH DIVAR IP product range:  The DIVAR IP Appliance installer contains Microsoft update packages available from Microsoft at the time BOSCH creates the Appliance installer. But all Microsoft Updates release after the Appliance installer release date are not included in the BOSCH package. It is therefore recommended to check for Microsoft updates whenever a Bosch DIVAR IP Appliance installer is installed. For VRM (Video Recording Manager) stand-alone Systems and Servers with VSG (Video Streaming Gateway) installed, it is also strongly recommended to check for Microsoft OS updates before the VRM Master Installer is installed/updated. Note: In case an error code 5100 is shown during the VRM Software installation, please ensure that all Microsoft updates for the used Operating Systems are installed and run the BOSCH Software installer after that once again. For more details Microsoft provides more informaiton here: https://blogs.msdn.microsoft.com/astebner/2008/10/13/net-framework-setup-verification-tool-users-guide/ For older BVMS and VRM installations please also refer to the following previous article: https://community.boschsecurity.com/t5/Security-Video/-/ta-p/416

Question  What's new or fixed in Project Assistant 1.2.2? Answer Next to general stability improvements and bug fixes, version 1.2.2 of the Project Assistant introduces the following new feature on all three platforms: Allow re-configuration of a camera, e.g. wirelessly adjust the field of view of a FLEXIDOME IP starlight 8000i , while local recording is running. One bug fix worth mentioning explicitly is that we addressed a connectivity issue, which was faced, when connecting wirelessly to multiple FLEXIDOME IP starlight 8000i cameras one after another. Related News We have published a new Excel template file that makes the import of existing information into the Project Assistant even easier. Feel free to check out the updated Knowledge Base article. Further information can be found in the release letter attached. Best regards, Your Project Assistant Team!

+++ Update: new Excel template file with detailed explanations of all parameters +++ Intro: The Project Assistant offers two ways of importing existing project data: Option 1) Importing a .bpassist file, which was exported from the app at some point and which contains all information and data ever created/entered inside the app for that specific project. Simply select the "Project Assistant" mode >> click "continue" >> and press "import". Option 2) Importing from a tab-separated text file. This option may be useful, if you have existing project data, e.g. in an Excel spreadsheet, which you want to transfer into the Project Assistant for further use. This article deals with option 2 and explains the steps potentially needed before you can refer to the steps explained in the following Youtube video ("Import from file"). Let's assume you already have existing project data prepared in an Excel spreadsheet and you want to transfer that data into a format that can be imported to the Project Assistant Go to the Bosch Security Systems DownloadStore and download the provided template file "example_project_import_report_template.txt" or the NEW Excel file " 2019_02_20_example_project_IMPORT_template.xlsx" , which also includes detailed instructions and explanations on each parameter. Import the .txt template file into Excel by opening the template file with Excel and following these steps:  Select "delimited" as well as "My data has headers." Select "Tab" in the Delimiters section and finish up the Excel import by pressing "Finish". INSTEAD, you can also use the NEW Excel file, where you can avoid the above described initial import step of the .txt file.   [Option A] According to the provided data columns, copy and paste your existing data from your initial spreadsheet file into the template file (you do not need to populate every column of the template) [Option B] This option works the other way around. Use the Project Assistant header tags, e.g. [ip], [mac], etc., which you can find in the template file and add these tags to the column headers in your initial Excel spreadsheet (cf. screenshot below). The Project Assistant is capable of searching the .txt import file for these tags and of filtering out the corresponding columns (no matter the order of the columns). Go to "Save As" in Excel and save the newly populated template file as a "Unicode Text (*.txt")" file   Transfer the file to where you can find it with the Project Assistant and start the app Create a new project Set a password for the project itself as well as default passwords for the cameras that you would like to assign That's it - Now it is time to refer to the Youtube video mentioned above Enjoy using the Project Assistant and feel free to share your feedback with us!  

The attached documents should help you to make the upgrade process as smooth as possible. The upgrade itself is not restricted to BVMS software only. The supported software and firmware versions can be found in the release notes of the related BVMS version. An attachment is added to this article for each BVMS version. Currently the upgrade guides for BVMS 8.0 and 9.0 are attached to this article.

 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.

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.          

Version 1.2.1 has been released for iOS only. It resolves an issue when trying to connect wirelessly to a FLEXIDOME IP 8000i camera. There was an issue where the operating system blocked the Wi-Fi access.

With the introduction of the Configuration Manager 6.10, we will make the transition from one tool to the other smoother by offering an import feature, which allows you to import all cameras from a .bpassist project file without having to re-enter the individual credentials of each device. The feature allows you to: import one or multiple encrypted .bpassist project files at once automatic integration of device credentials check the software seal information to make sure configuration of each device has not been tampered with integrate the project file grouping into your existing structure create a backup of your system configuration after a successful import   Example: Go to the "Tools" menu and select "Import Project Assistant File..."    Select one or more .bpassist files that you want to import    After entering the project file passwords, the Configuration Manager can decypt the files and you will then be prompted with an overview of the project file content Choose where in your existing structure you want to integrate the new devices ("Import to group" section) Verify project file content Select, whether you want to create a backup after import Select, whether you want to keep the project file groups after import After successful import, you can find all newly added devices in your target directory  

For larger projects, where many cameras need to be commissioned, the question might come up on how to tackle it in the most efficient way using the Project Assistant. In the end, a Project Assistant file can comprise up to 500 cameras. Especially if multiple contributors perform the commissioning step in parallel, you need an appropriate approach. For visualization reasons, let's use a simple example. Let's imagine we have a project that comprises 500 new cameras in total. 250 cameras for building A and another 250 cameras for building B. Here are two options: Creating multiple (sub-) projects and merge them in Configuation Manager If you cannot use Dropbox for synchronisation via the cloud, you can simply create 2 projects - one for building A and one for building B. Both projects can be prepared ahead of time, e.g. in the office, and exported in order to share them. Sharing the exported as well as encrypted project files can be done via E-mail, thumb drive, any of the major cloud storage services, etc.*. Now let's assume that there is one contributor working on building A and one working on building B. After each contributor has commissioned his or her 250 cameras each, they can themselves export the project files. To re-combine or merge both sub-projects, we have introduced a Project Assistant project file import feature in our Bosch Configuration Manager 6.10. This feature allows you to conveniently import multiple project files at once and to easily integrate them into your existing system structure. Please, check out the corresponding "How to import project files into Configuration Manager 6.10" article in this community. * Restrictions due to project file size might apply depending on the sharing medium. The synchronization functionality is only available for Dropbox. Using the Dropbox Synchronization feature This feature let's you plan and preprare a project ahead of time, e.g. in the office, which can then be shared via Dropbox with multiple other contributors as needed. That means everyone that was "invited" to work on this project has access to the same project file, where there is only one "master" version residing in the cloud that is accessed and synchronized via Dropbox. Consequently, you can avoid managing multiple versions of the same project file. Therefore, depending on the internet connectivity of all contributor's devices, you can see the real-time progress of the project, no matter if you are in building A, building B or even in the office. All updates to the project are immediately synced via Dropbox among all contributors. If you want to know how to setup it up, please check out the following videos:   Of course, the Project Assistant project file import feature in our Bosch Configuration Manager 6.10 is also available for futher configuration and system integration for this option, as well.

 In August 2018 (10-08-2018) the VRM version 03.71.0029 was released. The Video Recording Manager 03.71.0029 is fully supported with BVMS 8.0 and Product Management of BVMS and VRM recommend to use this VRM version instead of the former Release version of VRM 03.70.0056. Changes / Bug Fixes: One of the main bugfix reasons to use VRM 03.71.0029 is a fix in regards to correct display and replay of recorded clips in continous and alarm recording mode. This fix is listed on page 2 of hte attached Relase Letter. For Troubleshooting and support reasons it is essential to double-check a reported gap in recording and to analyze on Level 2 and Level 3 support side what circoumstanced could lead to a video gap. See in the following chapter what kind of data a trained BOSCH partner, Installer or Video expert should provide to the BOSCH Technical Support to advise on next steps. The data described here below can and should be collected before the software VRM is changed and updated to a latger version. Note: Video Recording Manager version 03.71.0029 is not the latest available version of VRM, but in combination with other 3rd party implemantation or usage of special BOSCH VMS software version (e.g. BVMS 8.0) this VRM version 03.71.0029 may be required. VRM logging to collect for in depth expert troubleshooting In certain situations and troubleshooting scenarios extended logfiles might be required. The BOSCH Level 1 and BOSCH Level 2 team will assist all users on how to collect these data and cooperate with the BOSCH Level 3 Support where needed. Backup the configuration of BVMS and VRM (BVMS elements and VRM config.xml file) Enable debug logging of the VRM Depending on the used Configuraiton Software the debug logging need to be enabled to get an extended logging informaiton. In case a gap in recording happened in the past it is anyhow helpful to enable the debug logging for a defined time for future incidents. To analyze the already occured video recording gap the available VRM logging must be collected. Depending on 32-Bit or 64-Bit version of the VRM software, the loggings are found in the "primary" or "secondary" sub-directory structure. Surch for     ...\Bosch\Video Recording Manager\VRM Server   folder at your VRM server to find a similar directory view like shown in the screenshot here below: Inside the directory "log" the standard logging data of the VRM are found and need to bre collected. In addition to the standard logfiles of the relevant day, the debug logging from a defined time period need to be provided in case debug logging was enabled prior to an incident. Here the "debug" logfiles are found: The debug loggins are saved in a special directory "debug". The Spanhistory logging does provide details of the storage usage. It describes which internal "storage block" was used. It describes the IP of the target, the LUN and the block used for a recording. The Spanhistory of the day where the recording was done and shows issues (e.g. the video reocriding gap), the related spanhistory logfiles is required. As seen in an earlier screenshot above the VRM configuration file is found in the directory:     ...\Bosch\Video Recording Manager\VRM Server\primaryAll versions of the config.xml need to be provided to the Technical Support.  

  Issue: The Bosch VRM Monitor page does not open correctly, but instead displays an Error. Any Replay client requesting video from the  Bosch Video Recording Manager service, only receives the Time-Line but the video is alway Black. Bosch VRM by default uses Ports 80 & 443. In most cases the problem is caused by another web server (e.g. IIS) that is installed on the same machine and is also making use of the default web ports 80 & 443. Related product: Bosch Video Recording Manager (VRM) Bosch Video Managment System (BVMS) Bosch Video Client (BVC) Bosch Video Security Client (VSC) Any Replay Client/ Managment System which accesses recorded video data via HTTP/HTTPS Solution: Disable any of the other web services or change the default Ports they are using.

rectrieve live video with Video Security Client Software for Windows version 2.2

Symptoms When scanning a QR or Data Matrix code on a label using the Project Assistant app, it can happen that you get an error message that the MAC address cannot be found (1) or that only part of the address is correctly extracted (2). Diagnosis  First of all, there are different types of labels: product labels (on the device) box labels (on the outside of the box/packaging) installer / UX labels (inside the box /packaging) Symptom (1) can only happen when scanning a product label because some QR or Data Matrix codes do not contain a MAC address, depending on the product, even though the MAC address is available in plain text right next to the code.   The box and installer label codes, however, always contain the MAC address information. Symptom (2) can happen when scanning certain installer labels due to legacy formatting. Solution We have further standardized the labels so that the symptoms mentioned above will be resolved. There will be a transition period, however. As an alternative for symptom 1, you will have smooth experience when preferably scanning the box label. If you encounter symptom 2, we ask you to enter the MAC address manually or use the December 2018 release of the Project Assistant (version 1.2) PS: For full transparancy on QR code / Data Matrix content and/or troubleshooting purposes, you can use conventional code scanning apps available in the resepective app stores.

The attached file explains how BVMS can be configured to connect to an LDAP (or Microsoft Active Directory) and use it as a base for user authentication.