I think the 6-month period can be changed in the Resource Settings in OWA.  I 
put mine at a year.

Jay Dale
I.T. Manager, 3GiG
Mobile: 713.299.2541
Email: jay.d...@3-gig.com 

Confidentiality Notice: This e-mail, including any attached files, may contain 
confidential and/or privileged information for the sole use of the intended 
recipient. If you are not the intended recipient, you are hereby notified that 
any review, dissemination or copying of this e-mail and attachments, if any, or 
the information contained herein, is strictly prohibited. If you are not the 
intended recipient (or authorized to receive information for the intended 
recipient), please contact the sender by reply e-mail and delete all copies of 
this message.


-----Original Message-----
From: Kurt Buff [mailto:kurt.b...@gmail.com] 
Sent: Thursday, February 25, 2010 3:19 PM
To: MS-Exchange Admin Issues
Subject: Re: Direct Resource booking for Exchange 2003

Interesting.

So, if I, as a lowly accountant who is not a member of this group, try
to book a conference room as a resource (not as an optional or
mandatory attendee), the attempt fails?

That's not what is wanted. I wish anyone to be able to book the
resource as a resource, but not as a mandatory or optional attendee.
Further, I want to arrange it so that people who open the calendar for
the resource directly are prevented from entering new appointments
directly, or deleting existing ones.

I'm beginning to suspect that this won't work with the direct booking
model, and that I might have to implement Auto Accept Agent. The
benefit from that, according to
http://msexchangeteam.com/archive/2006/02/22/420275.aspx is that the
limit is 6 months. I'd like it to be 1 year, but I can probably
persuade folks to live with 6 months.


Kurt

On Thu, Feb 25, 2010 at 12:47, Chinnery, Paul <pa...@mmcwm.com> wrote:
> Kurt,
>
> I would think it is the same.  We upgraded from 2000 to 2007 last year.  We 
> have a Meeting Planners security group set up in AD.  They are the only ones 
> who can book resources.  Works fine for us.
>
>
>
> -----Original Message-----
> From: Kurt Buff [mailto:kurt.b...@gmail.com]
> Sent: Thursday, February 25, 2010 2:59 PM
> To: MS-Exchange Admin Issues
> Subject: Direct Resource booking for Exchange 2003
>
> All,
>
> There is advice in this link:
> http://www.slipstick.com/calendar/skedresource.asp#ol2000
>
>        :TIP: Using your Exchange Server administration tool,
>        set the mailbox to not accept messages from anyone.
>        (A distribution list or security group is good for this.)
>        That way, if users forget and add the resource as a
>        required or optional attendee, the request will bounce
>        back to them from the resource mailbox.
>
> And, I do specifically remember our Exchange 5.5 server being
> configured this way. However, after being told that some mysterious
> things are happening with our resource calendars, I find (using ADUC)
> that all of the resources are configured to accept mail from anyone.
>
> However, my memory of what happened during our upgrade is dim and
> vague, and I was wondering if the tip above still applies, or if
> things work differently.
>
> I ask, because as a test I disabled sending email on one resource, and
> almost immediately got a complaint from one of our staff that she was
> getting refused email notifications on a long-standing recurring
> meeting, and it looked to me as if she had done the correct thing by
> booking the room as a resource, so I've switched it back to the way it
> was.
>
> I've done some googling, and don't see clear guidance on this, so a
> word from someone more knowledgeable than me would be appreciated.
>
> Lastly, will following the tip above prevent someone from opening a
> resource calendar and directly entering an appointment in it? If not,
> is there a way to do that and preserve direct resource booking?
>
> Kurt
>
>


Reply via email to