We have an Exchange 2013 deployment running on Windows 2012 Standard servers. Some of our people and all our groups are not showing up in the Outlook Address Book on people's client application. This despite the fact that "hide name from address book" is unchecked on these people and groups.

This affects both those running Outlook and OWA.

Any idea how I can go about troubleshooting

Actually, I stand corrected.  The groups do appear in Outlook, but not in OWA.  People are all appearing in OWA but the new ones aren't appearing in Outlook.  Which makes me wonder if Outlook is running off an old OAB that isn't updating properly?  So there's that, and I have to figure out how to get groups to appear in OWA address book.

Hi,

From your description, I would like to clarify the following things:

1. Outlook in cached mode automatically updates the offline address book on the client every 24 hours. The 24-hour time period is measured from the time that the offline address book was last downloaded successfully. So sometimes new users can't be displayed immediately on Outlook.

2. If you would like to show the dynamic distribution groups in All Groups, you can use the following cmdlet.

Set-AddressList -Identity "all groups" -RecipientFilter "(RecipientType -eq 'MailUniversalDistributionGroup' -or RecipientType -eq 'MailUniversalSecurityGroup' -or RecipientType -eq 'MailNonUniversalGroup' -or RecipientType -eq 'DynamicDistributionGroup')"

Here is a helpful thread for your reference.

Let the dynamic distribution groups be shown in All Groups

https://social.technet.microsoft.com/Forums/en-US/d32a94af-eb46-407e-9129-c977c32d2a48/let-the-dynamic-distribution-groups-be-shown-in-all-groups?forum=exchangesvrgeneral

Hope this can be helpful to you.

Best regards,

If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

Hi,

Have you checked the suggestion I provided?

Is there any update with your issue?

Best regards,

If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

I tried running this cmdlet on Friday.  So far groups still haven't appeared in webmail.  Though I did run it on the mbx server, as I was having cas issues.  I'm going to try running it on my cas today and see if that fixes it.

... I'm getting a "load quota for the system has been exceeded" error when I try to log into EMS on the CAS ...

Hi,

About the "load quota for the system has been exceeded" error, you can do an IISReset to check the result.

What's more, after running the above cmdlet, please use the Get-AddressList -Identity "all groups" |fl Name,RecipientFilter cmdlet to check if the RecipientFilter is updated. If no, please use the Update-AddressList -Identity "all groups" cmdlet to update it and check the result.

Hope this can be helpful to you.

Best regards,

If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

Hi,

Is there any update with your issue?

Best regards,

If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

Ugh still figuring out why my CAS's are getting this "load quote for the system has been exceeded" issue. Stay tuned.

Turns out none of the threads I searched could help me with that error. So I went ahead and asked a separate question at this link:

https://social.technet.microsoft.com/Forums/office/en-US/a37b5107-ea6c-41f1-bcfc-e458e93fab2a/cant-access-ems-or-toolbox-get-load-quota-for-the-system-has-been-exceeded-error?forum=exchangesvradmin

Hi,

In your case, I recommend you check if the Anonymous is enabled on the PowerShell VD on the Back End Server. If yes, please disable it and do an IISReset to check the result.

Hope this can be helpful to you.

Best regards,

If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

Yup, that worked. Got the answer off my other thread. Now let me try and see if I can get the cmdlet to make groups visible.

Okay, well, I tried running your cmdlet. I don't think it's properly formatted or something. This is what I get when I run your "get-addresslist" cmdlet ... I'm assuming I should be seeing a list of all the company's groups here?

[PS] C:\Windows\system32>Get-AddressList -Identity "all groups" |fl Name,RecipientFilter

Name            : All Groups
RecipientFilter : ((((((RecipientType -eq 'MailUniversalDistributionGroup') -or (RecipientType -eq
                  'MailUniversalSecurityGroup'))) -or (RecipientType -eq 'MailNonUniversalGroup'))) -or (RecipientType
                  -eq 'DynamicDistributionGroup'))

Actually, the groups I have set up aren't Dynamic Distribution Groups. They're regular Districution Groups.  I think my issue is that these groups were inherited from our Exchange 2010 organization.  We had a few things port over that didn't get their settings quite straightened out. 

This might be an issue because I still use the Exchange 2010 Hub Transport role, to sync up with Edge Transport.  I haven't bothered trying to resync it with the Exchange 2013 organization.  So having this one 2010 HT server might be tripping up some members and groups.

Hi,

In your case, your environment is different from pure Exchange server 2013 environment. I recommend you resync the Transport server with Exchange 2013 server and check the result.

Hope this can be helpful to you.

Best regards,

If you have feedback for TechNet Subscriber Support, contact  tnmff@microsoft.com