Package Settings
This page details the different settings available for deployed packages
Last updated
Was this helpful?
This page details the different settings available for deployed packages
Last updated
Was this helpful?
For managed packages, you can use the Automation tab to configure automatic publishing of new version of packages from the package store to your environment.
Automate Main Channel - Automatically deploy new versions of this package to your users. ("Main" subscription)
Automate Preview Channel - Automatically deploy new versions of this package to your pilot users. ("Preview" subscription)
The Preview Channel will take the newest version available from the App Store pushing its current version to the main channel.
Recommendation:
Automate only Main Channel for software that can upgrade without prior testing, like web browsers from major vendors.
Automate only Preview Channel for software you want to test before deploying. Push the validated version to Main Channel after testing and start testing the next version in Preview.
You can always manually push a newer version available in Package Store directly to Preview or Main Channel to skip a version you don't want published.
... defer X days - Wait for this number of days to pass before publishing a new version to the channel. This is useful to avoid stress for users/clients if multiple package versions are published rapidly.
Deploy At Night - Schedule automatic deployment during nighttime
Select target timezone - If you use Deploy At Night, use this Time Zone to indicate when "at night" is.
If wanted, you can assign multiple Technical Application Owners (TAO) to a package via storing their email-addresses.
For receiving automated notification emails for package updates, you can enable the switch below in addition.
Arguments allow you to pass command line switches to an application installation. This is commonly used to customise your package with language options, a license key etc. that need to be present at installation time.
Some packages include a Technical Help, to explain possible Arguments and other Requirements.
Allow reinstallation
This option allows the user to reinstall and therefore override their current installation of the package at any time. E.g.: suitable for packages that help fixing client issues via self-service (time sync, ...).
Yes
Allow background installation
Executes package updates directly after configuration updates have been detected on the corresponding device (standard RJ sync interval: 30 minutes). In addition, updates are starting without warning (no snooze option). Do not use this option for regular packages as this might interrupt users when using the corresponding software.
Yes
Require compliance
The package is installed as soon as RealmJoin is able to verify that the device is considered "compliant". This might stop the roll out for some time. The installation of the package and all other mandatory packages with higher order numbers are getting queued and only installed when the client is compliant.
Yes
Pre-Release
Yes
Auto upgrade
Automatically upgrade the package if a newer version gets deployed. So, when the version number of the subscribed package is higher than the installed version on scoped devices, the package will re-run with the current version and perform the update. This option might be turned off for packages with an integrated auto updater or alternative update mechanisms (e.g.: VPN client updated via gateway). So, if the package is updated and "Auto upgrade" switched to "off", only newly installed clients will get the new version installed via RealmJoin. RealmJoin agent: Upgrades required and available packages on the corresponding devices. Intune: Upgrades required packages on the corresponding devices.
No
Only in VDI / Ignore in VDI
Execute this package on VDIs (W365 and Azure Virtual Desktop/WVD) devices only or exclude them from the installation.
Yes
Only on hybrid-joined devices / Ignore on hybrid-joined devices
Execute this package on hybrid-joined devices only or exclude them from the installation.
Yes
Ignore on private devices
Exclude private devices (not Entra ID joined) from the installation.
Yes
Group name
Category in which the package will show up in RealmJoin tray menu.
Yes
Depends on
Indicates if other packages are required before installing this package. RealmJoin will install the listed packages before running the package itself. Take care, that the depended packages are assigned, too (e.g. as "available"). Example: Runtime environment like "Microsoft VC Redistributable Runtime" required for a software to run.
Enter the package ID (see RJ portal "Unique RJ ID" on the desired package) in the following format:
["package-id"]
For multiple packages:
["package-id1","package-id2"]
Example:
["generic-microsoft-vcredist-2019","generic-microsoft-net-core-desktop-runtime-6"]
Yes
Order
The order number is an integer and defines the package installation sequence. The lower the number the higher the importance, therefore a 10 will be installed before 100. Note that "0" is translated to "no sequence" (executed after packages with an order number). In addition, the order number is only taken into account at the initial roll out of a client.
Yes
Dependency and Order should not used on the same package. This might prevent the back-end from correctly resolve the order installation: During the initial rollout, or any rollout of mandatory packages after a login for this purpose, RealmJoin in the first step resolves all dependencies of the packages. If there are any, all packages which are listed as a dependency for a different package are installed. In the second step, the original packages are installed. This may cancel out any order numbers.
For example:
Package A, order 1
Package B, order 101 and depending on Package C, order 100.
If all packages are assigned as mandatory, the installation sequence will be C, A, B
User settings within application packages are treated as a set dependency.
Deployment rate
Select the deployment rate which allows or blocks users from deferring the package installation until the displayed date. You have the choice between "Slow", "Fast" and "Tomorrow". Example: When choosing "Tomorrow", the current date + one day will be stored as fixed value. Users can defer until this date. Afterwards, the installation will just execute without further control. Note that the date is not dynamic (so, not depending on the client's last check in time).
Yes
Main app restrictions
This option allows to define who can run a package installation and when it will happen (phase).
Define whether this package should run just for the primary user of a device (visible and changeable in RealmJoin portal), only secondary users or for both of them.
Choose between the the following phases or combinations of them. Default is "Normal, Initial & Manual".
Logon: The package runs after the user has logged on.
Manual: The package will run when the user starts installation via tray menu manually.
Initial: The package only runs during the initial client deployment.
Normal: Neither Logon, nor Manual, nor Initial. Deployment during the normal usage of a client.
Yes
User part restrictions
Same options as before - but for the user part (if available for the corresponding package). E.g.: contains settings or scripts executed under the current user ("user" instead of "system scope").
Yes
These values can be globally preconfigured for newly imported packages in . Configuring them on a per package basis will overwrite the global defaults.
Legacy setting - see .
