Humor me please?
If you can recall a patch directly causing impact to your systems please email me directly – email susan-at-msmvps.com (change the -at- to @) with the KB number and what it impacted please? I would love to put together a list of real patch pain, and not just perceived patch pain.
Fact: There have been a lot of non security updates that are impacting our patching views.
(I’m looking at you Exchange)
Case in point:
8/26/2014 CU 6 for Exchange 2013 http://support.microsoft.com/kb/2997209 http://blogs.technet.com/b/exchange/archive/2014/08/26/released-cumulative-update-6-for-exchange-server-2013.aspx
Fact: There have been a lot of click to run issues impacting our patching views:
6/13/2014 Click to run Uninstall/reinstall http://blogs.technet.com/b/office_sustained_engineering/archive/2014/06/13/june-public-update-issue-affecting-click-to-run-users.aspx
5/22/2014 Click to run Activation issues http://blogs.technet.com/b/office_sustained_engineering/archive/2014/05/22/c2r-update-may-2014.aspx
Fact: There have been hiccups in Office releases – especially in regards to Outlook:
8/13/2014 Outlook 2013 KB2881011 Replaced with KB2889859 http://blogs.technet.com/b/office_sustained_engineering/archive/2014/08/13/august-2014-office-update-release.aspx
Lord knows KB2919355 has impacted my view of this year.
Off the top of my head these are recent pulled patches:
MS14-045 pulled and rereleased.
Anytime you see a Kernel update, expect slight turbulence especially in the consumer side. Kernel updates interact with malware infected machines, pirated machines and antivirus vendors that get a little too much protection efforts.
I see the problem as a bit like the Ebola scare in the USA. We’re scared because of a lack of communication.
There’s a lack of post release follow up and communication as I see it. We have no idea how many machines are impacted, we just see the social echo of headlines and twitter feeds.
I am concerned that it seems like it’s taking longer to get investigations done.
We’re a week after release date and I still haven’t a clue why KB3000061 is failing, if the RDP patch is going to get a fix or if the fix should be expected from the vendors or what.
While security patches have a known issue section, other patches need a “we’re investigating” section with follow up.
So? Can you help me out with a feel on REAL patch pain versus perceived patch pain? I don’t want to know “I heard about an issue on a random blog/twitter account that someone was impacted”… I want to know exactly what patch gave you pain.
Getting ready for a migration at the office from the 2008 R2 era HyperV to a 2012 R2 era hyperV
And as the server sounds like a jet engine taking off…
it always makes me laugh how small the drives are, and how big the unit it
Makes ya wanna buy more hard drives and fill that sucker up.
So one of the things I’m doing this time is rather than doing a router in front of the server to separate out from the production network, I’m trying a virtual router
Fastvue Sophos Reporter How to Deploy Sophos UTM on Hyper-V in 7 Simple Steps:
So far it’s not as simple as that leads one to think it is. I obviously have networking/binding to the nics mucked up because it won’t find the web console address.
I’ll try again tomorrow and let you know how I get along with a virtual router.
I install Exchange update rollups all by themselves and on 9/24 Exchange put the 2007 and 2010 update rollups on MU and WSUS. Normally they don’t kick a reboot but this time it did.
While I have seen issues reported with the 2013 update especially in a mixed Exchange deployment with 2010, I have not seen issues with 2007 nor 2010.