Has this ever happened to you? You’re trying to do a proper investigation of a problem, but you can’t because the log file was overwritten too quickly? Did you know that the default log file size for all site server logs is 2 MB? This size is too small for an average System Center Configuration Manager (SCCM) site. Since I still get asked about how to increase the size of SCCM site server log files, I decided to update my original 2015 blog post.
In that post I recommended that the site server log file size be increased to at least 10 MB in order to be able to review the log file over a 5-day period. I still stand by that recommendation because reviewing a log file over a 5-day period is very useful when troubleshooting an issue.
New in this post is an easy way to increase, all at once, all of SCCM Current Branch’s site server log files to 10 MB! I’m including this information in case you don’t want to individually select each component. As well, if you’re still using SCCM 2012, or even if you’ve upgraded to Current Branch, I’ll show you how to find and use Configuration Manager Service Manager to increase the size of log files.
I will start off by showing you where Configuration Manager Service Manager is found within the console and how to increase the size of log files by using it (new). Then I will show you how to edit the log file sizes via the registry (from the original blog post). Finally, I will show you how to change all of the log file sizes at once (new).
In SCCM 2007 you could use Configuration Manager Service Manager to increase the size of the site server log file.
I thought for the longest time that Configuration Manager Service Manager was removed from the SCCM 2012 console. However, it turns out that it was there all along, hidden deep within the console. Below I’ll show you how to find it!
How to Access Configuration Manager Service Manager
How to Increase the Log File Size with Configuration Manager Service Manager
Start by expanding the Site Code and then the Components node. Next, expand the component where you want to increase the log file size. In my case it’s SMS_AMT_PROXY_COMPONENT.
Next select the server name. In the right pane, right-click on the component (SMS_AMT_PROXY_COMPONENT) and click on Logging.
In this case I’ll increase the log file size from 10 MB to 15 MB. After increasing the size, click on the OK button. At this point you need to either restart the component or wait for the server to reboot. I generally wait until the next server reboot. This method is fine for one or two log files, but not for more than 50 different log files! Stay tuned for more information later on in this post about my easy method for how to increase log file sizes.
How to Manually Increase the Size of SCCM Site Server Log Files
Since this information isn’t readily available, I put together the following instructions in 2015 to save you some time. Keep in mind that I’m using the SCCM 2012 screenshots from my original post, but all of the steps are the same with Current Branch.
On your site server, open Regedit.exe and browse to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Tracing
Here each component is listed under the Tracing key. As you can see in the screenshot above I have the SMS_AD_FOREST_DISCOVERY_MANAGER key selected for this example and it has a key called MaxFileSize of type REG_DWORD.
Double click on this value (MaxFileSize), change the Value data to A00000 (10 MB) and then click OK. The SMSExec service will need to be restarted in order for the new log file size to take effect.
Repeat this step for each component where you want the log file size changed.
If you want to return the log file back to its default size of 2 MB, change the Value data to 280000.
Easy Method to Increase All SCCM Current Branch Site Server Log Files to 10 MB
To make your life easier, okay, it was to make my life easier, I created a registry file that increases the size of all SCCM Current Branch log files to 10 MB. There are currently over 50 different components in Current Branch! This same trick will work for all older versions of SCCM, however, I haven’t created registry files for them. If you create registry files for older versions, let me know and I will add links to them.
Start by downloading the registry file from Enhansoft’s website.
On your primary site or CAS, open Regedit. Click on the File menu and then click on Import...
Select the SMSTracing 10mb.reg file and then click on the Open button.
Click OK and you are done!
Isn’t that a lot easier than manually editing each component one at a time, especially when you consider that there are over 50 components?
Don’t forget that SCCM services needs to be restarted in order for the new file size settings to take effect. I generally wait for the server to reboot during the next Software Update deployment cycle. Once SCCM services is restarted all SCCM components will have a 10 MB log file size.
Note: Keep in mind that until SCCM services is restarted, some log file sizes may be 10 MB while others may still be 2 MB.
Restoring Log Files Back to 2 MB
If you would like to restore your log files back to the default size, simply repeat the process above, but instead use the SMSTracing 2MB.reg file.
Current Branch Note
Now that SCCM Current Branch is being updated on a regular basis and new features are often added, don’t forget to go back and increase the log file size of all new components.
If you have any questions, please feel free to contact me @GarthMJ.