I think... but I'm not really sure because I haven't looked at it lately and my
memory is poor :) ... I think that what's displayed in the console for that
info comes from one of the ClientHealth tables in the database?
CH_ClientSummary? If you run this in SQL management Studio against your CM_xxx
database, and input the collection ID of that collection with "boxes with hinv
within the last 7 days", if I'm remembering right, the chlasthinv will be all
stuff from June 30th and earlier, but the 'lasthwscanReally' will be within the
last 7 days.
For anyone else reading this, and trying it on their own database, note the
CH_clientSummary stuff will almost NEVER perfectly match for every client--the
"lastHWscanReally" will almost always be newer, for many clients, than what
ch_clientsummary has. That's because the clientsummary is based on a
summarization task, that runs on a schedule -- a schedule no one can control.
so don't worry about it if it's not exactly matching.
but for Mike, if your data is ch_clientsummary is way out of whack, at least
you know what to start with when you open that call. You can show them quite
quickly that you think the issue is based on "summarization tasks not
finishing".
select fcm.Name, ch.lastddr 'chlastddr', ch.lasthw 'chlasthinv', ws.LastHWScan
'LastHWScanReally'
, ch.lastsw 'chlastsw', ch.LastPolicyRequest 'chlastpolicy'
from CH_ClientSummary ch
join v_GS_WORKSTATION_STATUS ws on ws.ResourceID=ch.MachineID
join v_FullCollectionMembership fcm on fcm.resourceid=ch.machineid
where fcm.collectionid = 'ThatCollectionHere'
On Tuesday, August 4, 2015 4:49 PM, "Murray, Mike" <[email protected]>
wrote:
#yiv4610933125 #yiv4610933125 -- filtered {font-family:Helvetica;panose-1:2
11 6 4 2 2 2 2 2 4;}#yiv4610933125 filtered {panose-1:2 4 5 3 5 4 6 3 2
4;}#yiv4610933125 filtered {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2
4;}#yiv4610933125 p.yiv4610933125MsoNormal, #yiv4610933125
li.yiv4610933125MsoNormal, #yiv4610933125 div.yiv4610933125MsoNormal
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;}#yiv4610933125 a:link,
#yiv4610933125 span.yiv4610933125MsoHyperlink
{color:blue;text-decoration:underline;}#yiv4610933125 a:visited, #yiv4610933125
span.yiv4610933125MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}#yiv4610933125
p.yiv4610933125msonormal, #yiv4610933125 li.yiv4610933125msonormal,
#yiv4610933125 div.yiv4610933125msonormal
{margin-right:0in;margin-left:0in;font-size:12.0pt;}#yiv4610933125
p.yiv4610933125msochpdefault, #yiv4610933125 li.yiv4610933125msochpdefault,
#yiv4610933125 div.yiv4610933125msochpdefault
{margin-right:0in;margin-left:0in;font-size:12.0pt;}#yiv4610933125
p.yiv4610933125msonormal1, #yiv4610933125 li.yiv4610933125msonormal1,
#yiv4610933125 div.yiv4610933125msonormal1
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;}#yiv4610933125
p.yiv4610933125msochpdefault1, #yiv4610933125 li.yiv4610933125msochpdefault1,
#yiv4610933125 div.yiv4610933125msochpdefault1
{margin-right:0in;margin-left:0in;font-size:10.0pt;}#yiv4610933125
span.yiv4610933125msohyperlink {}#yiv4610933125
span.yiv4610933125msohyperlinkfollowed {}#yiv4610933125
span.yiv4610933125emailstyle17 {}#yiv4610933125 span.yiv4610933125emailstyle18
{}#yiv4610933125 span.yiv4610933125msohyperlink1
{color:blue;text-decoration:underline;}#yiv4610933125
span.yiv4610933125msohyperlinkfollowed1
{color:purple;text-decoration:underline;}#yiv4610933125
span.yiv4610933125emailstyle171 {color:#1F497D;}#yiv4610933125
span.yiv4610933125emailstyle181 {color:#1F497D;}#yiv4610933125
span.yiv4610933125EmailStyle29 {color:#1F497D;}#yiv4610933125
span.yiv4610933125EmailStyle30 {color:#1F497D;}#yiv4610933125
.yiv4610933125MsoChpDefault {font-size:10.0pt;}#yiv4610933125 filtered
{margin:1.0in 1.0in 1.0in 1.0in;}#yiv4610933125 div.yiv4610933125WordSection1
{}#yiv4610933125 In fact, we have a collection using the below query that shows
clients with a recent HW inventory (7 days or less). It is populating! Yet,
hardware & software scan date columns are at 6/30/2015. This is mind boggling.
select
SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client
from SMS_R_System inner join SMS_G_System_WORKSTATION_STATUS on
SMS_G_System_WORKSTATION_STATUS.ResourceID = SMS_R_System.ResourceId Where
DATEDIFF(dd,SMS_G_System_WORKSTATION_STATUS.LastHardwareScan,GetDate()) < 7
From: [email protected]
[mailto:[email protected]]On Behalf Of Murray, Mike
Sent: Tuesday, August 4, 2015 2:43 PM
To: [email protected]
Subject: RE: [mssms] Before I open a support ticket with MS... Thanks,
Sherry. I can see my system in the dataldr.log on the site server, so it looks
like the data is getting there. But it’s not updating in the console. :/
From:[email protected] [mailto:[email protected]]On
Behalf Of Sherry Kissinger
Sent: Tuesday, August 4, 2015 1:33 PM
To: [email protected]
Subject: Re: [mssms] Before I open a support ticket with MS... Start
here:http://www.enhansoft.com/blog/troubleshooting-inventory-flow and see
where inventory falls down. On Tuesday, August 4, 2015 3:21 PM,
"Murray, Mike" <[email protected]> wrote: Yes, we are. The time sever
outage affected everything. From:[email protected]
[mailto:[email protected]]On Behalf Of Kent, Mark
Sent: Tuesday, August 4, 2015 11:32 AM
To: [email protected]
Subject: RE: [mssms] Before I open a support ticket with MS... Are you not on
an AD domain? Your clients don’t synch time with your DC’s? Mark Kent (MCP)
Sr. Desktop Systems Engineer Computing & Technology Services - SUNY Buffalo
State From:[email protected]
[mailto:[email protected]]On Behalf Of Sean Pomeroy
Sent: Tuesday, August 4, 2015 2:23 PM
To: [email protected]
Subject: Re: [mssms] Before I open a support ticket with MS... If you go to
view hardware inventory classes in client settings, does the console crash?
On Tue, Aug 4, 2015 at 1:47 PM Murray, Mike <[email protected]> wrote:
Quick background – our NTP time server went down for a short while a couple of
months ago. As a result, we had wonky timestamps in CM. Some had the year 2034.
We worked with MS and they were able to clear this up. Now we have a new
issue, and they want us to open a separate case to address it (even though I
believe it’s a direct result of the work they already performed). Our hardware
and software inventory in the console only goes up to 6/30/2015 (the day they
worked on our server). I can see newer inventory when I open resource explorer
on machines, but it’s not showing in the console. Policy requests are showing
current dates. Any ideas of things to try before I spend any more money with
MS? Best Regards, Mike Murray Desktop Management Coordinator - IT
Support Services California State University, Chico 530.898.4357
[email protected]
