On Sat, Aug 29, 2015 at 1:18 PM, Ken Dibble <[email protected]> wrote: > > I don't ever allow any computer under my supervision to automatically > download or install ANY updates until I am satisfied that they won't break > the computer. And I almost never install any of the non-security or other > "important" updates in any case. MS can't be trusted as regards hardware > drivers, and I'm usually not interested in anything else they have to offer. >
That's quite a pragmatic attitude. I agree. But that's a model of having a "computer guy" in the office, or at least involved on a daily basis. Most of my business has been selling vertical-niche or custom apps to clients who do as they like. Some have organizations that manage their IT based on some strategy or another (some of them as wacky as mine) and others run out to Staples and buy whatever machine is on sale when they need a new one. When asked what OS they're running, they answer "Windows" as if it's s silly question. What, there's more than one? So, I have to be prepared to support, or tell them they need to get support, for any variety of OSes. One client just finished upgrading and migrating their apps to Win 7. They'll move to 10 around version Windows 10 2035 edition. I'm hoping to be retired by then. Others hire consultants who move all their files on to the latest SBS and then migrate all their desktops to hosted Windows-in-the-cloud. I'm so glad I don't have to sysadmin client's setups! > So KB3035583 is not installed on any computer that I am responsible for. > > Nor would I ever "upgrade" any MS OS. When I get new ones, they are > installed from scratch. MS OSes that are "upgraded" tend to be unstable. Less true today than it was in the past, but that doesn't make it NOT true. The advantage of an in-place upgrade is not having to reinstall apps or find obscure drives, the advantage of a Freemanize (R) is that you find out what's obsolete up-front. > I haven't purchased any Win 10 boxes yet. When I do, I will only purchase > the "enterprise" version, because that is supposed to provide the maximum > amount of control over updates. > > That is supposed to include deferring anything that is not a "security" > update indefinitely. As best as I can tell, "home" doesn't allow delaying > any type of updates. "Pro" allows delaying non-security updates for some > relatively brief period of time, after which they are installed by force. > That means that MS can at some point change the OS so much that my software > will no longer work on it, and there would be nothing I could do about it. > That is not acceptable. The worst I find is returning to a machine the next morning and finding it restarted. While I *should* have finished what I was doing before quitting for the night, that's not always under my control. > So I'm waiting for "enterprise", which is supposed to allow me prevent > non-security updates indefinitely. And it is also suppose to allow me to > establish my own schedules and "rings" for exposing machines to other types > of updates. > > However, my reading on this indicates that this feature is not yet actually > available, and won't be fully implemented until sometime next year. I don't > use an update server now, and I don't see the value of using one unless and > until it can give me complete control over updates. > > MS is just as capable of screwing up a "security" update as it is of messing > up other updates. They've done it many times. Until I am certain that I can > prevent ANY update from being installed until I know it is safe, I won't be > putting Win 10 into production. Isn't there some Windows Update Service you can put in place so all the updates are delivered to your organization, but you control when they actually apply to your machines? https://technet.microsoft.com/en-us/windowsserver/bb332157.aspx > I do believe that MS will eventually change its tune about this, because > there are many, many people who are not happy campers. I'm pretty sure the industry is going in the opposite direction, where all of the machines become proprietary closed boxes controlled by the vendor and updates happened without any control by the end user. > I wanted to get a Win 10 box to experiment with in the meantime, but I think > now I'll wait until at least after next "major" update, scheduled for > October, and then see what the situation is after that. It's time: http://blogs.windows.com/windowsexperience/2015/11/12/first-major-update-for-windows-10-available-today/ -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CACW6n4sF92S38=xdyb6lwsx9hyevy6fsuq5w2d5r6ugz0ex...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
