![]() So where do I go from here? Lock down 1709 and fret at least once a month over updates again? If I do that, I’m basically back to square 1 and no better off than I was with 7, where I also had to fret over updates at least once a month – only then, 7 didn’t sneak things in and try to install updates (or anything else) without asking my permission. I’m hesitant to upgrade to 1803 within the next few weeks, because let’s face it, a broken watch is right 2 times a day – surely MS can’t keep their stride and pull off the improbable 3 times. I make daily backups with Veeam Endpoint on all my machines, but now I’m trying to figure out where I go from here. (I give the proverbial “deaf ear”, for the most part.)īut now I’m on that edge. ![]() I’m now in Group A, I let my machines install updates as they come. 1709 installed fine, and I’ve had no issues with it either (same as with 1703). After awhile, I kinda threw my arms up and caved. Defer upgrades, delay updates, the whole nine yards. Initially, I locked down 1703 and refused 1709. And I flashed it at home over all my 7 machines, after doing full images of course (in case of a change of mind). ![]() Then I started a new job at a mid/large company which was already 90% through the 7 > 10 conversion, with gen pop systems on 1511 and IT (my bailywick) on 1703, behind SCCM/WSUS. I planned on running my 7 image until the wheels fell off, at which case I’d clean install 7 again, update it, install nothing but Steam and VirtualBox, and use Steam for games and VirtualBox (which would then run a flavor of Ubuntu) for everything else, with practically every available hardware resource being passed through to it. I’m legitimately worried about this right now, and I feel like I’m on the edge of the cliff.Ħ months ago, I was a total Win10 avoider and I didn’t like it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |