SCCM 1702 Clientservicing log file details

SCCM 1702 Clientservicing log file details – Many of you are wondering about what’s this clientservicing log file ?. What does this log file actually contain. There are threads on Reddit and Technet forums about this. Not much details about this log file is available online. Few users have noticed Clientservicing.log file logging huge data during operating system deployment. In this post I will try to cover the info about clientservicing.log file which i got from the product group.

SCCM 1702 Clientservicing log file details

Here is an explanation to what is clientservicing.log file in SCCM 1702. Microsoft recently came up with a new client servicing endpoint for facilitating client auto-upgrade or piloting. Currently this file helps deliver the client deployment state messages only. If the client agent is upgraded successfully (ccmsetup for the success case), at the end it will just write the state message to WMI. This endpoint will pick up to try delivering to MP and fall back to FSP only when the client wasn’t able to assign/register. This can help to improve the reliability and latency of the deployment state messages. The log file is for this component.

The clientservicing log file is located under \Windows\CCM\Logs folder path.

SCCM 1702 Clientservicing log file detailsOpening clientservicing.log file contains the following lines.

Started client deployment pending message handler job.
StateId: 400, SiteCode: ‘TEC’, ClientVersion: ‘5.00.8498.1008’
Params: ‘5.0.8498.1008 Deployment [DP]$/TEC00002’
Details: ‘<ClientDeploymentMessage ErrorCode=”0″><Client Baseline=”1″ Platform=”2″> <SourceType Value=”DP”/><SourceLocation Value=”$/TEC00002″/><DeploymentMethod Value=”1″/>
Client is registered. Sending client deployment state message using State Message Endpoint.
Received WMI __InstanceModificationEvent Event notification for class CCM_PendingDeploymentStateMessage

If you feel the above info is incorrect, do write in comments.

Related Posts
1 Comment
Oldest Most Voted
Inline Feedbacks
View all comments

So, why are people reporting large file sizes for a log that only contains client deployment state messages? And what should be done if the file gets huge?

This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Accept Read More