访问拒绝运行远程PowerShell，但仅当从开发服务器运行时才能正常工作

Question

I am trying to run a remote PowerShell command against our exchange server but am getting an Access Is Denied error when that command is ran from our development server. The code works fine when I run it on my local machine, I can even remote to the development server and run a PowerShell command and make the connection perfectly fine. I need help in figuring out why we are getting the Access Is Denied error when only running the code from the development server.

public static void CreateEmailBox(string samAccountName)
{
    var securedPassword = new SecureString();
    foreach (char character in ConfigurationManager.AppSettings["ServiceAccountPassword"]) { securedPassword.AppendChar(character); }
    var loginInfo = new PSCredential(ConfigurationManager.AppSettings["ServiceAccountUser"], securedPassword);

    var connection = new WSManConnectionInfo(new Uri("http://exch-svr.domain.local/powershell"), "http://schemas.microsoft.com/powershell/Microsoft.Exchange", loginInfo);
    connection.AuthenticationMechanism = AuthenticationMechanism.Kerberos;

    using (var runspace = RunspaceFactory.CreateRunspace(connection))
    {
        using (var powershell = PowerShell.Create())
        {
            powershell.AddCommand("enable-mailbox");
            powershell.AddParameter("Identity", samAccountName);
            powershell.AddParameter("Database", "Mailbox Database 4");
            runspace.Open();
            powershell.Runspace = runspace;
            powershell.Invoke();
            runspace.Close();
        }
    }
}

Answer 1

The issue would be with the password, and how it is being stored as the Secure String.

Secure Strings are different between computers because the encryption key used to encrypt/decrypt the password is different on every computer.

You either need to use a shared key, or store a separate Secure String for each computer that you are going to run this from.

For more information, on how to pass Secure Strings between computers see my more detailed Answer on: ConvertTo-SecureString gives different experience on different servers