Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrades.
Please accept our apologies in advance for any inconvenience this might cause.

Block Installation of Windows XP SP3 and Vista SP1

Created: 20 May 2008 • Updated: 20 May 2008 • 6 comments
riva11's picture
+7 7 Votes
Login to vote

Many companies are waiting to deploy the Windows XP SP3 and Vista SP1 on their computers. In case you have the same target and use the Microsoft Windows Update or WSUS for the patch management, you will have to block these Service Packs on your computers otherwise will be automatically downloaded.

Some helpful information is in the Ghacks article, at the following link: Block installation of Windows XP SP3 and Vista SP1.

An intersting tip is to create a script with the reg modification and using DS server run on the target client where you need to block this update:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
"DoNotAllowSP"=dword:00000001

Remember that you can re-enable the Service Pack deployment on the Windows Update, simply by deleting the registry key. The next reboot will start the SP deployment.

Paolo

Comments 6 CommentsJump to latest comment

craze's picture

I am definitely going to recommend this article to the network administrator and computer science supervisor on campus. The new service packs can open up alot of vulnerabilities that our school is not yet prepared for. Thanks!
PS: Helping the professor out is always a good, grade-wise :P

+4
Login to vote
erikw's picture

Also remember that Vista SP1 is getti g you in troubles when you wish to capture apps in SVS.
It simply will not work?

Regards
Erik
www.dvs4sbc.nl

Regards Erik www.DinamiQs.com Dinamiqs is the home of VirtualStorm (www.virtualstorm.org)

*************************************************************
If your issue has been solved, Please mark it as solved
***********

+2
Login to vote
Jordan's picture

Well that's really not true, I've yet to hit something I can capture in Vista pre SP1 that I cannot capture in SP1 and I've actually been using SP1 since December.

There may be things that don't install that use to, but that's not an SVS issue.

If a forum post solves your problem please flag is as the solution

+2
Login to vote
riva11's picture

Some IT admins after Windows XP SP3 upgrade discovered a surprise, in the device manager there where missing network connections and the registry was full of thousands of bogus entries.

In case you have to deploy this Service Pack and use the Symantec products as reported below, you should disable SymProtect prior to installing the Windows XP SP3 upgrade.

An interesting article is published on gHacks.net.

[quote]If you are running the Symantec products Norton Internet Security 2008, Norton SystemWorks 2008, Norton 360 or Norton AntiVirus 2008 on a machine with Windows XP Service Pack 2 and want to upgrade to Service Pack 3 you should disable the SymProtect feature before doing so or your operating system could go kaboom. More precisely users would be left with an empty device manager and network connections window. This is apparently caused by a large number of bogus Registry keys starting with special characters that have been added to the Registry during the update.[/quote]

Link : http://www.ghacks.net/2008/05/28/symantec-disable-...

+4
Login to vote
riva11's picture

Update: please note that this tip prevents the Win XP SP3 update to be delivered over Windows Update.
In other words, you are allowed to install Windos XP SP3 a CD or downloading the package from Microsoft.

+4
Login to vote
spazzzen's picture

If I remember correctly, and assuming this is basically what the ServicePack blocker provided by MS does, then it will only block the service pack for 6-12 months.

0
Login to vote