Quantcast
Channel: Configuration Manager 2012 - Application Management forum
Viewing all articles
Browse latest Browse all 4762

Ways to report on installed SCCM applications

$
0
0

Hi,

I'm looking for some help, or inspiration, on an issue I'm currently working on.

I'm in a company that has SCCM 2012 which it uses to push applications out to client machines (as in many other companies).

But the issue here is that the applications are being deployed in various ways via SCCM. Whether being direct membership of a collection or being deployed via a universal application collection which is used by MDT at the build stage.

The problem is that this universal collection in non-reportable. In that no status of the deployments are shown within monitoring part of SCCM, and on top of that the application is not being reported as installed within software center of the client machine either.

What I would like to do is create query based collections which use AD groups as the root, and lock down the collection memberships to only packagers/admins with modify rights.

But I need to populate the AD groups with the machines that have the relevant software already installed, in order for the collections to get populated and so to give an accurate picture.

This is easy for the machines that have direct memberships, I can just export those and then populate them into AD as members of the AD groups. But I'm struggling to think of a way to gather the info of the clients that have SCCM applications installed, but not a member of any collections.

Is there a way I could use WQL to query the application scope ID's, in order to work out what SCCM applications are installed on each client machine. I could then use this info to populate the AD groups. Note: we do not have asset intelligence currently enabled.

Or could anyone recommend another way to achieve this goal?

Many thanks

James


Viewing all articles
Browse latest Browse all 4762

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>