ExpandGroup method returns no results for Dynamic Distribution Group in Exchange 2010
Strange but TRUE! This work in Exchange 2007 but does not in Exchange 2010. Below is the request and response that I get from a Exchange 2010 server for the ExpandGroup Exchange Web Services call:
Request:
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="https://www.w3.org/2001/XMLSchema-instance" xmlns:m="https://schemas.microsoft.com/exchange/services/2006/messages"
xmlns:t="https://schemas.microsoft.com/exchange/services/2006/types" xmlns:soap="https://schemas.xmlsoap.org/soap/envelope/">
<soap:Header>
<t:RequestServerVersion Version="Exchange2010" />
</soap:Header>
<soap:Body>
<m:ExpandDL>
<m:Mailbox>
<t:EmailAddress>TestDDL@bhargava.com</t:EmailAddress>
</m:Mailbox>
</m:ExpandDL>
</soap:Body>
</soap:Envelope>
Response:
<?xml version="1.0" encoding="utf-8"?>
<s:Envelope xmlns:s="https://schemas.xmlsoap.org/soap/envelope/">
<s:Header>
<h:ServerVersionInfo MajorVersion="14" MinorVersion="1" MajorBuildNumber="269" MinorBuildNumber="0" Version="Exchange2010_SP1" xmlns:h="https://schemas.microsoft.com/exchange/services/2006/types"
xmlns="https://schemas.microsoft.com/exchange/services/2006/types" xmlns:xsi="https://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="https://www.w3.org/2001/XMLSchema" />
</s:Header>
<s:Body xmlns:xsi="https://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="https://www.w3.org/2001/XMLSchema">
<m:ExpandDLResponse xmlns:m="https://schemas.microsoft.com/exchange/services/2006/messages" xmlns:t="https://schemas.microsoft.com/exchange/services/2006/types">
<m:ResponseMessages>
<m:ExpandDLResponseMessage ResponseClass="Success">
<m:ResponseCode>NoError</m:ResponseCode>
<m:DLExpansion TotalItemsInView="0" IncludesLastItemInRange="true" />
</m:ExpandDLResponseMessage>
</m:ResponseMessages>
</m:ExpandDLResponse>
</s:Body>
</s:Envelope>
In this case the TestDDL group had members but we got no results. It turns out that this broke as a result of a change trying to synchronize behavior between various Mail Clients. Fortunately, we have decided to fix this and the fix should be available in one of the upcoming Rollup Updates for Exchange 2010 Service Pack 1.
The only workaround I know is of using LDAP to get the membership of a Dynamic Distribution Group if it fits your requirements.
Update:
|
Enjoy!
Comments
- Anonymous
July 07, 2011
Hello,I have just encountered this problem and the only place that I can find any reference to it is here.I have tried Exchange 2010 SP1 rollup 3 and rollup 4, but both are showing this problem.For your information we are using the Exchange Web Services API 1.1 to talk to EWS.Do you know if or when this issue will be fixed?Best regardsDuncan - Anonymous
July 08, 2011
This will be fixed in SP 1 RU 5. We can provide you with a Interim Update. If that is needed please open a case with PSS. - Anonymous
September 29, 2011
The comment has been removed - Anonymous
September 30, 2011
No this is an Interim Update for Exchange 2010 Sp 1 RU 5. This cannot be applied to RU 2. The fix is included in 2010 SP 1 RU 6.Exchange 2010 SP 2 should be out sometime towards the end of the year. - Anonymous
September 30, 2011
thanks for your reply.