Video Screencast Help

Packaging MessageSave 5 with Wise Package Studio

Created: 08 Nov 2012 • Updated: 08 Nov 2012 | 1 comment
Language Translations
CableGuy41's picture
+6 6 Votes
Login to vote

When it comes to handling application licensing in the packages, it is essential to know the type of licenses and how they impact packaging. Following are some of the common license types that we come across in day to day packaging.

1. Per-User license: Per-user licenses can't be included inside the package as every user will have a unique License Key. So we can create a single package that caters all the users. We can also check with the vendor to see if all per-user licenses can be consolidated to a volume license key. This approach worked for us sometimes.

2. Volume license: Volume license can cover a few users to few hundred users depending upon the agreement with the vendor. We an accommodate volume license key in the package as the same.  

3. Enterprise license: Enterprise license can cover the entire customer segment group or even the entire organisation. Application package can be configured with Enterprise license key.   

There are several license types. However I tried describing common license types that I came across. Now coming back to MessageSave 5, the application has volume as well as enterprise wide licensing options.

During packaging we specify the license key in the license key registration option and we monitor the registry/file that is being updated. In MessageSave 5 case, the details are saved in the form of a configuration file. But it has machine specific details as shown below:

<SystemIdentifiers xmlns="">

      <Identifier Name="MachineName">XXXXX</Identifier>

      <Identifier Name="NICMAC">XXXXX</Identifier>

      <Identifier Name="RootVolumeID">XXXXXX</Identifier>

      <Identifier Name="CPUInfo">XXXXXX</Identifier>

      <Identifier Name="HDInfo">XXXXXXX</Identifier>



Once the application is registered with the license key, the license file is generated. But it has machine specific information in an encrypted format. So we can include this file in the package for mass deployment.

Solution 1:

Implementing Group Policy by configuring license key in the ADM file. Attached is the ADM file template.

Solution 2:

If you prefer not to use GPO, then you can deploy license key via registry that can be configured in the package.

Registry Key: HKEY_CURRENT_USER\Software\\MessageSave

Value: InstallCode (REG_SZ)

As this is a HKCU registry entry, you can implement this via Active Setup.

I hope this helps.

Comments 1 CommentJump to latest comment

Eshwar's picture

Registry key seems to be the best possible method during packaging.



Login to vote