#Inetinfo process windows install
#Inetinfo process windows windows

Monitoring these processes will not help you because the server will reboot to fix the issue before you have found time to act.

#Inetinfo process windows windows

For most of these processes, Windows does not even allow them to be killed and if they for some reason would stop, that will crash the server intendedly. By monitorring the event log, you would not only monitor running critical proceses and services, but also their health!Īfter all a running process does not always functions as desired.Īlso monitoring running services can help in quickly adressing issues with your server.Īnother thing that might help in your consideration: there are few really important Windows processes. Most iportant of those is of course the event log. Therefore there are a lot of alternative wys to dterine the health of a server. (IIS is pretty critical on most webservers.) On top it is hard to define which processes are critical,īecuase that also depends on the services deleverd by the server. So monitoring from this perspective would be difficult to achieve. My general recommendation would be to not focus on general OS processes.These are launched and stopped when neede in a lot of cases. Wmiprvse.exe the WMI provider: needed for remote managemnt and tooling Spoolsv.exe the print spooler for printservers Svcost.exe(netsvcs)Host Process for Windows Services most instances are critical indeed Perfomon.exeResource and Performance Monitor runs only if perfomance monitoring is on, not critical Winlogon.exeWindows Logon Application critical to maintain user sessions

Wininit.exeWindows Start-Up Application critical SystemNT Kernel & System yes indeed pretty critical ) Net.TCP Port Sharing Service, as far as I know related to UAC Ism.exe (RDP Clip Monitor) Local Session Manager critical Isass.exeLocal Security Authority Process critical

LogonUI.exeWindows Logon User Interface Host as far as I know, only used for RDP sessions Inetinfo.exeInternet Information Services IIS 7.0 only needed for webservers with IIS I've added some comments on your list below:Ĭsrss.exeClient Server Runtime Process indeed criticalĭwm.exeDesktop Window Manager only needed when GUI is a requirement, runs as the logged on userĮxplorer.exeWindows Explorer only needed when GUI is a requirement, runs as the logged on user You might focus on processes launched by the system account, the network service account, the local service account or any configured service account on the server

#Inetinfo process windows install

On the delivered service what proceses are critical.Īn angle of attack might be to install the server(s) with their critical services and then list the processes remotely (without logging on!) using a tool like pslist.exe You should first define what you think is a critical proces: for example in your list, explorer.exe and inetinfo.exe are not really critical fo the OS to run.Įven more, explorer.exe is a user-proces that only runs for a logged on user (which might be critical if is a terminal server) and that is not needed even when a user is logged on (you can try: logon, open task manger and kill explorer.exe).