I just migrated over to a 2010 setup from 2007 (2007 box is still up and running at the moment). I noticed when I did the 2010 install, that if I sent an email to a "Everyone" dynamic distribution group I had defined, I would get a delivery failure message back MsExchDiscoveryMailboxD919BA05-46A6-415f-80AD-7E09334BB852@domain.com Your message can't be delivered because delivery to this address is restricted. I have just moved all of my users mailboxes over to 2010 and I still get this same error sending to that group. I'm lost on where this is coming from for sure, or what I can do about it.

Ok, just an update... I deleted the "Everyone" dynamic group and recreated it. Let it set for a little bit, but noticed I could no longer send to that group. Tried to force a update on the OAB and force a re-download of the address book in Outlook 2010 and get a error 0x80190194. Just for sake of argument, I created another OAB, assigned it to the database in question and still same error. Noticed warning in event log about group metrics, defined group metrics for the mailbox servers, but still getting those same warnings. I get the same MSExchangeSA 9413 warning on both OABs when I force an update. Any ideas?

Hi, First I'd like to know the steps that you create dynamic group including the filters. Please post here. Please check if you have RequireSenderAuthenticationEnabled settings on dynamic group. You can use get-distributiongroup |fl to check it. Note: The RequireSenderAuthenticationEnabled parameter specifies whether to require e-mail message delivery from authenticated senders. If the value is $true, messages are accepted only from authenticated senders. Valid values are $true or $false. The default value is $true. For OAB, please try to use test e-mailatuoconfiguration check url for OAB, if you have SSL enabled for OAB virtual directory. Please post the result here. Please try to raise up the level of diagnostic log for OAB. After that, please check the event again and then post the detail error information here. Set-EventLogLevel -Identity "MSExchangeSA\OAL Generator" -Level Expert -Verbose Update-OfflineAddressBook -Identity "Default Global Address Book" Set-EventLogLevel -Identity "MSExchangeSA\OAL Generator" -Level Lowest Regards, Xiu Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thanks for the reply Xiu...before I run through what you mentioned, I checked again this morning and I guess things settled down in Exchange as now I can force an update of the OAB and not get the MSExchangeSA 9413 warning, I have also successfully sent a message to that distribution group without getting back a nondelivery on the msexchdiscoverymailboxid bla bla bla.domain.com... I also was able to force a address book download from that Outlook 2010 client successfully. My worry now is having created this new OAB for one of my databases to use, but I've got the other database I have pegged to the original default. Are there any caveates in removing the old OAB completely before I decommission the 2007 box?

Hi, When we create OAB, we will have OAB generation server, so if you want to use the new OAB, then please try to point to the new OAB generation server. Note: After you move OAB generation server, please check if you have OAB created on mailbox server. Besides, please check if CAS server has copied OAB. I'd like to share related article to you: Move the Offline Address Book Generation Process to Another Server http://technet.microsoft.com/en-us/library/bb125184.aspx Exchange 2007 Offline Address Book Web Distribution http://blogs.technet.com/b/exchange/archive/2006/11/15/3397281.aspx Regards, XiuPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I had already moved the generation process for the OAB that was on 2007 over to one of my 2010 boxes. Would I need to do anything in regards to replicating OAB over to the other server I have for redundancy?