1. The software package is not properly assigned to the user
- In Azure AD: Is there a software distribution group for this software and is the user member of this group?
- In RealmJoin Admin Portal: Is there a package for this software and is this package assigned to the correct Azure AD group?
- Is the software package assigned for automatic (mandatory) or manual install?
2. The software is assigned but the assignment is not received by the client
- Is RealmJoin running?
- Is the RealmJoin configuration up to date?
- Is the RealmJoin version up to date?
- Are there any errors in the RealmJoin logs?
3. The assignment reaches the client but the installation is not started or fails
- Is the software assigned for manual installation?
- Is it possible to start the installation manually and are there any errors shown?
- Check RealmJoin logs and software installation logs if available?
You need to know the software Distribution Group to which the software should be deployed.
Select appropriate software distribution group and verify if the user is member of this group.
Find the RealmJoin icon in your taskbar.
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.
Click the software if it is shown as ready to install. This should start the software installation. Click Show Details
If the installation fails, collect complete RealmJoin logfiles (see below) and attach to the incident ticket. Incident tickets to glueckkanja-gab without full logging will be closed.
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:
User Context Installations and other tray component tasks:
RealmJoin Service events in the application eventlog.
Chocolatey Install Logfiles:
MSI Installations logs.
NOTE: For all support related incidents, please exclusively add the complete zip containing all relevant logfiles only. Do NOT attach just a part of the logfiles as mentioned above. The logs can be automatically collected and save to the current users desktop via the debug window (see the section below) or collected via the RealmJoin portal. Windows event logs may be added additionally be when opening a ticket.
To open the tray debug (and enter the debug mode) click STRG + SHIFT + Click on the RealmJoin Icon. The Client menu will open but with a further entry at the end of the menu: Show Debug Window.
Show Debug Window contains seven different diagnostic tools. If a device is not able to be addressed by the server or can not connect to the back-end, this tool will provide the user with the tools for the first steps of diagnosis.
You can ping the RealmJoin back-end to check connectivity.
You can check if the client version is up to date.
You can check if the user configuration is up to date. This includes the assigned software packages.
If a new user configuration is available, you can update the configuration.
You can reset the user configuration. After this is done, it is required to update the user configuration with Check Config
You can collect the RealmJoin log files automatically.
- It is possible to reinstall packages: during the Debug Mode all packages assigned to the user are visible and can be restarted.
- Package version numbers are displayed: for all assigned packages the available versions can be seen and checked against the desired state.
If the Debug Mode is activated, mandatory software is marked with *.
There are several possible approaches to repair token errors.
To trigger a new token request, delete the file
C:\Users\username\AppData\Local\RealmJoin\token.datand restart your device. Newer RealmJoin (starting with v4.10) versions that detect broken tokens may repair them automatically.
In the RealmJoin tray, you might use the Reconnect to Domain or Change Domain Password options to reinstate the connection authentication.
Replaced with Admin Console!
In Software select the required software package. At the right users and groups are visible which have been assigned to 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.
If the installation of software packages produce error messages hinting to a corrupt Chocolatey installation, it is possible to reinforce 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.
It is not supported to remove the RealmJoin application from a client. However, for test scenarios, there are two ways to remove the application from a client.
- 1.Reimage the client.
- 2.Delete manually.
Manual deletion instruction:
- Stop all running RealmJoin processes
- Remove the service, execute "sc delete realmjoin"
- Remove the executables from C:\Program Files\RealmJoin
- Delete registry hive HKLM and HKCU\SOFTWARE\RealmJoin
- Delete folder %LocalAppData%\RealmJoin
- Delete folder C:\ProgramData\RealmJoin
You may find the data as follows:
- Chocolatey install scripts: %PROGRAMDATA%\chocolatey\lib\tools\chocolateyInstall.ps1
- Chocolatey blobs: Windows\Temp\chocolatey\
- Craft scripts are cleaned up after the execution