RealmJoin Docs

Possible reasons why a software package might not install

1. The software package is not properly assigned to the user

2. The software is assigned but the assignment is not received by the client

3. The assignment reaches the client but the installation is not started or fails

Review installed & available Software

Find the RealmJoin Icon in your taskbar.

Tray

Click the RealmJoin icon and click „Software Packages“. Check if the Software is listed and which status is displayed. Grayed-out indicated Software is already installed. “Black Text” (ready to install) indicates Software is not installed. In this case the installation failed or the software package is configured for manual installation.

Tray-Menu

Click the software if it is shown as ready to install. This should start the Software installation. Click “Show Details”

Install-Citrix

Select and copy everything in the details If the software installation fails. Attach this information to the incident ticket.

Install-Citrix-Details

RealmJoin Log Files

Loging

RealmJoin records all event data into log files. Those can easily be accessed on the client device using the Windows Event Viewer (eventvwr.msc). RealmJoin logs can be found under Event Viewer (Local) / Windows Logs / Application.

To troubleshoot package execution problems or RealmJoin Problems there are several Log Files available:

System Context Installations and other system tasks: C:\Windows\Logs\realmjoin.log

Log

User Context Installations and other tray component tasks: %LocalAppData%\RealmJoin\tray.log

Log

RealmJoin Service events in the application eventlog.

Log

Chocolatey Install Logfiles: C:\ProgramData\chocolatey\logs\chocolatey.log

Log

MSI Installations logs.

Log

Alternatively the logs can be automatically collected and save to the current users desktop via the debug window (see section below).

Advanced RealmJoin Options

Hold “control” & “shift” keys and klick RealmJoin Tray icon. Select “Show Debug Window”.

Advanced

You can ping the RealmJoin Backend to check connectivity.

Advanced

You can check if the client version is up to date.

Advanced

You can check if the user configuration is up to date. This includes the assigned software packages.

Advanced

If a new user configuration is available you can update the configuration.

Advanced

You can reset the user configuration. After this is done it is required to update the user configuration with “Check Config”

Advanced

You can collect the RealmJoin logfiles automatically.

Advanced

Verify Group Membership in Office 365 Admin Center

You need to know the Software Distribution Group to which the software should be deployed.

Open Office 365 Admin Center Group management at: Office 365 Admin Center

O365 Portal

Select appropriate software distribution group and verify if the user is member of this group.

O365 Portal

Token Error

There are several possible approaches to repair token errors.

Delete Token.dat

To trigger a new token request, delete the file
C:\Users\username\AppData\Local\RealmJoin\token.dat
and restart your device. Newer RealmJoin (starting with v4.10) versions that detect broken tokens may repair them automatically.

Reconnet to Domain

In the RealmJoin tray, you might use the Reconnet to Domain or Change Domain Password options to reinstate the connection authentication.

RealmJoin Backend

Replaced with Admin Console!

Go to RealmJoin Backend admin portal at: RealmJoin Backend Portal

RealmJoin Portal

In “Software” select the required software package. At the right you can see which users and groups have been assigned this software package. In this example it has not been assigned to any individual user but to 2 groups. Assignments for automatic installation are shown in bold letters.

RealmJoin Portal

Corrupted chocolatey installation

If the installation of software packages produce error messages hinting to a corrupt chocolatey installation, it is possible to reenforce the automatic chocolatey installation through RealmJoin.
To do so, remove the %chocolatey% environment variable and enforce a reboot of the client machine and the RealmJoin agent. This will trigger a reinstallation of chocolatey.