Jump to content


GarthMJ

Moderators
  • Posts

    1945
  • Joined

  • Last visited

  • Days Won

    93

Everything posted by GarthMJ

  1. Keep in mind that query will only find x86 version of Office 365. You need to add the x64 class too if you want both x86 and x64.
  2. Enable the win32_printer class within hardware inventory to get local printer.
  3. This report query will help you out. http://smsug.ca/blogs/garth_jones/archive/2012/07/02/how-to-find-an-application-installed-in-the-last-7-days.aspx
  4. Replace 'ES-06' with @PC This will create a prompt for the report. If you want to make it fancy you can then add a drop down or browse list for the PC name. The easiest way to convert your CM07 to CM12 report is to make sure that you have already converted them from ASP to SSRS then you can upload the same converted reports to CM12. Other than that, I your recommend rebuilding them and filtering out all the old junky reports.
  5. Yes, you can do that you will need to open the report and edit SQL to do it. I would recommend that make your own version of that report, instead of replacing it.
  6. It is not possible to run CM12 with any other collation and you want you temp db to be the same collation too. As an aside I NEVER recommend that SQL be remote from CM12.
  7. I generally agree with AdinE but if this is seriously only for 150 users/devices then I would think that you can do it one 1 box, assuming SCSM will allow you to install everything on 1 box.
  8. Create a report, I think that I missed that tidbit, did you copy the SQL certificate to you local PC? And just to close off the other bit, can you run report from your RPs?
  9. Where did you install the RP? Are you trying to access the site via the cluster or the one of the node of the cluster?
  10. There is no best practice either way, there is few note about performance on site with 100 000 device or more. However, from a management standpoint you will have far fewer support issues with SQL be local than with it being remote. Heck I add 15 days to any project where SQL is remote due to the complexity it add and the inevitable problem that will crop up over time.
  11. SSRS is not supported to be installed on a cluster. You can install SSRs on one or both node but each will be separate install of SSRS. In order to use CM12 RP you would need to install the RP on each node and access then via the node address not the cluster address. As an aside, I never recommend splitting SQL from the primary server.
  12. What is causing the reboot messages? Are you sure they are CM12 Messages and not something like Windows Update?
  13. You can do this with WSUS or CM07/CM12. Are you using CM07 orCM12?
  14. We are looking for your help! Help us about by take 2 minutes to complete this survey about SCCM reports. It will help us decide on what new reports to add to Enhance Web Reporting (EWR) and what new reports we will be giving away in the future. http://fluidsurveys.com/surveys/info-HZv/configmgr-ssrs-report-survey-sept-2013/
  15. Then you will NEVER be able to install any service pack using CM12 and SUP.
  16. Have you talked to the team at Flexera to see how they suggest you handle this issue? They are the best people to talk to about this.
  17. This should be an non issue as you are using the CM12 server for SSRS, just create the reporting role on the server and then use the real CM12 db for the source.
  18. There isn't a spreadsheet like this. if you want one you will need to create one on your own.
  19. Have you look at the software updates Superflow on troubleshooting SU? http://technet.microsoft.com/en-us/library/ff385001.aspx
  20. Moving to the CM07 forum... You will need to review the log file to see what is going.
  21. What is wrong with the query that I posted?
  22. To be honest, I have never looked at the InventoryProvider.log, I haven't found a need to.. After a quick review of my InventoryProvider.log, it too has a number of errors, so I would suggest that they are normal.
×
×
  • 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.