54 replies to this topic 3 votes

[cork1958]

Gary7, on 16 March 2013 - 00:00, said:

I really don't care if you install it or not. I obtained it from a reputable souce. MS decided that it was not going to put it on Windows Update. You have a problem call Ballmer.

Dang dude,
Lighten up!!

I simply said I wasn't going to jump right on this YET and would keep track of topic to see what others might say. How many people do you know that don't jump right on an OFFICIAL SP release from MS ?

Sheesh!!

[Mando]

joking aside, does anyone actually add these kind of rollups (or service packs for that matter) on live production servers, without actually testing the 5h1t out of it in your test env first (if you have one of course, if not why the hell not VMware player/ESXi costs nada?

If it was me, id sack any tech/engineer who thought that was actually a sensible way to go in my line of work and department tbvh.

Its from MS so it will be ok....errr no MS can only test it to their parameters, they don't know all the quirks and diff from the norm setups deployed worldwide.

and lets face it, been plenty of QA tested releases that have broken Windows in the past.

[Obi-Wan Kenobi]

Wow, thanks for the heads up! I've been working, and catching up here and there when I can. Didn't notice this thread. Thank you!

[Gotenks98]

I dont know maybe I am doing this wrong but the largest file here is 31mb? I know SP1 was almost 1gb, just the 107 updates currently in my image are way more than 31mb. So where is the rest of it? I was hoping I could add this to MDT and be done with alot less crap. But this does not seem to be the right files.

[SHoTTa35]

Gonna slap this on my workstation tomorrow and see what's up. It's getting a backup now anyways so big deal if it crashes, just restore the image in the morning and keep it moving!

[Jeff Stokes]

Gotenks98, on 20 March 2013 - 22:26, said:

I dont know maybe I am doing this wrong but the largest file here is 31mb? I know SP1 was almost 1gb, just the 107 updates currently in my image are way more than 31mb. So where is the rest of it? I was hoping I could add this to MDT and be done with alot less crap. But this does not seem to be the right files.

You can import the files into WSUS and point MDT at it.

[cluberti]

Gotenks98, on 20 March 2013 - 22:26, said:

I dont know maybe I am doing this wrong but the largest file here is 31mb? I know SP1 was almost 1gb, just the 107 updates currently in my image are way more than 31mb. So where is the rest of it? I was hoping I could add this to MDT and be done with alot less crap. But this does not seem to be the right files.

Given this is not a service pack but a performance-related rollup targeting specifically slow boot, slow logon, and related performance issues, you aren't going to get 1GB of binaries. In fact, I'd say the performance benefits of this rollup (again, it's a targeted rollup, not a service pack) versus the size is pretty incredible.

As to the testing questions, this is not a security update and has not been tested as such, but these updates (individually) have been tested many (many many) times over in enterprises large and small. However, they are still considered hotfixes and should be tested in your test labs for any kind of issues before you release them to the wild.

[bittin]

Cool stuff

[Salty Wagyu]

They really need to put out a post-SP1 security rollup, it takes an eternity installing 120 individual updates where we refurbish 10~ machines a day at work.

[cluberti]

I would postulate that continuing to rebuild machines without either hosting your own WSUS server or using Microsoft's (free) MDT tool to do so is definitely not a good idea. If you use MDT to host Windows, applications, drivers, and hotfixes/non-security updates, and point MDT's rules at your WSUS server for updates you will find it much quicker and easier to do what you're doing. There's a slight learning curve, but it's slight, and it will save you hours on the other end not doing everything slowly or by hand.