title: ConvertTo-SecureString gives different experience on different servers
body: <p>I am running into an issue creating a Credential Object from an XML File on a remote server. Here is the code I am using to test</p>
  
  <p><strong>XML File</strong></p>
  
  <pre><code>&lt;Objs Version="1.1.0.1" xmlns="http://schemas.microsoft.com/powershell/2004/04"&gt;
    &lt;Obj RefId="0"&gt;
       &lt;TN RefId="0"&gt;
          &lt;T&gt;Selected.System.Management.Automation.PSCredential&lt;/T&gt;
          &lt;T&gt;System.Management.Automation.PSCustomObject&lt;/T&gt;
          &lt;T&gt;System.Object&lt;/T&gt;
       &lt;/TN&gt;
       &lt;MS&gt;
          &lt;S N="UserName"&gt;domain\username&lt;/S&gt;
          &lt;S N="Password"&gt;01000000d08c9ddf0115d1118c7a00c04fc297eb010000001f19c6a42b9b0d48af2c531892e737ce000000000200000000001066000000010000200000006fb8862fbaea7b83cd2bcab35d7a8c8b4d71b7764c2a91d68eb3873864bc9d83000000000e8000000002000020000000fcbcc5552c3eb40ec337594f8286b08780709c1ac583d4679dcd7a3f5a92441b20000000c8e274811ed7a411b6741b2c65a67363f6aef380e684d13218d1ecc1281dfdb940000000c7279e81e21a1e57eed7da61e969f34fe2adf3d7e534bb5e10b89902adf4fdf20a69ec7e9b9e56dab512c789043a3b2cf0611e3b4893658b7c20f7892ce0ddfd&lt;/S&gt;
  &lt;/MS&gt;
  </code></pre>
  
  <p>
  </p>
  
  <p><strong>PowerShell Code</strong></p>
  
  <pre><code>    $cred = Import-Clixml "Payload\DeploymentCredential.xml"
      write-host $cred
      $cred.Password = ConvertTo-SecureString $cred.Password 
      write-host $cred.Password
      $Credential = New-Object System.Management.Automation.PsCredential($cred.UserName, $cred.Password)
      write-host $Credential.GetNetworkCredential().password
  </code></pre>
  
  <p>On one server (my local machine) it works completely fine, but on the remote server, I get this error</p>
  
  <pre><code>Key not valid for use in specified state.    
  + CategoryInfo          : InvalidArgument: (:) [ConvertTo-SecureString], CryptographicException
  + FullyQualifiedErrorId : ImportSecureString_InvalidArgument_CryptographicError,Microsoft.PowerShell.Commands.ConvertToSecureStringCommand
  </code></pre>
  
  <p>Both have the same version of PowerShell (3.0 Build -1 Revision -1), so I am not sure what the issue is.</p>