Exchange 2007 Free/Busy not working after migration to new server

We migrated our Exchange server to a new computer.  All works except Free/Busy and Out of Office.

When users try to see Free/Busy or Out of Office in Outlook 2007 they get the message that the server is unavailable.

If I try to do a GetWebServicesVirtual Directory in the managment shell it tells me that it cannot reach IIS on the old Exchange server.

What to do?

Thanks

ciosystemsAsked:
Who is Participating?
 
MesthaConnect With a Mentor Commented:
They run off the availability service. You will need to do the test again to see what URLs are returned for the availability URL.

You might also want to look at this blog posting.
http://www.exchange-genie.com/2007/07/exchange-2007-autodiscover-service-part-1/
The images are broken, but the content is still good.

Simon.
0
 
MesthaCommented:
Something hasn't been migrated across correctly, or there are still settings in the domain for the old server.
Has the old server been removed? Was it removed correctly using add/remove programs?

Both of those settings that you have flagged are coming from the availability service. I would start with an autodiscover check (hold down CTRL while right clicking on the Outlook icon in the system tray) and check what URLs it is giving out and ensure that they are valid and resolve to the correct place.

You may also want to run the Best Practises tool from the toolbox, see if that flags any errors.

Simon.
0
 
ciosystemsAuthor Commented:
https://autodiscover.domain.com fails

Is there a place to modify that so it will point to our server instead of that URL?
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
ciosystemsAuthor Commented:
The DNS record for autodiscover.domain.com pointed to the old Exchange server.  I updated it.  Now the autodiscover check succeeds but Free/Busy and Out of office still don't work.
0
 
ciosystemsAuthor Commented:
I should add that it works over OWA.
0
 
ciosystemsAuthor Commented:
I ran the best practices analyzer.  It showed no errors.

I ran the email autoconfiguration test:

I get:

autodiscover to:  https://autdiscover.xyzdomain.com/autodiscover/autdiscover.xml failed

localdiscover for xyzdomain.com failed

redirect to  https://autdiscover.xyzdomain.com/autodiscover/autdiscover.xml failed

srv record lookup for xyzdomain.com failed
0
 
MesthaCommented:
Does that URL resolve internally?

Simon.
0
 
ciosystemsAuthor Commented:
Yes
0
 
MesthaCommented:
Did you go through the blog posting that I entered above?

Simon.
0
 
ciosystemsAuthor Commented:
This is odd.....  We are using Server 2008.  I cannot see the Configuration container in ADSIEDIT.MSC.... it does not appear in the list.
Hint?

Thanks.
0
 
ciosystemsAuthor Commented:
I found how to get to the config.  Under naming context.....
0
 
ciosystemsAuthor Commented:
ALL FIXED!!!!!

Your blog referral solved the issue.  I did a TestOutlookWebServices in the EMS and found that the permissions for the EWS website were set to Anonymouse authentication.  I changed it to Integrated Windows Authentication and all is well.

Thank you!
0
 
ciosystemsAuthor Commented:
He pointed me to a blog that guided me through diagnosis.
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.

All Courses

From novice to tech pro — start learning today.