Bosch Building Technologies

    cancel
    Showing results for 
    Search instead for 
    Did you mean: 

    Security: Video

    Sort by:
    Wednesday
    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
    100% helpful (3/3)
    Friday
    Potential for Data Inconsistency Issues on E-Series Storage Systems With the controller firmware 11.50.1 and newer version like NetApp controller firmware 11.50.2 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. At that time the Firmware for NetApp E2800 controller recommended was version NetApp Firmware 11.50R1. This is also 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 not approved 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 currently shipped by Netapp via BOSCH NetApp Firmware: 11.50.2P1 11.50.3 11.60 Please follow our BOSCH Knowledge Base and monitor for updates at this article for important news. Eventhough NetApp inbuild functions for BOSCH video optimized recording 24/7 and generic firmware is used at E2800 iSCSI storage systems, BOSCH is evaluating new firmware versions provided by NetApp on a regular bases. The BOSCH submodel ID 356 ensures that the NetApp system is optimized for 24/7 video recording. Products 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. status 06/2019: controller firmware version minimum 11.50R1 status 10/2019: controller firmware version to be used 11.50.2 Where to get the Controller Firmware All customers with a full NetApp NOW support account can download the controller firmware by using the own NetApp user account. All other customers are requested to contact the BOSCH Support organisation. The controller firmware package can be downloaded fro mthe NetApp website directly.  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
    a week ago
    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 Customers can upgrade the DIVAR firmware to v3.1.0, this will resolve the DIVAR Mobile Viewer v3.1.0 app connectivity problems. An improved DIVAR Mobile Viewer app is planned to be published on short notice. This will make the app compatible with both DIVAR hybrid/network firmware v3.0.0 and firmware v3.1.0
    View full article
    a week ago
    In many cases a minimum and maximum retention time needs to be defined in a video surveillance systems due to legal requirements. While the minimum retention time defines the time period for how long video recordings need to be stored, the maximum retention time defines after which period of time the recordings have to be deleted. Thus, the minimum retention time is going to influence the amount of storage needed. The higher the minimum retention time the more storage space is required. Hence, the storage space needs to be large enough to store the recordings for the minimum retention. For the maximum retention time this doesn’t have to be the case. Still users might be confused why recordings gaps might appear sort-of randomly, if the system does not have enough storage space to keep all recordings until the maximum retention time is reached. To understand what is going on we have to remember the principle of the VRM block assignment first. For each camera in the system the BOSCH Video Recording Manager (VRM) generates a list of recording blocks (LUNs) on which the camera can next record. Therefore, the VRM makes an estimation based on the data rate and the amount of data of each camera in the system (global optimization). Basically, the VRM predicts when which camera needs a new block and always lists the block which will be the oldest block at the time the camera needs to record on the next block. One could think of it as a “next oldest block” estimation done by the VRM. But the prediction of the VRM might differ from the reality (mainly because of variance in recording bitrate) and this can cause recording gaps if the storage space is not large enough to support the maximum retention time. Let’s have a closer look on the following two cases: Sufficient storage space for maximum retention time Insufficient storage space for maximum retention time Sufficient storage space for maximum retention time In case of sufficient storage space to fulfill the maximum retention time for every camera in the system no random recording gaps will appear, because the VRM will always assign a block containing recordings, which are older than the maximum retention time. Thus, for each camera the recording blocks will be kept until the maximum retention time is reached as illustrated in Figure 1. Figure 1: Enough storage space to cover the maximum retention time for each camera of the system Insufficient storage space for maximum retention time In case the system is designed such that the storage space is not large enough to store all recordings from all cameras until the maximum retention time is reached, the VRM will of course still do its estimation and predict the oldest recording block when a camera will ask for a new block. Assuming an ideal setup (with ideal network connection where each camera has the same data rate and all cameras record the same amount of video data simultaneously), the oldest block would always be assigned by the VRM. Hence, no recordings gaps should appear for recordings older than the minimum retention time, compare Figure 2. This is was most customers falsely assume or expect. Figure 2: Customer expectation of the system behaviour in case of insufficient storage space to cover the maximum retention time for each camera of the system However, in reality the stated assumptions do not apply. Network connection, data rate, amount of recorded video data, etc. varies. Thus, the “next oldest block” estimation of the VRM can differ from reality. Since each camera already got its block list from the VRM and records according to this block list, it can happen that not the truly oldest block is used and recording gaps appear as shown in Figure 3. Figure 3: System behaviour in case of insufficient storage space to cover the maximum retention time for each camera of the system How to avoid or minimize this effect To avoid this effect of random recording gaps simply add enough storage to your system. To get the best out of your system in terms of storage usage, the optimum would be to set the maximum retention time to storage limit, see Figure 4, but that is almost impossible to realize in practice. Figure 4: In principle a maximum retention time set to the storage limit would avoid random recording gaps Option 1 to minimize the effect in practice is to estimate the maximum retention time so that it will not exceed the storage limit of the system as illustrated in Figure 5. Figure 5: Maximum retention very close to the storage limit will minimize the random recording gaps Another less recommended option is to set a smaller time difference between the minimum and maximum retention time. But especially when the minimum retention time is shifted closer to the maximum retention time that introduces the risk that the VRM cannot free up storage space in case the minimum retention time is reached, which might result in a recording stop. Thus, we recommend to go for the first option. One last hint: Changing the retention time on a running system is not going to influence the retention time of already recorded blocks. but will of cousre only be applied to new recorded video footage. Hence, changing the retention time is no option for an immediate change of required storage.  
    View full article
    a week 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. 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: 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
    2 weeks ago
    Level confidentiality: external Related Products: Video SDK Overview: Analyzing issues with Video SDK based application is a challenging task. One needs to determine if the issue is based on wrong implementation of the Video SDK functionality, wrong programming practices, functionality and runtime behavior of the system with SDK functionality or Video SDK issues. In order to start troubleshoot Video SDK application support needs the following initial information and logging. Please prove the following information to support. 1.VideoSDK version 2.VideoSDK issue description                 What is the expected behavior?                 What is the issue? 3.Environment                   Which shared resources are accessed by SDK actions? (Dome cameras, decoders, etc.)                  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, ...)  Please provide source code and/or Log files The optimal approach is to provide both source code and logging for the problematic Video SDK application. 1.Try to reproduce the issue with one of the  Video SDK samples (Advanced C# Sample, Complete C# Sample, Simple C# Sample) and provide the result from the test. 2.Source Code                     Provide a little sample application that illustrates the Video SDK issue and list the reproduction steps. 3.Logfiles                    Enable VideoSDK backdoor logging, reproduce the issue (note the date and time) and provide the Video SDK logs. How to collect Video SDK log files   
    View full article
    3 weeks ago
    Do you want to know more about designing a BVMS system?
    View full article
    ‎12-19-2019 08:33 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
    ‎12-16-2019 09:00 AM
     BVMS customers can download camera updates free of charge, in order to integrate approved, third-party cameras. BVMS scans for third-party cameras, automatically configuring motion and other key events; it also enables installers to configure the most important settings for third-party cameras from a single user interface, without the hassle of having to access the websites of other camera manufacturers. The attached files include a list of compatible cameras and the ONVIF mapping files for each specific BVMS version.
    View full article
    100% helpful (1/1)
    ‎12-12-2019 01:54 PM
    How to configure a generic Microsoft Windows Server (2012 R2 or 2016) based server
    View full article
    ‎12-03-2019 01:29 PM
    Keeping an eye on system messages and to collect logging data at a central site just got a whole lot easier General information: Syslog feature is implemented in all IP BOSCH Products for many years. Since latest firmware versions e.g. Firmware version  6.xx and even more enhanced in firmware 7.1x and later a GUI on the WEB-page of the IP cameras was added. The BOSCH IP cameras as network devices can continuously send system messages via Syslog to a Syslog server software. This funciton must be activated and configured before. One aspect is to setup a Syslog server that can receive such information and Inside the IP cameras the IP of such a Syslog server can be configured in order to tell the IP camera to whic hSyslog server the messages should be send to. Enabling this funciton will allow a continous monitoring information even troughout a complete IP camera power cycle (reboot) as the camera starts connecting to the syslog server IP as soon it is getting back online. Network administrators usually monitor these messages and should also be able to offer and inform about Syslog server IPs to use.  Tools as Syslog server: There are many different monitoring tools available and common in the market. Configuration and technical analysis functions of those are in responsibility of those software vendors. Examples of some easy tools to start working with can be e.g.: PRTG NETWORK MONITOR from PAESSLER Kiwi Syslog Server EventLog Analyzer from ManageEngine and many more. When to make use of SYSLOG Especially for incidents that happen unpredictable and do not necessarily trigger an alert message can be analyzed with syslog even throughout reboots of equipment (switch reboot / IP camer reboot etc.) as the syslog reconnects to the destination server. As well in cases were many systems / devices are involved this can be very helpful as the different loginformation can be compared by having the same time bases (Syslog server time when messages arrive).  By using the BOSCH Configuration Manager (stand-alone configuration software) or Bosch Configuration Client software (part of BVMS) can help to quickly setup the syslog function for many cameras in just a few mouseclicks.  💡 Via the device webpage or above mentioned configuration tools it is easy to configure loggings that are also sent out via syslog. There are different levels of logging information that can be sent out:  Event-log data alarm-data debug logging (on advice of a BOSCH expert) In addition there is a chance to download recent history of such data (if enabled before) via the configuration section at the device webpages. Details are described in the product manual. For continous long-term monitoring the syslog function is best choice. Please feel free to get contact with your Level 1 support contact and if needed 2nd Levle support agent to get commands for section (3) debug logging syslog printouts if needed.   
    View full article
    100% helpful (1/1)
    ‎11-28-2019 12:51 PM
    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. From BVMS 10.0 onwards a description on how to migrate systems has been included as well.
    View full article
    ‎11-19-2019 01:34 PM
    Collect Video SDK Logs for VSDK based applications:
    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
    ‎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
    ‎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
    100% helpful (1/1)
    ‎11-05-2019 11:47 AM
    Introduction: Bosch has been providing 2 types of VRM packages: a 32bit and a 64bit version. Since VRM 3.82 we are only offering the 64bit version. As all of our released DIVAP IP units started off as 32bit VRM which includes a Transcoder service. Problem If you do not use the Start.exe included in the VRM Master Installer, you will not be offered the oppertunity to also upgarde the Transcoder. Just running the Setup_VRM_Service_<version>.exe found in the <Install\Bosch> folder, will cause the Transcoder service to stop functioning! This includes if the upgarde is done via BVMS installer. Since BVMS 10.0, VRM 3.82 "64bit" was implemented. Due to the fact that BVMS does not manage the transcoder, it was not installed. Also see Firewall settings: HowTo Configure Windows Firewall Rules, includes PS script to adjust the VRM 64bit and Transcoder rules. Solution Download the appropriate VRM version from our Downloadstore Run the Start.exe Deselect all components and choose only the Transcoder Service   Click on "Install" To confirm that the Transcoder is fully functional, open your browser and navigate to the VRM Monitor: https://<VRM_IP_Address>/ Log in with you Credentials    
    View full article
    100% helpful (3/3)
    ‎11-04-2019 10:06 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
    ‎10-30-2019 08:07 AM
    Symptoms During the introduction of BVMS 10.0 the BVMS Plus unmanaged site expansion licenses were not introduced, even though this functionality was announced to be available. Solution The LIF file attached to this article (in the zip archive) can be imported in BVMS Plus 10.0 installations using the license manager (the license manager can be found in the "Tools" menu of the BVMS Configuration Client). Once imported, the purchased licenses (MBV-XSITEPLU-100) can be activated.
    View full article
    100% helpful (1/1)
    ‎10-28-2019 08:43 PM
    BVMS Installer - Windows Pending Restart Message Issue:  The pop-up dialog window message: "Setup has detected a pending restart.  Please reboot the system and rerun the installation"  appears when attempting to run the valid BVMS windows installer package. BVMS Installer Pending Restart Message   Cause:  This is a known Windows specific problem when another (non-BVMS) installer does not properly manage its creation and deletion of the “PendingFileRenameOperations” registry key. The most common user created way for this key value to be left resident in the system is when an installation prompts for a restart, yet the system is not expeditiously restarted.     Resolution:  A. Restart the affected workstation B. If the issue still persists, delete the orphaned "PendingFileRenameOperations" registry key value Open a registry editor, such as Regedit.exe or Regedt32.exe.   Navigate to "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\" In the right navigation pane, right-click the "PendingFileRenameOperations" key value and select delete Close Registry Editor. Run the software Installer again as Administrator   Note:  This message is not a Bosch product failure message. This is a problem within windows and it's registry clean-up handling.  This is a Windows work around. 
    View full article
    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