> 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/convertto-rdmentryxml.md).

# ConvertTo-RDMEntryXml

ConvertTo-RDMEntryXml serializes a live Remote Desktop Manager entry or a historical version to XML, using the same serializer as the Windows client's Compare feature.

### Synopsis

Serialize a live entry or a historical version to XML

### Syntax

#### InputObject

```
ConvertTo-RDMEntryXml -InputObject <PSConnection> [-ForcePromptAnswer <DialogResult[]>]
 [<CommonParameters>]
```

#### History

```
ConvertTo-RDMEntryXml -History <PSConnectionHistory> [-ForcePromptAnswer <DialogResult[]>]
 [<CommonParameters>]
```

### Description

Serialize a live entry (from Get-RDMEntry) or a historical version (from Get-RDMEntryHistory) to XML, using the same serializer as the Windows client's Compare feature. Diffing the XML of two versions, or of the live entry against a version, with Compare-Object mirrors the Windows Entry history Compare button. Deleted-entry records from Get-RDMDeletedEntry cannot be converted and are refused.

### Examples

#### Example 1

```powershell
PS C:\> $xml = Get-RDMEntryHistory -InputObject $id | Select-Object -First 2 | ConvertTo-RDMEntryXml
        Compare-Object ($xml[0] -split "`n") ($xml[1] -split "`n")
```

Compare the two most recent versions of an entry.

#### Example 2

```powershell
PS C:\> $currentXml = Get-RDMEntry $id | ConvertTo-RDMEntryXml
        $currentUserName = ([xml]$currentXml).Connection.Credentials.UserName
        foreach ($version in Get-RDMEntryHistory -InputObject $id) {
            $versionUserName = ([xml]($version | ConvertTo-RDMEntryXml)).Connection.Credentials.UserName
            if ($versionUserName -eq $currentUserName) {
                continue
            }
            Compare-Object ($currentXml -split "`n") (($version | ConvertTo-RDMEntryXml) -split "`n")
            $version | Restore-RDMEntryHistory
            break
        }
```

Compare the live entry against the last version before its username was changed, then revert to it.

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

#### -History

Version obtained from Get-RDMEntryHistory

```yaml
Type: RemoteDesktopManager.PowerShellModule.PSOutputObject.PSConnectionHistory
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: History
  Position: Named
  IsRequired: true
  ValueFromPipeline: true
  ValueFromPipelineByPropertyName: false
  ValueFromRemainingArguments: false
DontShow: false
AcceptedValues: []
HelpMessage: ''
```

#### -InputObject

Live entry obtained from Get-RDMEntry

```yaml
Type: RemoteDesktopManager.PowerShellModule.PSOutputObject.PSConnection
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: InputObject
  Position: Named
  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

A live entry obtained from Get-RDMEntry

#### RemoteDesktopManager.PowerShellModule.PSOutputObject.PSConnectionHistory

A version obtained from Get-RDMEntryHistory

### Outputs

#### System.String

The XML representation of the entry or version

### Notes

For more information, type "Get-Help ConvertTo-RDMEntryXml -detailed". For technical information, type "Get-Help ConvertTo-RDMEntryXml -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/convertto-rdmentryxml.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.