Windows Thread, .NET 2.0 SP1 KB110806 in Technical; I currently install .NET 2.0 using MSI and Group Policy, i have recently approved .NET 2.0 SP1 to roll out ...
17th July 2008, 03:43 PM #1
.NET 2.0 SP1 KB110806
I currently install .NET 2.0 using MSI and Group Policy, i have recently approved .NET 2.0 SP1 to roll out from our WSUS box. When the update installs on the next reboot i see the message below
"The assignment of application Microsoft .NET Framework 2.0 from policy Software GPOsucceeded"
is the WSUS update installing the whole of .NET 2.0 and then the msi is trying to repair itself? Everything seems to work ok but i'm just wondering why it shows as having reinstalled.
IDG Tech News
17th July 2008, 10:12 PM #2
I'm a little confused - why are you deploying .NET Framework 2.0 using an MSI and installing .NET Framework 2.0 SP1 by WSUS? You should do both by WSUS to avoid problems.
18th July 2008, 09:55 AM #3
Ah ha well you see i've been deploying .NET 2.0 for ages via msi but without SP1, i recently released SP1 from the WSUS thinking that it was just SP1 for .NET framework 2.0 NOT the full .NET 2.0 with SP1.
Am i wrong?
So how do you depoy .NET 2.0 SP1?
I should also add that the reason i deploy .net 2.0 via msi is to enable Paint.net to install otherwise Paint.net repeatedly fails to install untill the box can be bothered to fetch SP1 from the WSUS.
Last edited by cookie_monster; 18th July 2008 at 11:29 AM.
18th July 2008, 12:04 PM #4
Ok found the answer, i had a hard time finding those instructions for some reason. Why it's not the same procedure as .NET 2.0 grrr
Aaron Stebner's WebLog : Creating an administrative install point for the .NET Framework 2.0 SP1
So next question, do you remove .NET 2.0 and then deploy .NET 2.0 SP1 or leave them both on side by side like 1.1 and 2.0?
Last edited by cookie_monster; 18th July 2008 at 12:08 PM.
18th July 2008, 02:23 PM #5
I don't actually deploy .NET Framework by WSUS as I install .NET Framework 1.1, 2.0 and 3.0 (plus service packs) on all my base images. My reasons are because they're fairly large updates, and secondly it avoids problems like you describe with applications as they're installed from the start.
The reason I suggested doing both via WSUS (in your position) is to avoid any conflicts, as WSUS knows what updates your machines need and do not need.
In your position I would probably remove the .NET Framework 2 MSI and let WSUS install it again as new, with SP1. It might be a little long winded and require a few reboots.
In future I would highly recommend you put .NET Framework 1.1, 2.0 and 3.0 on from the start (when creating an image) and you can do this using my Post XP SP3 Pack.
18th July 2008, 02:28 PM #6
I've changed the deployment order so 2.0 will be removed and 2.1 will be put on, i've tested it now and it works ok. From now on a new box will put 2.1 on straight away so there shouldn't be any issue. Currently we don't use images as i haven't had time to create them so we're installing a flat image off of the WDS server.
Notebooks that don't receive software from group policy will be delt with by WSUS.
By maplay in forum MIS Systems
Last Post: 3rd October 2009, 06:44 PM
By sgknowler in forum Windows Vista
Last Post: 1st May 2008, 11:24 AM
By Simcfc73 in forum Windows
Last Post: 22nd February 2008, 04:44 PM
By Lee_K_81 in forum Windows Vista
Last Post: 19th April 2007, 12:13 PM
By tosca925 in forum Windows
Last Post: 3rd July 2006, 02:00 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)