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

Question on Exchange EWS in Exchange 2010 SP1

I have a user that is having issues with Lync and Exchange 2010 SP1. I don't know the specifics of the error just yet but this prompted a different question as to whether EWS was enabled for this user. Now I would think this would be the default for Exchange. I looked at some mailboxes and using the get-casmailbox command, examined a few mailboxes. I noticed that EWSEnabled is set to blank.I though well this could not be possible because everything is working. Maybe its set Organization wide? Using the get-OrganizationConfig command and piping to FL, I found the EWSEnabled setting but its blank also!! So, my question is why does it not say Enabled at the Org level. Is blank an implied Enable?
0
osiexchange
Asked:
osiexchange
  • 3
  • 3
1 Solution
 
PradeepCommented:
AFAIK it is not enabled by default.
We should enable using the commands which u have mentioned.

once go through this article :

http://thoughtsofanidlemind.wordpress.com/2010/08/12/controlling-ews-access-in-exchange-2010-sp1/
0
 
osiexchangeAuthor Commented:
I already read that article. That is what prompted this post. How can it be that EWS is not enabled when things like Free/Busy, Rules, Out of Office and the laundry list of other services provided by EWS is working?
0
 
PradeepCommented:
I dont understand why it was showing null to you.
try set command once and test.
0
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

 
PradeepCommented:
Sorry for above post :

EWS will be enabled by default in Exchange 2010 with no changes needed. It can be affected by common changes made to the system after installation. Installing an SSL certificate with a different name than the server's can cause problems.
For example  using mail.company.com instead of exmail01.company.com

Use Set-AutodiscoverVirtualDirectory command  to change the Internal and External URLs used to connect to EWS/Autodiscovery.

0
 
osiexchangeAuthor Commented:
I think we are all set with our certificates. We have been running for at least a year. I was careful in ceritficate creation and we use SAN certificates for everything. This all came up because I had someone from our tech support team say EWS is not working for a particular user. I believe the problem is that Conversation History is not being saved in Outlook for this user and apparently this is somehow tied to EWS in Exchange. I started looking around and found Redmonds article and then looked at the mailboxes and Organization. I was surprised to find a Null value here but certainly reluctant to change anything. My other question is why Null?
0
 
osiexchangeAuthor Commented:
I found the solution myself my calling Microsoft
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

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

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