Hallo Everybody, Hope someone can help me. I think the configuration is quit simple but sadly i have a issue. i want that everytime a delegate gets a request. No autoaccpect. My Infrastructure is: Windows 2008 R2 Domain and Exchange 2010 RTM RollUp 4 (no SP1). My Problem is: My resource Mailboxes perform absolutely correct during a "out of policy" request but during a "in policy" request the delegate don´t get the request and the resource accept the request themselve. Current configuration: out of policy: Users who are allowed to submit... -> all users in policy: - meeting request that will be automatically approved -> selected recipients <no recipients added> - subject to approval by a... delagate: -> all users Delegate is set, forwarding is set, booking attendant is enabled. Everything else is default. I create a new resource Mailbox and try a other user as delatage. same problem! I think there is no permission problems becouse the delegate gets out of policy requests. Any suggestions?? Bug? Knowhow Problem?

Get-CalendarProcessing -Identity my_room | fl RunspaceId : 4594cb2d-13ed-43a9-a31c-735a3e1d50b4 AutomateProcessing : AutoAccept AllowConflicts : False BookingWindowInDays : 365 MaximumDurationInMinutes : 1440 AllowRecurringMeetings : True EnforceSchedulingHorizon : True ScheduleOnlyDuringWorkHours : False ConflictPercentageAllowed : 0 MaximumConflictInstances : 0 ForwardRequestsToDelegates : True DeleteAttachments : True DeleteComments : True RemovePrivateProperty : True DeleteSubject : True AddOrganizerToSubject : True DeleteNonCalendarItems : True TentativePendingApproval : True EnableResponseDetails : True OrganizerInfo : True ResourceDelegates : {mydom.com/myuser} RequestOutOfPolicy : AllRequestOutOfPolicy : True BookInPolicy : AllBookInPolicy : False RequestInPolicy : AllRequestInPolicy : True AddAdditionalResponse : False AdditionalResponse : RemoveOldMeetingMessages : True AddNewRequestsTentatively : True ProcessExternalMeetingMessages : False RemoveForwardedMeetingNotifications : False Identity : mydom.com/myroom can anybody help me?

Get-CalendarProcessing -Identity my_room | fl RunspaceId : 4594cb2d-13ed-43a9-a31c-735a3e1d50b4 AutomateProcessing : AutoAccept AllowConflicts : False BookingWindowInDays : 365 MaximumDurationInMinutes : 1440 AllowRecurringMeetings : True EnforceSchedulingHorizon : True ScheduleOnlyDuringWorkHours : False ConflictPercentageAllowed : 0 MaximumConflictInstances : 0 ForwardRequestsToDelegates : True DeleteAttachments : True DeleteComments : True RemovePrivateProperty : True DeleteSubject : True AddOrganizerToSubject : True DeleteNonCalendarItems : True TentativePendingApproval : True EnableResponseDetails : True OrganizerInfo : True ResourceDelegates : {mydom.com/myuser} RequestOutOfPolicy : AllRequestOutOfPolicy : True BookInPolicy : AllBookInPolicy : False RequestInPolicy : AllRequestInPolicy : True AddAdditionalResponse : False AdditionalResponse : RemoveOldMeetingMessages : True AddNewRequestsTentatively : True ProcessExternalMeetingMessages : False RemoveForwardedMeetingNotifications : False Identity : mydom.com/myroom can anybody help me?

I can confirm the same behavior, Exchange 2010 Enterprise SP1 (version 14.1, build 218.15). I believe this is a bug. Basically I want all in-policy meeting requests to be forwarded to a delegate *unless* they are in the list of permitted in-policy auto-approved users (BookInPolicy attribute). All out-of-policy requests should go to delegate. As it stands now: all users submitting in-policy requests are auto approved, regardless of whether they are on the list. Out-of-policy requests are working as expected. Bummer.

I can confirm the same behavior, Exchange 2010 Enterprise SP1 (version 14.1, build 218.15). I believe this is a bug. Basically I want all in-policy meeting requests to be forwarded to a delegate *unless* they are in the list of permitted in-policy auto-approved users (BookInPolicy attribute). All out-of-policy requests should go to delegate. As it stands now: all users submitting in-policy requests are auto approved, regardless of whether they are on the list. Out-of-policy requests are working as expected. Bummer.

Seeing the same issue here - always getting auto approvals and the delegates are not receiving any notification whatsoever. Running Exchange 2010 SP1. Room mailboxes were migrated from Exchange 2003. I also tried creating new meeting room mailboxes with same results.

Seeing the same issue here - always getting auto approvals and the delegates are not receiving any notification whatsoever. Running Exchange 2010 SP1. Room mailboxes were migrated from Exchange 2003. I also tried creating new meeting room mailboxes with same results.

Wondering if you guys figured out what the issue was here? Jeremy Whittaker MCSE MCSA CCNA CCA Senior Consultant N2 Network Solutions http://www.N2NetworkSolutions.com

Wondering if you guys figured out what the issue was here? Jeremy Whittaker MCSE MCSA CCNA CCA Senior Consultant N2 Network Solutions http://www.N2NetworkSolutions.com

Actually it looks like it is a known bug and fixed in rollup 4 for Exchange 2010. http://support.microsoft.com/kb/982639 http://www.microsoft.com/downloads/en/confirmation.aspx?FamilyID=09b4973e-3a80-4fb9-9f60-5c6e2b7a2727&displaylang=enJeremy Whittaker MCSE MCSA CCNA CCA Senior Consultant N2 Network Solutions http://www.N2NetworkSolutions.com

Actually it looks like it is a known bug and fixed in rollup 4 for Exchange 2010. http://support.microsoft.com/kb/982639 http://www.microsoft.com/downloads/en/confirmation.aspx?FamilyID=09b4973e-3a80-4fb9-9f60-5c6e2b7a2727&displaylang=enJeremy Whittaker MCSE MCSA CCNA CCA Senior Consultant N2 Network Solutions http://www.N2NetworkSolutions.com

I don't see anywhere where this issue is listed in the reference KB article. I believe that this is still an outstanding bug that has existed since Exchange 2007.

I don't see anywhere where this issue is listed in the reference KB article. I believe that this is still an outstanding bug that has existed since Exchange 2007.

I agree, we're Running Exchange 2010 SP1 RU5 and are having exactly the same issue. Has anyone got a link to the KB article where it declares this as fixed, so we can take it up with our support?

I agree, we're Running Exchange 2010 SP1 RU5 and are having exactly the same issue. Has anyone got a link to the KB article where it declares this as fixed, so we can take it up with our support?

Has anyone figured out a resolution for this? I am having the same exact issue. Is there a bug fix? Thanks.

Has anyone figured out a resolution for this? I am having the same exact issue. Is there a bug fix? Thanks.

Jeremy, do you know this as a fact? It isn't in the release notes in the KB.

This issue is fixed in SP2, could someone test it and let me know. I was able to repro this in lab with SP2 and it is working as expected . Test for following behavior A -All in-policy meeting requests to be forwarded to a delegate . *unless* they are in the list of permitted in-policy auto-approved users (BookInPolicy attribute). All out-of-policy requests should go to delegate. now with SP2 : all users submitting in-policy requests are forwarded for delegate approval. and out of policy should be worknig as expected . Manju

This issue is fixed in SP2, could someone test it and let me know. I was able to repro this in lab with SP2 and it is working as expected . Test for following behavior A -All in-policy meeting requests to be forwarded to a delegate . *unless* they are in the list of permitted in-policy auto-approved users (BookInPolicy attribute). All out-of-policy requests should go to delegate. now with SP2 : all users submitting in-policy requests are forwarded for delegate approval. and out of policy should be worknig as expected . Manju

This is not fixed in SP2. I am running SP2 RU1 and can reproduce this. First Scenario: -If you set the Out-of-Policy requests to "all users" -Set In-policy requests for automatic approval to "Selected users" with no users selected. -Set In-policy requests for subject to delegate approval to "All users" The above leads to all In-Policy requests to be automatically accepted and all out-of-policy requests to be forwarded to delegates Second Scenario: -If you set the Out-of-Policy requests to "Selected users" with no users selected. -Set In-policy requests for automatic approval to "Selected users" with no users selected. -Set In-policy requests for subject to delegate approval to "All users" This leads to all In-Policy requests forwarded to delegates but all Out-of-Policy requests do no generate any response. Not sure why setting the out-of-policy changes In-policy delegate forwarding behavior. I am assuming this is the default behavior and not a bug since it's been around since RTM, but I cant understand the logic behind it. Can anyone from Microsoft confirm this is by design and not a bug. Perhaps provide with a while paper explaining the logic behind this?

This is not fixed in SP2. I am running SP2 RU1 and can reproduce this. First Scenario: -If you set the Out-of-Policy requests to "all users" -Set In-policy requests for automatic approval to "Selected users" with no users selected. -Set In-policy requests for subject to delegate approval to "All users" The above leads to all In-Policy requests to be automatically accepted and all out-of-policy requests to be forwarded to delegates Second Scenario: -If you set the Out-of-Policy requests to "Selected users" with no users selected. -Set In-policy requests for automatic approval to "Selected users" with no users selected. -Set In-policy requests for subject to delegate approval to "All users" This leads to all In-Policy requests forwarded to delegates but all Out-of-Policy requests do no generate any response. Not sure why setting the out-of-policy changes In-policy delegate forwarding behavior. I am assuming this is the default behavior and not a bug since it's been around since RTM, but I cant understand the logic behind it. Can anyone from Microsoft confirm this is by design and not a bug. Perhaps provide with a while paper explaining the logic behind this?

We also have this issue. We are a new Exchange install from scratch running SP2 and are attempting to setup room bookings for the first time and can confirm that this is not fixed in SP2. Any news on a fix Microsoft?