Not really because it’s likely, as you noted in an MMS presentation, that SINV
will timeout before it completes.
________________________________
John Marcum
MCITP, MCTS, MCSA
Desktop Architect
Bradley Arant Boult Cummings LLP
________________________________
[H_Logo]
From: [email protected] [mailto:[email protected]] On
Behalf Of Jason Sandys
Sent: Thursday, October 29, 2015 1:58 PM
To: [email protected]
Subject: RE: [mssms] SCCM 2007 R2 - Software Inventory is Incredibly slow
Note though, that Sherry’s script, great as it is, only looks for PSTs actively
attached to Outlook. This may or may not satisfy the actual requirement. If the
requirement is to find all PSTs, in use or not, then the script does not
fulfill this. SW Inv does however.
J
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Garth Jones
Sent: Thursday, October 29, 2015 1:30 PM
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] SCCM 2007 R2 - Software Inventory is Incredibly slow
“Because up until 5 minutes ago I didn't know it existed. I will assuredly be
looking into it now tho, that's for sure.”
☺
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of ccollins9
Sent: Thursday, October 29, 2015 2:14 PM
To: mssms
Subject: Re: [mssms] SCCM 2007 R2 - Software Inventory is Incredibly slow
"Are you simply telling SW inventory to look for .PST?"
Yes, unfortunately we have it looking at all hard drives because there are
several fileservers out there that it can be on. That and I've seen users store
them in very odd locations of their profiles. So right now we have it set to
*.pst, all drives, excluding windows folder.
"Again, why wouldn’t you use a CI or Sherry’s PST script?"
Because up until 5 minutes ago I didn't know it existed. I will assuredly be
looking into it now tho, that's for sure.
On Thu, Oct 29, 2015 at 12:51 PM, Garth Jones
<[email protected]<mailto:[email protected]>> wrote:
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]>
[mailto:[email protected]<mailto:[email protected]>]
On Behalf Of Kent, Mark
Sent: Thursday, October 29, 2015 11:46 AM
To: [email protected]<mailto:[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?
________________________________
Confidentiality Notice: This e-mail is from a law firm and may be protected by
the attorney-client or work product privileges. If you have received this
message in error, please notify the sender by replying to this e-mail and then
delete it from your computer.
