Has this worked for you? We just set ours for 30 mins a few days ago and have not seen any better results. The machines are still taking several hours to report back. [image: Inline image 1]
Thank you, Amy Thank you, Amy Zitta ITS | 314-977-2117 On Tue, Jun 23, 2015 at 7:15 AM, Roland Janus <[email protected]> wrote: > Even better J > > > > I probably go shorter then you, have only 1000 clients. > > > > I thought it must be something like this, but does that also apply to > after OSD? > > Would that make any sense? > > > > One client is not reporting at all, but I can live with that. Will be > reinstalled anyway > > > > Thanks, Roland > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Sherry Kissinger > *Sent:* Dienstag, 23. Juni 2015 13:43 > *To:* [email protected] > *Subject:* Re: [mssms] hardware inventory not triggered on new client > installation > > > > 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 SCC > > JOIN SC_SiteDefinition SD ON SD.SiteNumber = SCC.SiteNumber > > JOIN SC_ClientComponent_Property SCP ON SCP.ClientComponentID = SCC.ID > <http://scc.id/> > > WHERE 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: > > > > > > > > > >
