Windows Update Fevruary 2015

Hello

I noticed on 2 different servers (2012 R2 and 2008 R2) that Windows Update of February 2015 (from yesterday or 2 days ago) take about 1 hour to setup

I applied updates on a Windows 2012 R2 server and it took more than 1 hour for the server to finish rebooting normaly

THan I noticed also on a Windows 2008 R2 server set for automatic Windows Update that updates started at 3h00 and finished at 4h03

Is that normal?

Does anyone found any problem with these updates?

THank you
gadsadAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
rindiConnect With a Mentor Commented:
As I mentioned earlier, I wouldn't download them automatically, but rather use the setting I suggested, where you get notified about available updates, but you decide when to download and install them. Also as I mentioned, already, if they are already downloaded, you can delete them in the SoftwareDistribution\Downloads folder.
0
 
rindiCommented:
First, never do automatic updates on servers. Rather do it manually when you are there and in control of things, and so you can restore from your backups if something fails. Second, as m$ updates have encountered quite a few buggy updates the last year, which they had to remove again, I also strongly recommend to wait with your updates on servers for 1 or 2 weeks, as by that time those bugs are usually resolved.

So I suggest doing the updates manually on a weekend, and do a full OS backup before you start.

I haven't run my february updates yet, but from what I read, There are quite a lot of them and they are extensive, so you can expect it to take a long time.
0
 
gadsadAuthor Commented:
Thank you

If I wait one or 2 weeks before running updates, how can MS fix updates if they are already downloaded on the server ? You mean I should not even download updates on the server before 1 or 2 weeks so they can be fixed at Microsoft before downloading them. I guess that is they are already downloaded on the server (before installation) they cannot be changed. It that right?
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
rindiCommented:
In the updates settings select "Check for updates but let me choose whether to download and install them".

Besides that, if they are already downloaded, you can delete the contents of "C:\Windows\SoftwareDistribution\Downloads", that's where they get downloaded to and installed from, so if they aren't there, they will be downloaded again. As that folder can use up quite a lot of space in time, deleting them also cleans up disk space.
0
 
serialbandCommented:
If you have "extra" servers, you download and install on one for testing before you update the rest.  Don't ever autoupdate a production server.  If you manually download the updates and read the disclosures, you can just disable the services being updated and update them without rebooting.  It's a good way to reduce overall system downtime.
0
 
rindiCommented:
Talking of buggy updates, m$ has managed to include one of them this update Tuesday, and they have already removed it again. So it looks as if they are doing their best in keeping with the reputation they have recently built up.
0
 
gadsadAuthor Commented:
As I read your commentaries I think the best and safer thing will be NOT to update Windows and Not to install updates

Just check antivirus.

What do you think about NOT updating Windows Server 2008 and 2012 ?
0
 
rindiCommented:
You should run the updates, just don't do it on patch Tuesday, but rather wait 1 or 2 weeks. Not updating is a very bad idea.
0
 
serialbandCommented:
I would download on that Tuesday, or just set your auto update to download only, but don't patch right away.  If you have extra or spare systems to do testing, then use them to test the patches before actually patching your production servers.  If not, then let others with extra servers test the patches and report the bugs first.  Once the dust settles and the problems are discovered and fixed, then patch your systems.  Don't leave them unpatched too long.  Be sure to have your systems behind a firewall.
0
 
gadsadAuthor Commented:
Ok for letting others patch first and report bugs before patching myself buy:

1) if bugs are reported how can I change the bugged patch for the good one if it has already been downloaded on the server?
2) How do I know that a patch is bugged? looking through the internet will not be easy. Is there a way or a site to know bugged patchs?
 
Tks
0
 
gadsadAuthor Commented:
thanks
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.