Package item attributes

Main: General

Attribute name	Description
Package type	Package type describes which kind of tasks the package includes. Packages can include tasks related to installation, uninstallation or both. Possible package types are: Install Uninstall Install and uninstall Notice that package type is always "Install and uninstall" when the package status is "Under construction". If package status is either "Sent for approval" or "Approved", the package type is calculated based on enabled actions inside the package.
Status	A package item can have following system statuses: Under construction Active Waiting for approval Archived Removed The field may also include release and/or archive date. The release date displays when the package was activated, and the archive date shows when the package was archived. See also: Package life cycle.
Full name	Computed field. Package name is computed based on the fields below. See package naming.
Software name	Choose the managed software. This field is mandatory.
Package version	Set the internal version of the package. This field is mandatory.
Software platform	Choose the operating systems on which this package is allowed to be installed (requires installation and software testing on all of the selected operating systems).
Optional specification	Enter additional description to be added into package name, for example the specific system name for which this package is configured.
Description	You may enter free description of the package. This field is optional.

Main: Supported operating systems

Field name	Description
Defined by category	Supported operating systems are chosen by the category and subcategory in which they belong.
Manual selection	Supported operating systems may be chosen manually.

Main: Restrictions

Field name	Description
Name	Name of the restriction, i.e. installation scope.
Description	Installation scope description.
Type	Type (Allow/Deny) determines whether the scope allows or denies the installation this package to devices that are inside the defined scope. If the type is "Deny", the package cannot be installed to assets that match with the scope. Notice that if the installation scope denies the installation of the package for certain assets (for example, assets in certain location), the package cannot be added as "asset specific package" for the assets. Also activating the initial installation is prevented, if the installation of all packages is not allowed for the target asset.
Applies to	Applies to -selection determines the target assets of the installation scope. The installations can be restricted by asset group, device role, location, and organisation. Notice that a package cannot be added as "asset specific package" for an asset which does not fit inside the installation scope of the package.

Notice!

If any package installation scopes are not defined, the package is allowed for all assets.
A package can have multiple installation scopes and the scope numbers determine the priority of the scopes. A matching scope with highest priority is always used to determine whether the package is allowed for the asset or not. Drag and drop the installation scopes to change the priority if necessary.

Main: Media locations

Field name	Description
Free space (MB)	Enter the required free disk space for this software. Target computer is tested based on this limit before installation and package stops if the limit is not reached. This field is mandatory.
Installation folder	The target installation folder path.
Installation drive	Enter the drive where the application will be installed. Used also in the free space check (see Free space). Default: C
Media folder	Choose the path where the installation media can be found. Media folder is meant for storing clean installation media without any customizations or customer related data. This folder is useful for service providers with multiple customers because the contents of this folder can be basically copy-pasted when setting up new Miradore instances for other customers.
Package folder	Choose the path where the customer-specific packages can be found. Package folder contains all the files customized for each customer (e.g. scripts, configuration files including license keys and so on).

Main: Responsible persons

Field name	Description
Approver	Choose the person who approved/activated the package. This field is optional.
Builder	Choose the person who built and tested the package. This field is optional.
Configuration	Choose the person who knows how the software must be installed and configured in order to make it work correctly. This field is optional.

Main: Properties

Field name	Description
Initial install only	Choose Yes for packages, which are not meant to be installed separately, only as a part of initial install. Default: No
Group distributable	Choose Yes for packages, which can and are allowed to be group distributed (package has to be tested to work on unlocked/locked computer). Default: No
Hide messages	Choose Yes for packages meant to run totally silently (suppresses also standard start and end messages). Default: No
Add/remove asset binding	Choose Yes for packages which should be bind into device specific packages. Default: No
Interacts with desktop	Choose Yes for packages requiring interaction with visible "user" desktop. For example packages automated with AutoIt require the setup interface to be shown. Default: No
Allowed for helpdesk	This field defines if Miradore users with the role of Helpdesk are allowed to distribute the package to managed assets. If "Allowed for helpdesk = No", helpdesk users cannot distribute the package to any assets. If the field value "Yes", then helpdesk users can distribute the package to assets through the Asset configuration item's Tasks menu. Helpdesk users can never create or activate installation packages. Default value: No
Map installation point	Choose the correct option for installation point mapping. Network share: Choose this option if you want to use an installation point located on a local network share to distribute this package. This is the recommended option for deploying packages to computers which are connected to company network. HTTP: Choose this option if you want to use an HTTP installation point to distribute this package. Use this option if the package will be deployed to computers which are not connected to company network, meaning they cannot connect to the installation points on the local network shares. No: Choose No for packages which do not need any files from installation point during package installation.
Package timeout (min)	Enter the package installation timeout in minutes. This value will override the default value set in system settings . If left empty, package installation will use the default system settings value.
Limit concurrent installations	This field defines whether the location-specific limit for concurrent package installations is taken into account when this particular package is distributed to managed assets. The limitation for concurrent installations is ignored if the setting has not been configured for the target asset's location or it's parent locations. If this field is set to "No", then the package will be distributed to assets without checking the number of concurrent package distributions, no matter what has been configured with the location items. If this field is set to "Yes", then Miradore Management Suite checks the number of on-going package distributions in the target location before it starts new package deployments. If the limit for the concurrent package distributions is reached, new package distributions are not started. The system attempts to start the package distributions again when Miradore client from the target asset polls Miradore server for the next time. Notice that there is an Analyze tab at the Location item page, which is handy for tracking and troubleshooting package deployments if they get jammed.
Limit bandwidth for file copying	This field defines whether the location-specific limit for bandwidth usage is taken into account when executing the "copy file/folder" package action of this particular package in managed assets. The bandwidth limitation is ignored if the setting has not been configured for the target asset's location or it's parent locations. If this field is set to "No", the package will be executed in managed assets without any limitations to the bandwidth usage, no matter what has been configured at the asset's location. If this field is set to "Yes", Miradore client checks the maximum allowed bandwidth consumption limit from the location where the asset is assigned to when the distribution starts, and then executes the package action accordingly. If no limit has been configured at the Location item, the limit will be inherited from the location's parent location. If there is no parent location, or if the limit hasn't been configured for any of the parent locations, then the package will be executed without any limits for the bandwidth usage. Notice: The bandwidth limit doesn't have any effect on other package actions. It only determines whether the bandwidth usage limit for the "copy file/folder" package action is enabled or not on the Windows platform. The bandwidth limit for file copying will not be taken into account if either the source or the destination is not a network file system.
Pinned package	Miradore users can use this field to pin the most important or frequently needed packages to the top of the list in the package selection window that appears, for example, when user distributes a package to an asset through the Asset configuration item's Tasks menu. For more information, please read Pinned packages.
Run as	This setting defines the context in which the installation package will be executed. The options are: Miradore client (default) executes the package in the context of MiradoreClient, which is a local user account managed by the Miradore Client. Although, the account is not a member of any administrative groups, the installation process has administrative permissions. SYSTEM executes the package in the context of a local SYSTEM account. Administrator executes the package in the context of a local Windows built-in administrator account. The use of this options requires that "Miradore set administrator password" package has been executed successfully in the target device(s), because otherwise the administrator password is not known and the package fails with the error 1326 (logon failure: unknown username or bad password). You can attach the password package to the initial installation, or you can deploy it manually to a device through the Asset configuration item's Tasks > Custom tools > Reset local administrator password. Logged in user (any) executes the package in the context of a logged in user. When selecting the session, a console session is preferred. If any console sessions don't exists, then the first remote session will be used. Notice that if the logged in user is not having administrative permissions, then also the installation process lacks the administrative permissions. Logged in user (responsible person) executes the package in the context of a logged user IF the logger user is the asset's responsible person in Miradore Management Suite. The package installation fails with an error code 17015 if the asset's responsible person is not logged in. Notice that if the logged in user is not having administrative permissions, then also the installation process lacks the administrative permissions. Custom executes the package using the username and password specified in the Run as account field. Notice that this feature is supported by Miradore clients for Windows 3.5.0 and newer. Older clients will always use the default MiradoreClient context.
Run as account	This field specifies the username and password that are used to run this package in a managed device. The defined account can be either a local account or a domain account. When using a domain account, remember to fill in the domain prefix in front of the username (e.g. TRESTACOM\uid00001). With local accounts, the prefix is not needed. This field is only visible in the user interface if Run as = Custom.

Main: Prerequirement packages

Field name	Description
Packages	Select the prerequirement package from the list. Also, reboot after the package installation can be enabled. Prerequirement packages are not chained when installing so that only the configured prerequirement packages for the package to be deployed will get installed, not their prerequirements.

Main: Self service portal settings

Field name	Description
Show in self service portal	Choose Yes for packages, which are wanted to be shown in self service portal. Default: No
Display name	Display name is shown to end user on the Self service portal as the name of the package. If the field is left empty, a full name of the package is shown. This field is optional.
Information for users	Available if "show in self service portal = Yes". Enter a comment that will be shown to the user installing/requesting this package at the self service portal. This field is optional.
Approval workflow enabled	Available if "Show in self service portal = Yes". Choose Yes for packages that require an approval workflow prior to installation. Default: No Related information in article How to request for a software using Self-service portal.
Require approval from all approvers	Available if "Approval workflow enabled = Yes". If multiple approvers have been defined for the package, this defines whether all the approvers are required to approve the package installation request. If "Require approval from all approvers = No", then any of the defined approvers can approve the package installation request alone.
Approvers	Available if show in self service portal = Yes. Choose the approver(s) that must approve the installation of this package when requested via the Self service portal. If approval workflow is enabled, at least one approver must be defined.
Information for approvers	Available if show in self service portal = Yes. Enter a comment that will be shown to the approver(s). This field is optional.

Main: Additional information

Field name

Description

Attachments

An attachment file can be added here. About attaching files. This field is optional.

Comments

Comment about this package can be added here. This field is optional.