You must use caution when changing the IIS settings for Exchange 2010.  The reason is simple.  Powershell or the Exchange management console EMC uses IIS to manage Exchange.  So if you incorrectly change settings you will render your Exchange EMC and Powershell useless.\n
VERBOSE: Connecting to cas01.testDomain.com\n The WinRM service cannot process the request because the request needs to be sent to a different machine. Use the redirect information to send the request to a new machine.  Redirect location reported: https://owa.testDomain.com/owa/PowerShell. To automatically connect to the redirected URI, verify "MaximumConnectionRedirectionCount" property of session preference variable "PSSessionOption" and use "AllowRedirection" parameter on the cmdlet.\n    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportRedirectException\n    + FullyQualifiedErrorId : PSSessionOpenFailed\nFirst thing you'll want to do is go to your default website and change the redirect.  Use the settings from this image below.  Use them exactly, you have been warned.\n\nOnce that is complete you have to uncheck redirect on all of these sub directories.\n
    \n\t
  • aspnet_client
    • \n\t
  • Autodiscover
    • \n\t
  • ecp
    • \n\t
  • EWS
    • \n\t
  • Microsoft-Server-ActiveSync
    • \n\t
  • OAB
    • \n\t
  • PowerShell
    • \n\t
  • Rpc
    • \n
\nExchange, Exchweb, and Public virtual directories should redirect to /owa.\nNow if you try to open Internet Explorer you will receive a HTTP 403.4 error.  That is because SSL is required.  Select the default website just like the image below and remove the SSL requirement.\n\nOnce again you will have to go through these virtual sub directories and make sure the SSL box IS checked!\n
    \n\t
  • Autodiscover
    • \n\t
  • ecp
    • \n\t
  • EWS
    • \n\t
  • Microsoft-Server-ActiveSync
    • \n\t
  • OAB
    • \n\t
  • owa
    • \n\t
  • Rpc
    • \n
\nWarning: If you require SSL for the PowerShell virtual directory, you will render Remote PowerShell inoperable!