Everything, Everything - October 2017

2021: January
2020: J F M A M J J A S O N D
2019: J F M A M J J A S O N D
2018: J F M A M J J A S O N D
2017: J F M A M J J A S O N D
2016: J F M A M J J A S O N D
2015: J F M A M J J A S O N D
2014: J F M A M J J A S O N D
2013: J F M A M J J A S O N D
2012: J F M A M J J A S O N D
2011: J F M A M J J A S O N D
2010: J F M A M J J A S O N D
2009: J F M A M J J A S O N D
2008: J F M A M J J A S O N D
2007: J F M A M J J A S O N D
2006: J F M A M J J A S O N D
2005: J F M A M J J A S O N D
2004: J F M A M J J A S O N D
Tuesday 31st October, 2017 20:50
Looks like someone may not have fully anticipated the increased volume for Halloween? Or just bad timing?… https://t.co/3WiYTNQ87u
Sunday 22nd October, 2017 13:42
Predictable start for Arsenal. Good strike from Rooney though.
Saturday 14th October, 2017 19:02
How did Ozil not score then? And now Watford have scored from a harsh penalty decision. Hopefully Giroud can score a winner.
Installing KB4035631 With Server 2016
Wednesday 11th October, 2017 13:18
You can fail to do it the easy way or you can manually do it the hard way. The TL;DR is download and install the MSU file manually.

I started off trying the easy way, letting my Azure VM download it through Windows Update. Despite saying "Downloading", something had clearly finished as TIWorker.exe was causing high CPU usage. I rebooted, for good measure, then used sconfig.cmd to try and download and install the update. I left it running. Overnight. TIWorker.exe used 8 hours of CPU time (about 12 hours elapsed time) before I gave up and killed the process.

I decided to go with Plan B, downloading the MSU file from Microsoft Update Catalog:


Download the Server 2016 version and once that file is on your server, simply open it to install the update in a matter of seconds.

This appears to have been acknowledged in the comments on this Microsoft Partner Support page in the last few days as a known issue allegedly related to the use of Express CAB files that will supposedly be addressed in the coming weeks, and as it's not a security update this isn't a huge deal, but it is annoying and more importantly it may result in increased CPU usage (on a single core) that could affect performance on some servers.

I can definitely understand why many organisations are still using Server 2012 R2 and keeping clear of Server 2016 for now.
Tuesday 3rd October, 2017 12:40
An interesting read on how easy it is to get a gun in America: https://t.co/8I7XSEnLdS
© Robert Nicholls 2002-2021
The views and opinions expressed on this site do not represent the views of my employer.