Jump to content


GarthMJ

Moderators
  • Posts

    1939
  • Joined

  • Last visited

  • Days Won

    92

Everything posted by GarthMJ

  1. That make sense, but why not start with it? Then you can built on that.
  2. Do you have any Windows Embedded devices?
  3. Look at the built-in report for this and filter out all but the Windows 7 and Window xp
  4. Post of screenshot of you Client version on the client itself and within the CM12 console.
  5. I'm not sure why you are looking at the different place within the computer properties windows. As it doesn't list the discovery and inventory data/times. However at the bottom of that screenshot, you can see the both Heartbeat and Hardware inventory have been updated on June 12 2015.
  6. That query looks fine. But keep in mind that it will only work on the x86 version of "GlobalProtect".
  7. I'm confused. Did CM12 work before or not? if so what changed? A Site reset will allow you to change the db location.
  8. It is generally recommend that you install SQL on CM12 site server itself. So why do you want it remote from CM12?
  9. Since you didn’t say, I can only assume that HW inventory and Heartbeat discovery are not listed within the device properties, right???
  10. CM07 will only report what is within the database, if there are issue within in the database on what is on the client you need to dig into the problem. The simplest solution is to force a Full hardware inventory cycle on all client. Here are some blob post to review. http://www.enhansoft.com/?s=force+hardware&post_Ptype=post
  11. The simplest way is to use the Software Update report within CM12. You can get a list of everyone who is missing that SU.
  12. It will only retry if you set a new deadline. 1603 is a generic error code that basically say review the MSI log file. MSI log files are not created by default.
  13. The issue is your detection rule is wrong. fix your detection rule and everything will be good.
  14. Use the built-in reports to get this information.
  15. There is no need to post duplicate posts. Error 5 = Access Denied.
  16. 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.
  17. Does it make it to the dataldr.log?
  18. 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?
  19. You need to look at MP_DDR.LOG for Heartbeat discovery.
  20. It should work as long as your computer is within the same domain and ports are not blocked between the CM12 server and the console.
  21. 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
  22. 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.
  23. 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.
  24. 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.
  25. Have you seen this one. http://blogs.msdn.com/b/chrissu/archive/2014/07/22/ssrs-error-the-defaultvalue-expression-for-the-report-parameter-usertokensids-contains-an-error-there-are-currently-no-logon-servers-available-to-service-the-logon-request-rsruntimeerrorinexpression.aspx
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.