Remember my FAVORITE patch .NET?

On February 2, 2009, in news, by

Remember my FAVORITE patch .NET?

On this one, just say no. – THE OFFICIAL BLOG OF THE SBS “DIVA”:
http://msmvps.com/blogs/bradley/archive/2009/01/30/on-this-one-just-say-no.aspx

Okay so here’s the skinny. 

Scott Hanselman’s Computer Zen – How to set an IIS Application or AppPool to use ASP.NET 3.5 rather than 2.0:
http://www.hanselman.com/blog/HowToSetAnIISApplicationOrAppPoolToUseASPNET35RatherThan20.aspx
Scott Hanselman’s Computer Zen – Update on .NET Framework 3.5 SP1 and Windows Update:
http://www.hanselman.com/blog/UpdateOnNETFramework35SP1AndWindowsUpdate.aspx
The WSUS Support Team Blog : When will the .NET Framework 3.5 SP1 be pushed to Windows Update?:
http://blogs.technet.com/sus/archive/2008/12/10/when-will-the-net-framework-3-5-sp1-be-pushed-to-windows-update.aspx

From reading those posts, it appears that it was their intent to have us deploy this 3.5 family .NET patch all along if you have .net 2.0 or higher. 

Bottom line if you have Quickbooks 2008 or 2009 on your desktops, you will get this .NET update.  You will get it on your SBS 2003 box.  You are supposed to get it on your Vista 64bit and Windows Server 2008 64bit boxes as well but it’s still missing in action. 

Q.  Do you need to install it?

A.  Someday yes.

Q.  When do you need to install it?

A.  During a good maintenance window.

Q.  What do you mean by that?

A.  Ensure you have a good backup first.  Ensure that you’ve tested it on a system to know how long it takes (on workstations it may take some time) and if the a/v needs to be disabled (some folks patching workstations have had to disable a/v).

Q.  Why do you dislike .NET patches so?

A.  History of issues with .NET.  Mainly because they are not well behaved.  They have a nasty tendency to flip the default websites on SBS from the 1.1 they are supposed to be to v2.  On workstations they can get stuck during installation and you have to use Aaron Stebner’s .net clean up tool.

Q.  Should I do any post install checking to ensure everything works as it should?

A.  On a SBS server in particular, run the www.sbsbpa.com and ensure that the .net install hasn’t flipped anything.  Launch Remote Web Workplace and test. 

Q.  If I use the clean up tool you mentioned, how do I use it?

A.  You remove all of the .nets and then you reinstall all of the versions.  Pulling them out with that tool and then reinstalling them usually works.

Q.  Usually?

A.  Uh yeah, that’s why I say have a backup.

Q.  Is there any date by which I should install these .NET service packs?

A.  They are not security patches.  They were delayed getting on Microsoft update in the first place.  We’ve lived without them this long.  They can wait.  As I told folks in a CPA listserve I’m on, April 16th (the day after taxes are due) sounds like soon enough in my book.

Q.  Do you always pretend that someone other than you is asking you questions?  I mean you are the one typing up these Q and A entries to yourself.

A.  Uh… yeah.. I guess this is a bit weird huh?

 

One Response to Remember my FAVORITE patch .NET?

  1. Chris Knight says:

    Remember that there’s also an issue with .NET 3.5 SP1 and WSS 2.0.

    http://blogs.msdn.com/sharepoint/archive/2008/08/27/net-framework-3-5-sp1-issue-on-windows-sharepoint-services-v2-0.aspx

    Important if you’re using WSS 2.0 on your SBS 2003 box.