crmatthews Posted May 28, 2015 Report post Posted May 28, 2015 Hi, I will do my best to explain the issue i am having but it is a weird issue. We have a collection set up that shows us any client that is not on R2 CU4, Upon monitoring this i have noticed that i have a lot of workstations sat in this collection that have recently been re-imaged with a task sequence that uses CU4 in the wizard. i have checked the client manually and it seems to have built correctly, it has all the right software all the actions and it reports to have the correct client version. (5.00.7958.1501). Yet when i check in configuration manager on the properties of that client, the version is 5.00.7958.1000. These workstations have been stuck in this collection and like this for about a month. I checked and most of these workstations have had a heartbeat update within the last 2 days. I also believe this issue is related to why in my recent batch of updates they are reporting as unknown even though i have checked on the Clients themselves and they seem to have installed the updates. Any ideas will be appreciated. Thanks. Quote Share this post Link to post Share on other sites More sharing options...
GarthMJ Posted May 28, 2015 Report post Posted May 28, 2015 What is your Heartbeat discovery cycle set too? Quote Share this post Link to post Share on other sites More sharing options...
crmatthews Posted May 28, 2015 Report post Posted May 28, 2015 Hi Garth, Our heartbeat discovery is set to 2 Days currently. Quote Share this post Link to post Share on other sites More sharing options...
Garrett804 Posted May 28, 2015 Report post Posted May 28, 2015 Have you tried manually running a data discovery cycle on one of the machines with the issue to see if it then updates the data in the console? Quote Share this post Link to post Share on other sites More sharing options...
crmatthews Posted May 28, 2015 Report post Posted May 28, 2015 Yeah, no luck. Today i have Deleted about 25 workstations out of SCCM and AD, re-image them with the same name and they all reappeared in the collection with the wrong version number.At first i was thinking maybe its the Task Sequence, but i can re-image workstations that are reporting correctly or build machines for the first time and they report fine. So maybe its the SQL Server, I'm going to restart tomorrow out of working hours. Quote Share this post Link to post Share on other sites More sharing options...
crmatthews Posted June 1, 2015 Report post Posted June 1, 2015 So after restarting the SQL Server, i have run a full Discovery Data Collection Cycle on the whole site. I noticed the pc's would then report back correctly with the right version number. Only for this to last about 30 mins before reverting back. Which makes no sense. I have also run a Delete Aged Discovery Data cycle, still no luck. Any Ideas? Quote Share this post Link to post Share on other sites More sharing options...
GarthMJ Posted June 1, 2015 Report post Posted June 1, 2015 From that screenshot there is clearly a problem with that client or your MP. Notice that there is not listed for Heartbeat discovery within your computer properties. Also notice that there is no Hardware inventory date either. Quote Share this post Link to post Share on other sites More sharing options...
crmatthews Posted June 1, 2015 Report post Posted June 1, 2015 From that screenshot there is clearly a problem with that client or your MP. Notice that there is not listed for Heartbeat discovery within your computer properties. Also notice that there is no Hardware inventory date either. I have about 100 clients with the same issue, its not random though as it seems to be clients from 3 different rooms rather than all over our site. As for the screenshot, the Client in the image had just been rebuilt so i don't think it has done a hardware scan yet. Where would i find the heartbeat under the properties menu? Quote Share this post Link to post Share on other sites More sharing options...
GarthMJ Posted June 1, 2015 Report post Posted June 1, 2015 The HW inv would have happened within ~ 2 hours after it was imaged, unless it was blocked by SW inv. From the screenshot the last heartbeat was on May 28, therefore your HW inventory should have shown up by now. (unless you have crazy SW inventory rules) Look under agent names for Heartbeat discovery. But there is clearly something not right with that client or your MP. Quote Share this post Link to post Share on other sites More sharing options...
crmatthews Posted June 1, 2015 Report post Posted June 1, 2015 Ok, i don't think we have any crazy rules, both are currently set to 7 days? Most of the clients having this issue do have a recent SW and HW inventory scan. Sorry i didn't noticed i got rid of that by mistake. Quote Share this post Link to post Share on other sites More sharing options...
GarthMJ Posted June 1, 2015 Report post Posted June 1, 2015 IMO, Just having SW inventory enabled is crazy. http://www.enhansoft.com/blog/slow-software-inventory-cycle-in-sccm-2012 I recommend turning it OFF. IMO, both HW and heartbeat should be set to daily. Quote Share this post Link to post Share on other sites More sharing options...
crmatthews Posted June 1, 2015 Report post Posted June 1, 2015 Ok that is something we shall look into, do you think that could be something to do with the issue we are having, as it seems SCCM does get the right client information, but then some how reverts back? Quote Share this post Link to post Share on other sites More sharing options...
GarthMJ Posted June 1, 2015 Report post Posted June 1, 2015 If it is reverting back that would suggest a SQL issue but start by looking at why you are not getting HW inv. http://www.enhansoft.com/blog/troubleshooting-inventory-flow Quote Share this post Link to post Share on other sites More sharing options...
crmatthews Posted June 2, 2015 Report post Posted June 2, 2015 If it is reverting back that would suggest a SQL issue but start by looking at why you are not getting HW inv. http://www.enhansoft.com/blog/troubleshooting-inventory-flow Ok so using that guide applied to the Data Discovery Collection Cycle, when i am running the action, on the client inventory log i can see its running, it's successful in sending to the MP and i can see a record in the IIS logs. I can also see a record in the MP_Ddr log, for today, so that would suggest that its done a scan today? Yet in the console it says last scan was yesterday? Quote Share this post Link to post Share on other sites More sharing options...
GarthMJ Posted June 2, 2015 Report post Posted June 2, 2015 You need to look at MP_DDR.LOG for Heartbeat discovery. Quote Share this post Link to post Share on other sites More sharing options...
crmatthews Posted June 2, 2015 Report post Posted June 2, 2015 This is what todays log says: Full report from client M31-01, action description = Discovery 01/01/1601 00:00:00 0 (0x0000) Ddr Task: Translate report attachment to file "C:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box\MOHLB96O.DDR" returned 0 01/01/1601 00:00:00 0 (0x0000) Mp Message Handler: copying attachment to C:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box\DdrAttachmentCXF5T5KS.xml 01/01/1601 00:00:00 0 (0x0000) Inv-Ddr Task: processing xml file "C:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box\DdrAttachmentCXF5T5KS.xml" 01/01/1601 00:00:00 0 (0x0000) Yet in the console it says the heartbeat DDR was done yesterday at 8:20 Quote Share this post Link to post Share on other sites More sharing options...
GarthMJ Posted June 2, 2015 Report post Posted June 2, 2015 Is that from the mp_ddr.log or the dataldr.log? Do you see the record within the dataldr.log? why is your date 1601? Quote Share this post Link to post Share on other sites More sharing options...
crmatthews Posted June 2, 2015 Report post Posted June 2, 2015 Thats from the MP_Ddr.log. Good question all of the entries are like that on this log. I'm not sure why it's like that. Quote Share this post Link to post Share on other sites More sharing options...
crmatthews Posted June 2, 2015 Report post Posted June 2, 2015 Thats from the MP_Ddr.log. Good question all of the entries are like that on this log. I'm not sure why it's like that. I've checked and it seems to be Cm Trace not picking up the time stamps, but if i view the log in notepad its time stamped correctly. Quote Share this post Link to post Share on other sites More sharing options...
GarthMJ Posted June 2, 2015 Report post Posted June 2, 2015 Does it make it to the dataldr.log? Quote Share this post Link to post Share on other sites More sharing options...
crmatthews Posted June 3, 2015 Report post Posted June 3, 2015 Yes, It seems its taking long time to process the information, in the console i have a heartbeat record at 09:03 02/06/2015. Yet in the Datadrl.log the only entry is at 15:29 02/06/2015. So it's clearly done a Heartbeat DDR yesterday, but it's still showing the wrong version number in the client properties. Quote Share this post Link to post Share on other sites More sharing options...
GarthMJ Posted June 3, 2015 Report post Posted June 3, 2015 If the DDR is process successfully within dataldr.log then the data can be seen within CM12 console (devices) properties ASAP. Notice that I said "device properties". If you are looking at the summary data it will take up to 24 hour before that is updated. Hence why I never look at it. Quote Share this post Link to post Share on other sites More sharing options...
crmatthews Posted June 15, 2015 Report post Posted June 15, 2015 Sorry for the late reply, I have been on holiday. Yes it does make it to the dataldr.log file. Quote Share this post Link to post Share on other sites More sharing options...
GarthMJ Posted June 15, 2015 Report post Posted June 15, 2015 Since you didn’t say, I can only assume that HW inventory and Heartbeat discovery are not listed within the device properties, right??? Quote Share this post Link to post Share on other sites More sharing options...
crmatthews Posted June 16, 2015 Report post Posted June 16, 2015 I'm not sure where i am looking, is this correct? Quote Share this post Link to post Share on other sites More sharing options...
