About Central_Support

This article describes how to move one or multiple cameras from one company (account) to another one in Bosch Remote Portal.    Background:   In Bosch Configuration Manager there is a feature in "Connectivity" tab to re-register a camera to another account in Remote Portal. However it was discovered that the implemented procedure is not safe in presence of errors (such as transient network issues), and might end up in the camera being permanently disconnected: the installer would need to drive on-site to register the camera once again. Therefore please use the re-register feature in Configuration Manager only if you want to re-register the camera to the same account (e.g. to change the camera name in Remote Portal).  In Bosch Remote Portal there is now the feature implemented to change the cameras' company (account) without these effects.   Note: There might be some remaining manual work after the moving of cameras in the first step of implementation, however this can be done from remote, no travel on-site is needed for this clean-up.   Prerequisites:   To move the camera(s) to another company requires an Administrator user role in Remote Portal. The Administator needs to be a user in both companies, the source and the target company. The camera(s) need(s) to be online in the source company! There must not be any activity ongoing for this camera(s) (e.g. no firmware update, no company change ongoing) before the camera(s) can be moved. The Video Relay might change when moving the camera(s) to another company; therefore a different domain or IP address might need to be unblocked in the customer's firewall. Used domains see Troubleshooting Camera Connectivity & Bosch Remote Portal > Chapter 2    Known limitations:   Offline cameras cannot be moved. The cameras need to be online in the source company to become moved to another company! No groups can be moved to another company, but only cameras. Best practice: Only cameras of one group should be moved to the target company at one time After the change has been completed, the cameras should be moved from the root system hierarchy (highest level) to the related group in the target company before moving cameras of the next group All services activated for the camera and licenses assigned to the camera get deactivated and unassigned during the change! Best practice: Note down the license numbers assigned to the cameras to be moved in the source company. Note down the services which are activated for the cameras to be moved in the source company. Note down the users which are added to the cameras to be moved in the source company. Connectivity to linked applications such as Cloud VMS get lost for the cameras during and after the change. Note: There might be some remaining manual work after the moving of cameras in th first step of implementation, however this can be done from remote, no travel on-site is needed for this clean-up.   Step-by-step guide   In Bosch Remote Portal logon as Administrator In Systems tab select the list view Select the camera(s) to be moved to another company   Click the "Change Company" icon   A dialog shows the number of cameras where the company can be changed Select the target company Click the Move button and wait until the change has been completed (depending on the amount of cameras this may take several minutes)   In the target company, move the cameras to the related group   Licenses and services in the source company, copy the license numbers wich are now un-assigned after the change and delete the licenses in the source company in the target company add the license numbers in the Service Licenses tab in the target company activate the services which were activated before the change in the source company  in the target company add the users (customers) to the Remote Connect service like in the source company. Cleanup in linked applications (e.g. Alarm Management) Add the moved camera(s) to Alarm Management once again Add the moved cameras to the related service(s) in Alarm Management and delete the cameras from the source company from the service(s) accordingly Delete the cameras from the source company in Alarm Management's Devices tab Note: the moved cameras are now treated as new devices in Alarm Management. ... View more

Question   Can I use hash tag # as special character in BVMS or camera’s password?   Answer   Hash Tag "#" is one of the few special characters, which is accepted by the camera, but it cannot be accepted on BVMS side (in order to connect to the camera) — due to the limitations of communication specifics some BVMS components are using. And as a result, communication might not work properly and "No connection" warning message in Operator Client image pane and black screen might occur:   ⚠️ In BVMS Configuration Client, there's a very clear indication giving a warning, that this character should not be used: But it still allows saving it. Why? If you'd be connecting cameras which had already password configured with this character (like "#") you can still add it to the system and change the password afterwards (as also clearly indicated in the prompt message). If it wouldn't be possible to save it, it wouldn't be possible to add such camera to BVMS at all.   You need to differentiate the two different types of passwords used in BVMS: Camera password used to connect the camera with BVMS (where "#" is not allowed on BVMS side) BVMS user passwords used to log in to the Configuration Client or Operator Client — here there are no such additional limitations, so "#" is allowed and different rules apply. ... View more

Question   What to do if BVMS Operator Client cameo is white and the camera can’t be displayed (device failed)?   Answer   This may be caused by the NVIDIA graphic card driver that might not be compatible. GPU decoding is supported on specific NVIDIA GPU’s: − In general, the following NVIDIA Series: Quattro, RTX and T series are supported − Specific NVIDIA Graphic card drivers need to be used to avoid issues. Therefore, depending on the BVMS version you have, please check the latest BVMS release notes.   GPU or CPU decoding? Which cameras benefit from which method in the Operator Client?   Below are the download links for compatible drivers for NVIDIA: These 2 are compatible for BVMS 11.1.1: 470 version: https://www.nvidia.com/download/driverResults.aspx/185532/en-us/ 510 version: https://www.nvidia.com/download/driverResults.aspx/186766/en-us/ and this is the Intel graphic compatible for BVMS 11.1.1: Intel® Graphics - Windows® 10 DCH Drivers HD Graphics 530/ UHD Graphics 630: https://downloadcenter.intel.com/download/30100/Intel-Graphics-Windows-10-DCH-Drivers Information found in BVMS Release Letter (page 10)   This is compatible for BVMS 12.0.1: 525 version: https://www.nvidia.com/Download/driverResults.aspx/199657/en-us/ and this is the Intel graphic compatible for BVMS 12.0.1: Intel® Graphics - Windows® DCH Drivers HD Graphics 530/ UHD Graphics 630: https://www.intel.com/content/www/us/en/download/19344/732078/intel-graphics-windows-dch-drivers.html Information found in BVMS Release Letter (page 12)  Along with installing the drives, if the issue persists, try also to disable the integrated GPU from BIOS. ... View more

Question   Why is the BVMS SMA validity displayed as expired in License Manager, even if SMA is valid in Remote Portal? For example, according to the Remote Portal is valid until 22.12.2025   While on the local software, the License Manager it is showing to be expired on 22.12.2023.   Answer   This behavior occurs when you have requested the SMA extension and you didn't upload the Activation file in the BVMS Configuration Client. In the first instance, when ordering the SMA extension, the Order desk provides you with a MBV-MBase license that must be activated in Remote Portal. In order to see the new expiration date in the BVMS Configuration Client and get a notification in Operator Client when the SMA is about to expire, please upload the Activation file downloaded from Remote Portal in the License Manager from Configuration Client (see here the steps).  ... View more

Possible causes and solution(s)   Symptoms   When integrating Intelligent Insights with a self-signed certificate, the BVMS operator client always shows an error message when opening a widget in the BVMS operator client image pane.   Solution   In order to solve this issue, install the self-signed certificate in the trusted root certificate store of the local machine. Intelligent Insights Certificate handling 1.0.2 (azureedge.net)   If you need to create a new certificate, follow the below steps: In the certificate dialog of IGI click on create new certificate. pay attention to the common name The common name (CN) is the computer or server name associated with your TLS/SSL certificate. For example:  MyComputer.  For instance, https://example.com the common name should be example.com. In this example screenshot it would be XXX.30.11.101 pay attention to the validity time   Save the certificate   Install the certificate on the Operator Client PC in the Trusted Root Certification Authorities section:    Restart you Operator Client and your widget should work   Nice to know: Are there any restrictions on using Intelligent Insights widgets in BVMS Op Client on a DIP AIO? How to add Intelligent Insights widgets to BVMS?  Intelligent Insights Certificate handling 1.0.2 ... View more