FYI, if anyone else is interested in this issue.

I burned (and got credited) one of my PPS Support Contract calls on this
issue.  Apparently the feature was broken in Outlook XP SP4, and all
releases of Outlook 2003.  Microsoft will point to the "Best practices",
but won't say why this feature was removed (I suspect they didn't even
realize it).  I have been promised that this will be escalated to
possibly generate a work-around or patch (I'll believe it when I see
it), but they did confirm that it is an issue with Outlook and not
related to Exchange or anything else we did on our end (other than
upgrading Outlook).

Thanks to those of you who offered various suggestions for
troubleshooting this.

Bob

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Webb, Andy
Posted At: Thursday, October 13, 2005 5:40 PM
Posted To: ExchangeDiscussions
Conversation: Resource Booking
Subject: RE: Resource Booking


My guess is that someone filed a DCR because it behaved the way you
liked it and it was found to be an unintentional side effect or bug.  On
the other hand, it could have changed unintentionally and you've found a
regression bug.  Complete guess.  Sounds like the behavior of the
organizer field changed in OL2003.  You can open a PSS case and say
"this changed and I don't think it should have" and someone will dig in
and try to figure out if they meant to do that, if they didn't mean to
do that, or if there's in fact an optional regkey or whatnot that makes
it a configurable option.

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
ExchangeDiscussions
Sent: Thursday, October 13, 2005 4:06 PM
To: Exchange Discussions
Subject: RE: Resource Booking

OK, a little bit of success followed by more information.

I just confirmed that this is an Outlook 2003 issue, not an Exchange
issue.

I loaded up a copy of Outlook 2000 (and Outlook XP) had some in a vm.
If I book either way with these older versions the results are posted
correctly as the booking user and not as the resource.

I retried booking with Outlook 2003 with cached mode turned off, but
that doesn't matter.

Adding events directly to the calendar with Outlook 2003 doesn't show
the booking user as the "Organizer" while the older versions do.

It occurs at the time the event is booked though as I can open an
Outlook 2003 scheduled event in older Outlook and it still shows the
resource name in the "From/Organizer" field and not the booker.

That would also explain why it started happening prior to our Exchange
2003 roll-out as we rolled out Outlook 2003 prior to swinging to our
Exchange 2003 server.

Anyone with any Ideas about why this would occur in the new version of
Outlook?  BTW, we DO have all of the Office/Outlook patches applied.

Bob

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
ExchangeDiscussions Posted At: Thursday, October 13, 2005 3:42 PM Posted
To: ExchangeDiscussions
Conversation: Resource Booking
Subject: RE: Resource Booking


We have a group (security DL) that has author permissions to the shared
calendar on the resource.  They can create entries just fine and delete
their own just fine.

Somewhere Exchange IS tracking who created the event as no one else can
alter it (just like author perms should do), but in the Outlook 2003
Field "Organizer" (from after you drag it out), it only shows the name
of the resource calendar for those users who added it directly to the
calendar.  Those events that are "Booked" using the "Invite Resource"
method show the "From/Organizer" field as the booking user just like
they are supposed to.

Functionally everything is working the way it is supposed to.  Visually
it works differently depending upon which booking method was used.

All clients are Outlook 2003 in Cached Mode.  I have tested, this shows
up the same in an Outlook 2003 non-cached mode also.  I will try to find
a copy of Outlook XP our previous client and see if it is a client
difference and not a server difference.

Thanks for any insights anyone can provide!

Bob

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Webb, Andy Posted At: Thursday, October 13, 2005 9:53 AM Posted To:
ExchangeDiscussions
Conversation: Resource Booking
Subject: RE: Resource Booking


Hard to say this isn't something changed by the move to Ex2003.  What
rights exist on the mailboxes/calendars?

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
ExchangeDiscussions
Sent: Monday, October 10, 2005 10:39 AM
To: Exchange Discussions
Subject: RE: Resource Booking

Hoping no one saw this and thought I would bump it.  Just curious if
anyone had any ideas why this would change or how to re-enable the
capability? 

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
ExchangeDiscussions Posted At: Wednesday, October 05, 2005 10:31 AM
Posted To: ExchangeDiscussions
Conversation: Resource Booking
Subject: Resource Booking


I'm trying to track down an apparent anomaly and see if it is possible
to correct.

Scenario: We have about 6 conference rooms setup as resource accounts.
These were on Exchange 2000 and migrated to Exchange 2003 about 6 months
ago.  We are using the MS AutoAccept agent works OK for us overall.  

When we migrated (or possibly before can't pinpoint it) we lost the
ability to track who books an appointment when the open the calendar
directly and post it.  We sometimes try to negotiate a room swap etc,
but using the Active Appointments view with the organizer field
selected.  If we post an event by inviting the resource it tracks it
just fine, but if we click File Open other users folder... And book that
way the resource name shows up in the organizer column.

I realize that this isn't the best way to book events perhaps, but it
allows us to give our secretaries a quick way to view the entire
calendar first by opening shared calendar.

Any thoughts or suggestions?
 
________________________________

Bob Reasoner
Harris County Public Health & Environmental Services

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange
To subscribe: http://e-newsletters.internet.com/discussionlists.html/
To unsubscribe send a blank email to
[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]
To unsubscribe via postal mail, please contact us at:
Jupitermedia Corp.
Attn: Discussion List Management
475 Park Avenue South
New York, NY 10016

Please include the email address which you have been contacted with.


_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange
To subscribe: http://e-newsletters.internet.com/discussionlists.html/
To unsubscribe send a blank email to
[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]
To unsubscribe via postal mail, please contact us at:
Jupitermedia Corp.
Attn: Discussion List Management
475 Park Avenue South
New York, NY 10016

Please include the email address which you have been contacted with.


_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange
To subscribe: http://e-newsletters.internet.com/discussionlists.html/
To unsubscribe send a blank email to
[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]
To unsubscribe via postal mail, please contact us at:
Jupitermedia Corp.
Attn: Discussion List Management
475 Park Avenue South
New York, NY 10016

Please include the email address which you have been contacted with.


_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange
To subscribe: http://e-newsletters.internet.com/discussionlists.html/
To unsubscribe send a blank email to
[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]
To unsubscribe via postal mail, please contact us at:
Jupitermedia Corp.
Attn: Discussion List Management
475 Park Avenue South
New York, NY 10016

Please include the email address which you have been contacted with.


_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange
To subscribe: http://e-newsletters.internet.com/discussionlists.html/
To unsubscribe send a blank email to
[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]
To unsubscribe via postal mail, please contact us at:
Jupitermedia Corp.
Attn: Discussion List Management
475 Park Avenue South
New York, NY 10016

Please include the email address which you have been contacted with.


_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange
To subscribe: http://e-newsletters.internet.com/discussionlists.html/
To unsubscribe send a blank email to
[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]
To unsubscribe via postal mail, please contact us at:
Jupitermedia Corp.
Attn: Discussion List Management
475 Park Avenue South
New York, NY 10016

Please include the email address which you have been contacted with.


_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Web Interface: http://intm-dl.sparklist.com/read/?forum=exchange
To subscribe: http://e-newsletters.internet.com/discussionlists.html/
To unsubscribe send a blank email to [EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]
To unsubscribe via postal mail, please contact us at:
Jupitermedia Corp.
Attn: Discussion List Management
475 Park Avenue South
New York, NY 10016

Please include the email address which you have been contacted with.

Reply via email to