Tag: web technology

IUSR_computername

IUSR_Domainname

IUSR_VirtualdirectoryName

Administrator

wpw3.exe

wpwQ.exe

wqwp.exe

winnt.exe

C:\WINDOWS\system32\Logfiles

C:\WINDOWS\system32\Logfiles\Date

C:\WINDOWS\system32\Logfiles\W8SVX10

C:\WINDOWS\system32\Logfiles\W3SVC1

Yes

No

Yes but depends on application design

Yes but not supported by Microsoft

YES

NO

YES Limited by Hardware capacity

In theory there is no limit but creating more then 60 App Pools is not recommended.

IIS cannot save such settings. It will throw error.

Yes, This is perfectly acceptable and IIS will work accordingly.

No If you set the idle timeout for an application pool to a period of time that is longer than the time specified for time-based recycling, IIS will ignore the settings that you specify and instead use the default settings

YES, If you set the idle timeout for an application pool to a period of time that is longer than the time specified for time-based recycling, IIS will apply the longer time period settings.

YES

NO

NO, But can be programmed to do so.

YES but not FTP Users

In Process Memory

Hard disk

RAM

With in IIS processes

You can use an Fire wall to hide

You can use an http Handler to hide

You can use an ISAPI filter to hide

You can never hide.

wpw3.exe

wpwc.exe

http.sys

ISAPI.exe