A package is a collection of automated tasks (actions) used to perform administrative tasks on a target device. These tasks may be installing, modifying or uninstalling software or configuring target device's operating system. Packages have a predefined life cycle in Miradore Management Suite. A package consists of one or more actions defined to run in specific order each with its own parameters. Package actions are predefined commands or functions which each utilize one or more parameter.
To run packages on a computer or device, it must have the Miradore client installed. The client applies the package actions one by one and runs the commands included in each action. If all actions are applied successfully, the client returns success result code to the Miradore server. If any action fails, the package installation stops there and the error code, error message and a pointer to the failing action are returned as a result.
Packages never include any installation media. If a packages requires media, such as files, scripts or configuration files, those are always read from a separate file share from the installation point. The correct installation point is dynamically selected for each package distribution so that the closest file share is always used.
Package building and software deployment is supported on the following client platforms: Windows, Linux, and OS X.
More information
Miradore features by desktop platform
To understand the package life cycle, roles and permissions
To understand the Miradore infrastructure components, installation points and their relationship to package building
To understand the item page workspace
To understand the package export and import utility
To understand the package distribution methods in Miradore
To understand the directory structure on the installation point
Create the Package item (Choose Operations > Software management > Packages). Users in the role of administrator or package builder can create packages.
Enter all required information to the Package item and save the Package item page. See Package item attributes for detailed field descriptions.
Open the Package editor tab and add required Package actions > Save the Package item page
Start testing
See Package testing scenarios and basic quality tests.
To install a test package to a device, open the Asset item page > choose Tasks > Package distribution > Test Package / Test uninstall package.
NOTE: Helpdesk operators do not have permissions to test packages even if they are allowed to install it. Notice also that licenses are not required in order to test install packages. Therefore, the package's license information is not checked during the test installation of the package.
If the package passed the testing phase, you can now move on to request the activation of the package. You can send package activation request through the Tasks menu of the Packages view or Package item page.
Users with the role of administrator or package approver can approve the package activation request and activate the package through the Tasks menu of the Packages view or Package item page.
When activating the package, make also sure that the files needed by the package have been copied to the media master installation point..
Test the package once more when it's activated into the production environment.
For examples, please see Package building example: Adobe Reader and Package building example: Microsoft Lync Basic 2013.
See also