Exchange 2013

Question

Dear Friends,

After Successful Installation i am facing below mention issue while trying to use Exchange shell or ECP

VERBOSE: Connecting to xxxx.xxxx.COM.PK.
New-PSSession : xxxx.xxxx.COM.PK. ] Connecting to remote server emailserver.nbpecl.com.pk failed with the
following error message : The WinRM client cannot process the request. The WinRM client tried to use Kerberos
authentication mechanism, but the destination computer ( xxxx.xxxx.COM.PK :80) returned an 'access denied'
error. Change the configuration to allow Kerberos authentication mechanism to be used or specify one of the
authentication mechanisms supported by the server. To use Kerberos, specify the local computer name as the remote
destination. Also verify that the client computer and the destination computer are joined to a domain. To use Basic,
specify the local computer name as the remote destination, specify Basic authentication and provide user name and
password. Possible authentication mechanisms reported by server: 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 : AccessDenied,PSSessionOpenFailed
  VERBOSE: Connecting to xxxx.xxxx.COM.PK .
  New-PSSession : [ xxxx.xxxx.COM.PK ] Connecting to remote server emailserver.nbpecl.com.pk failed with the
  following error message : The WinRM client cannot process the request. The WinRM client tried to use Kerberos
  authentication mechanism, but the destination computer ( xxxx.xxxx.COM.PK :80) returned an 'access denied'
  error. Change the configuration to allow Kerberos authentication mechanism to be used or specify one of the
  authentication mechanisms supported by the server. To use Kerberos, specify the local computer name as the remote
  destination. Also verify that the client computer and the destination computer are joined to a domain. To use Basic,
  specify the local computer name as the remote destination, specify Basic authentication and provide user name and
  password. Possible authentication mechanisms reported by server: For more information, see the
  about_Remote_Troubleshooting Help topic.

Answer 1

Hi @Sam Aly

According to my research, I found a similar question here: Problem with WinRM on Exchange 2013 Management Shell and Exchange Toolbox on a new exchange 2013 with CAFE and BE on single server installation
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

This is how I went about diagnosing this, with the first Exchange Server 2013 installed and running, I installed a second Exchange 2013 Server with only the Mailbox server role.
On the second Exchange Mailbox server I was able to access the EMS and the Exchange Toolbox successfully.
Now from here on it's simple I only have to do a comparison of the Powershell settings in IIS Manager on these two Exchange servers.

Internet Information Services (IIS) Manager, Sites, Default Web Site, PowerShell and in the Actions Pane, choose Basic setting, physical Paths - on exchSvr1 has C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\PowerShell while C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PowerShell on exchSvr1 changed the physical path to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PowerShell

After changing all these I did an IISReset on the exchSvr1 (the affected server) and tried the EMS and Exchange Toolbox, they all worked.

---

If an Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.