Hello,
since we have some issues with the Cube update procedure on some machines (and we must update because of an issue with the current cube version), we are wondering if there is a standard download option to always acquire the latest Cube version as an offline installer. As of now several downloads can be found when searching Cube installer on dataminer.services, but they are all pretty old...
Thanks!
Funny because we have the same issue. Client version was too old but we couldn’t update it. Just upgraded to 10.3 CU2.
Hi Nils,
The Cube installer on dataminer.services is intended to update itself to the latest version, however, this requires internet connectivity on the client machines.
There are 2 main ways to deploy a newer Cube version to offline clients. They both require you to download the full upgrade package of the version you want to use, for example 10.3.6.
- Extract the "shared" MSI installer from the full upgrade package (Update.zip > Webpages\Tools\Installs\DataMiner Cube.msi) and deploy this MSI on the client machines through any MSI deployment framework.
- Extract the Cube.zip + versions.txt files from the full upgrade package (Update.zip > Webpages\DataMinerCubeStandalone\*)
and set it as the enforced version on all agents in a cluster through Cube > System Center > System Settings > Manage Client Versions. Clients will then download this version from the DMA the next time they connect to it.
Which method you use depends on how Cube was initially deployed on clients, i.e. if the shared MSI installer was used previously clients are not permitted to automatically update from the DMA.
Some extra responses have come in since I started typing this reply - if only some of your clients are unable to retrieve the latest version from dataminer.services, it might be worth having a look at their logfiles to see if there are any network problems (e.g. DNS or a proxy?).
Thanks, Bert!
Maybe some easier procedure for deployment of a new Cube version would be nice, in case a client does not have internet access. We used the workaround to simply copy the versions directory into the correct file location on the client – seems to work just fine.
Hi Bert,
following your description, I can see what can be done here, but I still don’t see a way to enforce a specific cube version that has not been deployed in an upgrade package, but which has been released later on. This is where it all comes back to my initial question: where to acquire a specific cube version (I understand that it doesn’t have to be an installer)?
Hi Nils,
I’m not sure I understand this part: “a specific cube version that has not been deployed in an upgrade package, but which has been released later on”.
If for example your DataMiner system is on the 10.3.0 main release, and you wish for all operators to use Cube version 10.3.6 on their machines which have no internet connectivity, you could download the DataMiner 10.3.6.0-13026 Full Upgrade.dmupgrade, extract it as a zip file, then extract the update.zip to a local folder. Open Cube > System Center > System settings > Manage client versions > Force a specific version and select the Cube.zip from DataMiner 10.3.6.0-13026 Full Upgrade.dmupgrade/Update.zip/Webpages/DataMinerCubeStandalone/.
As to where to obtain a specific Cube version: that would be extracting it from a package in the “All Supported DataMiner Versions” section on the DataMiner Server upgrade packages page https://community.dataminer.services/dataminer-server-upgrade-packages/
The default page for this request seems to be https://community.dataminer.services/dataminer-cube-installer/, but right now there it is not the latest version that can be found.