> 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/es/powershell-commands/remove-dsgatewayfarm.md).

# Remove-DSGatewayFarm

Remove-DSGatewayFarm elimina una granja de gateways en una instancia de Devolutions Server y, opcionalmente, también sus gateways miembros.

### Sinopsis

Eliminar una granja de puertas de enlace

### Sintaxis

#### \_\_AllParameterSets

```
Remove-DSGatewayFarm [-ID] <guid> [-DeleteMemberGateways] [<CommonParameters>]
```

### Descripción

Eliminar una granja de gateways. De forma predeterminada, los gateways miembros se conservan y pasan a ser gateways independientes. Use el modificador DeleteMemberGateways para eliminar los gateways miembros junto con la granja.

### Ejemplos

#### Ejemplo 1

```powershell
PS C:\> $farm = Get-DSGateway -Name "Production Farm"
PS C:\> Remove-DSGatewayFarm -ID $farm.Id
```

Eliminar una granja de puertas de enlace y conservar sus puertas de enlace miembro como puertas de enlace independientes.

#### Ejemplo 2

```powershell
PS C:\> $farm = Get-DSGateway -Name "Production Farm"
PS C:\> Remove-DSGatewayFarm -ID $farm.Id -DeleteMemberGateways
```

Eliminar una granja de puertas de enlace y todas sus puertas de enlace miembro.

### Parámetros

#### -DeleteMemberGateways

Eliminar los gateways miembros junto con la granja. Si se omite, los gateways miembros se conservan y pasan a ser gateways independientes.

```yaml
Type: System.Management.Automation.SwitchParameter
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: (All)
  Position: Named
  IsRequired: false
  ValueFromPipeline: false
  ValueFromPipelineByPropertyName: false
  ValueFromRemainingArguments: false
DontShow: false
AcceptedValues: []
HelpMessage: ''
```

#### -ID

ID de la granja de puertas de enlace que eliminar.

```yaml
Type: System.Guid
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: (All)
  Position: 0
  IsRequired: true
  ValueFromPipeline: false
  ValueFromPipelineByPropertyName: false
  ValueFromRemainingArguments: false
DontShow: false
AcceptedValues: []
HelpMessage: ''
```

#### CommonParameters

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

### Notas

Para más información, escriba "Get-Help Remove-DSGatewayFarm -detailed". Para obtener información técnica, escriba "Get-Help Remove-DSGatewayFarm -full".


---

# 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/es/powershell-commands/remove-dsgatewayfarm.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.