Hi,

Ive migrated a customer from Exchange 2007 to Exchange 2013 successfully. However. There are troubles with booking resources. Users receive the following error message when booking a resource: Direct Booking Cannot directly book a resource for this meeting.

The user follows the following procedure:
The user opens his/her own agenda, create a meeting, use Scheduling Assistant to schedule a meeting with another user and to add a Room. When hitting Send the above message appears.

When the user has Full Control to the resource mailbox and the user opens the agenda of the resource directly and follows the above procedure in the resource agenda he/she is able to book the resource without a problem (this workaround is not preferred as a final solution).

To fix this, Ive tried the following:

Add a registry key to the client. HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Options\Calendar\EnableDirectBooking (0)

Turn cache mode ON, this works.
However for some users cache mode must be turned off, so this workaround doesnt apply for all the users.

I worked with Full Control permissions on the resource, so that the user is able to book directly from the resource agenda.

Some more information:
Public Folders are not in use anymore.
There are several clients in the environment:
Windows XP with Outlook 2007
Windows 7 with Outlook 2007
Windows 7 with Outlook 2010  (I do not have a confirmation if these symptoms also apply on these clients as well).

Does anyone has a final solution for me?
Or how can I troubleshoot this any further?

Thanks in advance,
Yuri

The same problem for new Room Mailboxes.
Exchange 2013 CU7.

Hi,

According to your description, I understand that user cannot book room and return an error Direct Booking Cannot directly book a resource for this meeting after move mailbox from Exchange 2007 to 2013.
If I misunderstand you concern, please do not hesitate to let me know.

I want to double confirm some points, please help to collect answers for below questions:
1. Move mailbox within same forest or cross-forest?
2. How about the OWA with problematic account?
3. How about new a mailbox in Exchange 2013?

If it works in OWA, please try to repair Outlook profile or re-create profile for testing.
If not, please run below command to double check the permission of resource mailbox:
Get-MailboxPermission room | select user,accesslight
Get-MailboxFolderPermission room:\calendar | FL

Additional, I find an similar thread about your question. For your reference:
https://social.technet.microsoft.com/Forums/exchange/en-US/78faa211-1af0-4a07-93d0-e9d39c8de9c8/resource-mailboxes-questions

Thanks

Hi Allen,

Thank you for your reply. Here my findings:
1- Same forest.
2- The booking procedure via OWA is working perfect.
3- Yes, the problem is also when the mailbox is created on the new environment.
4- Re-creating the Outlook Profile doesn't help.
5- Get-MailboxPermission gives me the correct user, but the Accesslight column is empty for all the results.
(I'm not sure what feedback you expect, please let me know if this info gives you a lead.)
6- MailboxFolderPermission calender shows:
User Default, has Reviewer AccessRights.
User Anonymous, has No AccessRights.
This seems fine to me.
For testing purposes, I've gave the problematic account Editor AccessRights, but that doesn't help.

I'll look into the other link you've sent now, but at this moment I have no solution yet.
If you, or anyone else, has a solution or leads, please share.

Hi,

Please forward me exchange 2007 to exchange 2013 migration document.

This will help me in implementation.

 

Thank you

Regards

arun av

 

Hi Arun,

Please start a new thread with your question with future inquiries, instead of using existing threads with other subjects.

Anyway, this link will help you: http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx

Good luck,
Yuri

Hi all,
The solution to the problem and symptoms above:
* Open Adsiedit on a Domain Controller and go to: Configuration | CN=Configuration,DC=..<domain> | CN=Services | CN=Microsoft Exchange | CN=<exchange organization name> | CN=Administrative Groups | CN=Exchange Administrative Group (..) | CN=Databases
* Right click (do this for all databases) CN=<databasename> and choose Properties
* Find: msExchHomePublicMDB | choose Edit | copy-paste the value to notepad for your reference | clear the value, so it becomes: <not set>.
* Restart you Exchange Server(s).
Best regards,
Yuri

• Marked as answer by Yuri NLD 15 hours 36 minutes ago