As Christmas is approaching, what best to receive presents, istn’t it?
Thinking on all of you that supported us during the year, we are releasing a “pre-beta” version of the SCCM 2012 R2 HealthCheck toolkit (you can download it form here).
This release has lots of changes from its predecessor (the SCCM 2007 HealthCheck toolkit).
As it is still in “pre-beta” stage, we only tested it remotely from a w7/w8.1 machines against a single primary site (cm12 sp1 cu3 and another cm12 r2) with admin rights to the CM12 box without any problem (we haven’t run it locally on the server)
Anyway, how to use it:
1- CollectData.ps1 (This script will collect information from a CM12/R2 Infrastructure). Open the powershell (64 bits) and run with an account that has admin rights on the cm boxes as it will connect remotely to registry, wmi, etc.
- CollectData.ps1 -smsprovider servername (ie. CollectData.ps1 -smsprovider srv0003)
- Once it collect data, it will create a CollectData.log under _Logs and will create a Date\servername folder (ie. 2013-12-05\srv0003)
2- ExportData.ps1 (this script will export the collected data to a Word 2013 format). Open powershell (64 bits) on a machine with Word 2013 installed (don’t need have admin rights on the local box this time)
- ExportData.ps1 -reportfolder C:\Temp\CM12R2HealthCheck\2013-12-05\srv0003 (this will perform a full export)
- ExportData.ps1 -reportfolder C:\Temp\CM12R2HealthCheck\2013-12-05\srv0003 -detailed $false (this will export summary information)
– We developed this for the R2 version, but it works (and we have tested) on a 2012 SP1 CU3 (we don’t know about older version)
– Word has a limitation on the number of pages, if you reach this number, i suggest exporting part of the queries each time. Easy way to do it is deleting the XML files from the folder you collected the data
– If you’re running on a SP1 environment, be careful with the report as it will report all systems as running older version of the client
– it will always fail to connect to the root\SecurityCenter2 wmi namespace
We also, we’d like to hear from you…send your queries/comments to firstname.lastname@example.org