> 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-rdmmessage.md).

# Remove-RDMMessage

Remove-RDMMessage elimina un mensaje seguro por ID u objeto de un espacio de trabajo de Devolutions Server o Devolutions Cloud.

### Sinopsis

Eliminar un mensaje seguro.

### Sintaxis

#### ID

```
Remove-RDMMessage [-ID] <guid> [-Force] [-ForcePromptAnswer <DialogResult[]>] [-WhatIf] [-Confirm]
 [<CommonParameters>]
```

#### Mensaje

```
Remove-RDMMessage [-Message] <DataSourceMessage> [-Force] [-ForcePromptAnswer <DialogResult[]>]
 [-WhatIf] [-Confirm] [<CommonParameters>]
```

### Descripción

Eliminar un mensaje seguro. El espacio de trabajo debe ser un Devolutions Server o un Devolutions Cloud.

### Ejemplos

#### Ejemplo 1

```powershell
PS C:\> Receive-RDMMessage -SentOn -Custom -Before 2021/12/31 | Remove-RDMMessage -Force
```

Elimina todos los mensajes enviados antes del 01/01/2022 (el valor Before es inclusivo). No aparecerá ninguna solicitud de confirmación.

#### Ejemplo 2

```powershell
PS C:\> $messages = Receive-RDMMessage -SentOn Today; $messages | Where-Object -Property FromName -ne 'First Last' | Remove-RDMMessage -Force
```

El usuario obtiene todos los mensajes recibidos hoy. Los lee todos. Decide conservar únicamente los enviados por 'First Last' y eliminar el resto sin ninguna solicitud de confirmación.

#### Ejemplo 3

```powershell
PS C:\> Receive-RDMMessage | Remove-RDMMessage -Confirm
```

Se solicitará al usuario que elimine cada mensaje uno por uno.

### Parámetros

#### -Confirm

Le solicita confirmación antes de ejecutar el cmdlet.

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

#### -Force

Omite la confirmación para continuar. Si el modificador DownloadAttachment está presente, se descargarán los adjuntos de todos los mensajes devueltos.

```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: ''
```

#### -ForcePromptAnswer

Modificador que debe usarse con precaución. Responderá automáticamente a las solicitudes que planteen preguntas de tipo sí/no, sí/no/cancelar u ok/cancelar. En caso de varias solicitudes, se pueden pasar varios valores a este parámetro. Estos son los valores aceptados:

* Yes: Acepta la solicitud. Cubre los valores OK y Automatic.
* No: Rechaza la solicitud sí/no/cancelar. "Cancel" es la opción alternativa si no existe la opción "No".
* Cancel: Cancela la solicitud sí/no/cancelar. "No" es la opción alternativa si no existe la opción "Cancel".

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

#### -ID

ID del mensaje que se va a eliminar.

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

#### -Message

Mensajes que se van a eliminar.

```yaml
Type: Devolutions.RemoteDesktopManager.Business.Messages.DataSourceMessage
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: Message
  Position: 0
  IsRequired: true
  ValueFromPipeline: true
  ValueFromPipelineByPropertyName: false
  ValueFromRemainingArguments: false
DontShow: false
AcceptedValues: []
HelpMessage: ''
```

#### -WhatIf

Muestra lo que ocurriría si se ejecutara el cmdlet. El cmdlet no se ejecuta.

```yaml
Type: System.Management.Automation.SwitchParameter
DefaultValue: False
SupportsWildcards: false
Aliases:
- wi
ParameterSets:
- Name: (All)
  Position: Named
  IsRequired: false
  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).

### Entradas

#### Devolutions.RemoteDesktopManager.Business.Messages.DataSourceMessage

El mensaje obtenido de Receive-RDMMessage se puede canalizar al parámetro Message.

### Notas

Para más información, escriba "Get-Help Remove-RDMMessage -detailed". Para obtener información técnica, escriba "Get-Help Remove-RDMMessage -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-rdmmessage.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.