5.00.8412.1000 is greater than 5.00.8355.1307 I would try to install it manually and see what happens on the upgrade readiness test.
When we had Symantec they didn't show you the minor version number so you never knew if the AV client was newer or older. Thanks, Jeff Jerousek<mailto:jeff.jerou...@lrs.com> From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Daniel Ratliff Sent: Tuesday, April 18, 2017 7:34 AM To: mssms@lists.myitforum.com Subject: [mssms] RE: Windows 10 Anniversary Update deployment error There are some major improvements to Windows 10 Upgrades in SCCM 1610. Definitely make sure you are there, or preferably SCCM 1702, since it is CB. Daniel Ratliff From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Kelkar, Bhushan Sent: Tuesday, April 18, 2017 6:21 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] RE: Windows 10 Anniversary Update deployment error Hi Ted; We are on configmgr 1606 with agent version 5.00.8412.1000. I think to get to 5.00.8355.1307 or higher we would need to upgrade configmgr to 1610. Is it really necessary ? because I am sure that to upgrade Windows 10 to anniversary update (14393). Minimum requirement was 1606. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Ted Koopman Sent: 18 April 2017 04:22 AM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] RE: Windows 10 Anniversary Update deployment error Be sure to have the client agent of 5.00.8355.1307 or higher. -Ted From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Kelkar, Bhushan Sent: Monday, April 17, 2017 3:16 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] Windows 10 Anniversary Update deployment error Hi; We had started rollout of Windows 10 Anniversary update in phases. In first batch of approx. 850 systems we hardly had 40 systems which failed to deploy the update due to various reasons. But in the second batch we had almost 200 system showing failure code 0x80240fff. I tried to research on this generic failure error and most of the sites/blogs suggest issues with BITS. Has anyone faced this kind of issue and if yes, found any solution to this? We are about to start rolling out to batch number 3 very soon and I'd like to fix this issue before that. P.S. all SUP/MP and DPs are healthy and no issues found on BITS on all of the boxes. Regards Bhushan The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
