I read on this page https://community.dataminer.services/documentation/dataminer-cube-deployment-methods/
- It is possible to provide a default configuration for all users by preparing a CubeLauncherConfig.json file and placing it in the same folder as where the bootstrapper is installed (by default: C:\Program Files\Skyline Communications\DataMiner Cube\).
I prepared my Cube with the servers I wanted and then copied my file from %APPDATA%\Local\Skyline\DataMiner\DataMinerCube\CubeLauncherConfig.json to C:\Program Files\Skyline Communications\DataMiner Cube\ before the first run on a new install but it did not get picked up. Instead I just got the one DMA server that the MSI was downloaded from.
What am I missing here?
Hi Sam,
I created a recording of the installation process. In this example I have a config file with 3 agents preconfigured that I place alongside DataMinerCube.exe in the default C:\Program Files\Skyline Communications\DataMiner Cube\ folder. After the bootstrap is installed, a user JohnDoe logs on for the first time. The preconfigured agents are immediately available to him (the 5kB settings file has been copied to his %LocalAppData%\Skyline\DataMiner\DataMinerCube folder).
Is there any chance the Cube was already installed for your user? If no default config file is supplied with the bootstrap MSI, there should be no items on startup. If there is one, this typically means the DataMinerCube.exe was downloaded from an agent via the landing page and not installed via the bootstrap.