SCCM client log and troubleshooting for patching

* SCCM is a beast in itself. It's client has so many components that even if 1 Component is not working,it can cause issues
* Log files are the heart of troubleshooting for SCCM.You have to know which log file to read in which order for effective troubleshooting
* All SCCM log files are in location C:\Windowds\ccm\logs folder
* For patching issues follow the following order for troubleshooting.
*First step is to see whether patches are getting download to the client. The patches once downloaded are stored in ccmcache folder.
*This folder is in C:\windows\ccmcache
*If patches are not downloaded  in this folder then you have problem with client not able to download the patches from WSUS server.
*  You should immediately look for log called wuahandler.log
*Look for errors in this log most likely you will see error connecting to WSUS server.
* Generally the easiest troubleshooting step I do if I see this error only on few clients is to uninstall and reinstall the client from the
* Mostly this should resolve if there is client issue. . I suggest doing the install from SCCM console and choose the location for the source to I still from site location.

SCCM 2012 R2 Log File for Client Notification issues

SCCM 2012 R2 Log File for Client Notification issues

Client Notification

The following table lists the log files that contain information related to client notification.

Log name	Description	Computer with log file
bgbmgr.log	Records details about the activities of the site server relating to client notification tasks and processing online and task status files.	Site server
BGBServer.log	Records the activities of the notification server such as client-server communications and pushing tasks to clients. Also records information about online and task status files generation to be sent to the site server.	Management point
BgbSetup.log	Records the activities of the notification server installation wrapper process during installation and uninstall.	Management point
bgbisapiMSI.log	Records details about the notification server installation and uninstall.	Management point
BgbHttpProxy.log	Records the activities of the notification HTTP proxy as it relays the messages of clients using HTTP to and from the notification server.	Client
CcmNotificationAgent.log	Records the activities of the notification agent such as client-server communication and information about tasks received and dispatched to other client agents.	Client

SCCM 2012 R2 Log Files for Troubleshooting -Client Troubleshooting

SCCM 2012 R2 Log Files for Troubleshooting

Client Operations

The following table lists the log files found on the Configuration Manager client.

Log name	Description
CAS.log	Content Access service. Maintains the local package cache on the client.
Ccm32BitLauncher.log	Records actions for starting applications on the client marked as "run as 32bit".
CcmEval.log	Records Configuration Manager client status evaluation activities and details for components that are required by the Configuration Manager client.
CcmEvalTask.log	Records the Configuration Manager client status evaluation activities that are initiated by the evaluation scheduled task.
CcmExec.log	Records activities of the client and the SMS Agent Host service. This log file also includes information about enabling and disabling wake-up proxy.
CcmMessaging.log	Records activities related to communications between the client and management points.
CCMNotificationAgent.log	Records activities related to client notification operations.
Ccmperf.log	Records activities related to the maintenance and capture of data related to client performance counters.
CcmRestart.log	Records client service restart activity.
CCMSDKProvider.log	Records activities for the client SDK interfaces.
CertificateMaintenance.log	Maintains certificates for Active Directory Domain Services and management points.
CIDownloader.log	Records details about configuration item definition downloads.
CITaskMgr.log	Records tasks that are initiated for each application and deployment type, such as content download or install or uninstall actions.
ClientAuth.log	Records the signing and authentication activity for the client.
ClientIDManagerStartup.log	Creates and maintains the client GUID and identifies tasks performed during client registration and assignment.
ClientLocation.log	Records tasks that are related to client site assignment.
CMHttpsReadiness.log	Records the results of running the Configuration Manager HTTPS Readiness Assessment Tool. This tool checks whether computers have a PKI client authentication certificate that can be used for Configuration Manager.
CmRcService.log	Records information for the remote control service.
ContentTransferManager.log	Schedules the Background Intelligent Transfer Service (BITS) or the Server Message Block (SMB) to download or to access packages.
DataTransferService.log	Records all BITS communication for policy or package access.
EndpointProtectionAgent	Records information about the installation of the Endpoint Protection client and the application of antimalware policy to that client.
execmgr.log	Records details about packages and task sequences that run on the client.
ExpressionSolver.log	Records details about enhanced detection methods that are used when verbose or debug logging is enabled.
ExternalEventAgent.log	Records the history of Endpoint Protection malware detection and events related to client status.
FileBITS.log	Records all SMB package access tasks.
FileSystemFile.log	Records the activity of the Windows Management Instrumentation (WMI) provider for software inventory and file collection.
FSPStateMessage.log	Records the activity for state messages that are sent to the fallback status point by the client.
InternetProxy.log	Records the network proxy configuration and usage activity for the client.
InventoryAgent.log	Records activities of hardware inventory, software inventory, and heartbeat discovery actions on the client.
LocationCache.log	Records the activity for location cache usage and maintenance for the client.
LocationServices.log	Records the client activity for locating management points, software update points, and distribution points.
MaintenanceCoordinator.log	Records the activity for general maintenance task activity for the client.
Mifprovider.log	Records the activity of the WMI provider for .MIF files.
mtrmgr.log	Monitors all software metering processes.
PolicyAgent.log	Records requests for policies made by using the Data Transfer service.
PolicyAgentProvider.log	Records policy changes.
PolicyEvaluator.log	Records details about the evaluation of policies on client computers, including policies from software updates.
PolicyPlatformClient.log	Records the process of remediation and compliance for all providers located in %Program Files%\Microsoft Policy Platform, except the file provider.
PolicySdk.log	Records activities for policy system SDK interfaces.
Pwrmgmt.log	Records information about enabling or disabling and configuring the wake-up proxy client settings.
PwrProvider.log	Records the activities of the power management provider (PWRInvProvider) hosted in the Windows Management Instrumentation (WMI) service. On all supported versions of Windows, the provider enumerates the current settings on computers during hardware inventory and applies power plan settings.
SCClient_<domain>@<username>_1.log	Records the activity in Software Center for the specified user on the client computer.
SCClient_<domain>@<username>_2.log	Records the historical activity in Software Center for the specified user on the client computer.
Scheduler.log	Records activities of scheduled tasks for all client operations.
SCNotify_<domain>@<username>_1.log	Records the activity for notifying users about software for the specified user.
SCNotify_<domain>@<username>_1-<date_time>.log	Records the historical information for notifying users about software for the specified user.
setuppolicyevaluator.log	Records configuration and inventory policy creation in WMI.
SleepAgent_<domain>@<@SYSTEM_0.log	Main log file for wake-up proxy.
smscliui.log	Records usage of the Configuration Manager client in Control Panel.
SrcUpdateMgr.log	Records activity for installed Windows Installer applications that are updated with current distribution point source locations.
StatusAgent.log	Records status messages that are created by the client components.
SWMTRReportGen.log	Generates a usage data report that is collected by the metering agent. This data is logged in Mtrmgr.log.
UserAffinity.log	Records details about user device affinity.
VirtualApp.log	Records information specific to the evaluation of App-V deployment types.
Wedmtrace.log	Records operations related to write filters on Windows Embedded clients.
wakeprxy-install.log	Records installation information when clients receive the client setting option to enable wake-up proxy.
wakeprxy-uninstall.log	Records information about uninstalling wake-up proxy when clients receive the client setting option to disable wake-up proxy, if wake-up proxy was previously enabled.

How SCCM 2012 R2 Client Communication Process Works

How SCCM 2012 R2 Client Communication Process Works

Once the agent is available on the network and the client is installed, the client goes through the following actions as part of the reporting process:

1. Client location services identify the site code and the MP it is supposed to connect to.
2. The client connects to the Management Point and downloads the policies.
3. Once the policies are downloaded it sends the heartbeat record to the server.
4.  Once the server receives this heartbeat record these are converted in to DDR and processed.  This will set the client flag to 1 which will make the client status display as Active in the console.
5.  On a regular basis the agent will send the heartbeat and if no heart beat or inventory shows up for a length of time then the client flag will be marked as 0 by the client flag maintenance task, setting the client status to Inactive.
6.  So only if this process is completed and it continues to happen will the client remain reporting to the server.  

Dell Client Management Pack Version 5.1 for SCOM 2012 R2

Dell Client Management Pack Version 5.1 for SCOM 2012 R2

The Client Management Pack enables the following operations to manage Dell client systems:

• Discover and monitor Dell Latitude, Dell Precision, and Dell OptipPlex computers running supported OMCI and client Windows operating systems.
• Group Dell Clients without instrumentation and client systems running without OMCI service under the Dell UnManaged Clients group.NOTE: Dell Vostro systems are displayed under the Dell UnManaged Clients group.
• Monitor the health status for client hardware components by polling at periodic intervals, and update the state of each component in the diagram view. A health status is a standardized description of the functional performance of a component, system, or service. For more information, see Tasks
• Perform client shutdown and reboot tasks.
• Launch remote desktop for Dell client systems.
• Generate reports on Dell Windows