But my suspicion is that there was some issue with it completing its normal background maintenance, and by moving the copy to another server, the two servers then had the processing time to correct their copies. Before this, the database had been reported as healthy, no eventlog issues, and search index was responding quickly, so I had no reason to suspect the database was the problem. So, I moved the active database copy back to the original server, and auto-accept was still working. After that, auto-accept was working just fine on all affected Room Mailboxes. The next morning, the CPU utilization was normal on the server where the database was moved. However we have one issue that may be unrelated. Weve recently replaced our Exchange 2010 server with a new one. 8 Comments 1 Solution 9320 Views Last Modified. I still was not able to get auto-accept to work. Exchange 2010 Room mailbox not auto-accepting meetings despite being set to autoaccept.

When I moved the active database copy to one of the other servers, the higher CPU utilization moved with the DB, so that made me suspect the DB had some page corruption or some other issue that background maintenance wasn't handling. I have 16 mailbox servers, so I was monitoring them and noticed that the server where the problem DB was located had a consistently higher-than-normal CPU utilization (60-80%) compared to all of the others. I even tried creating new Room Mailboxes on the DB and those would not auto-accept. Moving it back to the original DB, it stops working. If it is moved to a different DB, it works just fine. When the issue was occurring, if the room mailboxes exist on a particular DB, auto accept stops working. My suspicion is that there was some issue with the mailbox server completing its normal background maintenance, and by moving the DB copy to another server, the two servers then had the processing time to correct their copies.

I moved the active database back to the original server, and everything was still working.

The next morning, auto-accept was working again for all rooms on the problem database.

Still wasn't working even after the hour had passed, but left it overnight.BTW, I learned elsewhere that you sometimes have to wait an hour after moving it to test again. I moved the active DB copy to another server (Move-ActiveMailboxDatabase).The database with the issue is in a DAG.New room mailboxes would NOT work if they were created on this database, but would work if created on other DBs.If they are moved to a different DB, it works just fine.Room Mailboxes with the issue all existed on the same mailbox database.Even though the Room Mailbox is configured identically to other Rooms that were responding normally, some Room Mailboxes would not autoaccept meeting requests.

Exchange 2010 room mailbox