Microsoft Configuration Manager

What Has Changed From Configuration Manager 2012

2 September 2026Doc update+1 / −1 lines

In brief

The article now revises its explanation of how Configuration Manager distinguishes Windows Update client policies from WSUS, including the UseWUServer attribute.

What Intune admins need to know

Administrators can use the updated wording when planning or troubleshooting software update management.

This summary was assembled from the tracked documentation change. Verify important details in the full Microsoft Learn article.

Documentation change

View full page diff

View on Microsoft Learn

The comparison below shows only the changed extract. Use the full-page view for complete context.

Be aware of the following changes to software updates:

Configuration Manager can now detect the difference between software update management methods for computers. Specifically, it can differentiate between a Windows computer that connects to Windows Update client policies, and a computer connected to WSUS. The UseWUServer attribute is new, and specifies whether the computer is managed with Windows Update client policies. You can use this setting in a collection to remove these computers from software update management. For more information, see ~~Integration with Windows Update client policies~~Integration with Windows Update client policies.
You can now schedule and run the WSUS clean-up task from the Configuration Manager console. In Software Update Point Component properties, when you select to run the WSUS clean-up task, it runs at the next software updates synchronization. The expired software updates are set to a status of declined on the WSUS server, and the Windows Update Agent on computers no longer scans these software updates. For more information, see Schedule and run the WSUS clean up task.

@@ -111,7 +111,7 @@ Be aware of the following changes to application management:  Be aware of the following changes to software updates: -- Configuration Manager can now detect the difference between software update management methods for computers. Specifically, it can differentiate between a Windows computer that connects to Windows Update client policies, and a computer connected to WSUS. The **UseWUServer** attribute is new, and specifies whether the computer is managed with Windows Update client policies. You can use this setting in a collection to remove these computers from software update management. For more information, see [Integration with Windows Update client policies](../../../sum/deploy-use/integrate-windows-update-for-business-windows-10.md).+- Configuration Manager can now detect the difference between software update management methods for computers. Specifically, it can differentiate between a Windows computer that connects to Windows Update client policies, and a computer connected to WSUS. The **UseWUServer** attribute is new, and specifies whether the computer is managed with Windows Update client policies. You can use this setting in a collection to remove these computers from software update management. For more information, see [Integration with Windows Update client policies](../../../sum/deploy-use/integrate-windows-update-client-policies.md).  - You can now schedule and run the WSUS clean-up task from the Configuration Manager console. In **Software Update Point Component** properties, when you select to run the WSUS clean-up task, it runs at the next software updates synchronization. The expired software updates are set to a status of declined on the WSUS server, and the Windows Update Agent on computers no longer scans these software updates. For more information, see [Schedule and run the WSUS clean up task](../../../sum/deploy-use/software-updates-maintenance.md).