Jump to content


GarthMJ

Moderators
  • Posts

    1948
  • Joined

  • Last visited

  • Days Won

    93

Everything posted by GarthMJ

  1. Does it make it to the dataldr.log?
  2. 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?
  3. You need to look at MP_DDR.LOG for Heartbeat discovery.
  4. 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.
  5. 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
  6. 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.
  7. 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.
  8. 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.
  9. 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
  10. have you seen this? http://www.enhansoft.com/blog/configuration-manager-2012-r2-ssrs-and-windows-authorization-access-group
  11. Exactly what permission do you check? Do you get the same error within the Web interface? BTW I never recommend accessing SSRS from the console.
  12. What is your Heartbeat discovery cycle set too?
  13. CM12 MUST be installed in the EXACT same Domain/Forest (aka SIDs), if it is not it will fail. So unless this is an exact clone of your existing forest, (which I would never recommend doing) , the whole process will fail and is completely unsupported.
  14. Are you sure you are seeing MW or are they Business hours? They are NOT the same thing.
  15. You first query only finds x86 version of Visio. The report will find both x86 and x64. Create a second WQL query to find x64 copies of Visio.
  16. The minimum is 1 GB for Windows 7 but honestly I haven't not seen anything less than 4GB (3.5GB on x86) in years! If you have a TAM tell him about your issue and get him to "look at it". They will then get the right person to work on it.
  17. 2GB is tiny amount of RAM. Point your CSS team to this blog. http://blogs.technet.com/b/configurationmgr/archive/2015/04/15/support-tip-configmgr-2012-update-scan-fails-and-causes-incorrect-compliance-status.aspx
  18. What happens when you manually download that SU?
  19. To add to what Peter said, CM12 clients will randomly select a SUP to scan against, they ignore boundaries. Therefore a CM12 client might pick a SUP remote to them. Honestly once the initial SU catalog is download there is only minor traffic between the CM12 client and the SUP,.
  20. If you look at your query you are explicitly saying that you only want to look at x86 computer and don't want to see any data from x64. "SMS_G_System_COMPUTER_SYSTEM.SystemType = "X86-based PC"" This will filter out any x64 computer with an x86 version of Office.
  21. Why do you have a SUP on all of you DPs? It is generally not recommend to have too many SUP.
  22. Keep in mind that your will NOT find any x64 computers with x86 version of Office.
  23. Why don't you just turn off automatic pushing for the CM12 client? Use a start up script instead.
  24. If you are already working with CSS (MS Support) on a SUP issue. You should talk to them about this before making any changes.
  25. Let's be clear a 6GB laptop will never work.
×
×
  • 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.