> 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/pt/resolucao-de-problemas-e-faq/troubleshooting/package-installation-issues/intunewin-debugging.md).

# Depuração de intunewin

Depure instalações de pacotes intunewin usando os ficheiros de registo RjImeHost, instalador de pacotes e Intune Management Extension.

Como os pacotes intunewin não utilizam o agente RealmJoin para instalar aplicações, mas sim o Intune, o registo é diferente.

### Localizações dos ficheiros de registo

Os pacotes de aplicações implementados pelo intunewin escrevem três ficheiros de registo diferentes.

* Registos do RJImeHost: $env:Systemroot\Logs\RealmJoin\Packages\\\<package-id>\date\_package-id\_RjImeHost\_Install.log
* Registos do instalador do pacote: se disponíveis: $env:Systemroot\Logs\RealmJoin\Packages\\\<package-id>\\\*.log
* Registos gerais do IME: C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\intuneManagementExtension.log

<figure><img src="https://686519968-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>

As seguintes linhas do RjImeHost.log indicam o comando de instalação:

```
SAÍDA: 240926-083509.886+02:00| DEBUG: Entrou na função 'Install-RealmjoinPackage' com parâmetros [{"Key":"silentArgs","Value":["/VERYSILENT /ALLUSERS /LOG=\"%LOGFILEPATH%\""]},{"Key":"installerFileName","Value":"gimp-2.10.38-setup.exe"},{"Key":"installerFileChecksum","Value":"e3515980c9012eed67cf78f1151d216725529e95676c16f5ff7478d46230ddab"}]
SAÍDA: 240926-083512.671+02:00| A executar o instalador...
SAÍDA: 240926-083512.702+02:00| DEBUG: Entrou na função 'Start-RealmjoinProcess' com parâmetros [{"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]}]
SAÍDA: 240926-083700.796+02:00|     Execução do instalador concluída.
```

Esta secção conterá quaisquer códigos de erro de instalação.


---

# 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/pt/resolucao-de-problemas-e-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.
