This revealed that PSEXEC adds some text to the end of the STDERR line containing CLIXML data which trips up powershell when parsing out CLIXML XML strings. Here is what PSEXEC writes to STDERR: ...

They won't always have the same format or be under the same node. I do a bit of work with XML and other objects in PowerShell. Wrote ConvertTo-FlatObject to simplify exploring these.

As a result, I often parse the detailed move report using PowerShell or ask a customer to export it to XML for further analysis. There is actually quite a bit of valuable logging and debug information ...

It's not mandatory but you can always create a schema definition file known as a XSD file to validate the XML file against a particular schema. By doing so, this enforces the XML to meet certain ...

In the latest version of Powershell, working with an XML variable seems to have been stripped of these functions, at least when you're working with the last element in the tree.