> For the complete documentation index, see [llms.txt](https://docs.realmjoin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmjoin.com/troubleshooting-and-faq.md).

# Troubleshooting & FAQ

- [FAQ](https://docs.realmjoin.com/troubleshooting-and-faq/faq.md): RealmJoin FAQ: maintaining your own software packages and runbooks, expected Azure resource costs, and how RealmJoin integrates with Microsoft Intune.
- [Troubleshooting](https://docs.realmjoin.com/troubleshooting-and-faq/troubleshooting.md): Troubleshooting for common RealmJoin issues, including LAPS account problems and failed package installations.
- [Package Installation Issues](https://docs.realmjoin.com/troubleshooting-and-faq/troubleshooting/package-installation-issues.md): Troubleshooting Guide for failed software package installations
- [Collecting Logfiles](https://docs.realmjoin.com/troubleshooting-and-faq/troubleshooting/package-installation-issues/collecting-logfiles.md): How to easily collect logfiles required for troubleshooting
- [Logfiles Structure](https://docs.realmjoin.com/troubleshooting-and-faq/troubleshooting/package-installation-issues/logfiles-structure.md): Detailed explanation of the different log files collected by RealmJoin
- [Analysing chocolatey.log](https://docs.realmjoin.com/troubleshooting-and-faq/troubleshooting/package-installation-issues/analysing-chocolatey.log.md): This part will focus on how to troubleshoot failed chocolatey package installations.
- [Troubleshooting failed chocolatey packages](https://docs.realmjoin.com/troubleshooting-and-faq/troubleshooting/package-installation-issues/troubleshooting-failed-chocolatey-packages.md): Diagnose failed Chocolatey package installs by understanding the install stages and finding error messages in the logs.
- [Troubleshooting failed craft packages](https://docs.realmjoin.com/troubleshooting-and-faq/troubleshooting/package-installation-issues/troubleshooting-failed-craft-packages.md): Diagnose failed craft package installs by reading tray.log for user scope or realmjoin.log for system scope.
- [Fixes for common issues](https://docs.realmjoin.com/troubleshooting-and-faq/troubleshooting/package-installation-issues/fixes-for-common-issues.md): Targeted fixes for common RealmJoin package installation problems, such as BranchCache errors, for specific scenarios.
- [Intunewin Debugging](https://docs.realmjoin.com/troubleshooting-and-faq/troubleshooting/package-installation-issues/intunewin-debugging.md): Debug intunewin package installs using the RjImeHost, package installer, and Intune Management Extension log files.
- [LAPS Issues](https://docs.realmjoin.com/troubleshooting-and-faq/troubleshooting/laps-issues.md): Troubleshooting common LAPS issues
- [LAPS account passwords cannot be retrieved](https://docs.realmjoin.com/troubleshooting-and-faq/troubleshooting/laps-issues/laps-account-passwords-cannot-be-retrieved.md): Checking Azure Key Vault
- [Requested LAPS Accounts are not being created](https://docs.realmjoin.com/troubleshooting-and-faq/troubleshooting/laps-issues/requested-laps-accounts-are-not-being-created.md): Fix RealmJoin LAPS Supporter Accounts stuck in 'Requested' by logging off on- demand admin sessions or rebooting the device.
- [Offboarding](https://docs.realmjoin.com/troubleshooting-and-faq/offboarding.md): How to offboard RealmJoin from your tenant, covering both Intune-only and full RealmJoin deployments and what tenant deletion means for your data, portal access, and devices.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.realmjoin.com/troubleshooting-and-faq.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.