using the Package Builder - Community - LANDesk

More documents

Recommendations

Info

This order of execution limits conditional blocks from performing any tests onchanges that occur during the installation of the package. They exist solely tocheck the state of the machine before any installation occurs.COMMON ISSUESRegistry SettingsIf changes have been made to the HKEY_CURRENT_USER registry key in apackage, the installer detects whether someone is logged in and applies changesto that user’s registry and that user’s “documents and settings” directories.Also, the Package Builder Wizard offers a “build options” button. This dialogallows the administrator to configure how registry changes made toKEY_CURRENT_USER and file changes made to the current user’s “documentsand settings” directory (like the desktop, program files shortcuts, etc.) will beinterpreted upon install. The changes, when applied to target machines, can beassociated with either:1. Only the logged-in user2. All users profiles found in the registryDangerous Registry EntriesSometimes the Package Builder Wizard captures changes that can causecorruption of the system when deployed. These changes are typically registrysettings in the CurrentControlSet and Hardware subdirectories. Rather thanignore these changes, we wrap the registry calls in an “IF” statement like this:IF $DANGEROUS$ = "TRUE"BEGINREGISTRYKEY:new,"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Disk"VALUE:reg_dword,replace,"type","1"ENDREGISTRYENDIFThe user then has the choice of:1. Using the package without modification2. Defining the environment variable “$DANGEROUS$” equal to TRUE – thiswill allow the changes to be made on each machine with this variable set3. Editing the script to selectively delete “IF $DANGEROUS$” statementsBuild vs Rebuild All – Which Should I Choose?Adding files to a package is done in two main steps. In the first step, eachreferenced file is compressed into the working\temp directory to the namespecified in the .CFG script. The second step looks for files in the temp directoryBuilding Successful Packages - 12 - v1.0
and appends them to the package.The “Build” command will only update files in the temp directory that were notpreviously there.“Rebuild all” deletes all of the compressed files in the temp directory. Whenediting a monolithic exe, there is no difference between build and rebuild all forany files that still have the “name=” parameter specified in the .CFG file becausethey will be moved over directly from the previous instance of the package,unchanged.File replacement logicWhen rebuilding a monolithic .EXE, the builder will reuse all of the files put insidethe original package that are still referenced in the .CFG script. In order to triggerthe builder to grab existing files from your system instead of using the files in theprevious instance of the package, you must update the .CFG line that refers tothe file by manually removing the “name=” parameter. This will cause the builderto retrieve the file from your system each time. By default, the “name=”parameter is not included on the FILE: line of a script.Healing vs Reinstalling – Which is Best?Since version 6.5, when building a script to distribute a package, a “heal” or“repair” option is available. This feature is activated in a number of ways.o If a package is installed a second time and UI is disabled, then thepackage automatically goes into heal mode.o If a package is installed a second time and the /Ah+ parameter isprovided, then it goes into heal mode.o If a package is installed a second time and UI is enabled, the user will beprompted whether to heal the package or reinstall. If the user choosesheal, then the package goes into heal mode.RunAtExitTo perform complex operations in a package, it may be desirable to nestfunctionality in a child package that is launched by the parent package. This canbe done by typing either “~0000.exe” or “inst32.exe” followed by the desired childpackage name (which could be in the temp directory if flagged with the “temp”attribute in the parent’s CFG file). Path information is not important because theinstaller looks for either of these strings and automatically spawns another copyof itself with the specified package name.The advantage of running child packages by using inst32 instead of typing thepackage name is that another copy of inst32.exe, header32.exe, andenuinst32.dll need not be downloaded to the target computer (into the tempBuilding Successful Packages - 13 - v1.0
Page 1 and 2: LANDesk ® Management Suite 6.62Suc
Page 5 and 6: Successful Package Building using L
Page 7 and 8: • Base Installation• Appearance
Page 9 and 10: If conditionsIf $ASKn$If $SYSn$If $
Page 11: FONTNAMESETRUNATSTART2. Static “I

using the Package Builder - Community - LANDesk

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?