Asset Management Suite

Altiris - Migrate Software Product Licenses from 7.5 / 7.6 to 8.0 - License Rule fix 

Mar 17, 2017 08:08 AM

Hi,

We recently had a customer who performed an Off-Box upgrade from 7.5 to 8.0. They asked us to help migrate their products, however we encountered an issue migrating their Licenses due to a new feature called License Rules that exists against the License Type in 8.0.

The steps below are what we did to identify this. I've attached all screen shots and scripts for reference to the botton of this article.

However,  if you're just after the solution then after we raised this with Support, a fix was created and is available for 8.0 machines that are on HF6+.

The e-track is: 4073198. The fix is due to be released ~26.03.2017.

 

Identification / Migration steps

Import / Export Utility

  •          The customer has performed an Off-Box upgrade from 7.5/6 to 8.0
  •          We originally used the ImportExportUtility to export the following
    •     Software component
    •     Software Product
    •     Software Purchase
    •     Software License
    •     The above order is how they were then imported into the new 8.0 Environment using the ImportExportUtility. (You need the PO to migrate licenses, and it has to go in before the License in order to correctly associate).

What we found with this approach is that the new license rule was not populated on the imported licenses and thus would not associate with the Product. See the screen shot below, effectively against License rule would be the option "New Rule*".

License rule after ImportviaUtility_0.png

  • This was “resolved” by opening the License and selecting + creating the License Rule within the License. This would not do for a full migration.

We then tried the following steps.

Import / Export Utility + Data Connector

The thought behind this was to use SQL to generate a unique guid for the License rule element in the hopes that it triggered the correct action and associated a License Rule. 

  •          We originally used the ImportExportUtility to export the following
    •     Software component
    •     Software Product
    •     Software Purchase
  •          Software License was then imported using the Data Source and Import / Export actions.
  •          You can see the data source on the screen shot below and the sql to generate it under “GetLicenseInformationSQL.txt”. Data Source.png

 

  •          You can see the Import / Export rule below. You can see the License Rule that I have defined a field called RuleGuid.

Import Export Rules.png

  •     When I created a new License Rule (by getting SQL to generate a guid) It broke the system and showed me the below error.

License Rule Broke Message.png

  •     This is because the guid against the License does not reflect the guid in the License rule field that is automatically generated on import

As stated above, the work around is either manual intervention or to install the fix mentioned above.

 

Thanks,

Kevin

Statistics
0 Favorited
3 Views
6 Files
0 Shares
65 Downloads
Attachment(s)
png file
Data Source.png   17 KB   1 version
Uploaded - Feb 25, 2020
txt file
GetLicenseInformationSQL.txt   2 KB   1 version
Uploaded - Feb 25, 2020
png file
Import Export Rules.png   68 KB   1 version
Uploaded - Feb 25, 2020
png file
License rule after ImportviaUtility.png   19 KB   1 version
Uploaded - Feb 25, 2020
png file
License Rule Broke Message.png   7 KB   1 version
Uploaded - Feb 25, 2020
png file
License Rule Broke when creating new license rule.png   13 KB   1 version
Uploaded - Feb 25, 2020

Tags and Keywords

Related Entries and Links

No Related Resource entered.