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] On
Behalf Of Ted Koopman
Sent: 18 April 2017 04:22 AM
To: 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
