If you do not want Vista SP1

[Snuffy]

Mary Jo Foley December 7th, 2007
Here’s that Windows Vista service-pack blocker tool
December 7th, 2007
Posted by Mary Jo Foley @ 7:18 am

Categories: Vista, Windows client, Windows server, Corporate strategy, Windows XP, Service Pack

While some customers are clamoring for Windows Vista Service Pack (SP) 1, others aren’t going to rush out and install an update without testing it first.

As mentioned earlier this week, Microsoft is making available for download a service-pack blocker tool for Windows users who don’t want Vista Service Pack (SP) 1 pushed to users’ desktops without their IT administrator’s official OK.

The blocking tool — which also will prevent the installation via Windows Update of serice packs for Windows Server 2003 and Windows XP — is available now via the Microsoft Download site. The tool only blocks the SP updates for a set period of time. As Microsoft notes on the Download site, the tool will block Vista SP1 for 12 months following its general availability (in Q1 2008). It will block XP SP3 for 12 months following its general availability (some time in the first half of 2008), and Windows Server 2003 SP2 through March 2008.

A public Release Candidate (RC) test build of Windows Vista SP1 is due out next week. Currently, only those with access to the private Microsoft Connect test site and/or subscriptions to the Microsoft Developer Network (MSDN) or TechNet services can get the SP1 RC bits.

(Thanks to ActiveWin for the link to the tool.)

I can not believe someone does not want to improve Vista RTM??
but incase you do not.

[CrowdAds]

[Snuffy]

Microsoft publishes detailed Vista SP1 “changelog”
Published December 8th, 2007 by Long Zheng
Leading up to next week’s public beta-test release of Windows Vista Service Pack 1 Release Candidate, Microsoft today has published a 17-page document outlining in fine detail exactly what difference SP1 makes to Vista.

Some of the contents has been shared in bits in the past, but this is so far the most comprehensive “changelog” we’ve ever seen and probably will see as the final version is not expected to differ much from the RC, with the exception of WGA modifications as described below. I’ve highlighted some of the most interesting changes which you may or may not already know.

This document describes many of the notable changes in Windows Vista SP1, with the exception of some updates to the Windows Genuine Advantage experience which we are still developing for our customers and will be released in a later build.

some tib bits:
Improves performance over Windows Vista’s current performance across the following scenarios:
1..25% faster when copying files locally on the same disk on the same machine
2. 45% faster when copying files from a remote non-Windows Vista system to a SP1 system
3. 50% faster when copying files from a remote SP1 system to a local SP1 system
4. Improves the effectiveness of a Windows ReadyBoost™ device in reducing the time to resume from standby and hibernate by increasing the amount of data stored in the ReadyBoost device that can be used during a resume cycle.
5. Adds full support for the latest IEEE draft of 802.11n wireless networking.
6. Updated drivers are delivered primarily via Windows Update and directly from hardware vendors, not as part of a service pack. However, a small number of critical drivers are included as part of Windows Vista (e.g., display drivers, audio drivers) and some of these have been updated.
7. Improves OS deployment by enabling 64-bit versions of Windows Vista to be installed from a 32-bit OS. This will allow IT professionals to maintain just a single WinPE image.
8. With SP1, Windows Vista will report the amount of system memory installed rather than report the amount of system memory available to the OS. Therefore 32-bit systems equipped with 4GB of RAM will report all 4BG in many places throughout the OS, such as the System Control Panel. However, this behavior is dependent on having a compatible BIOS, so not all users may notice this change.
9. SP1 reduces the number of UAC (User Account Control) prompts from 4 to 1 when creating or renaming a folder at a protected location.

http://www.istartedsomething.com/200...sp1-changelog/

[Snuffy]

Windows Service Pack Blocker Tool KitPosted by Vasudev on December 7 2007, 9:45 AM with no comments
Filed under: Windows (general) A blocking tool is available for organizations that would like to temporarily prevent installation of Service Pack updates through Windows Update. This tool can be used with:

Windows Server 2003 Service Pack 2 (valid through March, 2008)
Windows XP Service Pack 3 (valid for 12 months following general availability)
Windows Vista Service Pack 1 (valid for 12 months following general availability)

This toolkit contains three components. All of them function primarily to set or clear a specific registry key that is used to detect and block download of Service Packs from Windows Update. You only need to use the component which best serves your organization’s computer management infrastructure.
A Microsoft-signed executable
A script
An ADM template
The executable creates a registry key on the computer on which it is run that blocks or unblocks (depending on the command-line option used) the delivery of a Service Pack to that computer through Windows Update. The key used is HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate.

When the '/B' command line option is used, the key value name 'DoNotAllowSP' is created and its value set to 1. This value blocks delivery of a Service Pack to the computer through Automatic Update or Windows Update.

When the '/U' command line option is used, the previously created registry value that temporarily blocked the delivery of a Service Pack to the computer through Automatic Update or Windows Update is removed. If the value does not exist on the computer on which it is run, no action is taken.

The script does the same thing as the executable, but allows you to specify the remote machine name on which to block or unblock delivery of Service Packs.

Note that the executable and script have been tested only as a command-line tool and not in conjunction with other systems management tools or remote execution mechanisms.

The ADM template allows administrators to import group policy settings to block or unblock delivery of Service Packs into their Group Policy environment. Administrators can then use Group Policy to centrally execute the action across systems in their environment.

Please note that this toolkit will not prevent the installation of the service pack from CD/DVD, or from the stand-alone download package. This simply prevents the service pack from being delivered over Windows Update.

http://www.microsoft.com/downloads/d...DisplayLang=en

[airman]

I will be waiting to see what this service pack does for Vista i hope it doesn't screw it all up, some are saying that test that it is not that great of a release.

[Snuffy]

I'm not sure what version your talking about but v.17063-668 for my part is SUPER, and every review I have found says the same.... I do hope you not refering to some pirate reviews...