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

I've read a few articles as to why performing an IISReset is not safe as it doesn't completely save XYZ (can't remember exactly what now).

What is the safest alternative to IISReset?

I ask this because I did an IISReset on one of our servers on the weekend and the exchange store service froze in the 'stopping' state - ended up fixing it by killing the store.exe process and restarting the service.

share|improve this question
up vote 1 down vote accepted

As far as I know, iisreset doesn't stop the Exchange Information Store - only the SMTP service.

You could try iisreset /noforce or you could fire up IIS Manager on the server and from the menu choose Restart Internet Services on [server name] (which for all I know, could just be doing iisreset /noforce in the background).

I have to bounce IIS on our Exchange server periodically (3rd party app keeps crashing) and personally, I use the GUI as I seem to have more luck with it.

share|improve this answer
I will try the /noforce switch when I next need to, thanks! I read a recommendation elsewhere whereby a net stop and net start was recommended but I can't remember the services they stopped - I didn't think that this was the best solution as I believe there are many services dependant on IIS. – emtunc Jul 7 '10 at 19:11

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.