How to plan and prepare for your BVMS System Upgrade from an Older BVMS Version to the Latest available?

Upgrading Bosch Video Management System (BVMS) from a legacy version to the latest version released can be a smooth and reliable process if a proper preparation and planning are done in advance.

This article outlines the most critical steps to follow, based on the official BVMS Upgrade Guide, to help ensure a successful upgrade with minimal disruption.

Important

Always refer to the official BVMS Upgrade and Migration Guide for a complete overview and detailed guidance.

Preparation Before the Upgrade

1. Validate Software Maintenance Agreement (SMA)

Ensure that your SMA is valid and allows for upgrading to the desired BVMS version.

If your SMA is fully current, then you can upgrade to the latest version.
If your SMA has expired, you can upgrade to any version published before your SMA expired. However, you will have no technical support, so the Upgrade is only advised with warnings to lack of support. To be clear, that means for Software versions going into general availability before the end of your SMA, then you can update to this version. But to reiterate, be aware of the lack of support if you will encounter problems.

2. Backup the System

Create a backup of your current BVMS system and store it in two locations: on the server and separately (like an external drive).

3. Obtain an Emergency License (if needed)

If upgrading outside of business hours, request an emergency license in advance.

4. Check the Third-Party Software Compatibility

Verify that any third-party systems or software connected to BVMS will work with the upgraded version and support decoupled mode (if applicable).

5. Understand Your System Setup

Check how many servers and workstations you have, and where BVMS components (like Management Server or VRM) are installed.

As an Example:

For systems with up to 500 cameras, both the Bosch Management Server and VRM can be installed on the same server. However, you can also choose to install them on separate servers.

In earlier versions, if Bosch MVS was installed, it was needed to be on a separate server. With version 12.3, this feature has been removed, so it’s no longer necessary, and any existing MVS server would become a spare.

Before starting the upgrade, make sure there are no un-activated changes in the configuration. Additionally, it’s a good idea to log back into the server from any client workstations before upgrading to ensure they have the most up-to-date database for decoupled mode connections.

6. Check for Custom Settings (e.g. Time Server)

Legacy versions may use different configuration files (e.g., BVMS CentralServer.exe.config) for time servers.

This is not used on current versions and is now configured in the BVMS Configuration Client and would need entering in there after upgrade. One way of checking this is to check on a Bosch camera what NTP time server is being used.

If this is the address of the BVMS server, then this was never configured.
If it is another time server setting, then that will need to be configured into the BVMS Configuration Client after upgrade.

7. Check Hardware and OS Compatibility

Check compatibility of existing servers and clients with the latest version of BVMS. PC and server specification is listed on the BVMS Datasheet (e.g. BVMS 12.3 Data Sheet)

8. Review Release Notes

Understand all major and minor changes across versions, e.g. BVMS 12.3 Release Notes

Consult Release Notes for BVMS which will detail changes made between old and new versions and ensure if there are any restrictions to be considered (e.g. removal of MVS in BVMS v12.3)

9. Camera Firmware Check

Check the firmware requirements listed in the BVMS Release Notes and ensure that cameras onsite have the minimum firmware version required installed.

Note

This cameras firmware upgrade process would be the only downtime for recording during the upgrade process as this should not be affected by the upgrade – this could be done at any time.

Firmware is available on our Download Store and is listed by CPP types. If you don’t know which CPP type a camera is, then you can find your model of camera in one of the CPP types listed here:

Which CPP corresponds to certain cameras and encoders?

10. Validate the Server Name

Check that the server’s name has not be renamed since the server was installed, as this may affect the SQL update.

Registry key where the current expected name is stored is below <hostname>. This is the stored name of the server and must match the servers actual name within Windows:

[HKEY_LOCAL_MACHINE\SOFTWARE\BVMS\Installer\SelectedValues]"LOGBOOKDB_SERVER"="<hostname>\BVMS"

11. Download/ request the required BVMS Upgrade Packages

Plan intermediate steps:
For example, from BVMS 9.0 to 12.3:

BVMS 10.1
BVMS 11.1
BVMS 12.1
BVMS 12.3
Earlier versions must be requested from Central Technical Support team.

Note: Also, it worth having the exact version of BVMS you have onsite currently, so in the instance of issue you can rollback and use your backup to restore the system to as it was.

12. Access to the Old License Portal

For BVMS 9.0 and to update the license from 10 to 11+ you will need access in: Old License Portal
If you don’t have access, arrange to transfer licenses to your business account and make sure that you have access in the Old License Portal – Transfer is available through Central Technical Support. However, please be aware this will require completion of a form from the end user owning the system to indicate you are authorized to hold the license

13. Access to the Bosch License Remote Portal Account

Ensure you or your organization has a Remote Portal account for licensing version 11+. Details of license handling are included in the BVMS Upgrade and Migration Guide.

14. Check the VSG Instances

Verify VSG gateways in use and plan for their upgrade according to supported versions as per the BVMS Release Notes.

15. Confirm System Health

Ensure all cameras are recording and fully operational before starting.
Document any existing issues to avoid false attribution post-upgrade.

Upgrade Process

General Rule:

We recommend going up 2 versions at a time (this would be just on the Management Server). The VRM and the clients can go straight from one version to the latest, once the main server is done. At each step you don’t need to license the server, you just need to ensure DB is updated correctly along the way which can be done by logging into the Configuration Client and checking if everything looks ok (it will be unlicensed).

Where you will need to activate the license will be on the update to version 11 or above, where the license portal changes to Remote Portal.

Step-by-step guide

To upgrade the software itself, is as simple as running the installer through on each machine and selecting upgrade. Letting it finish, reboot the server and then move onto the next step:

Upgrade Management server – While this is being upgraded, it will not affect an operator getting live view, the system recording or an operator playing back from near time unless the system has had default for live view changed, in the case of VSG connected devices or encryption for storage at rest enabled, or in the case of playback. Even users who have not logged into the system before could walk up to a client PC and login (as long as the PC has logged in recently – see step 5 above) and with the server unavailable they would revert to decoupled mode and allow normal operation albeit with a slow login. The only thing affected here would be:

Event status would not be reported because the Management Server handles events, and while it is off, none would be reported or logged.
Logging would not be updated while the server is off as there is no DB to send the details to.
Video Wall if used would not be able to be changed as this is handled by the server.

It is advised licensing this as soon as you cross over from 10 to 11 and then again when you get to the final version. Instructions for migrating the license are in the BVMS Upgrade and Migration Guide.

Upgrade VRM Server – This can be done at the same time as above, if the VRM is on the same server. Otherwise, it should be done after the Management Server has worked its way up to the desired BVMS version.

This can be down for up to 7 days (default system setting is 4 days, if never changed)
The camera can be disconnected from the VRM as long as it retains power. It will already have its storage locations stored in the camera for where it is storing video for the next 4-7 days (depending on the settings in VRM) and it won’t need the VRM until the blocks run out.

Upgrade Operator Clients – Again this can be done after the server has reached its final stage. Doing these one at a time ensures you don’t lose connectivity to the cameras. If you are already at the latest version on the management server, then these should reconnect as soon as the BVMS version is on Management server
Any additional client configurations (other than the one on the main management server) should be done at the same time as the management server is being configured.
At this stage upgrade any VSG instances used to bring in non-Bosch Cameras.
At this stage if the Cameo SDK is installed on any third-party systems, we would recommend updating that next
At this point update the firmware of any Video Wall decoders onsite

________________________________

Post-Upgrade Checklist:

Confirm all workstations connect to server and show correct recording status.
Adjust Time Server settings as per Step 6 in preparation.
Verify time synchronization across all devices (cameras, clients, servers).
Ensure all cameras are streaming/recording correctly.
Test playback functionality.
Validate that all configured alarms and events trigger as expected.
Open the system logbook and confirm data is writing correctly.

________________________________

Server Migration (If needed)

If any item needs to be moved to another server as part of the upgrade, then consult the official BVMS - Upgrade and Migration guides for details on how to migrate the server and any considerations

By following this structured approach, you can significantly reduce the risk of downtime and ensure a seamless upgrade of your BVMS infrastructure. For detailed instructions, always refer to the official Bosch Upgrade Guide.

Nice to know: