I'm working to identify a misstep in my software updates deployment process.
I've identified that the windows 10 21H2 enablement package hasn't even been downloaded. Once I get that, I'd like to confirm it doesn't automatically 'unlock' windows 21H2 everywhere and I can still stage it's deployment in typical ways using collections as my deployment targets.
Seems silly as a question perhaps, the customer has a VERY low tolerance for downtime so I'm validating. I've done some due dilligence searching and I do see issues which have come up in different situations.
