You can also reference C:\Windows\WindowsUpdate.log which is a windows native log and not to SCCM, but is updated with actions taken by SCCM in regards to updates. Provides information about the compliance status for the software updates that were assessed during the compliance scan cycle.Provides information about when the Windows Update Agent on the client searches for software updates.Provides information about the scan requests for software updates, what tool is requested for the scan, the WSUS location, and so on.Provides information about software update compliance scanning and about the download and installation of software updates on the client.Verbose logging shows additional information about the interaction with the client user interface. SCCM is largely ineffective at patching third-party applications. Provides information about the deployment on the client, including software update activation, evaluation, and enforcement.Remember to always use CMTrace as your SCCM log viewer, it just makes your life easier.Īll of these listed directly below, should be located in C:\Windows\CCM\logs on your client. These should get you 95% of the way on your troubleshooting (from the client side anyways). The most powerful enterprise-level patch managers can scan systems on your network (often across multiple platforms), detect missing patches (both third-party apps and operating system. Today I had to compile a list of client logs to check for a friend of mine, and thought I’d share. We all know SCCM can be your best friend, and your worst nightmare. SCCM Client Logs for Software Update Troubleshooting
0 kommentar(er)
