When our customers have already a DMA licence for 10.1
Is a new licence needed when they want to upgrade from 10.1 to 10.2?
Hi Cristel,
The upgrade from 10.1 to 10.2 is a major upgrade, and for a major upgrade you indeed need a new license file. But the good news is that the upgrade package of 10.2 will contain the new license file and automatically install that one. All DMAs with an active support contract will be included. And this mechanism is applicable for all major upgrades for course, so also for upgrading to 10.3 and 10.4.
So, when you have an active maintenance contract, you should be fine and you can always upgrade to the latest version. If you don’t have an active maintenance contract, you can only install the small updates or CUs of the version you are running.
Let us know if something would not be clear.
Bert
The platform team has tried this, but at first glance it does not work:
Administrator@DMA-1-1 /cygdrive/c/Skyline DataMiner/Logging
$ cat SLErrors.txt
2024/02/16 09:10:03.380|SLLog|ApplyLogLevels|CRU|-1|Log Levels: Info: 5; Error: 5; Debug: 5 (init)
2024/02/16 09:10:57.989|SLDataMiner.txt|SLDataMiner|484|572|CDataMiner::Init|ERR|-1|10.2 – DataMiner is unable to start
Cause: No valid license file
Online registration: Unable to contact activation server
Offline registration:
To obtain a valid license file, email the file
‘C:Skyline DataMinerRequest.lic’ to
dataminer.licensing@skyline.be
Skyline Communications N.V. will then provide you an appropriate license-file, which should be placed in
the folder ‘C:Skyline DataMiner’.
Contact info:
Skyline Communications N.V.
Ambachtenstraat 33
B-8870 Izegem
Belgium
For further info check SLDataMiner.txt
2024/02/16 09:10:58.010|SLDataMiner.txt|SLDataMiner|484|572|CServiceModule::LaunchDataMiner|ERR|-1|!!! Start DataMiner failed The MAC address is not licensed. (hr = 0x80040291)
2024/02/16 09:10:58.011|SLDataMiner.txt|SLDataMiner|484|572|CDataMiner::NotifySLElementProcess|ERR|-1|Notify SLELement process failed (98): 0x8004024c: The element is unknown.
**********
maybe this is related with the “command-line installation” we do.
Remark: our installation procedure = install 10.1 then upgrade to 10.2
Nice:)