Andrew Buehler
New Member
- Messages
- 4
- Reaction score
- 0
- Points
- 1
My organization is working to bring up an instance of Configuration Manager version 2002.
I'm trying to create a Windows 10 servicing plan for the first time. I'm following the directions laid out at https://www.prajwaldesai.com/sccm-windows-10-servicing-plans/ (which I understand to be still basically up to date, given that they're linked to from - and substantially comparable to those at - https://www.prajwaldesai.com/configmgr-windows-10-20h2-servicing-plan-sccm-memcm/ which is much more current).
I initially did not have updates visible even in the "All Windows updates" list, but have resolved that. That list now includes many different updates, including the one I want to deploy; I have even been able to pre-download that update and create a package from it.
The problem I'm encountering is that on the "Select the property filters and search criteria" page, no matter what I enter as the criteria, the Preview button shows 0 results found. I infer that this would also result in no updates being selected for deployment as part of the servicing plan.
A bit of searching led me to https://social.technet.microsoft.co...uery-preview-issue?forum=ConfigMgrCompliance; that discussion (and apparently a few others, one of which seems to be linked to from there) indicates that this behavior can result if the "Defer Updates" Group Policy is set on the machines which are in the collection which is selected as the target of the servicing plan. We have to date normally enabled that policy on our endpoints, and set it to the maximum deferral period of 365 days, so that could potentially explain the observed behavior.
However, I have disabled this policy on one computer in that targeted collection (and verified that it no longer shows as active, using 'gpresult /h /scope:computer'), and the behavior is still occurring.
I also do not know how to trigger Configuration Manager to re-check whatever it is that is used to determine whether an update is considered applicable for purposes of a servicing plan. I have run software-updates scan cycles, software-updates deployment evaluation cycles, software inventory cycles, machine policy retrieval & evaluation cycles, and even discovery data collection cycles, with no effect. I also waited overnight, and rebooted the machine, in hopes of a re-evaluation happening automatically; again there has been no change. As such, I do not know whether the disabling of the policy has taken effect in terms of Configuration Manager's applicability detection.
Any advice or suggestions?
I'm trying to create a Windows 10 servicing plan for the first time. I'm following the directions laid out at https://www.prajwaldesai.com/sccm-windows-10-servicing-plans/ (which I understand to be still basically up to date, given that they're linked to from - and substantially comparable to those at - https://www.prajwaldesai.com/configmgr-windows-10-20h2-servicing-plan-sccm-memcm/ which is much more current).
I initially did not have updates visible even in the "All Windows updates" list, but have resolved that. That list now includes many different updates, including the one I want to deploy; I have even been able to pre-download that update and create a package from it.
The problem I'm encountering is that on the "Select the property filters and search criteria" page, no matter what I enter as the criteria, the Preview button shows 0 results found. I infer that this would also result in no updates being selected for deployment as part of the servicing plan.
A bit of searching led me to https://social.technet.microsoft.co...uery-preview-issue?forum=ConfigMgrCompliance; that discussion (and apparently a few others, one of which seems to be linked to from there) indicates that this behavior can result if the "Defer Updates" Group Policy is set on the machines which are in the collection which is selected as the target of the servicing plan. We have to date normally enabled that policy on our endpoints, and set it to the maximum deferral period of 365 days, so that could potentially explain the observed behavior.
However, I have disabled this policy on one computer in that targeted collection (and verified that it no longer shows as active, using 'gpresult /h /scope:computer'), and the behavior is still occurring.
I also do not know how to trigger Configuration Manager to re-check whatever it is that is used to determine whether an update is considered applicable for purposes of a servicing plan. I have run software-updates scan cycles, software-updates deployment evaluation cycles, software inventory cycles, machine policy retrieval & evaluation cycles, and even discovery data collection cycles, with no effect. I also waited overnight, and rebooted the machine, in hopes of a re-evaluation happening automatically; again there has been no change. As such, I do not know whether the disabling of the policy has taken effect in terms of Configuration Manager's applicability detection.
Any advice or suggestions?
