Scripts > Packager
Packager evaluates the state of the source machine before and after an installation and/or resource change. The Packager compiles the differences into a single executable file - the Package - that can be distributed via scripts to any managed machine.
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 target machine's operating system and does not continue if the Package is being deployed on an OS different than the source OS.
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.
For best results, we recommend you create a Package on a representative machine; that is, a machine that closely resembles the client machine(s) on which the Package will be deployed.
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.
Download and execute the Packager application.
Packager takes a snapshot of the source system.
Install any application and/or resource on the source system.
Execute Packager again. Packager records the changes in the source system and creates a Package.
Distribute the Package any way you choose. You can e-mail it, or store it on a server where a custom script can perform a silent installation on any managed machine.