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
        • 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

Was this helpful?

Edit on GitHub
  1. Other
  2. Troubleshooting

Package Installation Issues

Troubleshooting Guide for failed software package installations

Last updated 7 months ago

Was this helpful?

This guide will focus on troubleshooting failed RealmJoin software package installations.

This guide is only valid for software deployment using the RealmJoin client (not intunewin).

Especially the convenient way of collecting the required logfiles, directly on the client as well as remotely using the RealmJoin portal, only works with the RealmJoin tray application rolled out to your clients.

When using intunewin deployment, the logfiles will need to be collected manually from the clients, the most relevant folder being C:\WINDOWS\Logs\RealmJoin.

Required log files

Without log files a failed software package installation cannot be properly troubleshooted. The required log files needed for troubleshooting failed installations reside in several location on the local client:

  • C:\WINDOWS\Logs\realmjoin*.log

  • C:\WINDOWS\Logs\RealmJoin

  • %LOCALAPPDATA%\RealmJoin\tray*.log

  • %LOCALAPPDATA%\RealmJoin\Logs

  • C:\ProgramData\chocolatey\logs\

Please always provide the ZIP file containing the logs with any service request raised to the RealmJoin support.

The following chapters will explain how to obtain the logs, how to analyze them, and will explain some common issues and fixes for these common issues.

File structure of a RealmJoin exported logs ZIP file