Exchange 2003 SP2 Outlook 2003 SP3 I've dealt with F/B issues for many years but this one has me stumped. We have one conference room that simply will not publish its F/B info. Any user with a meeting invite will see hash marks for this room when checking availability. All other rooms work fine. All conference room mailboxes are running on a separate Exchange server (also 2003 SP2), which is in the same Admin group and Routing group as the server with the users. Things I have looked at: 1. ran /cleanfreebusy 2. made a new profile for the conference room, logged into it directly, made some dummy appointments, and then left it open for 15 minutes (the default F/B publishing time per Calendar Options) 3. made sure the room is being selected from the GAL and not from a nickname or a contact, etc. 4. If I log into the conf room and do a meeting request, the room can see its own F/B info fine but no one else's. 5. Checked LegacyExchangeDN value to make sure it did not have some strange value which would impact how its F/B info got published. 6. Same behavior with OWA (no big surprise there) What am I missing?
When you open the mailbox with Outlook is the setting configured to publish free/busy data for that mailbox? -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." . "Dave" wrote in message news:v1mPj.3273$y63.1108@trndny02... > Exchange 2003 SP2 > Outlook 2003 SP3 > > I've dealt with F/B issues for many years but this one has me stumped. We > have one conference room that simply will not publish its F/B info. Any > user with a meeting invite will see hash marks for this room when checking > availability. All other rooms work fine. All conference room mailboxes > are running on a separate Exchange server (also 2003 SP2), which is in the > same Admin group and Routing group as the server with the users. Things I > have looked at: > > 1. ran /cleanfreebusy > 2. made a new profile for the conference room, logged into it directly, > made some dummy appointments, and then left it open for 15 minutes (the > default F/B publishing time per Calendar Options) > 3. made sure the room is being selected from the GAL and not from a > nickname or a contact, etc. > 4. If I log into the conf room and do a meeting request, the room can see > its own F/B info fine but no one else's. > 5. Checked LegacyExchangeDN value to make sure it did not have some > strange value which would impact how its F/B info got published. > 6. Same behavior with OWA (no big surprise there) > > What am I missing? >
It's configured to publish 2 months out. I changed the default time to publish to 5 minutes, but I left an Outlook client logged directly into that mailbox open and idle for 40+ minutes. The first thing I did was to create a dummy meeting and then check the availability, and then I left it alone for the 40 minutes. "Ed Crowley [MVP]" wrote in message news:e3pDCdNpIHA.4928@TK2MSFTNGP04.phx.gbl... > When you open the mailbox with Outlook is the setting configured to > publish free/busy data for that mailbox? > -- > Ed Crowley MVP > "There are seldom good technological solutions to behavioral problems." > . > > "Dave" wrote in message > news:v1mPj.3273$y63.1108@trndny02... >> Exchange 2003 SP2 >> Outlook 2003 SP3 >> >> I've dealt with F/B issues for many years but this one has me stumped. >> We have one conference room that simply will not publish its F/B info. >> Any user with a meeting invite will see hash marks for this room when >> checking availability. All other rooms work fine. All conference room >> mailboxes are running on a separate Exchange server (also 2003 SP2), >> which is in the same Admin group and Routing group as the server with the >> users. Things I have looked at: >> >> 1. ran /cleanfreebusy >> 2. made a new profile for the conference room, logged into it directly, >> made some dummy appointments, and then left it open for 15 minutes (the >> default F/B publishing time per Calendar Options) >> 3. made sure the room is being selected from the GAL and not from a >> nickname or a contact, etc. >> 4. If I log into the conf room and do a meeting request, the room can >> see its own F/B info fine but no one else's. >> 5. Checked LegacyExchangeDN value to make sure it did not have some >> strange value which would impact how its F/B info got published. >> 6. Same behavior with OWA (no big surprise there) >> >> What am I missing? >> > >
Was there a response to this inquiry? I am having a very similar issue -- Cynthia Gambosh "Dave" wrote: > Exchange 2003 SP2 > Outlook 2003 SP3 > > I've dealt with F/B issues for many years but this one has me stumped. We > have one conference room that simply will not publish its F/B info. Any > user with a meeting invite will see hash marks for this room when checking > availability. All other rooms work fine. All conference room mailboxes are > running on a separate Exchange server (also 2003 SP2), which is in the same > Admin group and Routing group as the server with the users. Things I have > looked at: > > 1. ran /cleanfreebusy > 2. made a new profile for the conference room, logged into it directly, > made some dummy appointments, and then left it open for 15 minutes (the > default F/B publishing time per Calendar Options) > 3. made sure the room is being selected from the GAL and not from a > nickname or a contact, etc. > 4. If I log into the conf room and do a meeting request, the room can see > its own F/B info fine but no one else's. > 5. Checked LegacyExchangeDN value to make sure it did not have some strange > value which would impact how its F/B info got published. > 6. Same behavior with OWA (no big surprise there) > > What am I missing? > > >
