> 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/citrix-environment-windows-crash.md).

# Bloqueo de Windows en un entorno Citrix

Evite los fallos de Windows en un entorno Citrix causados por solicitudes repetidas de credenciales de RDS desactivando la solicitud de Windows en las sesiones RDP.

Cuando un servidor RDS solicita credenciales, utiliza una dll y, si se le solicita demasiadas veces por parte de muchos usuarios, Windows fallará.

### Solución

Todas las sesiones deben configurarse para no usar la solicitud de Windows. En las propiedades de las entradas:

1. Cambie el tipo de Credenciales a ***Predeterminado***.
2. Marque la casilla ***Solicitar siempre la contraseña***.

Si tiene muchas entradas que deben cambiarse, siga estos pasos (se recomienda hacer una copia de seguridad de su base de datos):

1. Seleccione todas las sesiones RDP que necesite editar (se puede utilizar una [Búsqueda avanzada](/rdm/es/ribbon-menu-bar/view/search/advanced-search.md)).
2. Haga clic derecho sobre ellas y seleccione ***Editar – Editar (Acciones especiales)***.
3. Seleccione ***Comando Powershell personalizado***.
4. Y en la ventana siguiente escriba el texto que aparece a continuación:

   ```powershell
   $connection.PromptCredentials = $true;
   $RDM.Save();
   ```
5. Haga clic en ***OK*** y entonces todas las sesiones se configurarán con la solicitud de credenciales.


---

# 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/citrix-environment-windows-crash.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.