> 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/powershell-universal/es/comandos-de-powershell/test-psuserverconnection.md).

# Test-PSUServerConnection

Test-PSUServerConnection comprueba si hay una sesión de Connect-PSUServer activa y puede devolver metadatos detallados de la conexión.

## SINOPSIS

Comprueba si se ha establecido una conexión con el servidor de PowerShell Universal.

## SINTAXIS

```
Test-PSUServerConnection [-Detailed] [<CommonParameters>]
```

## DESCRIPCIÓN

Informa de si los valores predeterminados de Connect-PSUServer están disponibles actualmente. Utilice -Detailed para devolver metadatos de la conexión, como el ámbito, el nombre del equipo y el tipo de autenticación.

## EJEMPLOS

### Ejemplo 1

```powershell
PS C:\> Test-PSUServerConnection -Detailed
```

Devuelve información detallada sobre el estado actual de la conexión con el servidor de PowerShell Universal.

## PARÁMETROS

### -Detailed

Devuelve metadatos detallados de la conexión en lugar de solo `$true` o `$false`.

```yaml
Type: SwitchParameter
Parameter Sets: (All)
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### CommonParameters

Este cmdlet admite los parámetros comunes: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutBuffer, -OutVariable, -PipelineVariable, -Verbose, -WarningAction, -WarningVariable y -ProgressAction. Para más información, consulte [about\_CommonParameters](http://go.microsoft.com/fwlink/?LinkID=113216).

## ENTRADAS

### Ninguna

## SALIDAS

### System.Boolean

### UniversalAutomation.ServerConnectionInfo

## NOTAS

## ENLACES RELACIONADOS


---

# 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/powershell-universal/es/comandos-de-powershell/test-psuserverconnection.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.