> 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/de/knowledge-base/troubleshooting-articles/black-screen-with-an-ard-session.md).

# Schwarzer Bildschirm bei einer ARD-Sitzung

Diagnostizieren Sie einen schwarzen Bildschirm in einer Apple Remote Desktop-Sitzung, indem Sie die ARD-Protokollierung unter macOS aktivieren, um Details für den Support zu erfassen.

Nach dem Verbinden mit einem Apple Remote Desktop-Sitzungseintrag erscheint ein schwarzer Bildschirm.

### Lösung

Das Aktivieren der Protokollierung auf dem Mac kann unserem Kundensupport-Team oder der Entwicklungsabteilung helfen, dieses Problem zu lösen. Um die Protokollierung serverseitig zu aktivieren, führen Sie den folgenden Befehl im Terminal aus:

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

Sobald dies erledigt ist, können Sie versuchen, sich normal mit Remote Dekstop Manager zu verbinden. Das Protokoll befindet sich dann im Ordner ***/tmp*** auf dem Mac-Computer. Senden Sie diese einfach an <service@devolutions.net> mit Details zu Ihrem Problem.

Um die Protokollierung zu deaktivieren, führen Sie diesen Befehl aus:

***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 dynamically 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/de/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 `build a script that syncs our docs to a CMS` 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.