ConfigMgr SCCM How to change Maximum Log File Size. ConfigMgr SCCM How to change Maximum Log File Size. A quick post on Maximum Logfile Size settings in the registry. I’ve tested this on Windows 2008 R2 server (x64).
The increasing log file size will be very helpful at troubleshooting. However, most people forget to change this reg key to the default value. This can cause space constraints on CM servers/clients.
ConfigMgr SCCM How to change Maximum Log File Size
The first thing you need to understand is operating system architecture. Is it x64 or x86?
The default size of the log file is 2.5 MB = Registry value is in bytes = 2621440 Bytes
So when you want to increase the SCCM Log File size to 10 MB, then covert this 10 MB to bytes first. ie 10 * 1024 * 1024 = 10485760 Bytes
1. When your SCCM 2007 server is on 64 bit OS
– Navigate through the following registry location and select the appropriate Key Name depending upon your requirement (for example, SMS_INVENTORY_PROCESSOR or SMS_DATABASE_NOTIFICATION_MONITOR or SMS_COLLECTION_EVALUATOR, etc…)
– Open up DWORD (32-bit Value) called MaxFileSize.
– Change the base to Decimal.
– Change the “Value Data” to default size (2621440 ).
– Restart the component service to change to take effect. (In my case, the changes take effect without restarting the service)
2. When your OS is x86, you can find the details if you navigate through the following location in the registry.
Follow the same steps mentioned above (Point 1) to complete the changes.
More Details about logging are available Here.
Anoop C Nair is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. He is Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc.