Soon, we’re upgrading from 9.6 CU14 to 10.1CU10 (with the intermedium step of 10.0 CU21) and we want to force the users to use the latest Cube version (aka Launcher).
Currently, they are using the 9.6 standalone x64bits, and since that is not fully compatible we want to force and know if the users are using the right Cube version.
How we can audit if the users are using the right Cube version?
With the 9.6 standalone version, we don’t have any warning/popup that informs the user that is using the wrong version.
Hi Luis,
On 9.6 there are 2 types of standalone that could potentially be in use:
- The ClickOnce StandAlone has an auto-update mechanism, but this type of installation has been phased out already. If you upgrade a 9.6 server to 10.1 this Cube will not detect any new version and keep running under the assumption it is the latest version. However, by modifying the remaining DataMinerCube.application file on the agents you can prevent users from accidently starting this up this version.
- The MSI StandAlone does not support updates by design. In this case the 9.6 version needs to be uninstalled and then the 10.1 version installed.
However, both these options on 9.6 were 32-bit by default. Did you specifically request a 64-bit Cube package for your environment? In that case you could either have used the MSI package (see above) or the ZIP package, which requires no uninstallation (simply delete the folder where the ZIP was extracted).
For 10.1 we recommend to use the Cube Launcher for deployment, if possible.
See https://community.dataminer.services/documentation/dataminer-cube-deployment-methods/ for an overview.
With regards to auditing you could look at the SLNet.txt or SLClient.txt logfile on the agents, although I am not sure if 9.6 clients will anything there. The protobuf version negotiation will be logged in SLNet.txt, that can be a good indicator:
2022-02-11 04:56:10.749|104|Facade.HandleMessage|Incoming (Cube (Administrator @ DESKTOP-SGL450L)): Setup ProtoBuf serialization for version 9.6.1829.8966