On using a particular version:
- Ideally, BrightSign OS should be kept up-to-date, as well as your client application (i.e.BrightAuthor:connected). Especially before a new deployment, one of the very first steps should be to update the player's OS (and client application if a newer version is available) before applying a configuration to the player.
- Newer OS versions include features that may be useful, as well as fixes to issues.
On validating a new version for use:
- If you have more than a few players that were already configured, you may want to update a single unit (or multiple units that may be configured differently--for example wired vs wireless) and use that for your testing to verify and accept the new OS version before deploying to a larger number of players.
- Publish a few presentations that you commonly use and monitor the behavior on the display alongside some of the key features that you typically rely on in your day-to-day publishing with the client software. In addition, check workflows that you use to manage your players to ensure they are working as expected.
- This would allow you to uncover any issues with the updated version, and report them to the support team. This process could help protect the rest of your fleet from being negatively impacted by any change of behavior caused by the potential update.
On the frequency of update
- It would be advisable to keep your players updated with the latest OS version. You may also consider adopting an internal policy to check for updates routinely.
- You can also subscribe for notification of updates from our Software Downloads page.
There are a few different ways to apply an OS update. Below article may be useful;
If you're using a CMS partner's application, they may have verified/recommended a specific OS version for use with their specific application, please contact them for guidance.