Prohibit Installation of .NET via Windows Updates

How can I prohibit windows updates from installing Microsoft .NET 3.0 and 3.5? (I am assuming they were  automatically installed since all PC's curently show in Add/REmoce Programs.  Although I did not think it was part of the 'critical' automatic updates.  I have managed the network for quite a while and have not manually installed either of these versions)

History: Our organization does not currently use a tool such as Microsoft SMS to manage PC updates.  All are Windows XP Pro workstations configured to run windows updates at the default weekly interval.  

Dilemma: A new application set to 'go-live' in two weeks does NOT work with .NET 3.0 or 3.5.  I have scripted the uninstall of the application and, in testing, appears to remove both .NET's listed above.  I am concerned that when Windows Updates runs next, it will automatically install the 3.0 and 3.5 versions again.  

What is the best approach to keep these .NET versions off the Windows XP PRO workstations?

Thanks for your insight!
LVL 1
davisAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

tsaicoCommented:
If you want to keep these out, you will have to manage them via WSUS or similar tool, then in the console disprove of the hot fixes in question.

Two weeks sound a little short for your environment, but spend the weekend trying to figure out the WSUS so you can change the GPO now to at least get your deployment off.  You may also want to check out any current workstation deployment scenarios you have in the GPO already, it might have been pushed out like that to your workstations.

As for desktop management, when I was first starting to play with larger networks and getting some expereince, I had used ScriptLogic's solution and it was pretty good for what I needed at the time.  It was really good for me, since at the time I really hadn't had much real world experience with working with AD, GPO, and dealing with 300 devices at once.  
0
BobintheNocCommented:
If you can figure out the installer's actual executable name, you could try a Software Restriction Policy from Group Policy to list the executables that shouldn't be allowed to run.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
davisAuthor Commented:
Without having to deploy another utility like WSUS, Software Restriction Policy via GPO should work well for keeping this version of .NET off the netwok systems.  I need to use this for prohibiting IE 8 installs, since the app is incompatible with it as well! thanks for the assistance
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.