Why use AD groups to populate collections?

Hi guys,

I've always used AD group membership for populating collections used for application deployment purposes.

App-install group for installs

App-uninstall group for uninstalls

My manager says this adds additional steps to procedures, ie having to add the accounts to the groups then SCCM has to pick up the new membership from AD and having to maintain 2 separate tools for 1 purpose.

Looking at it he may have a valid point.

I can place just about any query I like on the collection so why do we always use AD groups?

Cheers

Mark