• The WinRM client cannot process the request. If the authentication scheme is different

    Posted on August 20, 2013 by in Dotnet Tips & Tricks, Tips & Tricks

    If you are trying to invoke powershell commands from a client machine, failure to configure WINRM client to trust the exchange server residing on the remote will result in following error:

    Connecting to remote server failed with the following error message : The WinRM client cannot process the request. If the authentication scheme is different from Kerberos, or if the client computer is not joined to a domain, then HTTPS transport must be used or the destination machine must be added to the TrustedHosts configuration setting. Use winrm.cmd to configure TrustedHosts. Note that computers in the TrustedHosts list might not be authenticated. You can get more information about that by running the following command: winrm help config. For more information, see the about_Remote_Troubleshooting Help topic.

    Client Configuration:

    We have to do following configuration change on client machine where we run this application.

    Step 1: Launch “Local Group Policy user interface”  by typing gpedit.msc in the run promput.

    Step 2: Navigate to “Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Windows Remote Management (WinRM) > WinRM Client”.

    Step 3: Enable “Trust the remote machine”. On the setting window, add the remote exchange server name in the “trustedhostedlist” field.

    Create new user mailbox in Exchange 2010 using Powershell 3

    Be Sociable, Share!

    Written by

    Software architect with over 10 years of proven experience in designing & developing n-tier and web based software applications, for Finance, Telecommunication, Manufacturing, Internet and other Commercial industries. He believes that success depends on one's ability to integrate multiple technologies to solve a simple as well as complicated problem.

    View all articles by

    Email : [email protected]

    One Responseso far.

    1. […] note: “enable-psremoting” on it’s own might now work, you might also need to update gpedit.msc. […]

    Leave a Reply