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
      • 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
        • RealmJoin Tasks
        • Customer Tasks
      • App Deployment using the Agent
        • RealmJoin ESP
    • Deploying the Agent
    • User Interface
  • Logs
    • Connecting Azure Log Analytics Workspace
    • Audit Log
  • RealmJoin Settings
    • Overview
    • General
    • Permissions
    • Group Namespaces
    • Workplace Cloud Storage
    • Self Service Forms
    • Custom Roles
      • Available Permissions
  • 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
  • Request Types
  • New Packages
  • Package Updates

Was this helpful?

Edit on GitHub
  1. App Management
  2. Packages

Packaging Requests

Last updated 7 months ago

Was this helpful?

RealmJoin offers a Packaging-as-a-Services (PACKaaS) if application packages are required, that are not already available in the RJ store, or are outdated. This section shall give a comprehensive overview over different scenarios. For more detailed information get in touch with your RealmJoin consultant/partner/support.

Request Types

Three different PACKaaS requests are currently available: new package, update existing package and organic packages.

New Packages

If the application required is not already available in the RealmJoin store, it can be requested to be packaged via the RealmJoin packaging factory. A valid PACKaaS request must contain at least the following:

  • The binaries. A download URL is not sufficient, but might be provided for reference.

  • A documentation. All required configuration switches must be provided as command line parameters or registry keys or config files or similar. Screenshots are not sufficient. PACKaaS does not include Scripting-as-a-Service.

If the application package does not contain any customer specific information, it will be added as generic package to the public RealmJoin store, and if possible as a maintained package. All other application packages will be created as custom/private packaging. For fees please refer to the subscribed RealmJoin license options.

Package Updates

If an application is required in a newer version than available in the RealmJoin store, the same processes and rules apply as for the New Packages listed above. If the updated binary behaves exactly as the available version, command line parameters can be omitted in the request.

Note: Additional switches, new parameters or configuration files for an existing package are considered updates and shall be requested the identical way.

Tickets, Files and Setup

Please note that:

  • all requests need a file attached to be created successfully. Requests without any file upload are not submitted.

  • the request creates a ticket. All communication will be handled in this ticket, and it will only be sent to the account that created it. If this account does not have any active mailbox, the requester will not get any information.

  • the software requester role can be assigned to any user group in the tenant, therefore, an ADM account may not be required.

  • organic packages and PACKaaS might be not available right away, please get in touch with support@realmjoin.com if a feature is missing

Update and New package requests necessitate the provision of both binaries and documentation detailing the required command line parameters. If an update request does not entail changes from the previous version, the submission of new parameters is not required. All types of requests mandate a file upload, after which the generated ticket will be dispatched to the requesting account. Organic packages, offered at no cost, automatically extract the contents of the provided zip file to the C:\Install directory.

RealmJoin packaging request form