Hello

After installation on windows domain server/controller 2012 R2.

I got this message:

VERBOSE: Connecting to GolfServer.GOLFKLUB.local.
New-PSSession : [golfserver.golfklub.local] Connecting to remote server golfserver.golfklub.local failed with the follo
wing error message : The WinRM client cannot process the request. The WinRM client tried to use Kerberos authentication
 mechanism, but the destination computer (GolfServer.GOLFKLUB.local:80) returned an 'access denied' error. Change the c
onfiguration to allow Kerberos authentication mechanism to be used or specify one of the authentication mechanisms supp
orted by the server. To use Kerberos, specify the local computer name as the remote destination. Also verify that the c
lient computer and the destination computer are joined to a domain. To use Basic, specify the local computer name as th
e remote destination, specify Basic authentication and provide user name and password. Possible authentication mechanis
ms reported by server:   Digest Negotiate For more information, see the about_Remote_Troubleshooting Help topic.

I tried to find solution on many forums and I also check other erros in Event Log and Kerberos...

I also cannot connect to Administration center.

Can anyone help me, please.

Thank you very much

• Moved by Jason Johnston [MSFT]Microsoft employee Tuesday, February 10, 2015 3:36 PM Not a development question

Hi VachtiCZ,

Thank you for your question.

By the error, we could do the following steps to troubleshoot:

1. If there are another application which is installed on GolfServer.GOLFKLUB, we could open IIS and navigate Default Web Site to check if  the port 80 has been used by another application. if that we could change the port of application.
2. Check if we have disable the Kerberos authentication

   a.  Run gpedit.msc in Run

   b. Navigate Computer Configuration>Administrative Templates>Window Components>Window Remote Management(WinRM)>WinRM Service

   c. Check if  we have selected Enable on Disallow Kerberos authentication

       d. Then we could use gpupdate /force to update group policy.

I also cannot connect to Administration center

A: It was caused by the above error. So if we solve this error, we will access EAC. if there are coexistence in organization, for example Exchange 2010, we could refer to the following link to access EAC:

https://technet.microsoft.com/en-us/library/jj150562(v=exchg.150).aspx

In addition, I strongly suggest we didnt install Exchange server on Domain controller on production.

If there are any questions regarding this issue, please be free to let me know. 

Best Regard,

Jim

• Edited by jim-xu Wednesday, February 11, 2015 5:47 AM
• Marked as answer by Simon_WuMicrosoft contingent staff, Moderator Tuesday, February 17, 2015 9:36 AM

Hello

Thank you very much. I know that now it is not great to have Exchange on domain controller, but we have only one machine.

Now I uninstalled AD Certification server and etc.

I little bit know where is the problem, because the Exchange web is not runnig, but I tried to disable all other webs and I am still trying to change ports for secure exchange connection. And still I cannot run web server in IIS management. I have always used ports.

I will check that with Netstat -a -n -o .

Thank you very much