Open an elevated PowerShell session (not an Exchange Management Shell)

Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010

And yes, I am quite aware it says E2010. Trust me.

This is NOT supported and it completely avoids the protections provided by RBAC 
and audit logging.

From: [email protected] [mailto:[email protected]] On 
Behalf Of Graeme Carstairs
Sent: Thursday, December 17, 2015 10:54 AM
To: [email protected]
Subject: Re: [Exchange] Exchange 2013 Powershell cant connect to local server

?hi thanks,

Its Exchange management Shell on the Actual Exchange server
The server has two IPv4 addresses and two IPv6 addresses and all resolve when 
you NSlooup on the server itself, and ping fine etc.

no entries in hosts file

Workaround would be great as I think that the Powershell URI may be wrong as 
well as the outlook ones.



On 17 December 2015 at 15:47, Michael B. Smith 
<[email protected]<mailto:[email protected]>> wrote:
Check ur hosts file first.

This error message is generally a good indication of a DNS problem… but if ur 
sure about DNS…

I can give you a workaround if you want one. But it’s a workaround, not a 
solution.

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]<mailto:[email protected]>] 
On Behalf Of Graeme Carstairs
Sent: Thursday, December 17, 2015 10:39 AM
To: [email protected]<mailto:[email protected]>
Subject: [Exchange] Exchange 2013 Powershell cant connect to local server

HI There,

I am investigating an issue on an inherited Exchange 2013 set-up, with 
mismatched uri for internal outlook.


I need to run powershell on the Exchange server but when I try to start 
Exchange Management Shell

I get the following Error


VERBOSE: Connecting to server server.domain.com<http://server.domain.com>.
New-PSSession : [server.domain.com<http://server.domain.com>] Connecting to 
remote server server.domain.com<http://server.domain.com>
failed with the following error message : The WinRM client cannot process the 
request because the server name cannot
be resolved. For more information, see the about_Remote_Troubleshooting Help 
topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName 
Microsoft.Excha ...
+ 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: 
(System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : ComputerNotFound,PSSessionOpenFailed

When I try to google it this error is only referenced via Exchange online.

All DNS is fully resolvable and pingable on IPv4 and IP v6.

Any suggestions

TIA

Graeme



--
Good news everyone, you have just received an e-mail from me!



--
Good news everyone, you have just received an e-mail from me!

Reply via email to