outlook 2011 for mac exchange 2013

have exchange 2010 and exchange 2013 in my environment.  Migrating everyone from 2010 to 2013. 2010 server has all roles.  2013 deployment has 3 servers (2 cas and 1 MBX)  I started having trouble with outlook for mac 2011 and some phones after moving everyone to 2013.  I thought i had fixed the issues by increasing some of the throttling values on exchange 2013 server.  I have also used the test connectivity website Microsoft offers.  The exchange ews, notification test is successful against the 2010 server.  It fails against the 2013 servers.  The external URL's are configured correctly on the cas servers.  I've included a snip of the error:  <testresult status="Error" errorid="236ff98a-34b2-4bdd-b4dd-942887359316" contentUrl="" testdescription="Getting subscription events and confirming that the expected events exist." resultdescription="Events couldn't be retrieved or confirmed." additionaldetails="No notifications were returned.
cmkeurAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

tshearonCommented:
Have you actually gone and checked the EWS settings to see if it is correct? The following link describes how to use test-webservicesconnectivity to check to see if your ews settings are correct on your 2013 CAS.

http://technet.microsoft.com/en-us/library/aa998328%28v=exchg.150%29.aspx

You can view the ews settings on a particular server yourself by using Get-WebServicesVirtualDirectory -Identity YOURCASSERVERNAME.

You can set EWS by using your desired method by following this link:

http://technet.microsoft.com/en-us/library/aa997233%28v=exchg.150%29.aspx
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
cmkeurAuthor Commented:
good idea but the new-testcasconnectivityuser ps script fails.  PS can't parse the get-exchangeserver cmd-let in the script.  Any ideas on that one?
0
cmkeurAuthor Commented:
error is here
get-ExchangeServer : The term 'get-ExchangeServer' is not recognized as the name of a cmdlet, function, script file,
or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and
try again.
At C:\Program Files\Microsoft\Exchange Server\V15\Scripts\new-TestCasConnectivityUser.ps1:261 char:21
+   $exchangeServer = get-ExchangeServer $(hostname.exe) -ErrorAction:SilentlyCont ...
+                     ~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (get-ExchangeServer:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

cmkeurAuthor Commented:
please disregard my last two comments, i figured that out
the results of the test-webservicesconnectivity -ClientAccessServer provides two scenarios (autodiscover: soap provider and EWS: getfolder failure.
I'll research this but if you have a fix that would greatly appreciated.
0
tshearonCommented:
Have you checked the ews settings yet by running the get commands in my first post? If not you should do that and look for incorrect url's as being a potential issue. Typically this type of connectivity issue is due to incorrect ews url settings or incorrect authentication settings for the ews virtual directory in IIS.
0
cmkeurAuthor Commented:
i ran a get-webservicesvirtualdirectory | format-list and the external url for the 2010 box is correct as are the external url's for the 2013 box.  The only difference between the two are auth methods, 2010 has ntlm, windowsintegrated and wssecurity.  for the 2013 boxes basic, ntlm,windowsintegrated,wssecurity oauth.  So i guess the question is what is the correct auth methods?
0
Adam FarageEnterprise ArchCommented:
The external URL's are configured correctly on the cas servers.

Make sure the ExternalURL and InternalURL are proper on the EWS virtual directory. If it is Outlook for Mac, and they are internal they will utilize the InternalURL.

Furthermore, make sure that you have the DNS A records internally pointing to Exchange 2013 and not Exchange 2010.
0
cmkeurAuthor Commented:
the internal URL's and DNS are both correct also.
0
cmkeurAuthor Commented:
found out why the soap and ews test failed.  I used the local computer name rather than the fqdn in the test statement.
0
Adam FarageEnterprise ArchCommented:
If you rerun the test with -Verbose what is the output then?
0
cmkeurAuthor Commented:
they all are successful.  It must be a client issue.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.