Secunia is the primary reason I do software inventory.  Secunia requires an 
inventory of exe dll and ocx.  I can chose to collect that information using 
SCCM, Secunia's agent, or a remote scan.  All of these methods are going to 
scan the entire hard drive and collect information for all executables.  From 
my standpoint, I would rather use the SCCM agent to do this so that I have the 
information in the SCCM db for me to use for other stuff.  I could also install 
Secunia's CSI agent, but it is still going to scan the entire hard drive and 
look at every exe dll and ocx.

Anyway, my question was not about the merits of doing software inventory, but 
rather how to get it to work in an environment where you put computers to 
sleep.  WOL only wakes a computer for 2 minutes, which is not long enough to 
get much of anything done.


From: [email protected] [mailto:[email protected]] On 
Behalf Of Jason Sandys
Sent: Monday, May 13, 2013 1:07 PM
To: [email protected]
Subject: [mssms] RE: Keep awake for inventory

Not true to my knowledge. Per-user installs still properly register themselves 
with Windows and thus are returned via AI.

And of course, just because an exe exists on a system, does not mean the 
product is installed and is not necessarily indicative of a certain 
product/suite either; e.g., word.exe does not mean Office 2010 Pro is installed.

J

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Miller, Todd
Sent: Monday, May 13, 2013 12:31 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: Keep awake for inventory

It is really hard to say.  Looking at the inventory log file it just shows 
hardware inventory messages piling up.  Software inventory doesn't really write 
much to the log while it is running - so it is hard to guess what the process 
might be.  I am still on 2007 - it doesn't have a bunch of "beginning software 
inventory messgaes" without ends.  It just has a begin in there from a few days 
ago.  Maybe it will not restart on its own.

Asset intelligence only lets you know about software that was installed 
normally.  With the way that people are moving to have their software install 
without admin rights in the user's profile, it is less and less useful. The 
software like that is also the stuff that is most concerning.

None of that really answers the question about keeping a machine awake long 
enough for inventory processes to run.  SCCM keeps a machine awake for pending 
software installation - I'd think it would do that for pending inventory jobs 
as well.


From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Michael Mott
Sent: Monday, May 13, 2013 11:06 AM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: Keep awake for inventory

On a side note, does it pick up where it left off or does it start over?  Seems 
like it starts over actually, or did in 07

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Miller, Todd
Sent: Monday, May 13, 2013 10:20 AM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] Keep awake for inventory


When a  computer  begins SWINV it takes something like 1 hour to complete.  My 
trouble is that computers fall asleep during SWINV.  Computers that are lightly 
used are hardly ever left on long enough to complete the inventory process.

I have advertisements that go out occasionally that will use WOL to wake up 
machines, but a computer will go back to sleep after 2 minutes if it is sent a 
WOL and there is not activity from the user.

Why doesn't HWINV and SWINV count as "activity" to keep the computer from going 
back to sleep?  Is there a setting I could make that would keep the computer 
awake so that SWINV could complete when the computer wakes up via WOL?

I know there is a power setting for how long Widows 7 will stay awake from WOL, 
but that setting is not available in SCCM power management.  I don't think you 
can (or that it is a smart idea to) set some power settings via Group Policy or 
registry edits and some via SCCM power management.

As I ratcheted up more aggressive power savings, I am finding that SCCM is 
having more and more trouble keeping the machine's information up to date.  If 
SCCM agent on a machine is stuck on trying to finish Software Inventory, it is 
unable to send heartbeat - since that is also part of the inventory system.  
Software Inventory is blocking heartbeat and SCCM thinks the machine has fallen 
over.  Kind of a mess.

I would disable SW Inventory entirely except that we use the data to scan 
against for software vulnerabilities.

Basically, I am looking for a way to make it so that SCCM Inventory counts as 
activity, and that SCCM will prevent sleeping while an inventory is running.

________________________________
Notice: This UI Health Care e-mail (including attachments) is covered by the 
Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and 
may be legally privileged.  If you are not the intended recipient, you are 
hereby notified that any retention, dissemination, distribution, or copying of 
this communication is strictly prohibited.  Please reply to the sender that you 
have received the message in error, then delete it.  Thank you.
________________________________


________________________________


DISCLAIMER: This is a PRIVATE AND CONFIDENTIAL message for the ordinary user of 
this email address. If you are not the intended recipient, please delete 
without copying and kindly advise us by e-mail of the mistake in delivery. 
NOTE: Regardless of content, this e-mail shall not operate to bind 1E to any 
order or other contract unless pursuant to explicit written agreement or 
government initiative expressly permitting the use of e-mail for such purpose.


________________________________
Notice: This UI Health Care e-mail (including attachments) is covered by the 
Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and 
may be legally privileged.  If you are not the intended recipient, you are 
hereby notified that any retention, dissemination, distribution, or copying of 
this communication is strictly prohibited.  Please reply to the sender that you 
have received the message in error, then delete it.  Thank you.
________________________________




________________________________
Notice: This UI Health Care e-mail (including attachments) is covered by the 
Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and 
may be legally privileged.  If you are not the intended recipient, you are 
hereby notified that any retention, dissemination, distribution, or copying of 
this communication is strictly prohibited.  Please reply to the sender that you 
have received the message in error, then delete it.  Thank you.
________________________________



Reply via email to