Dynamic or Static Content Errors Applications Are Denied Access to Resources After a clean install, IIS 6.0 runs in worker process isolation mode. Applications running in this mode use the Network Service identity, by default. Network Service is an account with few user rights and therefore provides better security by restricting access to resources on the Web server. If you migrate applications to IIS 6.0 while the server is in worker process isolation mode, and if your applications previously ran in-process (in Inetinfo.exe) as LocalSystem, the applications may fail to access resources because of the restrictions set forth by the Network Service identity. The LocalSystem account has access to almost all resources on the operating system, and therefore creates serious security implications. You should avoid using the LocalSystem account when possible. If it is absolutely necessary to use the LocalSystem account on an application, run that application in a new application pool in its own virtual directory so you can reduce the attack surface by isolating the application. As an alternative, and if your application needs permission to use the Trusted Computing Base (TCB), run the application as a configurable identity and assign the TCB permission to the configurable identity. This alternative, however, still presents a security risk because the TCB permission is very powerful. For more information, see Configuring Worker Process Identities and IIS and Built-in Accounts.
Applications Are Denied Access to Resources
After a clean install, IIS 6.0 runs in worker process isolation mode. Applications running in this mode use the Network Service identity, by default. Network Service is an account with few user rights and therefore provides better security by restricting access to resources on the Web server. If you migrate applications to IIS 6.0 while the server is in worker process isolation mode, and if your applications previously ran in-process (in Inetinfo.exe) as LocalSystem, the applications may fail to access resources because of the restrictions set forth by the Network Service identity. The LocalSystem account has access to almost all resources on the operating system, and therefore creates serious security implications. You should avoid using the LocalSystem account when possible. If it is absolutely necessary to use the LocalSystem account on an application, run that application in a new application pool in its own virtual directory so you can reduce the attack surface by isolating the application. As an alternative, and if your application needs permission to use the Trusted Computing Base (TCB), run the application as a configurable identity and assign the TCB permission to the configurable identity. This alternative, however, still presents a security risk because the TCB permission is very powerful. For more information, see Configuring Worker Process Identities and IIS and Built-in Accounts.
C:\WINNT\Microsoft.NET\Framework\v1.0.3705\aspnet_regiis.exe -i
Windows XP HomeEdit 中文版 CD（拷在硬盘也可以）
2、Windows 2000 Advanced Server CD(最好也是中文版)
3、默认你的XP是安装在C:\WINDOWS下 开始动手 (如果你怕改错，先把C:\WINDOWS\INF\SYSOC.INF做一份备份) 用记事本打开C:\WINDOWS\INF\SYSOC.INF，在[COMPONENTS]下找到一行： iis=iis.dll,OcEntry,iis.inf,hide,7 然后把它改成 iis=iis2.dll,OcEntry,iis2.inf,,7 保存。 然后把Windows 2000 Advanced Server CD里的两个文件IIS.DL_和IIS.IN_拷贝到一个临时的目录（例如C:\AAA），然后在命令提示符状态下将当前目录转到C:\AAA，执行 EXPAND IIS.DL_ IIS2.DLL
EXPAND IIS.IN_ IIS2.INF 解出IIS2.DLL及IIS2.INF两个文件，将IIS2.INF复制到C:\WINDOWS\INF目录下，将IIS2.DLL 复制到C:\WINDOWS\SYSTEM32\SETUP目录下。 现在按“开始->设置->控制面板->添加或删除程序->添加/删除Windows组件”，这时你可以很兴奋地发现IIS出现了!!! 此后的过程就和PRO版的XP安装IIS差不多了，过程中会要求你选择Windows 2000 Advanced Server光盘和Windows XP HomeEdit光盘的位置，输入指定的目录即可正常安装。 安装完毕以后还不能直接用的，需要对IIS进行一些设置： 控制面板->管理工具->Internet服务管理器 然后点“默认WEB站点”的右键，转到“目录安全性”选项卡，点“匿名访问和验证控制”的“编辑”按钮，回弹出匿名方法新窗口，再点击其中“匿名访问”中的“编辑”按钮，将“允许IIS控制密码”全面的勾去掉，然后一路确定返回即可。
各位：ＩＩＳ我装好了的．不是ＩＩＳ的问题．
一气之下安了Ｃ＃builder，一样的代码（没有改动一个字），居然可以．
然后又下了个微软的WebMatrix．它也可以．
就是ＶＳ.net2003不行．急救．