• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 812
  • Last Modified:

Problems Configuring Exchange in SBS 2011

Hey Everyone -

Im trying to configure Exchange using the "Internet Address" wizard. However running into some issues. The wizard successfully creates the access to https://webmail.domain.com, however has a problem configuring exchange:

"The WinRM client cannot process the request. The WinRM Client tried to use the Kerberos authentication mechanism, but the destination computer (SERVER:80) returned an access denied error. Change the configuration to allow Kerberos  authentication to be used or specifiy one of the authentication mechanisms supported by the server..."

Any ideas?
0
tecpub
Asked:
tecpub
  • 4
1 Solution
 
SuperTacoCommented:
what account are you using for the migration?  is it domain, Schema, and enterprise admin?  also, i would not recommend "webmail.domain.com"  SBS uses "remote.domain.com" By default.  there is no harm done in changing it, it is just easier to work with the default when getting a UCC/SAN certificate.  Also make sure the account you're using is an Exchange org Admin in AD.
0
 
tecpubAuthor Commented:
Thanks, I will try that and check back.
0
 
tecpubAuthor Commented:
I am using domain\administrator for this wizard. This user is also a organizational manager.

I also changed back the prefix to remote rather than webmail, since this is a good point and it wont kill me either way.

However I'm still getting the same error. Any other ideas?
0
 
tecpubAuthor Commented:
Also, one thing to note. I did just deploy SharePoint 2010. I'm pretty sure it's using Port 80.

Does that cause any conflict?
0
 
tecpubAuthor Commented:
Found out that there was a conflict in the bindings in IIS. I recently deployed Sharepoint and found that host name was not entered for it. Once I made that change and restarted IIS, everything started working
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now