For those of us in the SBS world, we have a love/hate, with mostly hate, relationship with .NET Framework updates.  Seems they are always causing trouble with our boxes.  Turns out the recent .NET Framework 3.5 Service Pack 1 is no exception, both on Small Business Server 2008 and Small Business Server 2003 .  While it is supposed to fix 25+ issues in .NET , my personal SBS 2003 production box reacted so badly with it that the box had no idea it was running SBS anymore.  When I attempted to run the CEICW in an effort to bring back my RPC over HTTP / Outlook Anywhere functionality that had died after running with the update for a few days, here’s the error it came back with:   I was also having “issues” with POP3 and IMAP4 (we use SSL on each of these for specific tasks at our office) protocols stopping after either an iisreset or a full restart of the server.  Strange thing with those protocols was that their respective services were still running.  Figure that one out. I restored the system drive from a StorageCraft ShadowProtect image last night to get the machine back on its feet.  I personally have left 3.5 SP1 on our box and added the update patches that are supposed to resolve the problems the Service Pack is causing with our boxes; using our company’s server as a guinea pig before putting the service pack or subsequent update suite of three patches into production at client sites.  Personally, I will not install .NET Framework 3.5 Service Pack 1 without these fixes on any box I touch now.  I’d recommend you do the same for any machines you admin and ensure you have a very good back up before playing with these or any updates.  Steve