Problem with WinRM in Exchange Management Shell and Exchange Toolbox on a new exchange, with CAFE and is on Singl e-Server Installation

While deploying MS Exchange-I experienced issues with accessing the Exchange Management Shell and Exchange Toolbox. Whenever I tried to open the Exchange Management Shell I kept get the following error:


verbose:connecting to Exchange2013.DOMAIN.LOCAL
New-pssession: [exchange2013.domain.local] Connecting to Remote server exchange2013.domain.local failed with the following error message:the WinRM client cannot process the requ Est. The WinRM client tried to use Kerberos authentication mechanism, but the destination computer (exchange2013.domain.local) Returned an ' access Denied ' error. Change the configuration to allow Kerberos authentication mechanism to be used or specify one of the authentication Mechan ISMS 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 is joined to a domain. To use Basic, specify the local computer name as the remote destination, specify Basic authentication and provide user Nam E and password. Possible authentication mechanisms reported by Server:for more information, see the about_remote_troubleshooting help top IC.

Verbose:connecting to EXCHANGE2013. Local.com.
New-pssession: [exchange2013.domain.local:80] connecting to remote server exchange-bt.tmal.com 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 (EXCHANGE2013.LOCAL.COM:80) Returned an ' access Denied ' error. Change the configuration to allow Kerberos authentication mechanism to be used or specify one of the authentication Mechan ISMS 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 is joined to a domain. To use Basic, specify the local computer name as the remote destination, specify Basic authentication and provide user Nam E and password. Possible authentication mechanisms reported by Server:for more information, see the about_remote_troubleshooting help top IC.

Workaround and Resolution:

Searching the error on Google and all over the web resulted in various and numerous solutions most of the worked for there E Nvironment but failed to the address my issue, but made me realize the This is a Powershell website issue.
Exchange installs a Default Website (Client Access front End) on port, and 443 and also a backend Website on port 8 1 and 444.

Here's how I managed to sort out my issue, I had to change the physical path From:c:\program files\microsoft\exchange Se Rver\v15\frontend\httpproxy\powershell To:c:\program Files\Microsoft\Exchange Server\V15\ClientAccess\PowerShell And then issued an IISRESET.

This is what I went about diagnosing this, with the first Exchange Server installed and running, I installed a second Exchange server with only the Mailbox server role.
On the second Exchange Mailbox server I am able to access the EMS and the Exchange Toolbox successfully.
Now, on it's simple I, only has the comparison of the Powershell settings in IIS Manager on these and Exchang E 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 exchSvr2 have 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 a iisrest on the EXCHSVR1 (the affected server) and tried the EMS and Exchange Toolbox, th EY all worked.