Jump to content


GarthMJ

Moderators
  • Posts

    1939
  • Joined

  • Last visited

  • Days Won

    92

Everything posted by GarthMJ

  1. Use Maintenance windows to block the deployment of software. Keep in mind that this will NOT stop an administrator from manually installing software.
  2. I'm sorry to say this is not a simple task and would take weeks of effort for me to create these reports and this is clearly not a single report but my guess at least 10 different reports. My suggestion is a few fold, break it down into a few different reports. Start with the high level and get the result for each item listed below. Remove IP address from all reports. This will cause you headaches. For items like, Audit on AV and malware, define exactly how you would do this task manually, then you can try to automated it.
  3. Try this.. Watch out for typos.. I write this free hand. select distinct SMS_G_System_SYSTEM.Name, ARP.DisplayName, ARP.Version from SMS_R_System as Sys full join SMS_G_System_ADD_REMOVE_PROGRAMS as ARP on ARP.ResourceID = Sys.ResourceId full join SMS_G_System_SYSTEM on SMS_G_System_SYSTEM.ResourceID = Sys.ResourceId where ARP.DisplayName like "Sigmaplot %"
  4. Without having your first query it is impossible to answer this question.
  5. #1, I never recommend access the report via the console, there is just too much over head and too many problems. #2, have you reviewed the client side logs to ensure that the client is actually reporting data to CM12? 99% of the time when they display no data, it is because a GPO is blocking the client from using the CM12 SUP.
  6. I would start with the one listed within the docs for Daily, weekly and monthly tasks.
  7. Hi Nick, It is the AI classes that need to be abled to get the automatic rules created. But the automatic rules are useless because they will create a rule for Explorer.exe, or your AV software or other useless stuff like drivers, mouse software etc. On top of that they are disabled so what is the point of them. Honestly the best option is manually create the rule as you import the package and only for software which has a cost, otherwise there is no point to creating them.
  8. There isn't much too the process. CM12 download the policy that apply to them and apply them.. So exactly what you are looking for? Exactly what setting under custom device setting have you select within the Power Management option?
  9. I'm sorry but this is not true. You don't need SW inventory to make SW metering work at all. On top of that I NEVER recommend enabling SW inventory, it is generally not what people think and it is (IMO) all be useless.
  10. I never recommend enabling the automatic SWM rule. You will find that it will create junk rules. Instead manually create the rules that you need.
  11. ResourceID will NEVER match Name. Change the Name to ResourceID any everything will be fine. where SMS_R_System.ResourceId not in (select SMS_R_System.Name
  12. I see what wrong you are not comparing apples to apples.. in you subselct query, what are you returning? In your Where section of your second query what are you returning? Will they ever match???? Hint: Nope.. Make them the same it will work.
  13. So I'm a bit confused, what is you question? SSRS will not show up in the setup wizard if your don't have the right CU install on SQL/SSRS itself. Exactly what version of SQL and SSRS are you running? What CU have been applied to both SQL and SSRS? Was SSRS installed AFTER SQL was installed? Did you re-apply the CUs and SPs? Why are you trying to use anything but the CM12 computer account to access SQL/SSRS? Or are you taking about the SSRS execution account? Did you know that it is NOT recommend that have SQL (and SSRS) remote from CM12 itself? Permissions will automatically get reset on SSRS by CM12 http://www.enhansoft.com/blog/disappearing-permissions-for-ssrs-reports-in-system-center-2012-configuration-manager
  14. I would post it here. https://connect.microsoft.com/ConfigurationManagervnext, the TechNet forums will not help get thing fixed.
  15. Yes you can do it, I would try to do it using the OS name or maybe the Computer manufacturer.
  16. Error 53 = The network path was not found. So.... check DNS.
  17. I recommend that you post this suggestion to the Connect.microsoft.com site. This is the only way it will get fixed. I would also post the link back here so that others can vote it up.
  18. Yes that is what Peter is saying. If you want snow you should come up my way! ;-)
  19. This data will show up under the v_gs_network_adapter_configuration SQL view. so you can do select * from dbo.v_GS_NETWORK_ADAPTER_CONFIGURATION
  20. This information is not collected by default and therefore you need to inventory it first.
  21. Sure you can do this, write a script to add the computer account into your AD security group. Then run the script during the TS.
  22. GarthMJ

    Hardware age report

    Keep in mind that I work for Enhansoft. Therefore my view is slight biased. ;-) The question you need to ask is, how accurate do you want your results? Warranty Information Reporting (WIR) will give you accurate results. My PCs warranty on started on May 16, 2013. If I used the BIOS date, my warranty started on Sept 24 2014. That is 496 days AFTER my warranty started. If I look at the OS install date, my warranty started on Jun 19 2014, that is 399 days after the real warranty start date but almost 100 days before the BIOS date, How do you explain that to a manager?!?!?! So how accurate do you want your results? If you ever want a demo or have questions, let me know and I will do my best to make sure that I’m the one doing the demo.
  23. This is going to happen with one of three reasons, Software Inventory is not enabled (and IMO it should never be in the first place) After your site restore you didn’t fix up clients You site restore didn’t work. I’m not sure how you restored a site without a back up!
  24. In CM12, those items are inventory by default, you need to enable them in the client setting.
×
×
  • 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.