Download the Flash player at www.macromedia.com.
Home
Solutions
Solution Archives
Software Products
Site Search

 

03-Apr-05, ZWDynaUser Article posted! (Pt. 1)

28-Mar-05, Windows Process Authority article posted!

28-Mar-05, ZWXPDrive article posted!

22-Mar-05, ZENworks Enhancement Software Posted!

22-Mar-05, Site Updated!

Legacy Solution - Some information may be dated.
In conjunction with the "uninstall features of ZEN3", the Install-On-Demand methods can also be used to help control software licenses.

Software licenses come in two general types: "Concurrent Use" and "Installed Seats" licenses.

"Concurrent Use" licenses allow the software to be installed on as many workstations as desired, so long as no more copies of the software are running at any point in time that licenses are owned.  The licensing features of ZENworks are designed specifically to handle "concurrent use" licenses.

The "Installed Seats" license, though not specifically designed to work the ZENworks, can be easily managed through ZENworks.  A log file can be generated on a central file server that records each station that installs the software.  ZFD3, adds an uninstall feature, that will automatically remove the workstations entry when the software is removed.  Therefore the log file will automatically maintain a list of currently installed seats.

CADONDEMAND

The purpose of the CADONDEMAND application is to install the CAD application anytime a user clicks on a file with the CAD extension.  This way the user will not need to know which application to install or what steps to take to perform the install.

The registry entries for this application are the following.

REGEDIT4
[HKEY_CLASSES_ROOT\.CAD]
@="CAD_auto_file"
[HKEY_CLASSES_ROOT\CAD_auto_file]
@="CAD File"
[HKEY_CLASSES_ROOT\CAD_auto_file\shell\open]
@=""
[HKEY_CLASSES_ROOT\CAD_auto_file\shell\open\command]
@="F:\zenutils\Nalrun32.exe ithowto .CADAPP.HBG /P="%1""
[HKEY_LOCAL_MACHINE\Software\CLASSES\.CAD]
@="CAD_auto_file"
[HKEY_LOCAL_MACHINE\Software\CLASSES\CAD_auto_file]
@="CAD File"
[HKEY_LOCAL_MACHINE\Software\CLASSES\CAD_auto_file\shell\open]
@=""
[HKEY_LOCAL_MACHINE\Software\CLASSES\CAD_auto_file\shell\open\command]
@="F:\zenutils\Nalrun32.exe ithowto .CADAPP.HBG /P="%1""

These registry entries cause the ZENWORKS application "CADAPP" to be called when a file with the extension CAD is clicked.  The utility nalrun32.exe is executed with the parameters of the tree name, the fully qualified name of the application object, and finally the option to pass the %1 variable to the application, which will evaluate to the name of the file double-clicked.  The utility nalrun32.exe from the ZENWORKS 2 toolkit is used in this example due to a bug in the nal.exe program ZEN3 in the slash "/P" switch.  The file zenapp32.dll must be placed in the same directory as the nalrun32.exe utility because the zenapp32.dll that comes with ZEN3 is incompatible with nalrun32.exe util.  Nal.exe from ZEN2 functions correctly and does not need to use the nalrun32.exe utility.

All of the entries for this application are set to "Create if Does Not Exist".  The application is also set to always distribute.  This will cause the CAD software settings to not be overwritten if they exist, but it will reset the application to auto-install if necessary after the CAD application has been removed from a workstation.

CADAPP

The "CADAPP" will perform three main functions.

  1. The application will push all files, registry settings, etc required for the application to run.

  2. The application's shortcuts and file extensions will continue to be associated to the NAL app from the CADONDEMAND app above.  This is necessary for the proper tracking of app usage.  Otherwise, the application may uninstall for non-use, even though it was used since usage is tracked by the launching of the NAL app, not the executable.

  3. It will launch the CAD application and open the file on which the user clicked.

  4. Using the INI portion of the application object, modify an INI file located on a central server indicating that the application has been installed on this workstation.  The INI file will create an entry using the workstation object's name and enter the date on which the software was installed.
     


     

  5. The Application will automatically Uninstall after X days.  This will also clear the INI addition, recording the removal of the software license from this PC.  The Date the software was last installed on the PC can help locate orphaned entries.  This INI setting could also be set to "Distribute Always" to cause the date to reflect the "Last Used" date.
     

  6. To help reduce orphaned entries, the snapshot install routine should be modified so uninstall settings for the application call the ZENworks uninstall instead of the standard uninstall routine.  This will guarantee that the log file is cleaned up by the uninstall.  In the registry of the snapshot, you may see an entry such as the following:
    C:\WINDOWS\IsUninst.exe -f"D:\DirectCD\DCDUnins.isu" -cD:\DIRECTCD\Dcduhlp.dll
    This needs to be changed to NALWIN32 with the "L" parameter defining the app to uninstall such as, NALWIN32 L=.CADAPP.HBG