Sccm system ou name not updating
When you know which log files to research for what failure condition and at what time, issues that were once mysterious and difficult to understand may become clear and understandable.
The MDT log file format is designed to be read by Trace32, which is part of the System Center Configuration Manager 2007 Toolkit V2, available for download from the Microsoft Download Center.
The rest of this section details the log files created during deployment as well as during Windows Setup.
This section also provides examples of when to use the files for troubleshooting.
By running the following query, you get count of clients for each lasterrorcode that reported to CM12.
I have got lot many computers with error code –2016409966 .
Then, you can explore the client computer’s hard disk, view the event log, remove updates, change operating system settings, and so on.
Using reports/ collections, cleanup lot of old records ,fix SCCM client issues using scripts and clients are now at good success rate (95% ,for some reason, Software update scan is lower than 80% and that causes the SUP compliance failed to meet the SLA.Ran below SQL Query to pick one computer with above error code(–2016409966 ): select sys.name0 from v_r_system sys,v_updatescanstatus uss where sys.resourceid=uss.resourceid and uss.Last Error Code='-2016409966' connect to computer ccm\logs and check The above errors leads to me to think about GPO, if there is any such configured but after checking with Server Team ,there is no such group policy configured.The logs can also be read by the Configuration Manager Trace Log Tool (CMTrace) that is available with System Center 2012 Configuration Manager and later versions.Use these tools whenever possible to read the log files, because it makes finding errors much easier.