Managing RealmJoin

Administrative users have access to the RealmJoin administrator console. As RealmJoin is highly compatible with Microsoft Intune and Microsoft Azure, it incorporates the same group based user and policy management experience and uses the Azure AD defined groups as basis for software deployment. The default interval for group synchronization between Azure AD and RealmJoin is 15 minutes, while only groups with a defined prefix are taken into consideration. Only groups with at least one assigned user are syncronized, and the syncronization interval can be adjusted.

User Client

The RealmJoin client is enrolled on evey Windows 10 device. RealmJoin seamlessly fits into the modern workplace with its focus on user self-service and mobility. Using the RealmJoin client module, the user may install provided software, get basic information on the device and membership in the tenant domain wihout the need of contact an IT administrative.

Initial Start

When RealmJoin is enrolled and started for the first time, it asks for the User-Identity and then calls to the cloud Service for a policy.


RealmJoin “Security Requirement” assessment does some pre-checks (Encryption, Patch Level, Firewall, Anti-Virus, etc. – this is optional and can be replaced in parts by Intune-Health-Check). In the last step, all mandatory software will be installed (black screen installation). During this installation, any interaction with the client is suppressed.

RJ Sec Check

If no error occurs during deployment, RealmJoin is ready to use.

Client usage

After being successfully installed, RealmJoin is automatically started on the user login and is permanent active in the background. It is represented with an ID card icon. Clicking on the icon opens up the RealmJoin client menu. It contains basic information in the lower and a number of links in the upper part. The selector Software Packages opens a second context menu with all the software packages that are allocated to the user.

RJ Tray

If a user wishes to install any of the listed software, he/she is only required to select the package to start the installation.

RJ Add Package

The installation mode depends on the packages selected: If those are only user mode packages, they are installed immediately. In case of a higher permission level, RealmJoin starts a service (realmjoinservice.exe) and installs the packages with the SYSTEM user account.

Debug Mode

If neccessary, a debug window can be opened by clicking on the RealmJoin icon while pressing Shift+Strg on the keyboard. This reveals a new entry in the context menu listed as Show Debug Window. This window offers seven different diagnostic tools. If a device is not able to be addressed by the server or can not connect to the backend, this tool will provide the user with the tools for the first steps of diagnosis. Another new tray menu entry showing up in debug mode is Retry base installation, which allows the user to reinstall the RealmJoin client. Additionally, when the client tray menu is opened in debug mode, all packages are shown with the package version number.

RJ Debug Menu

Collect Logs is a quick way to access all log files, which will be saved in a zip-file to the users desktop. See chapter troubleshooting for a detailed description of the RealmJoin debug window and its features.

RealmJoin Portal

Device provisioning and RealmJoin configuration is done with the RealmJoin portal. Designed to mirror the style of the new Microsoft administration services, it is the main tool for the management of the RealmJoin clients and users. The web application can be reached under or the beta version under

RJ Dashboard

The dashboard provides a quick and beneficial overview. All sections can be accessed by either clicking on the corresponding number or selecting the section in the toolbar on the left.


There are two different roles available for the RealmJoin portal:

  • Administrator: Full rights within the portal.
  • Auditor: Read-only rights within the portal, access to all settings and assignments.


RJ clientsiconThe clients tab gives you a transparent overview over all enrolled devices as well as the respective primary user. To enter the devices’ states (see section States) or associate users, just click on the green numbers on the right. In this details you find two JSON files with basic information on the client and the primary user. It is possible change the primary device user if there is an inconsistency between the Azure and the RealmJoin portal. This might happen if a device is not correctly reseted and issued to a new user afterwards.Client:

  "id": 3714,
  "clientID": "f19c3d1a-75e3-0000-afe9-f8d3da72e2f1",
  "firstSeen": "2017-09-26T08:10:46.3211008",
  "lastSeen": "2018-03-20T14:50:25.4933509",
  "lastMachineName": "DESKTOP-B0815",
  "lastVersion": "4.11.6+25493.9f206a6d",
  "primaryUserID": 6325,
  "primaryUserName": "",
  "stateCount": 7242,
  "userCount": 0

Primary User:

  "id": 6325,
  "userID": "3239d4dd-0000-0000-90d6-611a7fd93dba",
  "userName": "",
  "graphUser": {
    "displayName": "testuser",
    "department": null,
    "jobTitle": null,
    "mail": "",
    "city": null,
    "officeLocation": null,
    "businessPhones": [],
    "mobilePhone": null

NOTE: It is important to understand, that the userID is equal to the userID from the Azure identity management, while the clientID is the ID Windows submitts during the installation and NOT equal to the clientID in Azure/Intune.


RJ rj-ac-usersiconA list of all users assigned to the tenant. The selectable details on the right include states, group membership, installed software packages, client devices and (to come…) individual settings. Users can’t be added or assigned to groups using RealmJoin, the management of users and groups has to be done in Azure AD. Selecting a user opens up the users detail page, which contains information gathered by RealmJoin using the Microsoft Graph API.

User settings

RJ usersettingsiconConfigurable group settings and policies. See section Policies for a list of implemented features. See Group Settings for a detailed description on configurating policies.


RJ rj-ac-groupsiconAll in this tenant registered user groups. RealmJoin synchronizes groups from Azure Active Directory into the RealmJoin backend. The details on the right contain users within the individual group, packages that are assigned to a group as well as group settings. Since not all users in Azure AD might be equipped with RealmJoin, only a specified range of groups are transfered into RealmJoin (depending on the group name). The groups can not be added or altered within RealmJoin, therefore the group naming conventions have to be established in advance.

While there are not strict naming pattern requirements in RealmJoin, we recommend the following convention:

*APP|CFG - Location-[Vendor-Product-Language-Type-Flavor]*  


CFG - Global-Core  
CFG - DE-Core  
CFG - DE7499-Core  
APP - Adobe-Photoshop  
APP - Microsoft-Visio  
APP - Mozilla-Firefox  
APP - Mozilla-Firefox-PreRelease  
APP - Mozilla-Firefox-Optional  
APP - Mozilla-Firefox-Optional-PreRelease  
APP - Mozilla-Firefox-x86  
APP - Mozilla-Firefox-x64  
APP - Mozilla-Firefox-DE7499  
APP - Mozilla-Firefox-withFlash  

The standard sychronization time is 20 minutes (hh:00, hh:20, hh:40), and all groups that start with *APP - * or *CFG - * are taking into consideration.The synchronization time schedule and the prefixes that are taken into account can be adjusted, currently only on request. Groups won’t be deleted from the RealmJoin backend, if they are removed in Azure/Intune.NOTE: The RealmJoin - All Users group is automatically created, containg all users with a RealmJoin installation on at least one of their clients.

Group settings

RJ rj-ac-groupsettingsiconConfigurable group settings and policies. See chapter policies for a list of implemented features. To change a policy, you have to first select the group, and then select the group settings number on the right. This will open the group settings web page with a filter on the selected group, allowing to create policies for this group. To configure a policy, add the tree path in the key field and the setting in the value section, e.g.:Policies.SetCurrentUserAdministratortrueto set a user or the users within the group to local administrators or set Key WebLinks with the following Value:

    "Name": "RealmJoin",
    "Target": "",
    "Platform": "any"
    "Name": "Google",
    "Target": "",
    "Platform": "any"

This creates new links available in the RealmJoin client tray. The created settings overwrite all default values.

Software Packages

RJ rj-ac-packagesiconA list of all added packages. The detail list contains the package version, install order, auto upgradibility and user/group assignment.

Add packages

The administrator is able to add created craft and choco packages to RealmJoin using the Add Choco / Add Craft buttons. This open the package setup window.

RJ rj-ac-packages

There are two ways to add the neccessary information: Entering the required fields Name, Version, Chocolatey Package ID (Chocolatey packages only), ID (Chocolatey Package ID and ID are usually similar), Location, Hash and Scope (all three craft packages only) manually or pasting the JSON code, which can be found in the corresponding package repository (pipeline).

RJ package-json-pipeline

While adding a package the following configuration entries are available:

  • Name

    • The name under which the package is listed in the client and RealmJoin admin console. Otherwise not used as an unique identifier.
  • GroupName

    • An optional group name may be entered. This name has no connection to the user groups, instead it will be shown in the RealmJoin client context menu to group the depicted applications.
  • ID

    • The RealmJoin internal name of the package, for example generic-videolan-vlc.
  • DependsOn

    • The DependsOn option is used to indicate if a package needs another package to be installed to work properly. This may be the case for Office user setting packages, that require an office installation upfront. It is possible to hide packages, so that the client context menu only shows one installation option (see section Package Assignment), but all involved packages have to be assigned to the user group for dependencies to work.For a working correlation, the correct package name has to be provided. If there is a multiple level-dependency, RealmJoin takes this into consideration. Before the installation process, all dependency-related packages are sorted (also including mandatories) and installed afterwards. The following images show the assignment of package dependency for the chocolatey package Microsoft Office 2016 ProPlus, which will be installed with usersettings:

      RJ package-dependency

      The user setting package Microsoft Office 2016 ProPlus ML UserSettings is assigned as usual, with the ID of the parent package generic-microsoft-office-2016-proplus entered as DependsOn. During the installation process in the RealmJoin client, RealmJoin understands the need of the generic-microsoft-office-2016-proplus package and installs the deployed version of it first.

      RJ dependency-installationRealmJoin takes 1:n dependenciey into account. It is possible to add more than one dependency using the synthax:["package-id-1","package-id-2"]

  • Order

    • The order number is an Int32 type figure and provides RealmJoin with a basic structure to determine the package installation sequence. The lower the number the higher the importance, therefore a 10 will be installed before 100. It has to be noted that a 0 is translated to “no sequence given” and the order number is only taken into account at the first roll out.
  • Args

    • If the packaged software has to be installed with arguments. If the package to be deployed is a chocolatey package, make sure to use the prefix -params and correct escaping, since chocolatey might mistake the arguments to be directed to it, for craft packages, the arguments can just be added.It has to be noted, that it is also possible to provide arguments in the package assignment stage (see section below). Globally relevant parameters (e.g. volume license number) should be provided at the package addition step, while more individualized arguments (e.g. language packs) are better specified during the assignment step.

NOTE: Do not use the dependency and order option on mandatory packages parallel. This might prevent the backend from correctly resolve the order installation: During the initial rollout, or any rollout of mandatory packages after a log-in 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. E.g.:Package A, order 1. Package B, order 101 and dependend on Package C, order 100. If all packages are assigned as mandatory, the installation sequence will be C - A - B.

  • Version
    • Version of the package to be installed (for conventions of the version numbering see chapter Packages).
  • Chocolatey Package ID (chocolatey packages only)
    • Exact chocolatey repository name of the package to be installed. The combination of name and version is used ensure that the correct package is installed. Usually similar to the internal RealmJoin ID.
  • Location (craft only)
    • Location of the package on the backend.
  • Hash (craft only)
    • Hash of the package
  • Scope
    • Craft packages might be installed in the user or system scope.


  • Availability

    • Allow Reinstall: This option allows the client user to reinstall and therefore override their current installation of the package. In case of craft type packages, the craft scripts are re-run.
    • Allow Background Install: The software package may be installed outside of the black screen installation, thus not blocking the access to the clients desktop and software.
    • Pre-Release: The pre-release flag as two distinctive features within RealmJoin. It allows a) to add a package with ID and version similar to another existing package in the portal and b), if assigned to a group or user, overwrites all other packages with the same ID assigned to the group or user.Those features are usually used for the testing of new packages or updates of existing one: The test-groups or test-users get the pre-release version of a package assigned during the testing.Note: Under normal circumstance it is highly advised to prevent a normal user having the same package assigned more than once.The pre-release flagged package is visually highlighted in the portal’s package list with an lightning symbol behind the name.
    • Require Intune Compliance (BETA): The package is installed, as soon as RealmJoin is able to verify via the GraphAPI that the machine is considered compliant. This might stop the rollout for some time. The installation of the package, and therefore all other mandatory packages with higher order numbers that are queued to be installed afterwards, is resumed when the client is compliant.
  • Auto Upgrade

    • The Auto Upgrade feature may be enabled to automatically update the package if a new version is assigned in RealmJoin. If not chosen, the user has to manually select the package to be upgraded. The automatic upgrade does apply to mandatory and non-mandatory packages.
  • Staggered Deployment

    • It is possible to use staggered deployment and distribute the risk of updating a software if desired. The two parameters needed are the target date and the amount of days over which the update should take place. The clients are not equally distributed in the deployment groups, with fewer deployments in the first part of the timeline and the majority on the last. Deployed package versions for each can be found in the user details of the package or the deployed package details of the users. Example distribution for n = 10000 and 8 days update time:

      RJ autoupdate_sim

NOTE: Do not edit assigned packages in the way, that you change the package name or ID (version number is fine). If you need a package in a different flavour, please add a new package and delete the obsolete one.

Advanced Options

With RealmJoin version 4.13 a new feature was published: the support of multi user devices. To represent these scenarios within the RealmJoin, advanced options are available when configuring a package.

RJ advanced optionsTo access this plane, press the Show Advanced Options button on the right. All new options will be available:

  • Includes User Script
    • In the latest generation of packages, it is not necessary anymore to create a second package for the deployment of corresponding user settings, but such a script can be part of the main package. If this is the case, it will be run automatically if this options is checked. Parameters can be transferred via arguments as established. User scripts will not run for secondary users if the main application is not installed.
  • Main Script Restrictions: Users
    • This option allows the RealmJoin administrator to define whether this package should run for just the primary device user (default) or also/exclusively for secondary users.
  • Main Script Restrictions: Phases
    • This options allows the RealmJoin administrator to define whether this package should be run during the initial provisioning of the device or during other phases.

Duplicate a package

Whenever a package with identical content is needed multiple times for the same user or group, the RealmJoin portal offers the possibility to use the same package multiple times while preventing conflicting installations.

A possible scenario may be: One user group needs the same package with different arguments (for example to map several network drives) and the RJ-Client requires unique package IDs.

  • Notation
    • To make the ID unique, a hash is written behind the ID and provided with a meaningful word/index, for example “package-id#Value”.

RJ rj-duplicate-packages

Assign Packages

Similar to the profile management with Microsoft Azure AD, packages can be assigned to groups and individual users. To assign a package, enter the group or user detail for the package in the package control panel. There are four options to override the package configuration when assigning, if in conflict with the package settings, the assignment settings override:

  • Availability
    • Packages can be labeled as mandatory to make the software package non-optional.
    • Packages might also be labeled as hidden, making them invisible in the RealmJoin client context menu. This might be used for mandatory software or for multiple level dependencies, when the user should only be able to install the highest hierachie and the underlying packages should be installed automatically.
  • Auto Upgrade
    • In addition to the configuration of the package itself (see section above for the feature description), auto upgrade can be enabled for the selected group / user individually.
  • Staggered Deployment
    • In addition to the configuration of the package itself (see section above for the feature description), staggered deployment can be enabled for the selected group / user individually.
  • Args
    • In addition to the configuration of the package itself (see section above for the feature description), Args can be set for the selected group / user individually.
  • Advanced Options

RJ rj-ac-packageoverrides


RJ rj-ac-statesiconGlück & Kanja maintains an ever-expanding library of ready-to-go applications that might instantly be added to the list of available packages and assigned to groups or users. For details, please check the AppStore section in the application sources chapter.


RJ rj-ac-statesiconThe states detail of the client or user control panel provides a list of the devices of the user and how frequently data was upstreamed. The Branch Cache column indicates how much this client has contributed to the package distribution over the Branch Cache feature (see chapter Infrastructure). Selecting the white arrow in the green circle returns the complete upstream file. It contains all the information about the device, OS, Defender Pattern States and installed packages that are transfered to the backend, where some of it is evaluated.

RJ rj-ac-states

It is possible to extend the states by custom states. See Custom States for details.


List of states

Information on the device:
Basic Client Information
  "Type": "win",
  "ClientID": "75cf4d56-0676-ae02-73ad-a1af9b89f269",
  "VersionTray": "4.9.15-canary+14869.bf207295",
  "VersionService": "4.9.15-canary+14869.bf207295",
  "OperatingSystem": {
    "Name": "Windows 10 Enterprise",
    "Edition": "Enterprise",
    "CompositionEdition": "Enterprise",
    "Version": "10.0.14393.0",
    "ReleaseID": "1607",
    "BuildBranch": "rs1_release",
    "Build": 14393,
    "BuildRevision": 0,
    "InstallDate": "2017-08-16T12:53:01Z",
    "Bits": 64,
    "Activated": false
  "MachineName": "DESKTOP-VH66R7X",
  "DomainName": "LEGACYDOMAIN",
  "JoinedDomainName": "legacydomain.local",
  "HostName": "DESKTOP-VH66R7X",
  "Timestamp": "2017-09-14T07:07:39.2543111+00:00",
  "User": {
    "LocalName": "JONDOE",
    "LocalLogonAt": "2017-09-14T07:07:06.3167385+00:00",
    "IsAdministrator": false
  "Firewall": {
    "ProfileStates": [

| Key | Value | SubKey | SubValue || — | — | — | — | | “Type”: | “win”, | | || “ClientID”: | “75cf4d56-0676-ae02-73ad-a1af9b89f269”, | | || “VersionTray”: | “4.9.15-canary+14869.bf207295”, | | || “VersionService”: | “4.9.15-canary+14869.bf207295”, | | || “OperatingSystem”: | { | | || | | “Name”: | “Windows 10 Enterprise”, || | | “Edition”: | “Enterprise”, || | | “CompositionEdition”: | “Enterprise”, || | | “Version”: | “10.0.14393.0”, || | | “ReleaseID”: | “1607”, || | | “BuildBranch”: | “rs1_release”, || | | “Build”: | 14393, || | | “BuildRevision”: | 0, || | | “InstallDate”: | “2017-08-16T12:53:01Z”, || | | “Bits”: | 64, || | | “Activated”: | false, || | }, | | || “MachineName”: | “DESKTOP-VH66R7X”, | | | | “DomainName”: | “LEGACYDOMAIN”, | | || “JoinedDomainName”: | “legacydomain.local”, | | || “HostName”: | “DESKTOP-0815VHX”, | | || “Timestamp”: | “2017-09-14T07:07:39.2543111+00:00”, | | || “User”: | { | | || | | “LocalName”: | “JONDOE”, || | | “LocalLogonAt”: | “2017-09-14T07:07:06.3167385+00:00”, || | | “IsAdministrator”: | false || | }, | | || “Firewall”: | { | | || | | “ProfileStates”: | [
]|| | }, | | |

Antivirus information and patterns
  "AvProducts": {
    "Installed": [
        "Name": "Windows Defender",
        "State": 397568,
        "Details": {
          "AMEngineVersion": "1.1.14003.0",
          "AMProductVersion": "4.10.14393.0",
          "AMServiceEnabled": true,
          "AMServiceVersion": "4.10.14393.0",
          "AntispywareEnabled": true,
          "AntispywareSignatureAge": 29,
          "AntispywareSignatureLastUpdated": "2017-08-15T14:37:45+00:00",
          "AntispywareSignatureVersion": "1.249.1077.0",
          "AntivirusEnabled": true,
          "AntivirusSignatureAge": 29,
          "AntivirusSignatureLastUpdated": "2017-08-15T14:37:46+00:00",
          "AntivirusSignatureVersion": "1.249.1077.0",
          "BehaviorMonitorEnabled": true,
          "ComputerID": "829DE85B-7B39-4093-85F1-6AEF62AC65DD",
          "ComputerState": 0,
          "FullScanAge": 4294967295,
          "FullScanEndTime": null,
          "FullScanStartTime": null,
          "IoavProtectionEnabled": true,
          "LastFullScanSource": 0,
          "LastQuickScanSource": 0,
          "NISEnabled": true,
          "NISEngineVersion": "2.1.13804.0",
          "NISSignatureAge": 0,
          "NISSignatureLastUpdated": "2017-09-14T07:06:25.604+00:00",
          "NISSignatureVersion": "",
          "OnAccessProtectionEnabled": true,
          "QuickScanAge": 4294967295,
          "QuickScanEndTime": null,
          "QuickScanStartTime": null,
          "RealTimeProtectionEnabled": true,
          "RealTimeScanDirection": 0,
          "PSComputerName": null

“AvProducts”: {

| Key | Value | SubKey | SubValue | | | | — | — | — | — | — |— | | “Installed”: | [ | | | | | | “Name”: | “Windows Defender”, | | | | | | “State”: | 397568, | | | | | | “Details”: | { | | | | | | | “AMEngineVersion”: | “1.1.14003.0”, | | | | | | “AMProductVersion”: | “4.10.14393.0”, | | | | | | “AMServiceEnabled”: | true, | | | | | | “AMServiceVersion”: | “4.10.14393.0”, | | | | | | “AntispywareEnabled”: | true, | | | | | | “AntispywareSignatureAge”: | 29, | | | | | | “AntispywareSignatureLastUpdated”: | “2017-08-15T14:37:45+00:00”, | | | | | | “AntispywareSignatureVersion”: | “1.249.1077.0”, | | | | | | “AntivirusEnabled”: | true, | | | | | | “AntivirusSignatureAge”: | 29, | | | | | | “AntivirusSignatureLastUpdated”: | “2017-08-15T14:37:46+00:00”, | | | | | | “AntivirusSignatureVersion”: | “1.249.1077.0”, | | | | | | “BehaviorMonitorEnabled”: | true, | | | | | | “ComputerID”: | “829DE85B-7B39-4093-85F1-6A62AC65DD”,| | | | | | “ComputerState”: | 0, | | | | | | “FullScanAge”: | 4294967295, | | | | | | “FullScanEndTime”: | null, | | | | | | “FullScanStartTime”: | null, | | | | | | “IoavProtectionEnabled”: | true, | | | | | | “LastFullScanSource”: | “1.1.14003.0”, | | | | | | “NISEnabled”: | true, | | | | | | “NISEngineVersion”: | “2.1.13804.0”, | | | | | | “NISSignatureAge”: | 0, | | | | | | “NISSignatureLastUpdated”: | “2017-09-14T07:06:25.604+00:00”, | | | | | | “NISSignatureVersion”: | “”, | | | | | | “OnAccessProtectionEnabled”: | true, | | | | | | “QuickScanAge”: | 4294967295, | | | | | | “QuickScanEndTime”: | null, | | | | | | “QuickScanStartTime”: | null, | | | | | | “RealTimeProtectionEnabled”: | true,| | | | | | “RealTimeScanDirection”: | 0, | | | | | | “PSComputerName”: | null | | | | | | } | | | | | | | } | | | | | | | ] | | | | |

Bitlocker status
  "Bitlocker": {
    "DriveStates": [
        "ComputerName": "DESKTOP-0815VHX",
        "MountPoint": "C:",
        "EncryptionMethod": 0,
        "AutoUnlockEnabled": null,
        "AutoUnlockKeyStored": null,
        "MetadataVersion": 0,
        "VolumeStatus": 0,
        "ProtectionStatus": 0,
        "LockStatus": 0,
        "EncryptionPercentage": 0,
        "WipePercentage": 0,
        "VolumeType": 0,
        "CapacityGB": 59.50976,
        "KeyProtector": []
  "OsUpdates": {
    "RefreshTime": "2017-08-16T14:38:44.1388364+00:00",
    "PendingUpdates": {},
    "Settings": {
      "DeferQualityUpdates": 1,
      "DeferQualityUpdatesPeriodInDays": 21,
      "BranchReadinessLevel": 32,
      "DeferFeatureUpdates": 1,
      "DeferFeatureUpdatesPeriodInDays": 60

“Bitlocker”: {| Key | Value | SubKey | SubValue | | | | — | — | — | — | — |— | | “DriveStates”: | [ | | | | | | | { | | | | | | | “ComputerName”: | “DESKTOP-0815VHX”, | | | | | | “MountPoint”: | “C:”, | | | | | | “EncryptionMethod”: | 0, | | | | | | “AutoUnlockEnabled”: | null, | | | | | | “AutoUnlockKeyStored”: | null, | | | | | | “MetadataVersion”: | 0, | | | | | | “VolumeStatus”: | 0, | | | | | | “ProtectionStatus”: | 0, | | | | | | “LockStatus”: | 0, | | | | | | “EncryptionPercentage”: | 0, | | | | | | “WipePercentage”: | 0, | | | | | | “VolumeType”: | 0, | | | | | | “CapacityGB”: | 59.50976, | | | | | | “KeyProtector”: | [] | | | |

BranchCache and Software
"BranchCache": {
  "DataCacheCurrentActiveCacheSize": 1424903614,
  "CurrentClientMode": "DistributedCache"
> Installed Chocolatey Version. Not upgraded automatically, RealmJoin uses specific version
"Chocolatey": {
  "RequiredVersion": "0.10.3",
  "InstalledVersion": "0.10.3",
  "Status": "Ready"
> Software installed via RealmJoin
"SoftwarePackages": {
  "Installed": [
      "ID": "chocolatey",
      "Version": "0.10.3",
      "ArgsHash": null
      "ID": "realmjoin-core.extension",
      "Version": "",
      "ArgsHash": null
      "ID": "contoso-adobe-reader-dc-classic",
      "Version": "15.6.30306.0",
      "ArgsHash": null
      "ID": "contoso-fonts",
      "Version": "",
      "ArgsHash": null
      "ID": "contoso-microsoft-office-2016-proplus-x64-en-de",
      "Version": "",
      "ArgsHash": null
      "ID": "contoso-office-templates-de",
      "Version": "",
      "ArgsHash": null
  > Software installed by other means (Admin, Appx)
  "Inventory": [
      "Name": "7-Zip 18.01 (x64 edition)",
      "Version": "",
      "Publisher": "Igor Pavlov",
      "EstimatedSize": 5123,
      "UserScope": false
      "Name": "Adobe Acrobat Reader DC (2015) MUI",
      "Version": "15.006.30417",
      "Publisher": "Adobe Systems Incorporated",
      "EstimatedSize": 552266,
      "UserScope": false
      "Name": "Chocolatey GUI",
      "Version": "",
      "Publisher": "Chocolatey",
      "EstimatedSize": 43896,
      "UserScope": false
      "Name": "Dropbox",
      "Version": "44.4.58",
      "Publisher": "Dropbox, Inc.",
      "EstimatedSize": 0,
      "UserScope": false
> Configured DO Group ID
"DeliveryOptimization": {
  "DefaultGatewayDiscovered": null,
  "GroupID": "00000099-0000-0000-0000-002cc8f1c3bd"
> Advanced Threat Protection status
"Atp": {
  "IsOnboarded": true,
  "OnboardingInfo": {
    "previousOrgIds": [],
    "orgId": "fa29db65-000c-0000-9409-369df149b5ba",
    "geoLocationUrl": "",
    "datacenter": "WestEurope",
    "vortexGeoLocation": "EU",
    "version": "1.13"
> Individual Custom States
"CustomStates": {
  "ComputerSystem_Information": {
    "Manufacturer": "Microsoft",
    "Model": "Virtual Machine",
    "SystemSku": "None",
    "SerialNumber": "8024-3966-0000-6152-8582-7818-84",
    "VersionGetRealmjoinComputerSystemModel": "180116",
    "BiosVersion": "Hyper-V UEFI Release v1.0",
    "TimestampOutRealmjoinCustomState": "2018-03-07T15:34:28.0907833Z"

Package upload

RJ rj-ac-uploadericonTo request new packages to be provided by G&K, use the uploader in the RealmJoin admin console. Please provide the necessary binaries as well as all installation requirements and additional information as a Readme.txt. After submitting the information (please do not forget a contact person!), you will be able to upload your zip file containing the binaries and the additional information. This will trigger a packaging request in the G&K ticketing system.

RJ rj-ac-uploader NOTE:To prevent spam and unsolicited requests, if no file is attached, the request is not processed. In case of a file-less request, a dummy.txt file hast to be attached.