I tried the hack-route, because it 'worked fine' in 98/98SE/XP/Win7 (until it didn't) and ended up with a bunch of angry upper-ranking staff members with brand new 'broken slow shitty laptops' which are difficult to remove from production for service. On a softer note, I get that it'll be an uphill battle to get the new ISO, and probably a pain in the arse to change your work flow and re-do all the custom settings you've built into the image, but for the sake of your production environment, images and future-you's sanity (which may be at stake if you bake hacks into your image) you should follow Microsoft's recommendations on this one. Think of it as a warranty voiding action. Doing so puts your organization at risk of not only weird issues, but lack of support from the manufacturer if/when they occur. Sadly, updating an OS revision from audit mode for windows10 is not supported, and the hack-arounds and the problems they're liable to cause are likewise not supported.
0 kommentar(er)
