I can re-image the 17134 machine back to 16299.665 if you would like. From experience, I have found it is not possible to revert an image from base version upgrades like moving to 17 series.

This is strange and I will look into our update setting through GPO and puppet again.

That sounds good to me. More important to get everything on the same version before worrying about which specific version we need. Thanks for investigating.

Currently we do not have a clean way to control which patch level the windows fleet is on after they have been imaged. The variance you see is due to sporadic forced windows updates before we were able to successfully block them. At the moment I can reimage the one off images back to the base version (16299.309) if you like but beyond that we can not control in mass the version of windows on the fleet. At the moment you only have a couple systems that are not part of the majority. Those would be the only ones I could reimage. To upgrade the fleet at the moment requires us rebuilding these machines in small batches by hand so we would need a really compelling reason to do so.

Our OKR at the moment are based around improving our imaging capabilities so any time we can spend doing that will make all of the much easier in the next few quarters.

I have finished reimaging your one machine that was 17xxx version of windows and installed the 388.16 driver on it. It is now reporting into swarming and running tests.

Your fleet is now made up of 15063 and 16299 machines. For the time being this is as close to in sync as we can provide. Once we have finished created a new windows 10 image for the 1809 release we can perform upgrades to the existing windows systems. Hopefully this will be done by the end of the quarter.

Thank you so much Adam for helping us get to a consistent fleet! We look forward to working with you to update to a new base image with a new driver fleet-wide. (We'll have to coordinate on this.)

Ditto to what Ken said. Thanks much!