We are having random issues with Outlook 2003 clients (sp3) reguarding free/busy. The problem is difficult to describe because its random. Some users will complain that they are unable to schedule meetings becuase the user will show up unavailable (that is slash marks, not to be confused with a gray bar which indicates free/busy is being updated). Now we have tried the following switches at the client level with limited success. 1) Reboot - This problem seems to be prevaliant after the weekend, like a users free/busy just drops off after awhile2) type "C:\Program Files\Microsoft Office\Office11\Outlook.exe" /cleanfreebusy 3) type "C:\Program Files\Microsoft Office\Office11\Outlook.exe" /cleanschedplusI discovered /cleansniff .. but not sure what it does and have not ran this particular switch against any outlook 2003 client.If that doesnt work then I use the updatefb tool which seems at 1st to resolve issues. The problem is, is that the issue keeps coming back or new users experience the problem. This is VERY frustrating to try and nail down as users describe different problems#1 When a user setups a meeting they do not see their existing meetings, but can do so otherwise.#2 Some users free/busy just becomes unavailable - sometimes a reboot works.(Note we publish 6 months worth of free/busy data)The following KB article talks about possible fixes post SP3... but you have to get Microsoft to send it to you. I've tried twice now using the online submission to obtain this but no luck. http://support.microsoft.com/kb/935411The fix above seems to direclty relate to #1 Free/Busy information may be missing in a meeting requestWhen you view the Free/Busy information for an attendee in a meeting request in Outlook 2003, the Free/Busy information may be missing. NOTE: Some Unique Items About Our Mail systemWe use IIFP to send and recieve contacts across domain treesWe use Inter-Organizatoin Replication Tool to send and recieve free/busy information across TreesUnfortunately we haven't been able to determine if this is an issue with Outlook SP3 or the above configuration as they both happened near the same time, or if the issue is even related. Suggestions welcomed.