I'm curious as to how others are handling new builds with Windows 10? We have an app currently that is on 90% of all of our machines, and we just found out it will not be supported on build 1607 for about another 8-9 months. Which means we will be going live with build 1511, but upgrading the build later. I've already tested the upgrade to 1607 via a script, but we have 20,000+ PCs. This just seems like a mess waiting to happen. Our users typically see the machine doing something, and will power it off.
1 Comment   [ + ] Show Comment

Comments

  • what we typically do is make all changes were pushing to take effect at boot up in the even a user powers off the system to avoid an update.

    as far as that application support on 1607, we have had a few that said that to us, but they all have worked without issue on 1607 so we went ahead and updated. You could test on a batch of 50 or so systems and see if the users encounter issues.
    • I'm currently testing the deployment using /quiet /noreboot switches. Our machines reboot every morning starting at 3 am, so as long as the update has finished by then I should be good (hopefully). Right now we only have a handful of machines, with us starting the rollout in November pretty heavy. It just seems like a messy way to do thousands of machines.

      The app was discovered that it didn't work correctly after testing in our lab. We test every app backwards and forwards. Unfortunately it wasn't discovered until I was done with my 1607 image.
Please log in to comment

There are no answers at this time

Answers

Answer this question or Comment on this question for clarity