NetworkD - LANDesk Platinum ESP
 

News, Press Releases
NetworkD Events
Contact NetworkD
Request Pricing
Free Trial Downloads
Federal, State, Local Government
Customer Successes
K-12, College, University, Private
NetworkD SiteMap

 

June Tips and Tricks:


LANDesk® Tip of the Month:

Software Packaging using Wise with LANDesk

Here are some tips regarding Software Packaging:

           Windows/System Folder
It is usually better to try moving any Windows/System files installed by an application to the [INSTALLDIR]; by doing so, you cut the risk of a possible corrupted Windows/System folder and that will also save you some time (and money :-) ) in Software Manager/Conflict Resolution database when importing that MSI without having to deal with annoying conflicts. In some cases an application won't work if the files aren't in System32/System, at that point you will need to move those files back to their original location. There’s a good chance that application will be too happy to have those files in its own directory.

            Add/Remove Program
Sometimes a client will ask you to install an application on a computer/OS (Win2000, XP), but do not want the user to uninstall it, well it is possible to hide an application from Add/Remove Programs. In Windows Installer Editor go to tab Add/Remove Programs and select Do not display in Add/Remove Programs List or simply go to Setup Editor and set the ARPSYSTEMCOMPONENT property to 1. You can also modify how this product appears on the Add/Remove Programs control panel for Windows 2000/XP.

            Dialog Display
You can easily edit the dialog boxes of any MSI during installation and add your own text and images. You can also select which dialog box you wish to display at the time of installation. Under Dialogs in Installation Expert select the dialogs to display during installation by marking their checkboxes in the Dialog list, change the theme of the dialogs by selecting a new theme from the Default Theme drop down-list. Edit dialog themes by clicking the Edit Theme button.

The LANDesk Inventory Scanner:

The Delta LDAppl3 Update scheme: The basic LDAppl3 update was to just download the entire LDAPPL3.INI if it is newer than the one on your managed node. The delta scheme uses a base LdAppl3 and a cumulative set of forward differences stored in a patch. That way you only have a single patch file.

On the Core when you use the Software Management plug-in to Publish your LdAppl3. The new version would be compared to an LdAppl3.BASE file. A delta is written as file LdAppl3.PAT. Using the special edition LANDesk patching utility you combine the .BASE and .PAT to get the current LdAppl3.INI. To further minimize network load all files are compressed. Thus there is a compressed .BASE, LdAppl3.BAZ, a compressed LdAppl3.PAT, LdAppl3.PAZ and the compressed form of the LdAppl3.INI, LdAppl3.LDZ.

The scanner does its delta LdAppl3.INI update check this way. When the /I= switch is evoked by the Client, it checks its LdAppl3.LDZ against the one on the Core Server. If the one on the Core is newer, it downloads the LdAppl3.PAZ. It then checks its LdAppl3.BAZ against the Cores. If the one on the Core is a newer edition it downloads that LdAppl3.BAZ.

The .BASE/.BAZ file is reset when the .PAT/.PAZ files are a significant percentage of the size of the .BASE/.BAZ. By default 25%, but the percentage can be changed in the registry. It is expected that it will take quite a while to accumulate enough changes to cause a .BASE/.BAZ reset. So this scheme helps alleviate the network load issues of the old LdAppl3 update scheme.

Back To Top


HEAT® Tip of the Month:

Emailing the Journal to an Alternative User

For some time now, many HEAT users have been using the 'out of the box' function that allows you to send the contents of a journal to the subset email address.

But if you wanted to send the journal to another address, you had to copy and paste the journal into an email. By using the auto task below, you will be able to open an email that automatically populates the email with journal information but leaves the TO: field blank ready for you to enter an alternative email address.

The above auto task assumes you are using Outlook 2003 to send email.  

To send from Outlook 2000 change the file name to:

C:\Program Files\Microsoft Office\Office\OUTLOOK.EXE  

Or for Outlook express the file name needs to be:

C:\Program Files\Outlook Express\msimn.exe  

And the arguments need to be:

/mailurl:mailto:?subject=YOUR EMAIL SUBJECT HERE&body=YOUR EMAIL BODY TEXT HERE  

This auto task can then be launched from the auto task list or via a button on the journal screen as below
* Third party product and company names herein are trademarks of their respective owners.

 
NetworkD Sitemap Product Information Contact NetworkD Free Trial Downloads Contact NetworkD Investors Message from the CEo Change Region Change Region