P
paulc
Exchange 2000
mixture of Outlook 2000 and 2003 clients
(Note..I posted this on a couple of other MS newsgroups but haven't found a
solution since posting.)
We use mailboxes to set up resource scheduling (each resource having it's
own mailbox). Recently, we added a new resource. Clients with Outlook 2000
can view the free/busy information on this resource. However, those with
Outlook 2003 cannot. I took a test machine and installed O2003 on it and
was surprised to see that I could view free/busy on this resource. I then
installed Office2003 service pack 2 and now the client cannot view the
free/busy data. What's interesting is that the free/busy data of those
resources whose mailboxes were created prior to the release of sp2 for O2003
can be viewed.
I confirmed this again this morning. I removed all Office products and just
installed Outlook. I could view the free/busy. I then added sp2 and not I
can't view it.
I originally posted this query to the Exchange group before I discovered
that it was an Office service pack that broke it. That's why I am posting
it here.
mixture of Outlook 2000 and 2003 clients
(Note..I posted this on a couple of other MS newsgroups but haven't found a
solution since posting.)
We use mailboxes to set up resource scheduling (each resource having it's
own mailbox). Recently, we added a new resource. Clients with Outlook 2000
can view the free/busy information on this resource. However, those with
Outlook 2003 cannot. I took a test machine and installed O2003 on it and
was surprised to see that I could view free/busy on this resource. I then
installed Office2003 service pack 2 and now the client cannot view the
free/busy data. What's interesting is that the free/busy data of those
resources whose mailboxes were created prior to the release of sp2 for O2003
can be viewed.
I confirmed this again this morning. I removed all Office products and just
installed Outlook. I could view the free/busy. I then added sp2 and not I
can't view it.
I originally posted this query to the Exchange group before I discovered
that it was an Office service pack that broke it. That's why I am posting
it here.