> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/da/knowledge-base/troubleshooting-articles/black-screen-with-an-ard-session.md).

# Sort skærm med en ARD-session

Diagnosticer en sort skærm i en Apple Remote Desktop-session ved at aktivere ARD-logning på macOS, så support kan få detaljerne.

Der vises en sort skærm, når De har oprettet forbindelse med en sessionspost til Apple Remote Desktop.

### Løsning

Hvis De aktiverer logning på Mac'en, kan det hjælpe vores supportteam eller ingeniørafdelingen med at løse problemet. For at aktivere logning på serversiden skal De køre følgende kommando i Terminal:

***sudo defaults write /Library/Preferences/com.apple.RemoteManagement ARDCollectLogs -bool YES***.

Når det er gjort, kan De prøve at oprette forbindelse normalt med Remote Desktop Manager. Loggen findes derefter i mappen ***/tmp*** på Mac-computeren. Send dem blot til <service@devolutions.net> sammen med oplysninger om Deres problem.

For at slå logning fra skal De køre denne kommando:

***sudo defaults write /Library/Preferences/com.apple.RemoteManagement ARDCollectLogs -bool NOTBD***


---

# 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.devolutions.net/rdm/da/knowledge-base/troubleshooting-articles/black-screen-with-an-ard-session.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.