Show me an explanation of the items on this page.
How do I deploy the software vendor's install package?
Most vendors provide either a single file (when downloaded from the web) or set of files (when distributed on a CD). Executing the installer file (typically named setup.exe) installs the vendor's application on any operating system.
Deploy the vendor's install package by writing a script to do the following:
Write the file or files to a location accessible by the remote machine (either the machine itself or a file server accessible by the remote machine).
Execute the installer on the remote machine.
Note: Using the vendor's installer typically requires users to answer questions during the install process. See Creating Silent Installs to create a package that does not require any user interaction.
Information on creating custom scripts...
What does the Packager do?
Each package is OS dependent. To deploy to multiple OS's, you need to build a package for each OS. During installation, Packager checks the OS and does not continue if the package is being deployed on an OS different than the source OS.
Close all applications before running Packager. This prevents open applications from modifying the system during package creation.
Packager picks up everything you do to a machine between the time you take the first snapshot and create the package. Be careful what additional tasks you perform on the source machine as any system changes will be rolled into the package.
What if installation fails? The Packager has complete rollback capability. The Rollback executable and associated restore files are located in the Agent directory on the target machine in the directory C:\Program Files\Kaseya\KPackage.
How do I create a Package?
Download and execute the Packager application.
The Packager takes a snapshot of the source system.
Install any application and/or resource on the source system.
Execute the Packager application again. The Packager records the changes in the source system and creates a Package file.
Distribute the Package file any way you like. You can e-mail it, or store it on a server where a custom script can perform a silent installation on any managed machine.
Information on creating custom scripts...