jnelson993
Posts: 900
Score: 127 Joined: 2/18/2005 From: Minneapolis, MN Status: offline
|
Yeah, AD processing, especially on large sites is a time-consuming operation. From the time that discovery is kicked off, to the time all the DDRs finish processing can be hours, and then if you've got collections based on that data, you have to wait longer for the collections to update. For that reason, we don't rely on AD group membership from discovery to handle time-sensitive software pushes. If we wanted to use it that way, I'd just use VBScript or PowerShell to pull the AD information and update my own tables directly instead of relying on the AD discovery. That way I can pull only those records that have changed since the last AD pull and I can run it more often. The processing would be faster, the amount of data SMS/CM has to deal with would be minimal and the time taken to get it all into SQL would be minimal. If you're looking to query the AD Group membership (for systems, not users) it's dbo.v_RA_System_SystemGroupName. I wouldn't query or update the underlying table directly (which is dbo.System_System_Group_Name_ARR). If you want to roll your own script that populates this, you'd jus create your own DDRs and put them in the inboxes.
_____________________________
Number2 (John Nelson) MyITForum - Blog MyITForum - Forum Posts
|