by Mark | Feb 17, 2017 | Features, Fixes, How To, SCCM, Security
SCCM update 1610 Hotfix KB4010155
If you are using Microsoft’s System Center Configuration Manager (SCCM), you may have experienced known bugs and issues. Fortunately, Microsoft released a hotfix on February 16, 2017, to fix them. In this article, we will discuss the hotfix, its features, and how it addresses some of SCCM’s known issues.
Fixing Known Bugs and Issues The following are some of the known bugs and issues that are fixed by this update rollup:
SCCM update 1610 Hotfix KB4010155
An update has been released for Microsoft’s System Centre Configuration Manager on the 16 of February 2017.
This update rollup for SCCM is to fix the following known bugs and issues;
| Component |
Bug/Issue |
Client
|
Internet-only clients can’t connect to management points or distribution points when proxy auto-configuration is used, and they change networks without restarting. |
Client
|
The Content Transfer Manager component of the Configuration Manager client repeatedly checks for content after the client roams to a location without available distribution points. |
Microsoft Intune and Mobile Device Management
|
Communication between a Configuration Manager site server and the Microsoft Intune service may fail randomly. |
Microsoft Intune and Mobile Device Management
|
After integrating Lookout mobile threat protection with Microsoft Intune, Windows devices are incorrectly displayed in the Device Threat Protection Compliance Status (iOS/Android) charts in the Administrator Console. |
Site systems
|
The Microsoft.Management.Services.ClientManagementService.Host.exe process doesn’t start if the Process ID (PID) assigned by Windows is greater than 32,767. |
Site systems
|
After you upgrade to Configuration Manager current branch, version 1610, the cloud management gateway connection point doesn’t start. |
Site systems
|
When you configure the SQL Server Service Broker for a database replica server, execution of the sp_BgbConfigSSBForRemoteService stored procedure fails. |
Site systems
|
Installing the Service Connection Point on a computer that’s not a site server triggers CPU usage of 100%. |
Operating system deployment
|
Deployment of the Windows 10 Anniversary Update (1607) to Windows 10 clients triggers a “0x80091007 (Hash value is not correct)” error. |
Software distribution and content management
|
The transfer of package contents between sites over slow network connections fails intermittently. |
Software distribution and content management
|
Every time content is sent to a distribution point, site control data is updated unnecessarily. |
Administrator console
|
After you add a new boundary to the Default-Site-Boundary-Group, that group is no longer listed on the Boundary Groups tab of the boundary properties. |
Administrator console
|
Individual threat details are not displayed as expected on the Device Threat Protection Details tab of the Devices screen in the Administrator console. |
Administrator console
|
The UpdatesDeployment.log file contains errors that resemble the following: Failed to get SDM CI for update (Site_{guid} SUM_{guid}) from type store, error = 0x80070002 Failed to GetSupersededUpdatesFromDigest for the update |
Administrator console
|
After you upgrade to Configuration Manager current branch, version 1610, resolving conflicting records fails for non-mobile device clients. |
Software updates
|
When an Alternate Content Provider encounters an error or retry condition while downloading an Office 365 job, the client does not fall back to the default download system as expected. |
Software updates
|
After you start installation of Office updates from Software Center, users do not receive a notification message to exit all open Office 365 applications. |
Software updates
|
The Allow clients to use Microsoft Update as a fallback source option doesn’t work as expected when you use it in a software update deployment or automatic deployment rule (ADR). |
How to install KB4010155 update rollup for SCCM 1610
Now that you have learnt about what are the fixes for this update rollup, now lets look at how to install this next. It is quite a simple process and should take you no longer than 30 minutes.
Step 1 – Open your SCCM console.
Open your SCCM console and navigate to Administration, then expand Cloud Services and finally highlight Updates and Servicing. Your SCCM should have downloaded the update and have it ready to deploy to your SCCM infrastructure.
Step 2 – Run Prerequisite Check
Highlight the Configuration Manager 1610 Hotfix (KB4010155), then right click and choose Run Prerequisite Check.
The prerequisite check should take no longer than five minutes as sn the background, SCCM will run and verify that you are able to install this hotfix.
Refresh your console until you see that the Prerequisite check passed notification.
Step 3 – Install Update Pack (KB4010155)
Hopefully the KB4010155 update pack is compatible with your SCCM environment and you are now ready for the installation. Again, highlight the update pack, right click and choose Install Update Pack.
Now the Configuration Manager Updates Wizard starts up. Click Next to proceed.
On the Client Updates Options window, you have the option to Upgrade without Validating or to Validate in pre-production collection. In this example, Im choosing to go ahead and update without validation. Click Next when ready to proceed.
The next window is the License Agreement window. You have to check the checkbox to accept the license terms and privacy statement before you can continue to install. Once you have done so, click Next to continue.
The Summary window details your installation options. Confirm these are correct before clicking on Next and continuing and then the installation will not start.
Now KB4010155 will install and update your SCCM environment. Once complete you will be presented with the following screen and KB4010155 will install in the background. Keep refreshing your SCCM console to confirm when it has udpated. You can additionally view the installation progress by looking at the CMUPDATE.LOG.
Conclusion
In summary, Microsoft released an update for System Center Configuration Manager (SCCM) on February 16, 2017, to address various known bugs and issues. These issues include problems with client connectivity, increased CPU activity, communication failures between Configuration Manager and Microsoft Intune, and errors during the deployment of Windows 10 Anniversary Update (1607) to Windows 10 clients. Other issues addressed by the update include software distribution and content management, problems with the Administrator console, and software updates. The update aims to resolve these issues to improve the performance and functionality of SCCM.
by Mark | Dec 15, 2016 | Fixes, How To, Patch Releases, SCCM
How to update to KB3209501 for Microsoft SCCM 1610
If you’re experiencing issues with Microsoft SCCM 1610, the recently released update KB3209501 might just be the fix you need. This update resolves various problems related to Configuration Manager version 1606 to version 1610 upgrade, Software Center, BITS for Windows Express Update Files, Task Sequences, and more. In this article, we’ll guide you through the process of updating SCCM 1610 to KB3209501, step-by-step.
KB3209501 FAQs
| Question |
Answer |
What is KB3209501?
|
KB3209501 is an update for Microsoft SCCM 1610 that was released in December 2016. It fixes various issues with SCCM 1610. |
What issues does KB3209501 fix?
|
KB3209501 fixes issues such as the SMS Agent Host process using 100% of available CPU time, Task sequence deployments failing, and more. |
How do I update to KB3209501 for Microsoft SCCM 1610?
|
To update to KB3209501, open your SCCM console, navigate to Administration > Cloud Services > Update and Servicing, and follow the steps. |
Should I install updates in preproduction prior to production?
|
It is always good practice to install any updates in preproduction prior to production. |
Is KB3209501 installation time-consuming?
|
Yes, KB3209501 installation may take some time to finish, so be prepared to be patient. |
Update to KB3209501
So now that you know what KB3209501 fixes now just follow the below tasks to update your SCCM environment.
Open your SCCM console and navigate to Administration, Cloud Services and highlight Update and Servicing
Next, highlight update KB3209501, then right click and choose Run Prerequisite Check.
Give the prerequisite checks sometime to complete.
Keep refreshing the console to see when it has completed.
Once the KB3209501 prerequisite checks have passed, again highlight the update and then right click and choose Install Update Pack.
You are now presented with the Configuration Manager Updates Wizard. Select whether you want to ignore any prerequisite check warnings if you received them or not and then click Next.
On the Client Update Options tab, you can select to update without validating against your preproduction environment before updating your production environment. As this is one of our many labs, I have chosen to go ahead without validating. While this is a lab, not everyone can has his luxury, so remember It is always good practice to install any updates in preproduction prior to production.
On the License Tab page, confirm you accept the license terms and privacy statement and then click Next.
Confirm what is shown is on the Summary Tab is correct and then click Next.
The installation will no be performed in the background, so on the Completion Tab click Close.
As you can see, KB3209501 is installing in the background. For my lab, it did take some time to finish so prepare to be patient.
Updating SCCM 1610 to KB3209501 is a straightforward process that can help you resolve a range of issues and improve the overall performance of your Configuration Manager environment. By following the steps outlined above, you can ensure a smooth and successful update. Don’t forget to install updates in pre-production first to avoid potential conflicts
by Mark | Jun 21, 2016 | How To, SCCM
SCCM Update Deployment Issues?
Troubleshooting Tips and Logs to Resolve Common Problems
Are you experiencing issues with deploying updates within SCCM? Don’t worry; you’re not alone. Many administrators struggle with troubleshooting and identifying the root cause of update deployment problems. However, with the right knowledge and tools, you can quickly resolve these issues and ensure your updates are deployed successfully. In this article, we’ll discuss some troubleshooting tips and the logs you can use to identify and resolve common SCCM update deployment issues.
Identifying the Appropriate Log to Troubleshoot SCCM Update Deployment Issues
One of the most challenging aspects of troubleshooting SCCM update deployment issues is identifying which log to look at. Fortunately, SCCM has many logs available to help you determine the root cause of any issues. Here are some of the logs you can review to identify the issue:
Server Side Software Update Logs:
- SUPsetup.log – Installation of SUP Site Role.
- WCM.log, WSUSCtrl.log – Configuration of WSUS Server/SUP.
- WSyncMgr.log – SMS/WSUS Updates Synchronization Issues.
- Objreplmgr.log – Policy Issues for Update Assignments/CI Version Info policies.
- RuleEngine.log – Auto Deployment Rules.
-
Client Side Software Update Logs:
- UpdatesDeployment.log – Deployments, SDK, UX.
- UpdatesHandler.log – Updates, Download.
- ScanAgent.log – Online/Offline scans, WSUS location requests.
- WUAHandler.log – Update status (missing/installed – verbose logging), WU interaction.
- UpdatesStore.log – Update status (missing/installed).
- indirWindowsUpdate.log – Scanning/Installation of updates.
Hopefully these logs will help you troubleshoot Update Deployment from within SCCM. Click these links to see how you can create a SCCM Automatic Deployment Rule for your Microsoft Updates and SCEP Definition Updates to help you automate your update and definitions deployments.
Troubleshooting SCCM Update Deployment Issues
Now that you know which logs to look at, it’s time to start troubleshooting. Here are some common SCCM update deployment issues you may encounter, along with their possible solutions:
Issue 1: Updates are not downloading or installing on client devices.
Solution: Check the UpdatesDeployment.log and UpdatesHandler.log for errors. Make sure the client devices have access to the update source location, and the content is distributed to the distribution point.
Issue 2: The SCCM client is not reporting update compliance status.
Solution: Check the UpdatesStore.log, UpdatesDeployment.log, and WUAHandler.log for errors. Verify that the SCCM client has the correct permissions to read the WSUS catalogs and update metadata.
Issue 3: Automatic Deployment Rules (ADR) are not working correctly.
Solution: Check the RuleEngine.log and WCM.log for errors. Verify that the ADR criteria and schedules are configured correctly and that the update metadata is up to date.
Automating SCCM Update and Definitions Deployments
Manually deploying updates and definitions can be a time-consuming task, especially if you have many devices to manage. SCCM offers Automatic Deployment Rules (ADR), which allow you to automate the process of deploying updates and definition updates. By creating an ADR, you can define criteria for the types of updates to deploy, when to deploy them, and to which collections to deploy them. Here are some links to help you get started with creating SCCM Automatic Deployment Rules for your Microsoft Updates and SCEP Definition Updates:
In conclusion, SCCM update deployment issues can be frustrating, but with the right knowledge and tools, you can quickly identify and resolve them. By reviewing the appropriate logs and following the troubleshooting tips we’ve outlined, you can ensure that your updates are deployed successfully. Additionally, by automating the deployment
by Mark | Feb 27, 2016 | How To, SCCM
SCCM Log files for Software Updates
System Center Configuration Manager (SCCM) is a powerful tool used by administrators for managing large-scale deployments. SCCM software updates provide a simple way to keep client systems up to date with the latest security and feature updates. SCCM log files contain valuable information about the software updates deployment process and can help administrators troubleshoot issues. In this article, we will discuss the important SCCM log files for software updates and how to analyze them to troubleshoot issues.
SCCM Log files overview
What are SCCM Log files?
SCCM log files are text files that contain information about the various processes and actions taken by SCCM. These log files are created by SCCM components during their operation and provide valuable insights into the workings of SCCM.
Why are SCCM Log files important?
SCCM log files are crucial for troubleshooting issues that may arise during software updates deployment. They contain detailed information about the actions taken by SCCM components and can help administrators identify the root cause of an issue.
SCCM Log files for Software Updates
The following are the important SCCM log files for software updates:
| Log Name |
Description |
Server Side or Client Side |
CcmExec.log
|
Records actions taken by the SCCM client on the local machine, such as software deployments, inventory scans, and software update installations. |
Client Side |
UpdatesDeployment.log
|
Records details of the deployment process for software updates, including whether they were successfully installed or failed. |
Client Side |
WUAHandler.log
|
Records the communication between the SCCM client and Windows Update Agent (WUA), which is responsible for checking for and installing updates. |
Client Side |
PatchDownloader.log
|
Records the download process for software updates, including the location from which updates were downloaded and whether they were successfully downloaded. |
Client Side |
SiteComponentManager.log
|
Records the status of SCCM components and their installation or uninstallation. This log is useful for troubleshooting SCCM server component issues. |
Server Side |
SMS_AZUREAD_CONNECTOR.log
|
Records actions taken by the SCCM Azure Active Directory (AAD) Connector, which is responsible for syncing user and device data between SCCM and AAD. This log is useful for troubleshooting AAD sync issues. |
Server Side |
CAS.log
|
Records actions taken by the SCCM Central Administration Site (CAS), which is responsible for managing multiple primary sites. This log is useful for troubleshooting issues that affect multiple primary sites. |
Server Side |
MP_Location.log
|
Records actions taken by the SCCM Management Point (MP), which is responsible for managing client communications and data. This log is useful for troubleshooting MP issues. |
Server Side |
Wsyncmgr.log
|
Records the synchronization process for software updates between the SCCM server and the WSUS server. This log is useful for troubleshooting update synchronization issues. |
Server Side |
DataTransferService.log
|
Records the transfer of data between the SCCM server and client machines, including software updates and packages. This log is useful for troubleshooting issues related to data transfer. |
Client Side |
UpdatesHandler.log
|
Records actions taken by the SCCM software update handler, which is responsible for coordinating the download and installation of software updates on the client machine. This log is useful for troubleshooting update installation issues. |
Client Side |
UpdatesStore.log
|
Records the location and status of software updates stored on the client machine. This log is useful for troubleshooting issues related to software update storage. |
Client Side |
UpdatesAssignments.log
|
Records details of software update assignments, including which updates are assigned to which client machines. This log is useful for troubleshooting update assignment issues. |
Server Side |
ContentTransferManager.log
|
Records the transfer of content between the SCCM server and client machines, including software updates and packages. This log is useful for troubleshooting issues related to content transfer. |
Client Side |
RebootCoordinator.log
|
Records actions taken by the SCCM reboot coordinator, which is responsible for coordinating system reboots after software update installations. This log is useful for troubleshooting reboot-related issues. |
Client Side |
Supersedence.log
|
Records details of software update supersedence, including which updates supersede which other updates. This log is useful for troubleshooting update supersedence issues. |
Server Side |
PolicyEvaluator.log
|
Records actions taken by the SCCM policy evaluator, which is responsible for enforcing client policies and settings. This log is useful for troubleshooting policy-related issues. |
Client Side |
Analyzing SCCM Log files
Analyzing SCCM log files is crucial for troubleshooting issues related to software updates deployment. Here are the steps for analyzing SCCM log files:
- Identify the relevant log file(s) for the issue at hand.
- Open the log file using a text editor such as Notepad++.
- Search for the relevant error or warning messages in the log file.
- Analyze the messages to identify the root cause of the issue.
- Take the necessary actions to resolve the issue based on the root cause identified.
Common SCCM Update issues and their resolutions
Here are some common issues related to software updates deployment in SCCM and their resolutions:
- Software updates are not showing up in the SCCM console: Check the synchronization status of the software update point and ensure that the latest software updates are synchronized.
- Software updates are failing to install on client systems: Check the relevant log files to identify the root cause of the issue and take the necessary actions to resolve it.
- Software updates are getting stuck in the downloading phase: Check the ContentTransferManager.log and PatchDownloader.log files to identify the root cause of the issue and take the necessary actions to resolve it.
SCCM Logs FAQs
What is SCCM software updates deployment?
SCCM software updates deployment is a process of deploying the latest software updates to client systems in a managed environment.
What are SCCM log files?
SCCM log files are text files that contain information about the various processes and actions taken by SCCM components.
Why are SCCM log files important?
SCCM log files are important for troubleshooting issues related to software updates deployment in SCCM.
How do I analyze SCCM log files?
To analyze SCCM log files, you need to identify the relevant log file(s), open them using a text editor, search for the relevant error or warning messages, and analyze the messages to identify the root cause of the issue.
What are some best practices for analyzing SCCM log files?
Some best practices for analyzing SCCM log files include using a log file viewer, taking regular backups of the log files, and understanding the structure and messages contained in the log files.
How can I automate a Snapshot prior to deploying patches to my virtual servers?
Use SnaPatch to automate the whole update process to your virtual machines.
Where are the SCCM Log files located?
The SCCM (System Center Configuration Manager) log files are located in different directories on the SCCM server and client computers. On the SCCM server, the log files are typically located in the “Logs” folder within the SCCM installation directory. The default installation directory is “C:Program FilesMicrosoft Configuration ManagerLogs”.
On the client computers, the log files are located in the “CCMLogs” folder within the Windows directory. The default path is “C:WindowsCCMLogs”. The log files are named according to the component or feature they relate to. For example, the “ClientLocation.log” file logs information about the client’s location, while the “SoftwareCenter.log” file logs information about the Software Center feature.
SCCM Logs – Conclusion
SCCM log files are crucial for troubleshooting issues related to software updates deployment. In this article, we discussed the important SCCM log files for software updates and how to analyze them to troubleshoot issues. We also discussed some common issues related to software updates deployment in SCCM and their resolutions. By following the best practices for SCCM log file analysis, administrators can ensure a smooth and successful software updates deployment process.
by Mark | Feb 27, 2016 | How To, SCCM
SCCM Clients failing to install windows updates
Microsoft System Center Configuration Manager (SCCM) is a popular tool used for managing and deploying updates to Windows clients in an organization. However, sometimes SCCM clients can encounter issues while installing Windows updates, resulting in failed installations. This can be a frustrating experience for IT professionals who are responsible for maintaining a secure and up-to-date environment. In this article, we will explore common causes of SCCM clients failing to install Windows updates and provide solutions to troubleshoot and resolve these issues.
Common Causes of SCCM Clients Failing to Install Windows Updates:
There can be various reasons why SCCM clients may fail to install Windows updates. Here are some common causes:
- Inadequate Disk Space: If the SCCM client has insufficient disk space, it may fail to install updates.
- Connectivity Issues: The SCCM client must have a stable and reliable connection to the network and the SCCM server to download and install updates. Any connectivity issues can cause the installation to fail.
- Corrupted Update Files: Sometimes, the update files downloaded by the SCCM client can become corrupted, leading to a failed installation.
- Incorrect Permissions: If the user account used to run the SCCM client does not have sufficient permissions to install updates, the installation may fail.
- Conflicting Software: Sometimes, other software installed on the client machine can interfere with the installation of Windows updates.
Troubleshooting SCCM Clients Failing to Install Windows Updates:
Now that we have identified some common causes of SCCM clients failing to install Windows updates, let’s look at some troubleshooting steps to resolve these issues.
- Check Disk Space: Verify that the SCCM client has sufficient disk space to install updates. Clear any unwanted files or increase the disk space if needed.
- Check Connectivity: Ensure that the SCCM client has a stable network connection to the SCCM server. Check for any firewall or network configuration issues that may be affecting the connection.
- Clear the Software Distribution Folder: Sometimes, clearing the contents of the Software Distribution folder on the SCCM client can help resolve update installation issues. To do this, stop the Windows Update service, delete the contents of the C:WindowsSoftwareDistribution folder, and then restart the Windows Update service.
- Verify Permissions: Ensure that the user account used to run the SCCM client has sufficient permissions to install updates. The user account should be a member of the local Administrators group on the client machine.
- Uninstall Conflicting Software: If other software is interfering with the installation of Windows updates, uninstall the software and attempt the update installation again.
The most common cause of Windows Update Failures
If you find no issues while looking at the Client and SCCM server Windows Updates logs and you determine that it isnt something else (as above), it maybe worth checking the following on the clients with the issues.
If you have issues with SCCM client machines during an update deployment, an issue that could be causing the problem is a proxy value has been set within the registry.
Open Regedit and navigate to the following key location
HKEY_LOCAL_MACHINE – SOFTWARE – Microsoft – Windows – CurrentVersion – Internet Settings – Connections – WinHttpSettings
Delete the WinHttpSettings value
Close Regedit and reboot the server.
FAQs
How can I tell if an SCCM client failed to install updates?
You can check the SCCM console to view the update deployment status. If the update installation has failed, you will see an error message with details of the failure.
What should I do if an SCCM client repeatedly fails to install updates?
Try the troubleshooting steps mentioned in this article to resolve the issue. If the issue persists, you may need to investigate further and seek assistance from Microsoft support.
What should I do if an SCCM client reports a download failure for an update?
First, check the client’s internet connectivity and ensure that there is no firewall or proxy server blocking the download. If the issue persists, try clearing the Software Distribution folder or restarting the Windows Update service on the client machine.
How can I troubleshoot an SCCM client that is stuck in “Downloading” or “Installing” updates?
Check the client’s connectivity to the SCCM server and ensure that there is enough disk space on the client machine. You can also try clearing the Software Distribution folder or restarting the Windows Update service on the client machine.
What are some common errors that occur when SCCM clients fail to install updates?
Some common errors include “Failed to install updates,” “Error 0x80070003,” and “Error 0x8007000e.” The specific error message can provide clues to the underlying issue.
How can I troubleshoot an SCCM client that is reporting a Windows Update error?
Check the client’s internet connectivity, ensure that there is enough disk space on the client machine, and verify that the user account used to run the SCCM client has sufficient permissions to install updates. You can also try restarting the Windows Update service or clearing the Software Distribution folder on the client machine.
How can I prevent SCCM clients from failing to install Windows updates in the future?
Ensure that the client machines are regularly maintained and have enough disk space available. Keep the SCCM server up-to-date with the latest updates and patches. Additionally, consider implementing a regular update schedule and enforcing compliance policies to ensure that updates are installed on a timely basis.
Conclusion:
SCCM clients failing to install Windows updates can be a frustrating issue to deal with, but with the right troubleshooting steps, it can be resolved. In this article, we have outlined some common causes of update installation failures and provided solutions to troubleshoot and resolve these issues. By following these steps, you can ensure that your SCCM clients stay up-to-date and secure.
