Gotcha, issue still stands as to why my Win10 box is not checking as required under the ‘All Windows 10 Updates’… It’s been over 24 hours and still nothing. It does check-in for software updates which is odd.
Sol From: [email protected] [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Thursday, August 18, 2016 11:50 AM To: [email protected] Subject: RE: [External] Re: [mssms] Windows 10 1607 upgrade issue This changed from ConfigMgr CB 1511 to 1602 I believe which is why you are not seeing them. Also, the downloading of all languages was also corrected in 1602 I believe. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Kamerman, Sol Sent: Thursday, August 18, 2016 9:10 AM To: [email protected]<mailto:[email protected]> Subject: RE: [External] Re: [mssms] Windows 10 1607 upgrade issue Interesting, at first this what I was planning on doing, but I am not seeing this in the All Software Updates. I have selected the appropriate Product Classifications and Products to be downloaded and it hasn’t showed up. I applied all patches related to the WSUS issue as well. Are there any other reasons why I’m not seeing in All Software Updates? Sol From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Linkey, Mike Sent: Thursday, August 18, 2016 10:02 AM To: [email protected]<mailto:[email protected]> Subject: RE: [External] Re: [mssms] Windows 10 1607 upgrade issue I deploy them just like a regular software update. That way I don’t have all of the extra languages and such downloaded. Working so far on the machine we have upgraded. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Adam Juelich Sent: Thursday, August 18, 2016 8:51 AM To: [email protected]<mailto:[email protected]> Subject: [External] Re: [mssms] Windows 10 1607 upgrade issue I would think you'd need to set your Servicing Options for it to detect and say that an update applies/needed to a specific machine....... I may be wrong... On Thu, Aug 18, 2016 at 8:34 AM, Kamerman, Sol <[email protected]<mailto:[email protected]>> wrote: 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]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Adam Juelich Sent: Thursday, August 18, 2016 9:24 AM To: [email protected]<mailto:[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 CONFIDENTIALITY NOTICE: The e-mail transmission (and/or the documents accompanying such) may contain confidential information. Such information is intended only for the use of the individual or entity named above. If you are not the named or intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of such information is strictly prohibited. If you have received this email in error, please notify the sender and then delete the email. Thank you for your cooperation.
