Again, why wouldn’t you use a CI or Sherry’s PST script? Both are lite weight in comparison to SW inv.
From: [email protected] [mailto:[email protected]] On Behalf Of Kent, Mark Sent: Thursday, October 29, 2015 11:46 AM To: [email protected] Subject: RE: [mssms] SCCM 2007 R2 - Software Inventory is Incredibly slow How are you doing PST’s? Mark Kent (MCP) Sr. Desktop Systems Engineer Computing & Technology Services - SUNY Buffalo State From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of ccollins9 Sent: Thursday, October 29, 2015 11:18 AM To: mssms <[email protected]<mailto:[email protected]>> Subject: Re: [mssms] SCCM 2007 R2 - Software Inventory is Incredibly slow We use software inventory to identify PSTs on a system. Our goal is to find them, import them, destroy them and ban the ability to ever create them again. Like terminating roaches!. It works, but I have run into the issues mentioned about the 4 hour timeout. There are other PST gathering tools out there, but we haven't had the chance (or money) to try them out yet. On Thu, Oct 29, 2015 at 10:12 AM, Burke, John <[email protected]<mailto:[email protected]>> wrote: Hi folks, We haven’t gotten the chance to upgrade to 2012 yet so I’m stuck with 2007. We are noticing a fair number of clients that are semi healthy with the exception of software inventory. I’ve seen some posts that simply say don’t bother using Software inventory because it’s too slow. That seems a bit silly. Why have the feature at all if it’s going to be useless. In our environment we often create collections based on exe versions or dll versions for upgrade purposes. Internet Explorer for example – seems to be something that you need software inventory to deal with. So – I’m wondering what you folks do with Sofwtare Inventory. Do you bother using it? Did you tweak it somehow to make them faster so they it doesn’t take hours?
