Report SCCM Update Error to Microsoft – ConfigMgr TP 2005

ConfigMgr TP 2005 introduced a new feature where you can report SCCM update error to Microsoft from the console. Let’s explore this new feature and see what it actually does.

Every Configuration Manager technical preview release comes with new features and improvements. However we ignore the new features because after all it’s a tech preview release. We aren’t bothered until it gets baked into current branch release.

Most of you might know that new features that you see in current branch release were actually part of some technical preview release. One such feature is the ability to report SCCM setup and update errors to Microsoft.

Let’s be honest, we all have had errors while installing the new updates in the Configuration Manager. For some of us the SCCM update didn’t download. For others either the prerequisite check failed or update got stuck while installing.

I have posted the solutions to most of these issues in different posts. However we now have a tool that we can use to report setup and upgrade errors to Microsoft. When the ConfigMgr setup or update process fails to complete successfully, you can now report the error directly to Microsoft.

Note – The option to Report update error to Microsoft is currently available in ConfigMgr technical preview 2005 and above. I hope to see this feature in the next current branch release.

Report SCCM Update Error to Microsoft

To report SCCM update error to Microsoft in console.

• In the SCCM console, navigate to Administration\Overview\Updates and Servicing.
• Right the update and click Report Update error to Microsoft.
• Next you will see Submit problem report window where you attach log files and send it to Microsoft.

On the Submit Problem report window, you will find lot of options. Let me cover them in detail.

1. You can provide your contact address and let Microsoft contact your regarding the feedback.
2. Describe the issue about the SCCM update and problems that you faced related to update install.
3. Include or attach additional log files. These are recommended log files and by default Microsoft don’t collect these without your permission.
4. A log file viewer tool that opens the listed log files.
5. Clear All option – Remove the attachments (in case you uploaded them by mistake).
6. Recommended log files that you can attach that would help Microsoft support to know more about the issue.

Logs Collected by Microsoft Feedback Tool

By default following log files are collected by Feedback tool and sent to Microsoft.

SMS_CM_EasySetupPackage.log
SMS_CM_UpdatePackagesHistory
SMS_CM_UpdatePackageSiteStatus
SMS_CM_UpdatePackDetailedMonitoring
SMS_CM_UpdatePackDetailedPrereqMonitoring
SMS_CM_UpdatePackDetailedSiteStatus
SMS_CM_UpdatePackDownloadMonitoring
SMS_CM_UpdatePackTopLevelMonitoring

In addition to the above log files, Microsoft recommends attaching some other log files which we commonly use for troubleshooting update related issues. These log files include.

• ConfigMgrPreReq.log
• ConfigMgrSetup.log
• CMUpdate.log
• hman.log

When you submit the feedback, you’ll be given a transaction ID for the feedback. A status message is also generated with this information.

• Message ID 53900 is a successful submission.
• Message ID 53901 is a failed submission.

Before you close the feedback tool, you can also save a copy of feedback and attachments.

Feedback Details

Here’s the summary of what happens when you submit feedback.

• Preparing feedback.
• Sending attachments to service. This may take a while if sending a large amount of data.
• Preparing attachments. This may take a while if sending a large amount of data.
• Sending attachment details to service.
• Sending upload request to service.
• Uploading data to service. This may take a while if sending a large amount of data.
• Successfully uploaded data to service.
• Verifying data received by the service.
• Finished sending attachments to service.
• Sending feedback to service.
• Finished sending feedback to service.
• Finished.