> 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/de/fehlerbehebung-and-faq/troubleshooting/package-installation-issues/intunewin-debugging.md).

# Intunewin-Debugging

Debuggen Sie intunewin-Paketinstallationen mithilfe der Protokolldateien von RjImeHost, Paketinstallationsprogramm und Intune Management Extension.

Da intunewin-Pakete für die Installation von Anwendungen nicht den RealmJoin-Agenten, sondern Intune verwenden, ist das Protokollieren anders.

### Speicherorte der Protokolldateien

Von Intunewin bereitgestellte Anwendungspakete schreiben drei verschiedene Protokolldateien.

* RJImeHost-Protokolle: $env:Systemroot\Logs\RealmJoin\Packages\\\<package-id>\date\_package-id\_RjImeHost\_Install.log
* Protokolle des Paketinstallationsprogramms: falls verfügbar: $env:Systemroot\Logs\RealmJoin\Packages\\\<package-id>\\\*.log
* Generelle IME-Protokolle: C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\intuneManagementExtension.log

<figure><img src="https://2298793958-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2FegS4C0BK2LBuSxywXkyw%2F24-09-26-13_56_01_vmconnect.png?alt=media&amp;token=e819c638-996e-47b2-8100-30205eb07b8c" alt=""><figcaption></figcaption></figure>

Die folgenden Zeilen in RjImeHost.log geben den Installationsbefehl an:

```
OUT: 240926-083509.886+02:00| DEBUG: Funktion 'Install-RealmjoinPackage' mit Parametern aufgerufen [{"Key":"silentArgs","Value":["/VERYSILENT /ALLUSERS /LOG=\"%LOGFILEPATH%\""]},{"Key":"installerFileName","Value":"gimp-2.10.38-setup.exe"},{"Key":"installerFileChecksum","Value":"e3515980c9012eed67cf78f1151d216725529e95676c16f5ff7478d46230ddab"}]
OUT: 240926-083512.671+02:00| Installationsprogramm wird ausgeführt...
OUT: 240926-083512.702+02:00| DEBUG: Funktion 'Start-RealmjoinProcess' mit Parametern aufgerufen [{"Key":"FilePath","Value":"C:\\Windows\\IMECache\\1ce860d8-c3a9-4032-b29d-cd51814038e9_1\\blobs\\gimp-2.10.38-setup.exe"},{"Key":"ArgumentList","Value":["/VERYSILENT /ALLUSERS /LOG=\"C:\\Windows\\Logs\\RealmJoin\\Packages\\generic-gimpteam-gimp\\2024-09-26_08-35-10.026_generic-gimpteam-gimp_2.10.38.0_install_gimp-2.10.38-setup.exe.log\""]},{"Key":"ValidExitCodes","Value":[0,1641,3010]}]
OUT: 240926-083700.796+02:00|     Installationsprogramm ausgeführt.
```

Dieser Abschnitt enthält alle Installationsfehlercodes.


---

# 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/de/fehlerbehebung-and-faq/troubleshooting/package-installation-issues/intunewin-debugging.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.