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
  • User-Context Logfiles
  • tray.log
  • Logs subfolder
  • Chocolatey Logfiles
  • System-Context Logfiles
  • realmjoin.log
  • Logs folder

Was this helpful?

Edit on GitHub
  1. Other
  2. Troubleshooting
  3. Package Installation Issues

Logfiles Structure

Detailed explanation of the different log files collected by RealmJoin

Last updated 1 month ago

Was this helpful?

User-Context Logfiles

The user-context logfiles written by RealmJoin can be found in %LOCALAPPDATA%\RealmJoin. This folder contains tray.log files and the subfolder Logs.

tray.log

The tray.log files are written by the RealmJoin tray application, which is running in the logged on users session. tray.log is the most-recent log file, older ones are suffixed with an ascending number, where the highest number is the second-most recent log file. The lower the number, the older the log file.

The tray.log includes information about various tasks carried out by the RealmJoin tray application:

  • Information about assigned packages, including dependencies, order, contraints, planned operations, restrictions

  • Package inventory with status (Installed, Outdated, NotInstalled)

  • Running and completed deployment phases

  • RealmJoin config and client updates

  • RealmJoin tray startup information

  • Changes to LAPS accounts

  • Commandline output from user context installation packages.

Logs subfolder

In the %LOCALAPPDATA\RealmJoin\Logs folder you may find folders named like package IDs. Only craft packages running in user context will potentially write individual setup logs in this folder. As this is not always the case, this folder may also be empty. If the user craft installation included a MSI or EXE file, you maybe able to find setup logs inside the corresponding package folder.

Chocolatey Logfiles

The chocolatey log files are written to C:\ProgramData\chocolatey\logs\. There are two different log files chocolatey.log and choco.summary.log. As the choco.summary.log only includes basic information, solely chocolatey.log is used for troubleshooting.

System-Context Logfiles

The system-context log files are located inside C:\WINDOWS\Logs. Inside the folder you will find realmjoin.log files as well as the RealmJoin folder.

realmjoin.log

The realmjoin.log files are written by the RealmJoin CloudConnector service, which is started on-demand by the RealmJoin tray application. The RealmJoin CloudConnector service is running in the Local Sytem account. realmjoin.log is the most-recent log file, older ones are suffixed with an ascending number, where the highest number is the second-most recect log file. The lower the number, the older the log file.

As the realmjoin.log file contains information from the RealmJoin service, it includes logs about tasks that need to be executed with system priviliges:

  • RealmJoin service startup information

  • Creation and deletion of LAPS accounts

  • Commandline output from system context / choco installation packages.

Logs folder

In the C:\WINDOWS\Logs\RealmJoin\Packages folder you will find folders named like package IDs. If supported by the setup file and package, logs written by the setup file will be found in the equivalent folder. The logfilename will usually include the timestamp of the installation, package id, setup filename, package version and the action taken (install/uninstall). As this is not always the case, these (sub)folders may also be empty.

tray.log is the most recent file, tray.904.log the second-most recent. The logs subfolder may contain individual setup logs.
Packages folder containing subfolders for each package, which may contain installer-written log files.