Resource permission requirements different in 2003 from 2000?
 

We have just upgraded all our Outlook clients from 2000 to 2003 and
automatic resources that were working well before are now not working the
way we would like. Exchange 2003 is used on the server.

Using Outlook 2003, when people book a conference room, it all works well.
When people attempt to book a car, they receive a message that they don't
have sufficient permissions. Our conference rooms work fine as everyone has
at least "author" permissions. With the cars, the permissions are lower than
what we have for our conference rooms, due to some unscrupulous person that
crashed a pool car, then removed all evidence that they had ever booked it.
We don't want most people to be able to change or delete a booking (even
their own). Only the owner of the car should have permissions to delete or
change a booking.

What can we do to let a person book a car resource without having rights to
change it later? Do we have to go back to a manual booking system?

- Peter Ogden

Resource permission requirements different in 2003 from 2000?
 

Here I go, talking to myself again...

I have just found the AutoAcceptAgent on Microsoft's site. Does anyone know
whether this requires the same level of permissions as the built in
automatic accept in Outlook 20003 (the documentation isn't clear)?

- Peter Ogden

"Peter Ogden" wrote in message
...
We have just upgraded all our Outlook clients from 2000 to 2003 and
automatic resources that were working well before are now not working the
way we would like. Exchange 2003 is used on the server.

Using Outlook 2003, when people book a conference room, it all works well.
When people attempt to book a car, they receive a message that they don't
have sufficient permissions. Our conference rooms work fine as everyone
has at least "author" permissions. With the cars, the permissions are
lower than what we have for our conference rooms, due to some unscrupulous
person that crashed a pool car, then removed all evidence that they had
ever booked it. We don't want most people to be able to change or delete a
booking (even their own). Only the owner of the car should have
permissions to delete or change a booking.

What can we do to let a person book a car resource without having rights
to change it later? Do we have to go back to a manual booking system?

- Peter Ogden