none
How to block a meeting room in Exchange 2007 or above using EWS Java API? RRS feed

  • Question

  • I'm able to send out meeting request but failed to book a room? I've tried setting the RequiredAttendees or Resources property with mail address and alias name.

    Is there any way can get this done using EWS Java API?

    Friday, February 14, 2014 3:22 AM

All replies

  • Are the Meeting Request messages actually being sent eg what SendInvitationsOrCancellationsMode are you using?

    Does the User sending the Meeting Request have permissions to book appointments in that Meeting Room.

    Have you checked the Meeting Room Mailbox to see if the Meeting Request is being received.

    Are you getting any response from the Meeting Room ?

    Are you able to book the Meeting Room using the same user in OWA ?

    Cheers
    Glen

    Friday, February 14, 2014 4:54 AM
  • I tried save() without setting the mode and SendToAllAndSaveCopy.

    Yes, the user has the permissions.

    Didn't see the request in the meeting room mailbox.

    No response from the meeting room.

    Yes, I'm able to do that in OWA.

    And I can see the room in the meeting request but just not blocked.

    Thanks,

    Kimi

    Friday, February 14, 2014 9:08 AM
  • Sorry, I'm not able to book the room in OWA. 
    Friday, February 14, 2014 9:34 AM
  • Okay well first step would be to enable automated booking on the Meeting Room

    http://technet.microsoft.com/en-us/library/bb123495(v=exchg.141).aspx

    >>I tried save() without setting the mode and SendToAllAndSaveCopy.

    You need to set this to ensure that Meeting Invitations are sent which is critical to the meeting room getting booked otherwise no invitation will be sent.

    Cheers
    Glen

    Monday, February 17, 2014 5:43 AM
  • Hi Glen,

    Thanks for you reply, as I don't have the admin access, before I raise the request,

    can you please clarify whether this configuration is still needed if I can book the room

    via outlook desktop client?

    Cheers,

    Kimi

    Monday, February 17, 2014 7:22 AM
  • Yes it is because the Outlook client could be booking the meeting using Outlook Direct Booking (this is an Outlook client feature). For EWS (and OWA) to work you need to have Automated booking enabled.

    Cheers
    Glen

    Tuesday, February 18, 2014 1:40 AM
  • Hi Glen,

    We're running the test on 2007. So the configuration for automatic booking should be different? While we're searching how to do if on 2007, our admin find out that the setting was already there.

    -------------------------------------------------------------

    AutomateProcessing                  : AutoAccept

    AllowConflicts                      : False

    BookingWindowInDays                 : 180

    MaximumDurationInMinutes            : 1440

    AllowRecurringMeetings              : True

    EnforceSchedulingHorizon            : True

    ScheduleOnlyDuringWorkHours         : False

    ConflictPercentageAllowed           : 0

    MaximumConflictInstances            : 0

    ForwardRequestsToDelegates          : True

    DeleteAttachments                   : True

    DeleteComments                      : True

    RemovePrivateProperty               : True

    DeleteSubject                       : True

    DisableReminders                    : True

    AddOrganizerToSubject               : True

    DeleteNonCalendarItems              : True

    TentativePendingApproval            : True

    EnableResponseDetails               : True

    OrganizerInfo                       : True

    ResourceDelegates                   : {}

    RequestOutOfPolicy                  :

    AllRequestOutOfPolicy               : False

    BookInPolicy                        :

    AllBookInPolicy                     : True

    RequestInPolicy                     :

    AllRequestInPolicy                  : False

    AddAdditionalResponse               : False

    AdditionalResponse                  :

    RemoveOldMeetingMessages            : True

    AddNewRequestsTentatively           : True

    ProcessExternalMeetingMessages      : False

    DefaultReminderTime                 : 15

    RemoveForwardedMeetingNotifications : True

    -------------------------------------------------------------

    and Microsoft Exchange Mailbox Assistants service is running as well. 

    But I still can't book the meeting room in OWA.

    Cheers

    Kimi

    Wednesday, February 19, 2014 7:10 AM
  • Same problem for me. 

    The meeting room is not really booked but in tentative mode and you can't cancel it from Outlook after a booking using EWS API.

    PS : My room mailbox is configured to auto-accept meeting invitations.

    Do you have found any solution? 

    Wednesday, February 19, 2014 10:37 AM
  • This sounds like you now have both Direct booking and AutoAccept enabled. For AutoAccept to work properly you first need to disable Direct booking - to do so you'll need to create a profile for the resource Mailbox and open it in Outlook and then modify the calendar options  see http://blogs.technet.com/b/exchange/archive/2013/05/09/use-exchange-web-services-and-powershell-to-discover-and-remove-direct-booking-settings.aspx

    Cheers
    Glen

    Thursday, February 20, 2014 5:55 AM
  • Hi Glen,

    Thanks for your info.

    Things are getting more complicated now...

    I tried with another meeting rooms, turned out that it's working for OWA but still not for EWS Java.

    any idea?

    thanks,

    Kimi

    Thursday, February 20, 2014 8:09 AM
  • Also encountered the same problem Yohann mentioned when testing other meeting rooms....
    Thursday, February 20, 2014 8:50 AM
  • Are you using  SendToAllAndSaveCopy to ensure the invitations are sent for the meeting ?. Are the other attendees receiving invitations ?. The feature uses the Meeting invitations to do the booking if your not sending invitations then it won't work.

    Cheers
    Glen

     
    Friday, February 21, 2014 1:53 AM
  • Yes, I was using SendToAllAndSaveCopy and invitations were received by others.
    • Proposed as answer by Yohann Ciurlik Friday, February 21, 2014 10:09 AM
    • Unproposed as answer by Yohann Ciurlik Friday, February 21, 2014 10:10 AM
    Friday, February 21, 2014 3:39 AM
  • Ok, I understand that Direct Booking is not compatible with EWS/OWA/Mobile solutions (and also with Outlook 2010/2013 without register tweak).

    Direct Booking and Resource Booking Attendant are conflicting technologies, and if enabled together, unexpected behavior in calendar processing and item consistency can occur.

    @kichen : We have both technologies enabled in our organization. I've done some tests on a meeting room with only auto-accept feature and it is working perfectly.

    I opened a Microsoft Ticket about the conflict between Auto-Accept and Direct Booking. I am waiting for an answer.

    Sources : 
    http://msexchangeanswers.blogspot.fr/2009/08/outlook-direct-booking-vs-auto-accept_17.html
    http://exchangeserverinfo.net/2013/05/remove-auto-accept-from-outlook-for-all-room-mailbox/
    Friday, February 21, 2014 10:10 AM