We help IT Professionals succeed at work.

Exchange 2010 Free/busy, Mailtips, OAB and Autoreplies not working with Outlook 2007/2010 client

Chadish7
Chadish7 asked
on
I have a problem with my Outlook clients on my network. They can't see the above information. I've tested autodiscover service using https://www.testexchangeconnectivity.com/ and it checks fine.

My environment is:

Windows 2003 AD and DNS
Exchange 2010 (CAS, Hub and MB) with Rollup 3 on Server A
Exchange 2007 (CAS, Hub and MB) with all Rollup's and SPs on Server B

Server B no longer hosts any mailboxes or OWA services and none of the pointers point to it, It's only there because I literally can not install it until SP3 for 2007 comes out (it's installed on win2008 R2)

Now, this whole set up was working just fine for months and months and now it's not. Like I say, autodiscover seems to be working fine but still these items are not even trying to work.

I also have 2 ISA/TMG firewalls, one for publising websites (OWA + RPC + autodiscover, etc) and the other is a web proxy and default gateway for our network. I'm only mentioning this  because they did affect this before but I managed to sort it out.

Wrap your head around that. I'm open to questions
Comment
Watch Question

BusbarSolutions Architect

Commented:
those services relies on the webservices internally not autodiscover exteranlly, can you check your config against my article below:
http://www.experts-exchange.com/articles/Software/Server_Software/Email_Servers/Exchange/Exchange-2007-2010-Web-services-and-Autodiscover-Ultimate-Troubleshooting-Guide.html

Author

Commented:
When ever I try to log on to /EWS on the CAS server it returns Error 403. Any Ideas?

Author

Commented:
I have tried to change the authentication types on the virtualdirectory with no joy.
BusbarSolutions Architect

Commented:
can you do
Get-WebServicesVirtualDirectory | remove-WebServicesVirtualDirectory
then
new-WebServicesVirtualDirectory
try again

Author

Commented:
When I run Get-WebServicesDirectory I get a Access Denied. Here is the Error:

An IIS directory entry couldn't be created. The error message is Access is denied.
. HResult = -2147024891
    + CategoryInfo          : NotInstalled: (EXCH2007\EWS (Default Web Site):ADObjectId) [Get-WebServicesVirtual
   Directory], IISGeneralCOMException
    + FullyQualifiedErrorId : 4AF6608A,Microsoft.Exchange.Management.SystemConfigurationTasks.GetWebServicesVirtualDir
   ectory

Author

Commented:
Any ideas? Any one?
BusbarSolutions Architect

Commented:
can you run /preparedomain again and re-publish the permissions and try again

Author

Commented:
How do you re-publish permissions?
BusbarSolutions Architect

Commented:
run setup.com /preparedomain

Author

Commented:
Still the Same thing

Creating a new session for implicit remoting of "Get-WebServicesVirtualDirectory" command...
An IIS directory entry couldn't be created. The error message is Access is denied.
. HResult = -2147024891
    + CategoryInfo          : NotInstalled: (EXCH2007\EWS (Default Web Site):ADObjectId) [Get-WebServicesVirtual
   Directory], IISGeneralCOMException
    + FullyQualifiedErrorId : 4AF6608A,Microsoft.Exchange.Management.SystemConfigurationTasks.GetWebServicesVirtualDir
   ectory

Author

Commented:
the Get-WebServicesDirectory works fine on the old Exchange 2007 box

Author

Commented:
It even lists in the EWS folder on the Exchange 2010 box
BusbarSolutions Architect

Commented:
can you go to IIS and look for the EWS folder does it exists.
are you sure that your user is member of the organization admin group

Author

Commented:
Yes the EWS folder is there in IIS and Yes the user is apart of the Exchange Organization admins. I tried with 2 different users, both Org Admins.

I need to interject here that the Exchange 2007 is installed on a Windows 2008 R2 box. I've asked about uninstalling it and I'm told that I have to wait for SP3 later this month. Would that make a difference on this problem tho?
BusbarSolutions Architect

Commented:
Exchange 2007 is not supported on 2008 R2, I believe this is the issue
Commented:
I called Microsoft and they solved the issue. The problem was that the Exchange Trusted Subsystem was not an administrator on the Exchange 2007 server. Once this was added, it all worked.