Have an availability address space of sub.domain.com with an access method of public folder. We have a recipient of type mailUser with an external SMTP address of user@sub.domain.com. The free/busy data for this user is perfectly visible from OLK2007 and OWA, but not from OLK2003.Seems I'm missing something here...if the access method is public folder aren't OLK (both versions) and OWA going to \non_ipm_subtree\schedule+ free busy\EX:/O=org/OU=AG/cn=recipients/cn=user.eml for free/busy? This users legacyExchangeDN is /o=org/ou=ag/cn=recipients/cn=userThanks,alex

Hi, Before we going on to solve the issue, lets try to clarify it first. 1. Which domain does your exchange server locate? 2. Do you mean user which is a contact with external email address cannot obtain free/busy information? 3. What is the relationship between sub domain and your domain? 4. If all the Outlook 2003 users cannot view free/busy information or not? If only one user free/busy information cannot be viewed, then I suspect something corrupt for that users free/busy information. If Outlook 2003 users cannot view all the free/busy information, then please try to go through the steps below to solve the problem. Note: If user@sub.domain.com use outlook 2003 to update its free/busy information, then it will be located in local public folder. With Exchange 2007,we are using availability service to retrieve the free/busy information for a user which is stored directly in the mailbox rather than from the Schedule+ Free/Busy system folder. Outlook 2003 does not support the availability service in Exchange 2007 which is replacing free/busy in Exchange 2003. So, with users using Outlook 2003, if you do not have free/busy, they will have problem working with calendar items such as meeting requests. What we need to check is: 1. Please try to check if you have public folder created in Exchange 2007. 2. Please check if you have system folder in Exchange 2007 public folder store. 3. Please try to check the public folder replic list. We can use PFDavAdmin to check it. Note: We must add the replica free/busy system folder on the Exchange 2007 server, and a full replicate must be completed before you decommission the Exchange 2003 server. Legacy free/busy should be available when installing an Exchange 2007 server into an Exchange 2003 organization as Exchange 2007 will include a public folder store for it. Outlook 2003 clients will not have connectivity issues if this is followed. More information to share with you: Users who use Outlook 2003 cannot publish their free/busy data in Exchange Server 2007 http://support.microsoft.com/kb/945602 Microsoft Exchange Server Public Folder DAV-based Administration Tool http://www.microsoft.com/downloads/details.aspx?FamilyId=635BE792-D8AD-49E3-ADA4-E2422C0AB424&displaylang=en Regards,Xiu

Hi Xiu,Let's see if I can clarify...1. Exchange exists in domain.com, sub.domain.com is a third party mail server that supports updating f/b using public folders.2. Public folders only exist on Ex2007 server (single...no replicas), the folder for this user is visible under \non_ipm_subtree\schedule+ free busy\EX:/O=org/OU=AG/cn=recipients/cn=user.eml3. Single server so only one replicaOutlook 2003 users can view f/b for all exchange users, and even some sub.domain.com users. Outlook 2007 users can see f/b for all exchange users...and all sub.domain.com users. OWA has the same result as OLK2007. I guess the question is what are the OLK2007/OWA2007 clients doing differently? The f/b data for users of sub.domain.com is published to the public folder, so do OLK/OWA 2007 still use availability service for those users? If so then that makes sense, I have just never read that or heard of that anywhere...-alex