Credential
objects allow you to decrypt a secure string (source):
PS C:> $pw = 'bar' | ConvertTo-SecureString -AsPlainText -Force
PS C:> $pw.GetType().FullName
System.Security.SecureString
PS C:> $cred = New-Object Management.Automation.PSCredential 'foo', $pw
PS C:> $cred.GetType().FullName
System.Management.Automation.PSCredential
PS C:> $cred.UserName
foo
PS C:> $cred.Password
System.Security.SecureString
PS C:> $cred.GetNetworkCredential().Password
bar
However, the encryption key for the secure string is tied to the user and computer that created the secure string, so it's not usable on another computer or by another user. You can work around this, but that would require to encrypt the secure string with a key generated by you, and that key would have to be available in plain text (or rather plain bytes) whenever the secure string needs to be decrypted. Which kinda defeats the purpose of encrypting it in the first place.
On top of that, if you have enough machines to make storing separate passwords a hassle, you also have enough machines to seriously consider putting them in a domain.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…