using the Package Builder - Community - LANDesk

More documents

Recommendations

Info

As a package contains files, registry keys, and other configuration items, it isimportant to build a package on the same platform to which it will be installed.For example, building a package on a Windows* XP operating system and theninstalling that package to a Windows 98 operating system will probably fail.Library files, registry keys and directory structures are different on theseoperating systems and may cause improper installation or functionality of theresulting application installation.The package also includes engine files that manage the package installation onthe target. The main installation engine is INST32.EXE.The PB Wizard uses snapshot technologyto take a ‘picture’ of the PB workstationbefore the installation of an application, andcompares that pre-installation snapshot to apost-installation snapshot to discover whatchanged on the workstation during theapplication installation. These changes are captured in a configuration (.CFG)file and then, when the package is built, all files that are referenced in theconfiguration file are copied into the package, along with the configuration fileitself. The configuration file is then used during package installation to list thechanges that must be made to the target workstation.A package does not have to consist of an application, such as Microsoft Word,but can simply be a collection of files, several registry changes, printer driverupdates, or specific desktop configuration changes that must be delivered to adistributed group of workstations.The PB contains an extensive scripting language that can be manipulatedmanually. These commands can be inserted into a snapshot packageconfiguration file, after the PB wizard iscomplete, or by opening the PB itself,without the wizard, and creating a newpackage configuration script.When a package is built, the .CFG scriptfile, the installation engine and all filesidentified by the Package Builder Wizard are compressed and wrapped into onestand-alone .EXE file. This file can be executed locally on a machine as any.EXE file can, or it can be scheduled to multiple workstations using the Schedulerin LANDesk® Management Suite.PACKAGE BUILDER COMMANDS AND OPTIONSThe Package Builder commands are grouped into the following categories:Building Successful Packages - 6 - v1.0
• Base Installation• Appearance• Messages & Input• System Changes• IF Conditions• Defaults & CallsEach category has several functionscommands that can be chosen as parta package.orofBase installationTitleFirstScreenDirectoryFileWinItemLastScreenUnInstallVersionInfoThis command displays the title which appears in the top left corner of thescreen during installation. The .CFG file can have two Title commands:one for the title and one for a subtitleThis command displays a personalized screen of text at the beginning ofthe installation process.The DefaultDir command is used to specify a default disk drive anddirectory for use during the installation.Use this command to tell the installation program which file(s) to copyfrom the installation diskette(s). Also use it to identify which directory thefiles should be copied to or copied fromThis command specifies a program group that adds the program to theStart | Programs menu in Windows.This command displays a personalized screen of text at the end of theinstallation process.This command specifies whether an uninstall program is to be created.This command defines the version information that will be associated withthis package and that can be viewed in Windows Explorer by right-clickingProperties.AppearanceAnimationIntroScreenIntroSoundScreenColorScreenGraphicThis command displays a series of bitmap files sequentially so that theyproduce an animation effect.This command displays a graphic (bipmap image) as the first step in theinstallation.This command plays a sound file (.WAV) as the first step in theinstallation.This command sets the background screen color.his command sets the background graphic to display during installation.Messages & inputsAskUse these commands to generate a prompt to the user and assign theuser's response to a variable.Building Successful Packages - 7 - v1.0
Page 1 and 2: LANDesk ® Management Suite 6.62Suc
Page 5: Successful Package Building using L
Page 9 and 10: If conditionsIf $ASKn$If $SYSn$If $
Page 11 and 12: FONTNAMESETRUNATSTART2. Static “I
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?