LogoLogo
LogoLogo
  • Welcome
    • Navigation
  • RealmJoin Deployment
    • Onboarding
    • Required Permissions
    • Infrastructure Considerations
      • Multi User Devices
    • Migration to RealmJoin vNext
  • User, Group and Device Management
    • Overview
    • User Profile
    • Organization Details
    • User, Group and Device Lists
      • Advanced Search
      • User Details
      • Group Details
      • Device Details
    • User and Group Settings
      • Available RealmJoin Policies
  • App Management
    • Packages
      • Package Store
        • Application Store Details
      • Package Management
      • Package Details
      • Package Assignments
        • Package Migration
      • Package Settings
      • Packaging Requests
        • Organic Packages
    • AVD Templates
  • Automation
    • Connecting Azure Automation
      • Required Permissions
      • Runbook Parameters
    • Runbooks
      • Runbook Customization
      • Runbook Permissions
      • Naming Conventions
      • Runbook Scheduling
      • Runbook Logs
        • Runbook Job Details
      • Runbooks Changelog
    • Requirements
    • Remediation Scripts
  • RealmJoin Agent
    • Features
      • Local Admin Password Solution (LAPS)
        • KeyVault
        • Application Insights
      • Notifications
      • AnyDesk Integration
        • AnyDesk configuration
      • App Deployment using the Agent
        • RealmJoin ESP
    • Deploying the Agent
    • User Interface
  • Logs
    • Connecting Azure Log Analytics Workspace
    • Audit Log
  • RealmJoin Settings
    • Overview
    • General
    • Roles and Permissions
      • Pre-defined Roles
      • Custom Roles
        • Available Permissions
    • Group Namespaces
    • Workplace Cloud Storage
    • Self Service Forms
  • Developer Reference
    • RealmJoin API
      • Authentication
    • Interacting with Runbooks
    • Simulating a Runbook Environment
    • Local Admin Password Management
  • Other
    • FAQ
      • Security
    • Troubleshooting
      • Package Installation Issues
        • Collecting Logfiles
        • Logfiles Structure
        • Analysing chocolatey.log
        • Troubleshooting failed chocolatey packages
        • Troubleshooting failed craft packages
        • Fixes for common issues
        • Intunewin Debugging
      • LAPS Issues
        • LAPS account passwords cannot be retrieved
        • Requested LAPS Accounts are not being created
    • Changelog
  • Legal
    • Licensing
    • Support
  • RealmJoin Website
Powered by GitBook
On this page
  • Subscription
  • Managed Deployment
  • Basic

Was this helpful?

Edit on GitHub
  1. App Management
  2. Packages

Package Assignments

Last updated 6 months ago

Was this helpful?

Subscription

On the Overview Tab of a package, you will find buttons, that allow you to import the package from the store into your environment.

They will create a Win32 software package in Intune when pressed. You have two options:

Managed Deployment

When a Managed package is chosen, RealmJoin will create Microsoft Entra groups to assign the application to users. These groups can be managed from both the RealmJoin Portal and Microsoft Entra ID. Managed deployment will automatically create four RealmJoin-managed groups:

The created Entra ID groups can be managed from both the RealmJoin Portal and Microsoft Entra ID.

Main (Blank)

RealmJoin or Intune will automatically install the application. These applications are mandatory and RealmJoin/Intune will continually attempt to install the application if not found on the device.

Available

The application will appear in the RealmJoin Agent tray and will require the user to initiate the download and installation

The application will appear in Company Portal -> Apps and will require the user to initiate the download and installation

Preview

Uninstall

RealmJoin or Intune will uninstall the package from the assigned users and devices. Adding a user or device to the Uninstall group will remove them from all other groups.

Update

Additionally, RealmJoin provides an Update group that is created on demand. The Update group will automatically onboard loose installations of a software title into management.

Click Enable Update Group and a new EntraID Group with the suffix "(update)" will be created and software installations also assigned to this group. RealmJoin will dynamically discover installed copies of the software that are unmanaged and add the device it has been discovered on to the update group.

Thus, new version of this software will also be installed on these devices to assert deployment of security patches across your environment.

Managed packages are the preferred way to deploy software to your users. You can combine it with automated package updates and ensure your users receive latest features and patches.

Changing Assignments

Users and devices should only be in one RealmJoin managed group at any given time.

Users and devices can easily be moved across groups using the Managed Users function.

Selecting Main, Preview, Available and Uninstall will add the user to the chosen group and remove the user from all other groups relevant to the package.

Selecting Assign will add users to the Main group by default.

Basic

Basic packages do not have any associated Microsoft Entra groups. You will have to manually assign groups, devices or users.

Groups, devices and users that are assigned to a Basic package will be assigned as Available by default and can be changed using the [change settings] button.

Users and devices in the Preview group will receive the latest version of the package before the other groups. Preview settings are configurable through the .

Automation tab
Subscribe Buttons
Application Groups
Enable an Update Group
Update Group Enabled