Windows Client 1.0 | AppsAnywhere Docs

Version 1.0.7 - Application

Released: 13^th April 2017

Added more specificity to WMI queries as on some systems results returned without the property required
Check for trailing slashes on protocol requests that could stop message decryption from succeeding
Added a retry if generation of device ID fails (in case WMI service is busy) before reporting an error

Released: 28^th March 2017

Management for entirely new update process
Switched service communication from TCP ports to named pipes to stop client conflicting with other applications

Released: 28^th March 2017

Completely new update process that uses MSI re-install to allow for all elements of the client to be updated

Released: 2^nd March 2017

Cloudpaging Player now launches by default as soon as an app is added to the player
Registry key override for the above feature to revert back to AppsAnywhere splash screen only option
Institution ID can now be included in client download filename to ensure it is present for the first launch of the application and subsequently be sent with the very first versioning check to ensure the correct Cloudpaging Player version is used for the given institution
Splash screens are no longer system modal

Logged on username not reported in some terminal server environments
Unsupported SCCM versions can cause validation failure
Applications auto-run regardless of AppsAnywhere delivery method setting
SVOROS and SVORUO registry keys being read from incorrect location in registry
Cloudpaging Player not being correctly initialized following installation when dependencies exist

Released: 25^th January 2017

Initial support for initiating deployment of SCCM applications
Support for registry override to disable self-update functionality
Removal of initialization screen by default with a registry override to make it display on startup
Better handling of errors when the updater fails to contact the versioning API
Better handling of errors contacting the versioning API on first run when Cloudpaging is already installed
Client is now automatically initialized following a validation/launch request if it is not already running in the background

Released: 7^th December 2016

Fixed a problem with updater not being able to update parts of the main application because they are in use
Updater now stops the core service and running processes before update and restarts them afterwards

Released: 7^th December 2016

Added ability for the main application (on initialization) to update the self-update executable
From this point, updates will be specific to either the main application or the updater

Released: 22^nd November 2016