Monday, August 22, 2016

Microsoft to push all-in-one Windows updates - gHacks Tech News

Should be titled "Windows 10, coming back to your computer whenever Microsoft feels like it". The first thing I thought of, when I started seeing pundit's peddling the party-line on the announcement below, was that MS just side-stepped folks (like myself) who manually tear out some Windows Update patches immediately after monthly patches. Odd coincidence I just tore back _7_ Windows-10-peddling & MS data-spying patches from my Windows7 and Windows8.1 machines, yesterday. And now, we find out that Microsoft is taking away your ability to even pick and choose between patches at all: Starting in October, they're just releasing a _single_ patch for Win7/Win8 just like they have been for Win10. I've been shifting more and more of my machines at home to Linux, with this baloney, it looks like I've gotten fresh motivation to start looking at the laptops along with the utility roles (home theater pc, file server, music server).
via Facebook

Tuesday, August 2, 2016

My Microsoft Office 365 woes: Constant crashes, malware macros – and settings from Hell

THIS. We shifted to Office365 Office at work in April (I early-adopted on April Fools Day, apropos? :D) In the past, the centrally-managed workstation patching processes included monthly MS Office patching, bundled into managed & scheduled OS & desktop app patches. Which resulted in 1-2 mandated 'patching' shutdown & reboots per month. Now, with Office 365, I have Microsoft independently _pushing it's own_ unmanaged patch reboot demands, _in addition to_ the preexisting OS locally-managed patches. I've worked at firms that required detail time-accounting, so I routinely track every minute of my day in an app. I also run a lot of monitoring and dev components open on my desktop - which takes a while to get reloaded, after a reboot (which is why I hibernate my laptop daily for the trip home). Net result, every mandated reboot costs a minimum of 20mins of work-time. So, when I look back at time allocated to 'Mandated Workstation Patching' (company managed + o365), I find that in June alone of this year, I had to perform _8_ separate reboots on different days of the month. Some were prompted (or unprompted) patches, and some were reboots tied to sorting out buggy code in Office365. And yea, I'd echo most of the complaints from the below. Compared to the Office 2010 I'd run at work until April: Office 365 is _much_ slower, much more bloated for memory, and annoying as spit to any power user that works primarily from the keyboard (the shift to touchscreen interface support made a lot of useful shortcuts go away). Fact is, I still run an old copy of Office 2003 Visio from time to time at home, and I do some pretty fancy architecture diagrams for the office (with Visio2013 & now 2016): Visio 2003 isn't missing a single core function I rely on in Visio 2016/O365, but it runs much snappier, and a lot cleaner. Not to mention with a lot more stability. I'm starting to believe Office365's 'Ever-Green' continuous-revision concept actually means, 'Never-Stable'. #^|
via Facebook