Windows 7 SP1 revealed

[gosh]

First details of SP1 are being released

http://www.microsoft.com/presspass/press/2010/mar10/03-18DesktopVirtPR.mspx

Two new features coming in Windows Server 2008 R2 service pack 1. Microsoft Dynamic Memory will allow customers to adjust memory of a guest virtual machine on demand to maximize server hardware use. Microsoft RemoteFX will enable users of virtual desktops and applications to receive a rich 3-D, multimedia experience while accessing information remotely.

[Tripredacus]

I sure hope we get a servicing option for 7. I'd really hate to rebuild all our images.

[MagicAndre1981]

no, SP1 will not be slipstreamable. MS already posted this last year in the Technet documentation.

[Innocent Devil]

no, SP1 will not be slipstreamable. MS already posted this last year in the Technet documentation.

Grrrrrr.. :realmad: Not Again...

[Win2k3EE]

Why the f*ck is doing microsoft un-slipstream-able service packs? Who's the id*** in the MS team with this dumb idea?

First no classic menu in win7, now un-slipstream-able service packs?

:realmad:

[MagicAndre1981]

because Updates work the same like in Vista and Windows 7 is a Vista R2 under a new name

[jaclaz]

You know how Windows 7 is promoted:

http://www.beingmanan.com/wp/2010/03/microsoft-launches-campaign-for-windows-7-professional-you-spoke-we-listened/

You Spoke. We Listened.

You do understand how with this clever idea, it is NOT MS's fault as usual , it's the dumb*** that spoke that should be crucified:

http://www.imdb.com/title/tt0079470/quotes

Brian: What will they do to me?

Ben the Prisoner: Oh you'll probably get away with crucifixion.

Brian: CRUCIFIXION?

Ben the Prisoner: Yeah, first offense.

jaclaz

[cluberti]

It's a victim of the image format. If the install was flat, it'd work; if the SP was able to be made as an MSP, it'd work. Unfortunately, the SP is it's own installable package, and as such you have to load an image, install the SP package, then repackage via sysprep (reverse integration). I wish it weren't so, but unfortunately it is. I guess since I keep a base image in MDT/SCCM and use that to build a base WIM to deploy I don't have the pain others do, but I doubt it'll change anytime soon. Until the SP itself can be made into an MSP package (don't hold your breath), it's going to be this way.

[MagicAndre1981]

this is not the cause why it can't be slipstreamed! You can slipstream the SP n into a version which has n-1 SP level (Sp1 into RTM, Sp2 into Sp1, when you have a fully configured reverse integrated version). The cause is the way the servicing stack handles the updates!

[cluberti]

Right - it's a victim of the initial image. We probably won't have this problem with SP2, but SP1 isn't going to work. I know what you're getting at, but I thought I already covered that . We won't get into the D drive issue on new images either - I still haven't figured that one out.

[Tripredacus]

Well I'm not really talking about slipstreaming. I had no problem servicing Vista with SP1 without recreating the image.

[DigeratiPrime]

Dynamic RAM will be very useful if we can increase and decrease the ram.

[EDIT] Found more info here

http://hypervoria.com/hyper-v/hyper-v-2-0-feature-overview.aspx

Dynamic Memory

Overview

Pool of memory is dynamically distributed across VMs

Memory is dynamically allocated/removed based VM usage with no service interruption

Benefits

Enables much higher consolidation ratios per host by addressing the greatest limiting factor to consolidation: Memory

How

VM memory configuration includes:

Initial (what VM will boot with)

Minimum (what VM is guaranteed)

Maximum (what VM can grow to)

Memory is added via Hot-Add MEM functionality

Memory is removed via Balloon driver (supported OSs)

Edited March 28, 2010 by DigeratiPrime

[nmX.Memnoch]

We won't get into the D drive issue on new images either - I still haven't figured that one out.

Are you talking about capturing and restoring SCCM images? There's a workaround but I don't have the information readily available right now...

[cluberti]

I'm aware of the workaround, it's just that it exists in the first place (and wasn't fixed in 7, when it was an issue with Vista and reported). I guess the build labs must do it that way and it can't easily be changed.