OpsMgr 2012 Data Warehouse Health Check Script Updated

Since I published the OpsMgr 2012 Data Warehouse Health Check Script last week, the responses I have received from the community have been overwhelming! As I mentioned the the post that there might be potential issues when executing the script for an environment where the Data Warehouse DB is hosted on a named SQL instance, man people have reached out to me and confirmed this is indeed the case. Over the last few days, I have been busy updating this script to address all the issues identified by the community. The version 1.1 is now ready. I have addressed the

OpsMgr 2012 Data Warehouse Health Check Script

Note (19/06/2015): This script has been updated to version 1.1. You can find the details of version 1.1 here: http://blog.tyang.org/2015/06/19/opsmgr-2012-data-warehouse-health-check-script-updated/. The download link at the end of this post has been updated too. I’m sure you all would agree with me that the OpsMgr database performance is a very common issue in many OpsMgr deployments – when it has not been designed and configured properly. The folks at Squared Up certainly feels the pain – when the OpsMgr Data Warehouse database is not performing at the optimal level, it would certainly impact the performance of Squared Up dashboard since Squared Up

SCCM Health Check Script Updated: Version 3.5

I have just updated the SCCM Health Check Script to from version 3.3 to 3.5 Version 3.4 was finished a while back but I never got time to publish it in this blog. I only emailed 3.4 to few people who contacted me from my blog. Now that I’ve updated it again to 3.5, I thought I’ll just publish version 3.5. What’s Changed Since 3.3? Added site system name under ‘site systems with issues’ section Detect site components that are missing heartbeats. Changed function Validate-DNSRecord to use Win32_ComputerSystem.caption rather than DNSHostname to retrieve computer name as DNSHostName is not available

SCCM Health Check PowerShell Script Updated to Version 3.3

I have updated the SCCM Health Check Script again. The latest version is now 3.3. Below is what’s been updated since my last post for version 3.1: Fixed the bug where when using DOTNET sending emails to multiple recipients, it only sends to the first recipient from the list. It now zip the txt attachment to zip file before sending it. this is to improve the performance and avoid sending large attachments. Added functionality to check all current active package distribution Able to create exemptions for DNS suffix check. This can be configured in the XML. (this is required at

Updated: SCCM Health Check PowerShell Script

I have updated the SCCM Health Check Script that I have originally posted here. Download Version 3.1 Here. Changes: 1. The script can now utilise Powershell Remoting to check inboxes sizes. It requires PS-Remoting to be enabled on all SCCM Site Servers. This dramatically reduced the execution time of the script in a multi-tier environment. In a production environment that I support, it reduced the execution time from 1.5 – 2 hours to around 35 minutes!  You can configure which method to use via XML file. To enable, set <PSRemoting><Value> to Enabled. Or Disabled if you want to use the

PowerShell Script: SCCM Health Check

30/01/2012: This script has been updated to version 3.5. Details can be found HERE. The download link on this article has also been updated to version 3.5. 26/05/2011: Version 3.3 has been posted here. The download link to the script on this post is also updated to the new version 3.3. 21/04/2011: Please be advised that I have posted a newer version of the script here. The existing script download link on this page has also been updated to point to the newer version. For the chanages in newer version, please refer to my updated post. Over the last few

%d bloggers like this: