Daily Best Practice for Healthy SCCM server

In order to make sure that you sccm environment should run smoothly always follow the below best practice

Ø  Administrative Checklist for Configuration Manager 2007

1.       Go to the site component and check SMS _SITE_BACKUP Component and last date when it was run and was it successful. I my experience I have seen that even if backup fail the SMS _Site_ Backup will not show it as fail. To be on safer side I recommend checking smsbkg.log on server.

2.       Expand the Site Status and look for error or warning in the site by check Component Status or Site System Status.

3.    Check the Processor :

The processor point status check is a check on the relevant servers Task Management status and the current status of the Processor on that server. If for some reason the processor is running high on utilization then this should be addressed to ensure that the issue is not a serious one.

To do this check the status of that sites Components and Site System Status information as above.

If the process is running ok (hovering between 30 and 60% generally) then a simple green box entry should be added to the Daily Checks spreadsheet as before,

However if there are failings on the processor checks (utilization is running very high into the 90 to 100% and steady) then these should be added into the spreadsheet as red boxes again as before which should also include an inserted comment explaining the issue and what you are doing to resolve the issue.

Important: If the processor is maxing out at around 90 to 100% on Primary site servers, check the following to ensure that is no excessive traffic to and fro the server cross the LAN / WAN

It’s also worth noting that a check on the Primary Site Servers SQL instance will be worth a look; as if SQL itself is struggling to process data quickly enough into the SQL Site database then this will cause the server to on occasions max out on the CPU.

4.       Check the size of SMS folder Structure to make sure that it is not flooding with any error or files.

         SMS inbox size andAlso\AUTH\DDM.BOX

5.       Check the IIS log Files :

Check the properties of the c:\windows\system32\logfiles\W3SVC1 folder

If the size of the folder (contents) exceeds 200Mb, then simply select all but the last 2 log entries (filter the display list by Date modified) and delete the log files. Keep the log files since last week and delete the rest

6.    SCCM Server Disk Space Check : Make sure that server should have 20% minimum disk space if you find that the space is less then just clean up the space to make sure that SCCM should not face any space issue.

7.    SCCM MP Check: To make sure that MP is working fine check the mpcontrol.log and also you can use the MP troubleshooter tool to check the health of MP.

8.    Removing the obsolete Systems: Create the collection with the query to collect all the obsolete systems in the environment.

Note: Always use delete special option while deleting the systems