I haven’t set up the Servicing Options yet since it’s not reporting that any clients require the update at this time. I am seeing that the Servicing is detecting that I have a machine considered ready, I believe this info might be coming from the Software Inventory and not the check-in but I could be wrong.
From: [email protected] [mailto:[email protected]] On Behalf Of Adam Juelich Sent: Thursday, August 18, 2016 9:24 AM To: [email protected] Subject: Re: [mssms] Windows 10 1607 upgrade issue What have you set for your Servicing Options? You can choose between CB, CBB, etc. with a time delay based on days. That may be effecting it - not totally sure as I haven't played with this yet. On Thu, Aug 18, 2016 at 6:21 AM, Kamerman, Sol <[email protected]<mailto:[email protected]>> wrote: All: I have my test environment setup with the latest CB of SCCM, and I can see the 'Feature update to Windows 10 Enterprise, version 1607' update listed in the ‘All Windows 10 Updates’. However, SCCM is showing zero machines requiring the update hours after the deployment took effect. I've also manually updated the client, refreshed the ConfigMgr client machine policy and run update scans/deployment evaluations on a couple of Windows 10 Enterprise 1511 machines. No machines are detecting the update and displaying it in Software Center. I am at a point where I don’t know what else to look at. Do any of you have SCCM successfully upgrading machines to 1607 via the Windows 10 Servicing method? -Sol
