Sherry wrote a post a while ago suggesting refining the sinv to *.exe in
%programfiles%, %programfiles(x86)% and %programw6432%. I've been using it
in our CM12 envirnoment.

 

With our ConfigMgr 2007 environment we were scanning *.exe on all disks too.
For our CM12 implementation I just sold this change as less processing time
on clients and we rarely use the sinv data anyway.

 

From: [email protected] [mailto:[email protected]]
On Behalf Of Poole, Richard
Sent: Friday, 24 May 2013 2:32 AM
To: [email protected]
Subject: [mssms] Software inventory best practices

 

Hey everyone,

 

Have a question from my desktop team that I'm trying to fight back with some
real documentation or numbers.  In our CM2007 environment we had the
inventory agent looking for *.exe throughout all hard disks, including the
Windows directory.  Their excuse for having it set that way is on some off
chance some executable gets installed somewhere in the Windows directory and
they want to query on it.  I personally hate the idea of an extra 2000+
lines of extra entries for each system being stored in the database when
they could just specify a file to add and they'd have the same complete
report in as many days as our software scan cycle occurs.  The price of
instant gratification for a "maybe" seems too high to me and really wanting
to change that mentality moving forward into the new CM2012 environment.

 

Does anyone know of anything out there showing either the resource hit on
the backend or how each entry that calls for a scan across the whole hard
drive is not very keen to the client machine either?  Heck, even a best
practices whitepaper on how one should streamline an inventory.

 

Thank you,

 

Richard Poole

IT Systems Engineer Consultant 

Infrastructure, Servers, Databases - System Center Configuration Manager
(ISD-SCCM)
Office:(480)684-7643 | Cell/Text/Pager:(602)317-5977

Banner Health - "We exist to make a difference in people's lives through
excellent patient care"
 <http://www.bannerhealth.com/> http://www.bannerhealth.com

 

 

 

 



Reply via email to