and... blogged
it.http://www.mnscug.org/blogs/sherry-kissinger/405-configmgr-2012-inventory-max-random-delay
On Tuesday, June 23, 2015 6:22 AM, Sherry Kissinger
<[email protected]> wrote:
There's something called "Inventory Max Random Delay", which is a sorta kinda
hidden setting. You can adjust it, just not via the console. My understanding
of what it is for is to randomize when, for example, someone uses client push
to say... their entire, newly discovered, every single system discovered in AD.
It's so that there isn't a flood of full inventory within 10 minutes in those
cases. Of course, if you're a mature installation--it's unlikely that you'll
have that. By default it is 240 minutes (4 hours)--we've changed ours to 60.
To see what it is set to, here's the SQL you'd run in SQL Server Management
Studio against your cm_sitecode database, just to see what yours it set at:
(view only, it changes nothing.) Each primary will have it set. (If you are
unlucky to have a CAS, it will have it as well; but a CAS has no clients so
it's not really relevant; but for consistency may want to change it) SELECT
SD.SiteCode, SCC.ClientComponentName, SCP.Name, SCP.Value1, SCP.Value2,
SCP.Value3 FROM SC_ClientComponent SCCJOIN SC_SiteDefinition SD ON
SD.SiteNumber = SCC.SiteNumberJOIN SC_ClientComponent_Property SCP ON
SCP.ClientComponentID = SCC.IDWHERE SCP.Name like '%Inventory Max Random
Delay%' To adjust the Max Random Delay, you run the attached vbscript, after
modifying the SiteCode to match the one you are changing You run it as cscript
whatever.vbs YourPrimaryServerName The3CharSiteCode (after changing the
desiredvalue and sitecode inside). If you have multiple primaries, you need to
run it on each one--it's per sitecode.
=============================
Take a look at inventoryagent.log.
-----Original Message-----
From: Roland Janus [[email protected]]
Sent: Tuesday, June 23, 2015 05:43 AM Eastern Standard Time
To: [email protected]
Subject: [mssms] hardware inventory not triggered on new client installation
I have that same issue on two 2012 R2 SP1 installations and never noticed that
before: The schedule for hw inv is set to once a day (regular, not custom).When
installing a system using OSD the ddr is sent right away, but hardware
inventory isn’t (software inv is empty).The action is available, so it knows
that it needs to or at least that it is enabled, I can trigger it manually and
it works fine then but unless I trigger it manually it just sits there . The
same happens when installing the client on existing machines. Not on all of
them but some. (given they are a mess and will be refreshed later on)But as it
seems to have the policy, why isn’t it triggering it right after the agent
install or OSD? I’ve never noticed that behavior on previous versions (I think)
-R
The information transmitted is intended only for the person or entity to which
it is addressed
and may contain CONFIDENTIAL material. If you receive this material/information
in error,
please contact the sender and delete or destroy the material/information.
On Tuesday, June 23, 2015 5:04 AM, Daniel Ratliff <[email protected]>
wrote:
#yiv3998758135 -- filtered {panose-1:2 4 5 3 5 4 6 3 2 4;}#yiv3998758135
filtered {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}#yiv3998758135
p.yiv3998758135MsoNormal, #yiv3998758135 li.yiv3998758135MsoNormal,
#yiv3998758135 div.yiv3998758135MsoNormal
{margin:0cm;margin-bottom:.0001pt;font-size:11.0pt;}#yiv3998758135 a:link,
#yiv3998758135 span.yiv3998758135MsoHyperlink
{color:#0563C1;text-decoration:underline;}#yiv3998758135 a:visited,
#yiv3998758135 span.yiv3998758135MsoHyperlinkFollowed
{color:#954F72;text-decoration:underline;}#yiv3998758135
span.yiv3998758135EmailStyle17 {color:windowtext;}#yiv3998758135
.yiv3998758135MsoChpDefault {}#yiv3998758135 filtered {margin:70.85pt 70.85pt
2.0cm 70.85pt;}#yiv3998758135 div.yiv3998758135WordSection1 {}#yiv3998758135
