In this post I will be showing how to change SCCM Server log file size using Configuration Manager Service Manager. Configuration Manager server side log files for Site servers are located under installation directory of Microsoft Configuration Manager\logs folders. If installation was done in d drive, then the location would be d:\Program Files\Microsoft Configuration Manager\Logs.

Configuration Manager creates log files for each specific component, let say mpcontrol.log which shows the health of the Management point has a component name called “SMS_MP_CONTROL_MANAGER” and each log file is assigned a specific log file size.

In case, more data is captured, it will become historical log file so as to start capturing the latest logs. Mpcontrol.log size if exceeds 2 MB, it will now have 2 files:

  • Mpcontrol.lo_ (historical log file – old one)
  • Mpcontrol.log (latest one)
Site Server logs

Requirement for increasing the log file size

But what if you were not able to capture all the details as log file of 2 MB looks pretty small and if you wanted to get the data 3-4 days old, and found it has been overwritten ?

This is where increasing the log file size will be useful to capture more data. Rather than specifying 2 MB, we can make it 10 MB or anything what we like.

Majority of Configuration Manager components / log files are having 2 MB log file while few of them are having different size. We can change the value for each specific component based upon our requirement.

How to increase SCCM Server log files size

SCCM Site Server log files size is saved under the registry key Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Tracing, where we can see list of all Site Server components.

For CONFIGURATION_MANAGER_UPDATE component, we can see maximum file size and log file name with location:

MaxFileSize is 15728640 (15 MB)

TraceFilename: d:\Program Files\Microsoft Configuration Manager\LOGS\CMUpdate.log

MaxFileSize

We can change the value here.

However, I would prefer much more professional and efficient way to change this using Configuration Manager console.

Launch Configuration console and navigate to \Monitoring\Overview\System Status\Component Status to display list of all Component Status.

Component Status

Right click any component, start and click Configuration Manager Service Manager.

Configuration Manager Service Manager

Once Configuration Manager Service Manager is launched, you can see list of Configuration Manager Site Servers, expand it to see Components and Servers.

Under Components, select any specific component, for example SMS_EXECUTIVE, on right pane select the component and right click to select Logging.

SMS_EXECUTIVE Logging

Which comes up with “Logging Enabled” along with:

  • Long filename: D:\Program Files\Microsoft Configuration Manager\Logs\smsexec.log
  • Log size (MB): 2
ServerLogFile 06

Make appropriate changes for log size and that’s it.

List of Component names along with log file and size

Following are the list of all Configuration Manager components, along with log file name and default size:

CONFIGURATION_MANAGER_UPDATECMUpdate.log15 MB
SMS_AD_FOREST_DISCOVERY_MANAGERADForestDisc.log2 MB
SMS_AD_SECURITY_GROUP_DISCOVERY_AGENTadsgdis.log2 MB
SMS_AD_SYSTEM_DISCOVERY_AGENTadsysdis.log2 MB
SMS_AD_USER_DISCOVERY_AGENTadusrdis.log2 MB
SMS_AI_KB_MANAGERaikbmgr.log2 MB
SMS_ALERT_NOTIFICATIONNotiCtrl.log2 MB
SMS_AZUREAD_DISCOVERY_AGENTSMS_AZUREAD_DISCOVERY_AGENT.log2 MB
SMS_BUSINESS_APP_PROCESS_MANAGERSMS_BUSINESS_APP_PROCESS_MANAGER.log2 MB
SMS_CERTIFICATE_MANAGERCertMgr.log2 MB
SMS_CLIENT_CONFIG_MANAGERccm.log2 MB
SMS_CLIENT_HEALTHchmgr.log2 MB
SMS_CLOUD_SERVICES_MANAGERCloudMgr.log2 MB
SMS_CLOUD_USERSYNCcloudusersync.log2 MB
SMS_CLOUDCONNECTIONSMS_CLOUDCONNECTION.log2 MB
SMS_COLLECTION_EVALUAT0Rcolleval.log2 MB
SMS_COMPONENT_MONITORcompmon.log2 MB
SMS_COMPONENT_STATUS_SUMMARIZERcompsumm.log2 MB
SMS_DATABASE_NOTIFICATION_MONITORsmsdbmon.log2 MB
SMS_DESPOOLERdespool.log2 MB
SMS_DISCOVERY_DATA_MANAGERddm.log2 MB
SMS_DISTRIBUTION_MANAGERdistmgr.log2 MB
SMS_DMP_DOWNLOADERdmpdownloader.log2 MB
SMS_DMP_UPLOADERdmpuploader.log2 MB
SMS_EN_ADSERVICE_MONITORadctrl.log2 MB
SMS_ENDPOINT_PROTECTION_MANAGEREPMgr.log2 MB
SMS_EXECUT1VEsmsexec.log2 MB
SMS_FAILOVER_MANAGERFailOverMgr.log2 MB
SMS_HIERARCHY_MANAGERhman.log2 MB
SMS_INBOX_MANAGERinboxmgr.log2 MB
SMS_INBOX_MONITORinboxmon.log2 MB
SMS_INVENTORY_DATA_LOADERdataldr.log2 MB
SMS_INVENTORY_PROCESSORinvproc.log2 MB
SMS_ISVUPDATES_SYNCAGENTSMS_ISVUPDATES_SYNCAGENT.log2 MB
SMS_LAN_SENDERsender.log2 MB
SMS_LICENSE_MANAGERlicensemgr.log2 MB
SMS_MESSAGE_PROCESSING_ENGINESMS_MESSAGE_PROCESSING_ENGINE.log2 MB
SMS_MIGRATION_MANAGERmigmctrl.log2 MB
SMS_MP_CONTROL_MANAGERmpcontrol.log2 MB
SMS_MP_FILE_DISPATCH_MANAGERmpfdm.log2 MB
SMS_NETWORK_DISCOVERYnetdisc.log2 MB
SMS_NOTIFICATION_MANAGERbgbmgr.log2 MB
SMS_NOTIFICATION_SERVERBgbServer.log2 MB
SMS_OBJECT_REPLICATION_MANAGERobjreplmgr.log2 MB
SMS_OFFER_MANAGERoffermgr.log2 MB
SMS_OFFER_STATUS_SUMMARIZERoffersum.log2 MB
SMS_OFFLINE_SERVICING_MANAGEROfflineServicingMgr.log2 MB
SMS_OUTBOX_MONITORoutboxmon.log2 MB
SMS_OUTGOING_CONTENT_MANAGERoutgoingcontentmanager.log2 MB
SMS_PACKAGE_TRANSFER_MANAGERPkgXferMgr.log2 MB
SMS_POLICY_PROVIDERpolicypv.log2 MB
SMS_PROVIDERScertificate.log2 MB
SMS_REPLICATION_C0NFIGURAT10N_M0NIT0Rrcmctrl.log2 MB
SMS_REPLICATION_MANAGERreplmgr.log2 MB
SMS_REST_PROVIDERSMS_REST_PROVIDER.log2 MB
SMS_RULE_ENGINEruleengine.log2 MB
SMS_SCHEDULERschedule.log2 MB
SMS_SERVICE_CONNECTORSMS_SERVICE_CONNECTOR.log2 MB
SMS_SITE_BACKUPsmsbkup.log2 MB
SMS_SITE_COMPONENT_MANAGERsitecomp.log2 MB
SMS_SITE_CONTROL_MANAGERsitectrl.log2 MB
SMS_SITE_SQL_BACKUPsmssqlbkup.log2 MB
SMS_SITE_SYSTEM_STATUS_SUMMARIZERsitestat.log2 MB
SMS_SITE_VSS_WRITERsmswriter.log2 MB
SMS_SOFTWARE_INVENTORY_PROCESSORsinvproc.log2 MB
SMS_SOFTWARE_METERING_PROCESSORswmproc.log2 MB
SMS_SRS_REPORTING_POINTsrsp.log2 MB
SMS_STATE_SYSTEMstatesys.log2 MB
SMS_STATUS_MANAGERstatmgr.log2 MB
SMS_WINNT_SERVER_DISCOVERY_AGENTntsvrdis.log2 MB
SMS_WSUS_CONFIGURATION_MANAGERWCM.log2 MB
SMS_WSUS_CONTROL_MANAGERWSUSCtrl.log2 MB
SMS_WSUS_SYNC_MANAGERwsyncmgr.log2 MB

Discover more from SCCM | Intune | Azure | Enterprise Mobility & Security

Subscribe to get the latest posts to your email.