Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top


A two pronged question for you all...

Here at work, we've prematurely put .NET 3.5 on our production server (Win 2003, which previously it had no .NET at all). Ever since, every time we apply windows updates have been restarting IIS. (Which is fair enough, since it's been patching the .NET installation.)

Now, first question: Is this new behaviour going to continue, or shall we assume that once it's "up to date" it'll return to the previous behaviour of rarely needing to restart?

Second question: What are the chances that we'll stuff something if we uninstall .NET entirely from our server?

(Info: We have been running ASP classic + a few 3rd party products from Persists)

share|improve this question

migrated from Feb 17 '12 at 3:32

This question came from our site for professional and enthusiast programmers.

up vote 1 down vote accepted

It's a good question but it's not a programmer question.

If I may offer brief and completely warrantee and guarantee free support though!:

1) There's no way to be sure of this; Installing it would have put the latest version on, it may be adding important security fixes. If this is a worry then make time to schedule for update deployments.

2) If you've not been using it then its likely that it won't hurt to remove it; However thats not to say that something installed since then doesn't use .Net, even if your stuff doesn't.

One possible thing to check is look at the Event logs and see if there is anything for .Net at all, that would give you a hint as to what code is using .Net

share|improve this answer
Mmmm, Logs. Good thought. I can't see that anything new & using .NET would have been installed. I've passed this information up the line, and have suggested better implementation of (1) rather than removal. We'll see how we go. Once we resolve this internally, I'll update this again. – Mark Feb 17 '12 at 5:20
Hi Russ. Well, this seems to now be moot, as the chief is happy to leave it on there now, as procedures have been adjusted & it doesn't seem to be having an effect anymore. Thanks for the help :) – Mark Mar 20 '12 at 23:54

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.