Learn How to Use PowerShell to Run Exchange Commands Remotely

re: Learn How to Use PowerShell to Run Exchange Commands Remotely

Jono — Tue, 16 Oct 2012 21:31:13 GMT

I am getting the following error. Can you help me out with this?

PS H:\> $cred = Get-Credential send\senditadmin

PS H:\> $session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://send-xchange/powershell -Credential $cred

New-PSSession : A parameter cannot be found that matches parameter name 'ConnectionUri http'.

At line:1 char:84

+ $session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http: <<<< //send-xchange/powershell -Credential $cred

+ CategoryInfo : InvalidArgument: (:) [New-PSSession], ParameterBindingException

+ FullyQualifiedErrorId : NamedParameterNotFound,Microsoft.PowerShell.Commands.NewPSSessionCommand

The first command worked perfectly. It asked for the credentials, which I gave it. The second command gives me the error.

Thanks,

Jono

re: Learn How to Use PowerShell to Run Exchange Commands Remotely

Satheshwaran Manoharan — Mon, 14 May 2012 15:57:59 GMT

Nice one !! Thanks !!

re: Learn How to Use PowerShell to Run Exchange Commands Remotely

IamMred — Mon, 23 Jan 2012 15:57:00 GMT

@JeremyEnbleWork I am glad the article was perfectly timed to meet your needs. While I would love to take credit for that aspect, alas I must mark it up to luck. However, I have seen many requests for this type of information, and therefore I wrote the article. You are absolutely correct. The remote connection credentials only apply to the proxy functions that appear after having made the remote connection to the Exchange Server. All other cmdlets, such as Get-Process or Get-Service will behave exactly as before -- they will refer to the local computer, and not to the remote Exchange server, and they will still operate within the original security context. This is one difference between implicit remoting (discussed here) and explicit remoting (discussed elsewhere on this blog) which actually creates a virtual PowerShell console on the local computer that thinks it is on the remote machine.

re: Learn How to Use PowerShell to Run Exchange Commands Remotely

JeremyEngelWork — Mon, 23 Jan 2012 15:32:25 GMT

Thanks, Ed! Your timing was very serendipitous as just encountered this very problem last night! One question though: Does this mean that any Exchange 2010 functions run under those supplied credentials, but non-exchange commands would continue to run under the normal user context?