RE: Free and Busy times not visible in OWA

Dennis,

Thanks for the advice, it is as I feared.

Could you point me to the tool you mentioned?

M@


On 29/4/05 1:32 pm, "Dennis Appelboom" <dennis.appelboom@xxxxx> wrote:

> http://www.MSExchange.org/
> 
> You do have to assign other users the right to view or edit your agenda.
> You can do this in outlook: tools --> options --> delegates.
> 
> Also, I think that you do need at least one entry in the agenda before
> it can show the busy/free time...Sounds obvious, but I think that the
> agenda is created when the first entry is added to that agenda. Before
> that, it shows up as a grey line...
> There is no way to assign calendar rights through OWA...unfortunately.
> 
> I know one tool that will assign read rights to all to view calendars in
> a exchange organization...
> 
> Hope this helps you.
> 
> Regards,
> 
> Dennis Appelboom
> XB
> 
> -----Original Message-----
> From: Matt Robbins [mailto:mrobbins@xxxxxxxxxxxxxxxxxxxxxx]
> Sent: vrijdag 29 april 2005 12:38
> To: [ExchangeList]
> Subject: [exchangelist] Free and Busy times not visible in OWA
> 
> http://www.MSExchange.org/
> 
> Hello,
> 
> You all helped me once before with the choice and configuration of my
> Exchange 2003 server, I am hoping you can help me once again.
> 
> I have OWA working fine except for the availability tab when arranging a
> meeting. Even when there are appointments on my schedule (created in
> OWA)
> the busy times are not visible to others when checked through the
> availability tab.
> 
> I know Outlook requires you to share your schedule but I can find no
> such
> setting through OWA.
> 
> I presume that it is some simple setting change that is required but I
> have
> checked the two books I am reading on exchange, the Microsoft site and
> MSExchange.org with no result so clearly I am not using the right
> terminology when I search.
> 
> Many thanks in advance.

-- 
Matt Robbins - Network Manager
Brooke Weston City Technology College
T:01536 396366 F:01536 396867
mrobbins@xxxxxxxxxxxxxxxxxxxxxx

Other related posts: