SCCM Server Infrastructure Monitoring Script Without SCOM OpsMgr Automation ConfigMgr

Let’s use the SCCM Server Infrastructure monitoring script without SCOM. We have a post about SCOM monitoring of SCCM infrastructure.

Hopefully, this automation script from Karthikeyan can help ConfigMgr admins automate some of the monitoring tasks.

“Have you ever wished you could peer inside the mind of one of the greatest SCCM bloggers in the world and find out exactly what makes them tick?” Yeah! Right. I have updated the script on 29th July 2021.

In this blog, we will discuss various SCCM components troubleshooting methods already used and documented by our experts to make our day-to-day operations much easier. You all have done the unthinkable.

SCCM Server Infrastructure Monitoring Script Without SCOM

Now, you will think you have already spent plenty of time reading those articles/blogs, so why should you waste more time on the same things again? Hey, Hear me out; we will not discuss those error codes, resolutions, root causes, and workarounds again.

Still, we will try to pick a few and find a method to automate them. So, let’s find out more details about SCCM Server Infrastructure Monitoring without SCOM OpsMgr below.

Note: The brain behind this scrip is Author: A. Karthikeyan

So, without any further delay, let’s see what we have.

Note: These instructions are intended for the ConfigMgr Team in the normal execution of infrastructure management.

• Top 50+ Latest SCCM Interview Questions and Answers
• SCCM 2403 New Key Features and Improvements
• SCCM Automation using Azure Runbook Hybrid Worker

Core Infrastructure Check – All in One

The main reason to pick the “all in one” check at the very beginning is that we all try to complete this check before entering the change request freeze window, and at that moment, all we can think of is that we should not leave any stone untouched.

So this script is essential for all those SCCM Administrators who always think, “What if I missed any component, and it’s going to create chaos?” Don’t worry. Be happy.

Copy the script from the bottom of this post and execute it on your CAS or Primary site, whichever you have the highest in your hierarchy. The script generates the output in HTML format with the status in different colours, making it easy to spot. Once execution is completed, the output will look like the below:

The output will be saved to the same directory where you saved this script during execution. In the above screenshot, you can see how detailed a check is performing. There is no untouched part we need to worry about.

To verify whether the script works, we purposefully broke the backup and executed it. The script highlighted that the backup failed. Screenshot below:

Status in red and with the type if it’s Site Backup or DB backup which failed. Hold on. We are not done yet. You can schedule a task to execute it and forget about it. There is more. You don’t have to jump to your server to check the status constantly. It can send the HTML file to your e-mail so you can read the current status.

Below are a few points we need to remember before setting up our SCCM Infrastructure.

ConfigMgr Administration Best Practices

Let’s check the list of best practices for administration. I hope you have all the information on SCCM server Infrastructure Monitoring without SCOM OpsMgr.

1. Use AD Sites to define ConfigMgr boundaries to avoid overlapping.
2. Automate maintenance tasks and create custom maintenance tasks.
3. Create OUs for ConfigMgr Servers.
4. Use AD Groups and Accounts to manage the ConfigMgr environment.
5. Keep administrative rights to a minimum level of Access.
6. Create a plan for role-based administration and apply only the rights necessary to perform job functions.
7. Use NTFS on all client and server partitions.
8. Assign the least permissions possible.
9. Do not install site servers on Domain Controllers.
10. Do not install other services that use the local system account.
11. Use GPO and ConfigMgr Client Push Method to install client agents on computers.
12. Add only required users to the ConfigMgr admins group, or create alternate groups and use role-based access control for permissions.
13. Create ConfigMgr AD OU containers for service IDs, Application Management IDs, Management groups and Servers.
14. Lock down the ConfigMgr Infrastructure using Domain Groups and Accounts.
15. Configure SUP on every primary and secondary site server.
16. Enable SMTP access on the Top ConfigMgr server to send custom SSRS Reports.
17. Only deploy the ConfigMgr client to trusted computers.
18. Do not use a domain admin account as the client push installation account.
19. SQL Server must be configured to use Windows Authentication.
20. Remove or Disable the Guest account from the ConfigMgr SQL Database.

Disclaimer – The information provided on site is for general informational purposes only. All information on the site is provided in good faith. However, we make no representation or warranty of any kind, express or implied, regarding the accuracy, adequacy, validity, reliability, availability, or completeness of any information on the website.

Script

Below is the script produced by Karthikeyan. Please review it and make the necessary changes before trying it out. Update 28th July 2021: How to use the script.

1. Copy the Script and execute. (If there are any errors at the initial level of execution, then let me know)
2. It will create a default config file for you on the same path as where you saved this script.
3. Modify the config.xml to match your server names, etc. Look for SCCMCentralDBName, SCCMCentralDBServerName.
4. More details are in the comments below.

Note: As soon as you execute the script it will ask to create a default configuration file to the same location where you have saved this script. Screenshot below:

Now you have a ConfigXML file. Open the ConfigXML file with Notepad, and please modify the values according to your infrastructure. A script required Admin rights on all SCCM Servers and read access required on the database to fetch the component error details. Screenshot below:

Download the Script from GitHub – https://github.com/AnoopCNair/ConfigMgr-Infra-Monitoring

Resources

• Monitor the hierarchy
• ConfigMgr MP Health Check Script | SCCM Endpoint Manager

Author

Deepak Rai is a Technical Lead with over 14 years of experience in IT. He specializes in SCCM (AKA ConfigMgr, CB, MECM, etc.), Intune, and Azure (Runbooks). Throughout his career, he has worked on various platforms such as Active Directory, Exchange, Veritas NETBACKUP, Symantec Backup Exec, NDMP devices like Netapp, EMC Data Domain, Quantum using Backup Exec 2010 and 2012, and HP StorageWorks 4048 MSL G3. He also has experience in data deduplication-related troubleshooting. Ultimately, he returned to his roots as an IT Engineer focusing on SCCM technology.