Join Brien Posey for an in-depth discussion in this video Analyze log files in Configuration Manager, part of Windows 10: Plan and Implement Software Updates.
- [Instructor] Configuring System Center Configuration Manager to handle updates can be a complicated process. There are a lot of moving pieces and there's a lot of room for things to go wrong. Fortunately, System Center maintains an elaborate set of log files that you can use to help you diagnose problems with updates. So I want to show you what some of those log files look like. I'm going to go ahead and open up file explorer and I'm going to go to this PC and I'll go to C and then program files and then Microsoft Configuration Manager and then logs.
And I'll go ahead and make this full screen. And as you can see, Configuration Manager has a lot of different log files associated with it. But there are a few different log files that you should look at if you're trying to diagnose problems with the update process. The first of these log files is SUP setup. I'll go ahead and go to that log file. And here it is right here. And the SUP setup log file has to do with the software update point. This log file is created when the software update point is set up and it shows you whether or not that set up process was successful.
I'll go ahead and open the log file and this log file is fairly short, but if we look at the very bottom of the log file, we can see that installation was successful. I'll go ahead and close this. Another log file that's worth looking at is WCM and you can see the WCM log file right at the bottom of the screen. This log file involves entries related to connecting your software update point to WSUS or the Windows Server Update Services. Let's go ahead and take a look at this one.
This log file contains a lot more information than the last, but when it comes to System Center Configuration Manager, the newest log entries are always at the bottom, so here we can see using posey lab WSUS_service credentials for network connections and we can see attempting connection to WSUS server. And then we can see successfully connected to server, IN-SS-SCCM.poseylab.com over port 8530. So this log file is useful in verifying that System Center Configuration Manager was able to successfully establish a connection to the WSUS server.
I'll go ahead and close out this log file. The next log file that I want to point out is WSUS control. And you can see that log file right here and this is another log file that can be fairly long, but once again the newest entries are at the bottom. So this log file contains information related to configuration database connectivity and WSUS server health. So if we look at the bottom of the log file, we can see that we are successfully connected to the local WSUS server and that there are no unhealthy WSUS server components on the WSUS server.
And we successfully checked the database connection on the WSUS server. So there are the types of log entries that you want to be looking for. I'll go ahead and close this out and there's one more log file that I want to show you. W sync manager, and that's at the very bottom of the list, and W sync manager contains information related to software update synchronization. So I'll go ahead and open that one up. And I'll scroll to the bottom of the log file. So as we look at this log file, there are a lot of things going on here, but what I'm really looking for is messages like this.
Done synchronizing SMS with WSUS server. And then a couple more lines down, sync succeeded. So we're able to make sure that our System Center Configuration Manager server was able to successfully synchronize with our WSUS server. So that's where this log file comes in handy. So as you can see, System Center Configuration Manager maintains an elaborate set of logs and those logs can be very helpful in allowing you to diagnose various problems that may have occurred.
- Deploying updates manually
- Monitoring deployments
- Configuring automatic deployment rules
- Analyzing log files
- Approving and declining updates in Intune
- Deploying software from SCCM, WSUS, and Intune