Solved

Outlook 2003 users can't see Free Busy Information in mixed mode Exchange environment

Posted on 2014-04-03
3
385 Views
Last Modified: 2014-04-04
We have Ex 2003 servers and a couple of Ex2010 HubCAS servers kind of conexisting at the moment whilst we migrate.

We have new OL2003 users who cannot see any Free Busy data in their calendars, they receive the 'Free Busy Unavailable' message and when running the Test E- Auto Configuration I receive the following:

Attempting URL https://autodiscover.domainname.co.uk/Autodiscover/Autodiscover .xml found through SCP
Autodiscover to https://autodisconver.domainname.co.uk/autodiscover/Autodiscover.xml starting
GetLastError =0; httpStatus=200
Autodiscover to https://autodiscover.domainname.co.uk/Autodiscover/Autodiscover .xml Failed (0x80c8203)
Attempting URL https://cas1.domainname.local/Autodiscover/Autodiscover .xml found through SCP
Autodiscover to https://cas1.domainname.local/Autodiscover/Autodiscover .xml starting
GetLastError=12002; httpStatus=0
Autodiscover internet timeout against URL https://cas1.domanname.local/Autodiscover/Autodiscover .xml

And so on......

What I see in the Calendar for the 2003 calendars is 'Free/Busy information is not available'

Does there have to be a Replica of the Public folder on Ex2010?
0
Comment
Question by:CTCRM
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 15

Accepted Solution

by:
jrhelgeson earned 200 total points
ID: 39975307
Exchange 2003 looks to the Public Folder for its Free/Busy information.  Have those users had their mailboxes migrated yet?  If the mailbox still exists on the 2003 server then it should still pull the public folder info from the old PF server.

Have you created a new PF on the new exchange environment?

Also - Exchange 2003 doesn't support autodiscover.  I think we're dealing with 2 different situations here.
0
 
LVL 43

Assisted Solution

by:Taurus
Taurus earned 200 total points
ID: 39976560
Best option is to move to Outlook 2010 or above. outlook 2003 is not a recommend client for Exchange 2010 and known for various issues with Exchange 2010. It is now more than decade old and Exchange is now totally redesigned.
0
 
LVL 2

Author Closing Comment

by:CTCRM
ID: 39977415
Thanks Guys, Free/Busy has started working for those 2003 clients, not sure why as I didn't make any changes. However, a full migration is long over due and should pushed out.
0

Featured Post

Creating Instructional Tutorials  

For Any Use & On Any Platform

Contextual Guidance at the moment of need helps your employees/users adopt software o& achieve even the most complex tasks instantly. Boost knowledge retention, software adoption & employee engagement with easy solution.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If you troubleshoot Outlook for clients, you may want to know a bit more about the OST file before doing your next job. IMAP can cause a lot of drama if removed in the accounts without backing up.
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …

696 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question