This is somehow a ‘sequel’ of the previous post: ‘Windows S4B clients don’t show some Distribution Groups‘ but for iOS based clients.
ISSUE #1 (and #2)
We have again the same Distribution Groups/Lists (DL’s) configured on our Destkop client (picture on the left), but when you sign-in with the iOS S4B (picture on the right) client some DL’s might not appear:
Would could just conclude that it would be the same reason as the previous WP issue, but as you can see the SMTP list (doesn’t have a displayname on AD) is being displayed while the one is missing is the DL’s with the Displayname doesn’t appear.
In this case you might not even consider an issue. The reason is simple as: if the DL’s don’t contain any members, the S4B client will not show it.
There is really no explicit entry on the client log file. The only evidence is that the GET https://<webservicesexternalurl>/…/expand will return the members of the DL (resource rel=”contact”):
HTTP/1.1 200 OK
Via: 1.1 dc1.mylab.local RtcExt
Content-Type: application/vnd.microsoft.com.ucwa+xml; charset=utf-8
<?xml version=”1.0″ encoding=”utf-8″?>
<resource rel=”distributionGroup” href=”/ucwa/v1/applications/212440241480/people/groups/Test.DL2@mylab.local/expand” xmlns=”http://schemas.microsoft.com/rtc/2012/03/ucwa”>
<resource rel=”contact” href=”/email@example.com”>
<link rel=”contactPhoto” href=”/firstname.lastname@example.org” />
<link rel=”contactPresence” href=”/email@example.com/presence” />
<property name=”name”>Test User1</property>
If you want to see the DLs on the iOS client, you just need to:
- Populate the AD distribution group with one or more member;
- Wait for AD replication
- Exit and reopen the Desktop client.
This will force the membership to refresh the DL (picture on the right)
- And the iOS client will start showing the group, right ?…
NOPE! :even if you restart the entire device,
remove and re-add the DL
…. the S4B client will not show it!
This will take us to a (new post?) issue #2: client user caching.
For now here’s two quick ‘workarounds’ preview solve it:
- Option A: Sign-in with another user and sign-in back with your user
- Option B: remove and reinstall the client on the iOS device
This behaviour was observed:
- With the current iOS/S4b version at the time:
Skype for Business v18.104.22.168
running on iOS 9.3.2 (13F69)
- It happens with both Lync 2013 and Skype for Business 2015 server infrastructure
(so it’s not an ‘upgrade caveat’)