4.2 / 5 ( 4 votes )

Summary

we started developing it back in 2012 (with 1st version released in April 2013) to check the health of a SCCM 2007 environment and in October 2013 (about 1 year ago), we released the 1st version for 2012 environment.

This tools has been created to check for problem/misconfiguration in the environment and, when possible, will provide you with some solutions for problems.

And today, we’re proud to announce a new version of our ConfiMgr 2012 R2 Health Check toolkit, our beta 02 version.

This version contains a series of bug fixes, performance improvements as well as new functionality as we can summarize bellow:

Fixed hierarchy connection

added debug mode to record log queries

fixed some queries issues, where queries where returning more data or not return any data at all

fixed bug when collecting Roles Installed

fixed bug when collecting service status

added information about issues found

added possible solution to issues found

Removed support for any version lower than R2 (site version 5.00.7958.1000).

fixed issue when connecting to remote registry

fixed issue when collecting AV information. We now support McAfee Security, Symantec Endpoint Protection, Sophos Antivirus, Avast!, Immunet Protect, F-Secure, AntiVir, Avira, F-Protect, Panda Security, Panda AntiVirus, BitDefender, ArcaBit, IKARUS, ESET Smart Security, G Data Antivirus, Kaspersky Lab Antivirus, Symantec VirusBlast, ClamAV, Vipre / GFI managed AV, Norton, Kaspersky, Windows Defender, Microsoft Security Essentials

Fixed “crash” when connecting to a server without administrative access

Added information about hotfixes installed on a server

We also would like to add the following notes/requirements:

We have tested this tool on a single primary site and single primary site with secondary sites. We do expect it to work on a CAS environment, however, we have not been able to test.

We have run the tool remotely as well locally on the SCCM server. The minimum PowerShell version supported is version 3 64-bit running on W7, W8, W8.1, W10 and Windows Server 2012 R2. (but remember to use the “run as administrator” option, otherwise the tool may not work properly)

we tested with CM12R2 CU2+, we know that it works on CM12R2 RTM, but if you have any issue when running it on a RTM or CU1, let us know

Firewall rules for SQL (normally TCP 1433), remote WMI/DCOM (http://msdn.microsoft.com/en-us/library/jj980508(v=winembedded.81).aspx ) and Remote WUA (http://msdn.microsoft.com/en-us/library/windows/desktop/aa387288%28v=VS.85%29.aspx) should be in place (even when running the tool locally on a single primary site with only 1 server)

The user running the tool must have the following rights: SQL Server (serveradmin) to be able to see database / cpu stats SCCM Database (db_owner) used to create/drop user-defined functions msdb Database (db_datareader) used to read backup information at least read-only analyst on the SCCM console local administrator on all computer (used to remotely connect to the registry and services)

To generate the report, the computer running the script reportdata.ps1 must have Microsoft Word installed and activated. We currently support word 2010 (v14) and 2013 (v15)

Known issues:

We are also aware of an issue caused by multiple SMS Providers and we’re working to get this issue resolved.

Number of pages on word. We noticed that when the report generates over 2000 pages, word sometimes crash

Running the tool

The tool contain 2 PowerShell script files and 2 xml files (settings files).

xml – has information about queries to run in the environment, it is divided in 5 sections section 1 is to report/collect information about each site. section 2 is to report/collect information about each server in the environment section 3 is to report/collect information about each database server section 4 is to report/collect summary information about the SCCM environment section 5 is to report/collect detailed information about the SCCM environment

ps1 – collect data from the environment and write the return in a xml format

ps1 – export the collected data for a word format

xml – has information about messages to write as well as possible solutions

When running the script, you need to specify some parameters, however, if you don’t specify the parameters it will ask you for the required information or use the default settings. The following list shows what parameters can be used on each script:

ps1 Smsprovider – SMS Provider address (can be IP, Netbios name or FQDN name). NumberofDays – how far back the tool will check for problems. Default is 7 days Healthcheckfilename – name of the query xml file – default is cm12r2healthcheck.xml Healthcheckdebug – print log messages on the screen – default true

ps1 Reportfolder – full path for the collected folder detailed – report will export section 5. Default true Healthcheckfilename – name of the query xml file – default is cm12r2healthcheck.xml Healthcheckdebug – print log messages on the screen – default true



As you are expecting, the tool can be download from the RFL Systems Resources Webpage at http://www.rflsystems.co.uk/resources/

Like this: Like Loading...