Planning the Installation : Installation Scenarios for IIS 7.0 (part 2) - IIS Managed Modules and .NET Extensibility Server Workload & IIS Full Install

start /w pkgmgr.exe /iu:IIS-WebServerRole;IIS-WebServer;
  IIS-CommonHttpFeatures;IIS-StaticContent;IIS-DefaultDocument;
  IIS-DirectoryBrowsing;IIS-HttpErrors;IIS-ApplicationDevelopment;
  IIS-NetFxExtensibility;IIS-ISAPIExtensions;IIS-ISAPIFilter;
  IIS-HealthAndDiagnostics;IIS-HttpLogging;IIS-LoggingLibraries;
  IIS-RequestMonitor;IIS-Security;IIS-RequestFiltering;
  IIS-HttpCompressionStatic;IIS-WebServerManagementTools;
  IIS-ManagementConsole;WAS-WindowsActivationService;
  WAS-ProcessModel;WAS-NetFxEnvironment;WAS-ConfigurationAPI

ServerManagerCmd.exe -install Web-Server
ServerManagerCmd.exe -install Web-Net-Ext

IIS Full Install

You might want to do a complete IIS 7.0 installation in a test environment to evaluate everything IIS 7.0 has to offer. When you install all 40-plus modules, you are guaranteed that everything you need is available. In a true development scenario, however, it is probably not a good idea to do a full installation, because you could run into issues when you migrate your applications to a production environment that contains only a subset of modules. If you install only the minimum number of modules and features in your development environment, you will gain a complete understanding of what modules are needed and why. This will help keep your production server installation footprint smaller and more secure. The fewer modules deployed, the better your application performance will be. The more you do to match your development environment to your production servers, the more likely it is that you’ll have a smooth transition from development to production.

Table 6 lists all the components installed when you do a full installation of IIS 7.0. The table includes the appropriate update names.

To install IIS features for a full server install via Package Manager, use the following command from a command prompt:

start /w pkgmgr.exe /iu:IIS-WebServerRole;IIS-WebServer;
  IIS-CommonHttpFeatures;IIS-StaticContent;IIS-DefaultDocument;
  IIS-DirectoryBrowsing;IIS-HttpErrors;IIS-HttpRedirect;
  IIS-ApplicationDevelopment;IIS-ASPNET;IIS-NetFxExtensibility;
  IIS-ASP;IIS-CGI;IIS-ISAPIExtensions;IIS-ISAPIFilter;
  IIS-ServerSideIncludes;IIS-HealthAndDiagnostics;IIS-HttpLogging;
  IIS-LoggingLibraries;IIS-RequestMonitor;IIS-HttpTracing;
  IIS-CustomLogging;IIS-ODBCLogging;IIS-Security;
  IIS-BasicAuthentication;IIS-WindowsAuthentication;
  IIS-DigestAuthentication;IIS-ClientCertificateMappingAuthentication;
  IIS-IISCertificateMappingAuthentication;IIS-URLAuthorization;
  IIS-RequestFiltering;IIS-IPSecurity;IIS-Performance;
  IIS-HttpCompressionStatic;IIS-HttpCompressionDynamic;
  IIS-WebServerManagementTools;IIS-WebServerManagementTools;
  IIS-ManagementConsole;IIS-ManagementScriptingTools;
  IIS-ManagementService;IIS-IIS6ManagementCompatibility;
  IIS-Metabase;IIS-WMICompatibility;IIS-LegacyScripts;
  IIS-LegacySnapIn;IIS-FTPPublishingService;IIS-FTPServer;
  IIS-FTPManagement;WAS-WindowsActivationService;WAS-ProcessModel;
  WAS-NetFxEnvironment;WAS-ConfigurationAPI

To perform a full server install via ServerManagerCMD, use the following command from a command prompt:

ServerManagerCMD.exe –install Web-Server –allSubFeatures

Table 7 lists all ServerManagerCMD update names. Note that to perform a full installation using ServerManagerCMD, you can simply specify the –a switch. Refer to Table 7 when you need to install specific modules.