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

# Pantalla negra en una sesión ARD

Diagnostique una pantalla negra en una sesión de Apple Remote Desktop activando el registro de ARD en macOS para recopilar detalles destinados al soporte.

Aparece una pantalla negra después de conectarse con una entrada de sesión de Apple Remote Desktop.

### Solución

Activar el registro en el Mac puede ayudar a nuestro equipo de atención al cliente o al departamento de ingeniería a resolver este problema. Para activar el registro en el lado del servidor, ejecute el siguiente comando en Terminal:

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

Una vez hecho esto, puede intentar conectarse normalmente utilizando Remote Dekstop Manager. El registro se ubicará entonces en la carpeta ***/tmp*** del ordenador Mac. Simplemente envíelos a <service@devolutions.net> con los detalles de su problema.

Para desactivar el registro, ejecute este comando:

***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/es/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.