One of our more junior Exchange techs hit a problem on an Exchange 2013 SP1 install Single Server client access and milbox roles
After working fine, for a few days after a reboot (no patches were applied between reboots) ECP and OWA were giving http 500 errors after logging in. His Google Foo located this site http://www.noelpulis.com/fix-error-500-when-loading-shell-or-ecp-on-exchange-2013-sp1/ He tried the time sync he tried the WinrM install (which he installed) Then he tried the recreate powershell Virtual directory the remove went well. But when he tried the New-Powershellvirtual directory he got a page of errors. Now when you start Exchange management shell you get New-PSSession : [td-ex1.tdocc.local] Connecting to remote server td-ex1.tdc.local failed with the following error message : The WinRM client received an HTTP status code of 403 from the remote WS-Management service. 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 : -2144108273,PSSessionOpenFailed All articles I can find about fixing this all use Powershell, and the Exchange one isn't working, and if you enter the commands in normal powershell it doesn't recognise them Any one got any ideas. The server is supposed to go to site tomorrow Thanks Graeme -- Good news everyone, you have just received an e-mail from me!
