PENDING Queries for Active Directory group membership no longer work

[Kellis002]

Queries for Active Directory group membership are no longer working. It seems that we are no longer able to properly link user and device AD group membership data. This has always worked successfully in the past. We are connected to a SQL always on listener with 2 SQL servers. We are running 2010 with the hotfixes installed. Microsoft has been working with my colleague to resolve, but we've had this issue for about 3 weeks now. Any thoughts would be appreciated.

These used to work, but now they collect all users not just users who are members of the active directory group.
select SMS_R_USER.ResourceID,SMS_R_USER.ResourceType,SMS_R_USER.Name,SMS_R_USER.UniqueUserName,SMS_R_USER.WindowsNTDomain from SMS_R_User where SMS_R_User.UserGroupName = "DOM\\MySecurityGroupName"
Or
select SMS_R_User.ResourceId, SMS_R_User.ResourceType, SMS_R_User.Name, SMS_R_User.UniqueUserName, SMS_R_User.WindowsNTDomain from SMS_R_User where SMS_R_User.SecurityGroupName = "DOM\\MySecurityGroupName"

There are no SCCM Site errors or Component errors relating to database or active directory synchronization.

 

[Garth]

The first query use AD discovery and Heartbeat discovery make sure that BOTH are working correctly.

 

[Kellis002]

The first query use AD discovery and Heartbeat discovery make sure that BOTH are working correctly.

Yes, they've been working correctly, but they cause the SQL disk queue lengths to go into the tens of thousands. This is new info to me. I've also learned that Microsoft believes the issue is related to SQL and our Nutanix data storage performance.

 

[Garth]

Yes, they've been working correctly, but they cause the SQL disk queue lengths to go into the tens of thousands. This is new info to me. I've also learned that Microsoft believes the issue is related to SQL and our Nutanix data storage performance.

It wouldn't surprise me.