The Boring Lab

Boring Blog

Milestone XProtect 2019 R3 – Upgrade Considerations

Milestone just released XProtect version 2019 R3 with some great new features:

  • Metadata Search in SmartClient
  • Driver Framework
  • Adaptive Streaming
  • and more…

However, there are three Milestone KBs that you should consider before jumping in.

Smart Clients older than 2019R3 are not compatible

KB 19309 discusses the details of the upgraded security protocols used in XProtect 2019 R3 and that this new version of XProtect will not be backwards compatible with older version of Smart Client.

With the release of XProtect 2019 R3, stronger security features were implemented, which means the Service Channel feature has been removed. As this feature was used in the earlier versions of XProtect, the older versions of the Smart Client will no longer be able to connect to an XProtect 2019 R3 server.


The solution:
Upgrade all your Smart Client users to 2019 R3.  The smart client itself IS backwards compatible with older versions of Milestone XProtect.

There are specific NVIDIA driver requirements

KB 17957 outlines performance issues and security flaws in the previous version of NVIDIA drivers when using hardware acceleration.  It also states that the minimum driver version of 418.96 onwards is required for XProtect 2019 R3.

When using Nvidia hardware acceleration for the XProtect Recording Server, Mobile Server and Smart Client, you may experience issues like (but not limited to) image quality degradation, lower performance than expected, memory leaks or even crashes in some cases.


The solution:
Upgrade NVIDIA drivers to v. 418.96 onwards.  

Installing mobile server might lock your user account

KB19308 discusses how the new version of mobile server may lock your user account due to how it passes the credentials to the data collector service.

If you install the XProtect® Mobile Server 2019 R3 under a domain\Windows account, the account may be locked (if there is a policy for locking the account after several unsuccessful attempts).


The solution:
Install the recording server initially as a network service account and then change the service to run as the windows service account.