> 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/powershell-commands/get-rdmentryhistory.md).

# Get-RDMEntryHistory

Get-RDMEntryHistory retrieves the version history of a Remote Desktop Manager entry, newest first.

### Synopsis

Get the version history of an entry

### Syntax

#### \_\_AllParameterSets

```
Get-RDMEntryHistory [-InputObject] <PSConnection> [-ForcePromptAnswer <DialogResult[]>]
 [<CommonParameters>]
```

### Description

Get the version history of an entry. Every time an entry is saved, its previous state is logged. This cmdlet returns those versions, newest first. The user must have the right to view the entry's history and the workspace must support version history. Pipe a version into ConvertTo-RDMEntryXml to materialize its content, into Restore-RDMEntryHistory to revert to it, or into Remove-RDMEntryHistory to delete it.

### Examples

#### Example 1

```powershell
PS C:\> Get-RDMEntryHistory -InputObject $id
```

List all versions of the entry, newest first.

#### Example 2

```powershell
PS C:\> Get-RDMEntry $id | Get-RDMEntryHistory
```

List all versions of the piped entry.

#### Example 3

```powershell
PS C:\> Get-RDMEntryHistory -InputObject $id | Where-Object ModifiedLoggedUserName -eq david
```

List only the versions saved by the workspace user 'david'.

### Parameters

#### -ForcePromptAnswer

Switch to use with caution. It will automatically answer prompt asking yes/no, yes/no/cancel, or ok/cancel questions. In case of multiple prompts, multiple values can be passed to this parameter. Here are the accepted values:

* Yes: Accept the prompt. Cover the OK and Automatic value.
* No: Refuse the yes/no/cancel prompt. "Cancel" is the fallback option if there is no "No" option.
* Cancel: Cancel the yes/no/cancel prompt. "No" is the fallback option if there is no "Cancel" option.

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

#### -InputObject

Entry to inspect. Accepts a PSConnection object or the connection's ID.

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

#### CommonParameters

This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutBuffer, -OutVariable, -PipelineVariable, -ProgressAction, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about\_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).

### Inputs

#### RemoteDesktopManager.PowerShellModule.PSOutputObject.PSConnection

Entry to inspect. Can be obtained from Get-RDMEntry.

### Outputs

#### RemoteDesktopManager.PowerShellModule.PSOutputObject.PSConnectionHistory

A version of the entry. No field can be modified.

### Notes

For more information, type "Get-Help Get-RDMEntryHistory -detailed". For technical information, type "Get-Help Get-RDMEntryHistory -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/powershell-commands/get-rdmentryhistory.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.