Windows 10 1703 CB versions are showing as "other" on the Windows 10 Servicing Dashboard. Also not even represented in the Windows 10 timeline yet.11 votescompleted · Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
This should now be fixed.
When a user installs updates from Software Center only the updates that were selected to be installed are evaluated for their state post reboot. The whole deployment those updates were in, even if all updates in the deployment were selected, will not be queried for compliance post reboot. This causes a delay in the deployment compliance reporting as you need to wait for the deployment to be evaluated on schedule. In some instances this could be days. Running evaluation on the deployments those selected updates were in post reboot would solve the reporting delay.11 votes
It would be nice to use Co-Management not for all Win10 1709 devices but only for a dedicated set represented in ConfigMgr as a collection. It would be easier for big customers to start testing.8 votescompleted · Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
This can be done in 1710 by using the pilot functionality.
Boundary awareness for SUPs / WSUS
- Clients do not switch automatically to Secondary Site WSUS, if the Secondary Site was installed later as the Primary Site
- Travellers / VPN connection within the company network
- No automatic failback if Secondary Site server was done
see also MS Support Case 1151214134896606 votescompleted · Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
SUPS are now boundary aware in 1702. They do not aggressively switch immediately, due to network cost of changing scan source – but they will more intelligently switch. You can force the switch by using the right click actions in the console UI.
Extend the Phased Deployments feature to include Software Updates if it is not already planned.6 votes
Add an option to software updates deployments to force targeted clients to always download update content from Microsoft Update (regardless of availability on a DP).6 votes
This is fixed and available in #sccm 1810
SCUP support or integration in SCCM Current Branch with Windows Server 20166 votes
With today’s release of SCUP, this should be resolved.
Select a collection and trigger clients to run a software update deployment evaluation cycle. For those scenarios where you need clients to check for updates (now) prior to the default schedule (5 days) that you setup in client settings.3 votes
- Don't see your idea?