Hello,
Deploying the 1909 FU to my 1709 devices. I have already gone through extensive testing and piloting and this is my production rollout. Phase 1 is a very small group to get an idea of how many calls we may get to our SD - so only 1,000 devices. This update is "Available" for a week before the required deadline hits next week. I was surprised when I looked at my monitoring node and saw 33 devices as "compliant" - as they are not.
I have found servicing to be less "automated" than I originally expected. For this employer I decided to take a more modern approach and ditch my IPU TS. What I found is that I really have to babysit the FU's as they come in -- a new FU completely kills my existing deployment. Though the Article ID numbers are the same, they are a different update and the previous deployment completely quits working and I have to deploy the new FU. Not the end of the world, but it did cause some confusion for me. I had to download and deploy the latest 1909 FU for this rollout so I think it may be related but I have found nothing in the logs to indicate this.
Site version: 2006 (no hotfixes)
Client version: 5.00.9012.1020 across the board
Latest 1909 FU
All clients patched with the latest CU and SSU released for 1709
Log files have not been helpful. All impacted devices show in there ScanAgent.log that the 1909 FU was found (CScanAgent::ScanByUpdates - Found UpdateClassification 3689bdc8-b205-4af4-8d4a-a63924c5e9d5 for Update:de66498e-7ef8-4e29-b69b-ffc91e9706c0) and UpdatesDeployment.log shows "Update (Site_GUID/GUID) added to the targeted list of deployment". However, there is nothing to find for this update in the WUAHandler.log. These devices were receiving their monthly patches and still continuing to get 3rd Party Patches just fine.
The numbers for "Required" on my updates do not entirely match up either; the numbers very slightly (150-500) between 1809, 1903, 1909, 2004, and 20H2. I chalked this up to client scans.
Any thoughts or ideas on where to go from here? I guess my next, and easiest step, would be repairing clients. I was hoping to get some assistance and maybe find a root cause before doing this though. I have read that declining the updates in WSUS have fixed this similar behavior for others, but I am wanting to move forward with my pilot groups on 20H2 so not sure I want to decline any FU's right now. I also do not want to try and build a new IPU TS in the eleventh hour.
Thanks for any and all advice.





