using the Package Builder - Community - LANDesk

More documents

Recommendations

Info

RemRunAtStartRunAtMiddleRunAtExitthis command in your .CFG fileThis command adds a remark to the .CFG file.This command runs an executable before the installation starts.This command runs an executable during the installation.This command runs an executable at the end of the installation.SCRIPT ORDER OF EXECUTIONWhen the package is executed on the target workstation, the package script fileis not executed in a top-down manner as one may expect.Builder stores a version of the configuration file script (.cfg) inside the monolithicexecutable. This configuration script is used to determine what happens duringthe installation.The installation engine (INST32.EXE) does not execute all of the commands inthe script in order. The purpose of this document is to explain why commandsare not executed in order, and the order of execution of commands.Reasons for Script ReorderingScript commands that produce user interface are at the heart of script reordering.Consider a script that installs a large number of files, and then user interface thatallows the user to choose which set of remaining files should be installed. Thiscauses two problems. The lesser problem is that the user must watch the entireinstallation in order to complete all dialogs. The greater problem is that if theuser selected the “Back” button, the large set of files must be uninstalled.The solution is to execute all user interface commands, and to execute “IF”statements that are based on the output of those interface commands beforeexecuting other commands like file and registry commands. If the “IF”statements return FALSE, the commands they enclose will be marked such thatthey will not be executed.Script Order DetailsThe installation engine makes multiple passes of the script; each time it attemptsto execute specific types of commands. The individual passes through the scriptare as follows:1. The following commands are processed:MINCPUTYPEANIMATIONPROMPTSBuilding Successful Packages - 10 - v1.0
FONTNAMESETRUNATSTART2. Static “IF” statements are executed. If the statement returns false, allcommands within the “IF” block (except those in the “ELSE” block) aremarked as non-executing. The static “IF” statements include:IF WINVER()IF DOSVER()IF ISFILE()IF MEMORY()IF CPU()IF VIDEO()IF SEARCH()IF SEARCH(Registry)IF SOUNDCARD()IF FINDMODEM()IF FILEVER()IF CDROM()3. Dynamic “IF” statements and user interface statements are executed, andthe “IF” blocks marked for non-execution depending on the result of the“IF” execution. The dynamic “IF” statements include:IF GROUPIF $ASKN$IF DISKSPACE()IF LOCATE()IF $4. File commands are processed in the order they occur in the script. Othercommands, like registry commands, are still not executed at this timeregardless of the order in the configuration file. The file commands arethen flagged so they will not be run again at a later stage. File commandsinclude:FILEINSERTDISKCOPYDELETERUNATMIDDLE5. All remaining commands, including registry, .ini file commands, andRUNATEXIT, are executed in the order they occur in the script.Building Successful Packages - 11 - 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: If conditionsIf $ASKn$If $SYSn$If $
Page 13 and 14: and appends them to the package.The

using the Package Builder - Community - LANDesk

Create successful ePaper yourself

Delete template?

Save as template?