|
Before deploying to target computers a package must first be created defining what is to be deployed and how. Once a package has been created it can be deployed to target computers or scheduled for later deployment.
Pro Mode is required to run multiple steps. Free Mode can only run one Install step per package.
Steps
A package is primarily a set of one or more steps. These steps are executed in turn on target computers.
Step
|
Description
|
Command
|
Execute commands from target computer (from within cmd.exe). Remember that any remote command must be able to run silently. If any user input is required (for example having to confirm Yes with hitting the Y key) the command will ultimately timeout unless the Run As option is set to Deploy User (Interactive) or Logged on User.
|
Install
|
Installs software using one or more install files. A variety of install file types can be used including scripts which can perform arbitrary tasks.
|
Nested Package
|
Execute other packages within this package.
|
Reboot
|
Reboots the target computer and waits for it to come back online.
|
Sleep
|
Pause the deployment for a number of seconds.
|
Message
|
Uses msg.exe on the target computer to display a message. Messages may be acknowledged by users by clicking OK.
|
File Copy
|
Copies files or folders to target computers.
|
Logoff
|
Logs off interactive logged on sessions.
|
Working with Packages
Packages are created from the Main Window using the New Package menu item or button. They can also be duplicated, imported & exported, and moved between Folders.
Packages are edited using the Package Window and viewed (along with their Deployments and Schedules) using the Package Page in the Main Window.
Package Nesting
Packages (in Pro Mode) can be run from within other packages using Package Nesting.
|