BODY WORN MANAGER PRO SOFTWARE RELEASE NOTE
=============================================

Products affected:	W800

Release date:		2025-04-16

Release type:		Production

Software version:	1.4.856

Preceding release:	1.3.763

Bundled software:	12.4.59

Compatibility:		Google Chrome (latest)

-------------------------------------------------------------------------------------------------------------------------
Improvements in 1.4.856 since 1.3.763
=======================================
* Manager Pro now rejects new systems with unsupported software
* Encourages user to upgrade systems with old software is more visible
* Added option to allow insecure AD connection in configuration application
* Users that are incorrectly deleted with systems using Genetec will now be recreated
 
 
Corrections in 1.4.856 since 1.3.763
=======================================
* Fixed an issue where Manager Pro would crash when installed on a machine with installed system language other than english
* Fixed an issue where Manager Pro showing users not assigned to a system
* Fixed an issue where user session expires prematurely
* Fixed an UI issue that would crash the browser when AD connection is flaky
* Fixed an UI issue that would show a fail error toast when upgrading a system even though it was successful
* Fixed an UI issue where wrong error was shown for AD group validation on system claim
* Clarified the consequences when removing a system from Manager Pro (you will need to reset the system after removing it)
 

Other updates in 1.4.856 since 1.3.763
=======================================
* Updated minimum TLS version to 1.3 for connections between Manager Pro and SCU


Corrections in 1.3.763 since 1.2.700
=======================================
* Improved login error messages
* Fixed an issue where Manager Pro would not start on non-English Windows installations
* Fixed an issue where the selected language was ignored
* Minor bug fixes and improvements


Other updates in 1.3.763 since 1.2.700
=======================================
* Admin account password has to be reset after upgrade, if used as login


New features in 1.2.700 since 1.2.577
=======================================
* Minor bug fixes and improvements


New features in 1.2 since 1.1
=======================================
* Added pagination to users table for improved performance and user experience


Corrections in 1.2 since 1.1
=======================================
* Improved user handling when moving users between systems


New features in 1.1 since 1.0
=======================================
* Added support for local login without the need of an AD account
* Added pagination for better handling of large AD accounts


Corrections in 1.1 since 1.0
=======================================
* Fixed an issue where rejected SCU's was still included in the system description file
* Fixed an issue where settings could be overwritten when using the tray application
* Fixed an issue where profile settings where not set after a firmware upgrade
* Fixed an issue when a reactivated AD account where not able to login
* Fixed an issue where pasted values did not enable the Apply button


Initial release 1.0
=======================================
* Added support for Active Directory
* Added support for centralised management of checkout tags (Active Directory or manual assignment through Manager Pro)
* Added support for centralised management of camera profiles
* Added support for centralised management of device software upgrade
* Added support for compliance of federated systems (device software version, users, user profiles)


Known limitations
======================
* Manager Pro only supports device software versions 12.2, 12.3, 12.4

* User(s) in multiple systems at the same time is not recommended. e.g same user created in Site A with group A, and Site B with group B

* Compliance status ONLY reflects main systems, not extensions or cameras

* When federating, old users are removed and new users are added, therefore the following information is lost:
   - BWA pairing
   - Holster pairing
   - Personal WiFi information
   - EMS history

* Removing a system from the federation also requires a factory reset on the affected system

* Changed system name, on federated SCU, does not propagate up to Manager Pro

* No IPv6 support

* Login with Active Directory might be attempted only on the preferred NIC

* If a user is present in multiple Active Directory groups, and these groups are used on the systems in the federation, the system will occupy more than needed licenses since the user will be created multiple times on a VMS

* Large Active Directories with many users can cause a slow synchronisation the first time