Shared Static HostingAdminister IIS by using command-line administration scripts or batch filesCreate a logical folder structureUse host header names to create multiple sites on one serverPut all static sites in one application poolRun all static sites with the same anonymous user accountRecycle the application pool worker process (optional)Monitor startup timesMonitor performanceEnable centralized binary loggingPartition log files on multiple disksShared Static and Dynamic HostingSeparate static and dynamic content sites in different application poolsSet content quotas for sitesConsider enabling Quality of Service (QoS) features for sites that are resource-intensiveConfigure one unique anonymous user per siteDevelop processes for handling service packs, security patches, and hotfixesFor ASP content, allow ASP pages to run on MTA instead of STAIf you need to set up more than 60 application pools where each pool is running as a unique identity on a server, change the UseSharedWPDesktop registry keyIf IIS is spinning up too many worker processes and your server is running out of resources, set a maximum number of concurrent worker processesLocate misbehaving applications and isolate them in their own application poolDedicated HostingConfigure one unique application pool per Web siteConfigure one unique anonymous user per siteConfigure one unique user to run as the process identity of the application pool