Sccm 2016 logs not updating
If you had already installed KB3174008, 1606 will revert the fixes included in KB3174008.
For clients, the logs are generally located in C: Windows CCMLogs (This will be different for older versions of SCCM).SCCM 1511 is still the baseline version if you’re starting from scratch.SCCM 1606 is now available as a new baseline media. In this episode, we share the latest support for Windows Server 2016 with updates for Shielded VMs and Nano Server; building Hyper-converged clusters with Storage Spaces Direct; Tuned alerting and better discoverability of Management Packs with Operations Manager and what's coming for hybrid management across your data center and the Cloud.You can try System Center 2016 for yourself at: aka.ms/trysystemcenter2016.But sometimes the console’s description may not provide enough information to help you troubleshoot the issue you may be having. Check out my recent blog on SCCM Troubleshooting 101: Log Files to learn more.
SCCM has extensive log files to help provide in depth information when you receive and error message.
Once you know what log you need to examine, you can open the log file and start reviewing it.
For example, if you are troubleshooting package and program deployment, you need to look at the on a client machine.
By default, if you double click to open the log file, it will open in Notepad as a text file.
Opening the log file in Notepad will certainly allow you to get information, but there is another tool in the SCCM troubleshooting toolbox that will revolutionize log file review – CMTrace.
CMTrace is a powerful tool for helping as we examine the many log files SCCM generates.