Hi,
I am needing a little help here. I have the following environment:
- Fresh install Server2008 R2 Domain Controller
- Fresh Install Server 2008 R2 Domain Member, Fresh install of Exchange Server 2010 SP3
- All dependencies have been met (I think)
I am only getting one error when connecting to Exchange through cloudpanel:
Connecting to remote server mbx1.domain.local failed with the following error message : The WinRM client cannot process the request. The authentication mechanism requested by the client is not supported by the server or unencrypted traffic is disabled in the service configuration. Verify the unencrypted traffic setting in the service configuration or specify one of the authentication mechanisms supported by the server. To use Kerberos, specify the 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 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.
I have enabled basic authentication on the powershell virtual directory.
The AppPool user is running with Enterprise admin rights.
Do you happen to know what I might be missing?
Thank You!
@skelsay Did you select basic authentication on the settings page in CloudPanel?
Also if it is a new environment and you have access, I would definitely start with 2012 R2 or 2016 server instead of 2008 R2. Not required, just a suggestion.
Would it be possible to send some screenshots of your IIS configuration and application pools?
Tried Server 2012 R2 first and got held up at the same point. Server 2008 R2 was a desperation move. Everything else seems to go smoothly. I thought it might be some security setting introduced. I presume it is a MS security issue stemming from a fully patched system to start wth, but just can’t quite locate it.
KMI Support 2018-01-10 20:23
You need to make sure you enable basic authentication with Exchange and not do it in IIS. I don’t know the issues you were having with 2012 R2 but I assure you it works fine even with up to server 2016 (Exchange and Server). I really would not advise starting off with Exchange 2010 and 2008 R2.
