Trouble: Resource Rooms do not reliably accept bookings. Events are created, and a room is added as a Resource, but the Room does not post the booking. No warnings or dialog boxes tell the user it hasn't been posted. (Luckily, users are suspicious now and go look at the room calendar later to see if it has posted or not). Background: Exchg org: Exchange 2007 SP2 (Rollup3), primary server, holds all Exch 2007 roles. Exchange 2003 SP2, prior server. Still in the organization but effectively decommissioned. (No mailboxes, no connectors, no public folders). Also is a DC. Soon to be deinstalled of Exchange and demoted from DC. Salient points: The Resource Room mailboxes were not brought over to the new (Exch 2007) server in accordance with http://technet.microsoft.com/en-us/library/bb232130.aspx The rooms were setup starting at step (2), that is, the "RegisterMailbox.vbs /u" was not executed prior to their move from the Exch 2003 server to the Exch 2007 server. We have gone over all the (apparently) relevant white papers, and verified automatic booking, etc. (See output of get-mailboxcalendarsettings inline below). All the users can see the room availabilty (i.e., no hatched lines -- the room calendar(s) are visible). The rooms all have an AD/LDAP value for "Exchange Home Server" that is correct (i.e., the new server). The event logs are not trapping anything useful with respect to the Rooms or the user accounts that book them that I have been able to see. ### Where should I look next? Or, do I quit troubleshooting, and expect that the removal of the old Exchange 2003 server will fix this problem for good? You can see how I wanted to investitate before that time, because if I need to take any action on the Exchange 2003 server, I'd better do it while it still exists. TIA, AceyMan <paste block 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 : {Office Manager} AllRequestOutOfPolicy : False BookInPolicy : AllBookInPolicy : True RequestInPolicy : {Office Manager} AllRequestInPolicy : False AddAdditionalResponse : False AdditionalResponse : <DIV><FONT size=2 face=Tahoma></FONT></DI V> RemoveOldMeetingMessages : True AddNewRequestsTentatively : True ProcessExternalMeetingMessages : False DefaultReminderTime : 15 RemoveForwardedMeetingNotifications : False Identity : hq.local/MyBusiness/Users/Resources/Ea st Conference Room end paste>

Can you try to move resource mailbox into other DB and then check after some time. One more thing.. You said that------ (Luckily, users are suspicious now and go look at the room calendar later to see if it has posted or not). Are room mailbox AD account not disabled ???Anil

HAve you opened any of these resource mailboxes up? Is the request sitting in the inbox? Does it work if you create a new resource mailbox on 2007?

Hi, Any updates? Is the Exchange 2003 resource mailbox an Auto Accept Agent-Based Resource Mailbox or shared one? From the Technet: How to Upgrade Exchange 2003 Auto Accept Agent-Based Resource Mailboxes to Exchange 2007 http://technet.microsoft.com/en-us/library/bb232130(EXCHG.80).aspx If this is an Auto Accept Agent-Based Resource Mailbox , maybe you should unregister the mailbox first. If this is an shared mailbox, it is OK to run the Set-Mailbox. More information: How to Convert a Mailbox http://technet.microsoft.com/en-us/library/bb201749(EXCHG.80).aspxFrank Wang

Hi AceyMan, Any updates on the issue?Frank Wang

@ Anil K Singh, asked "Are room mailbox AD account not disabled ???" Yes, the user AD accounts for the assocated Resource Rooms are all disabled. @ AndyD, asked HAve you opened any of these resource mailboxes up? Yes, I can open them in OWA via my Domain Admin account which has permissions on the resource mailbox. Is the request sitting in the inbox? Bingo, there are un-accepted invitations in the Resource mailbox. The events are marked on the calendar with the hatched lines as "Tentative" Does it work if you create a new resource mailbox on 2007? I haven't made any new, test resource mailboxes, but I will build one and report back with behavior. @Frank.Wang asked Is the Exchange 2003 resource mailbox an Auto Accept Agent-Based Resource Mailbox or shared one? It is setup for Auto-accept (as you can see from the output of get-mailboxcalendarsettings in my original post). As I noted up front, the mailboxes were migrated off the original server without performing the unregistration by doing the "Registermailbox.vbs /u" action while it was still in the Exchange 2003 store. The subsequent steps of BB232130 were all performed. As far as BB201749, this was followed, however, IIRC, one mailbox wouldn't re-link to the matching account, so I had to make a new AD user account and then connect it. The mailbox user accounts are all disabled at this time. #### So: will I need to move the resource mailboxes back to Exchange 2003 so I can do the unregistration action? Or would that blow-up? Or is there some other way I can solve the problem while the mailboxes remain on Exch 2007 (something like unlink the mailbox from the accounts, delete the accounts, make new ones and relink.. or something like that). Thanks for all the help. I'm amazed there were so many answers over the USA holiday weekend!

Hi, Since your old Exchange 2003 is still in your organization, I would suggest you convert the resource mailbox back, and move it back to Exchange 2003, then unregister the mailbox.Frank Wang

Update: To my chagrin and amazement, it appears that the rooms, while they were on the Exchange 2003 server, must have been operating in "Direct Booking" mode, ref: http://technet.microsoft.com/en-us/library/bb232195(EXCHG.80).aspx I came to that conclusion because the Exchange 2003 server has no path %Program Files%\Exchsrvr\Agents\AutoAccept. I take that as a tell tale that Direct Booking must have been in play. Ergo, I cannot use the un-registration script as cited in BB232130 , since they were never registered to begin with. Any more ideas to try? I still have not had a chance to make a new room and test its behavior, I will try to get that done within 24 hours.

Hi Aceyman, I would still suggest you convert the resource mailbox back, then move it back to Exchange 2003,after that, follow the link to upgrade Outlook direct booking resource mailboxes to Exchange 2007.Frank Wang

So the suggestion is that I: While the resource rooms still reside on Exchange 2007, Set-mailbox -type user Enable the User account linked to each mailbox Migrate the Mailbox back to Exchange 2003 ...and from there, follow http://technet.microsoft.com/en-us/library/bb232195(EXCHG.80).aspx Interestingly bb232195 doesn't really seem to "do much", but I suppose the steps where "Resource Scheduling" and "Permissions" are changed must be the secret sauce. If no one vetos my plan I will execute it as soon as I can. Thanks everyone.

Hi, I am little confused. Do u mean that these resource mailboxes are migrated from Exchange 2003 ? If yes was it ever working when they were in Exchange 2003 ? If Yes Can you confirm by checking if Direct Booking is Disabled on those resource mailboxes. Enable the AD account for the mailbox in Exchnage 2007 and create a Outlook Profile for it and check if the meeting request are present. Outlook---Tools---Calendar Option----Resource scheduling---Uncheck all the option below "Processing Meeting Requests" Please let me know if i was wrong in understanding your issue. Regards, Raghav

@ragharam That is correct, these room mailboxes were migrated from Exchange 2003 to Exchange 2007 SP2. As noted in the opener, the first step of article bb232130 was not complied with, which I felt might be the source of our trouble. I have tried to uncheck the "Processing Meeting Requests" option from Outlook 2007, however I cannot get past the Resource Scheduling button. It either fails with "the operation failed because of a registry or installation problem", or, alternately, "Not Implemented". Since that didn't work for me, here is what I did to try to get to that option. <begin process...> enabled AD user account for the mailbox in question. set-mailbox "Trouble Room One" -type regular doubleck that domainadmin has full-access permissions on smallconferenceroom open outlook as domainadmin build new Outlook profile for Trouble Room One open outlook tools > options > calendar options > resource scheduling result: errors with "the operation failed because of a registry or installation problem. restart outlook and try again. if the problem persists, reinstall" set-mailbox "Trouble Room One" -type Room try again, tools > options > calendar options > resource scheduling, "Not Implemented" thence, set-mailbox "Trouble Room One" -type Regular try again, tools > options > calendar options > resource scheduling, "Not Implemented" <end notes>

I have taken the following steps, which are a distillation of all the tips so far. process( set-mailbox type regular enable linked ad account export-mailbox to pst (for CYA purposes) fire up the %OLDSERVER% and start needed Exchange services move mailbox to %OLDSERVER% (Exchange 2003) logon to mailbox via OWA, logout (had to do this once because I was getting 'no profile' errors in Outlook) logon to mailbox via Outlook 2007 using the mailbox user account follow Technet bb232195, that is, turn off "Automatically accept meeting requests and process cancellations" under Calendar Options|Resource Scheduling move mailbox back from %OLDSERVER% to %NEWSERVER% (Exchange 2007 SP2) disable linked user account set-mailbox -type room set-mailboxcalendarsettings to autoaccept )end process

HI, Did u try to repair the Microsoft Office 2007 and then reboot the machine for the error related to the "the operation failed because of a registry or installation problem. restart outlook and try again. if the problem persists, reinstall" Regards, Ragharam