We have a mixed Exchange 5.5 and Exchange 2K setup. All of our public folders reside on the 2K box.
I have a user saying he cannot see a public folder, which is under another folder. So, I gave him "owner" rights to the Top level folder, called "network support" and underneath that folder there is "schedule". He also has "owner" rights on that folder, yet he says he cannot see the folder.
Is it a 5.5 user that can not "see" the items? If this is the case is the 5.5 user in another domain? If both of these are true - run domain prep [in domain where 5.5 resides] and then create a RUS to that domain.
The users mailbox resides on the Exchange 5.5 box, while the Public folders are on the Exchange 2k box.
There is a two-way ADC connection setup. The Exchange 2k box is in a domain, which is separate from the domain that the 5.5 box is in. But trust relationships exist between the two domains.
I understand what you are saying. We had the [almost] exact same issue. The HQ site was upgraded to E2K. Most of the field sites were at E5.5. A calendar on the E2K server could not be viewed by E5.5 users who were in another domain - even though the two-way trust was in place. E5.5 users from the HQ domain could view the calendar. After a goodly bit of time with Microsoft product support on this one, we installed the RUS to the other domain and everything became crystal clear.
This was proven out by looking at the AD attributes that had been pushed out to the other servers in the forest. The ADC pushes out some and the RUS pushes out some. Microsoft is very vague on this issue.
The user that could not access the calendar had the attributes proxyAddresses, showInAddressBook, and textEncodedORAddress, but was missing attributes msExchALObjectVersion, msExchUserAccountControl, and msExchPoliciesIncluded. All of these attributes are provided by the RUS, but the first three attributes are also provided by ADC.
Missing attributes equates to null values not being stored in AD.