Installing a simple Web server on Windows Server 2008 from a script

-

While there are more advanced Web server configurations, many products require the IIS Web engine as a prerequisite. Here's how to install a simple IIS Web server through a scripted role.

——————————————————————————————————————-

You can usually add features through the Windows Server 2008 Server Manager snap-in via a script. In the case of IIS 7.0, there are many options available for the feature install.

One way to ensure a consistent configuration for applications that require IIS (e.g., SQL Server) is to use a scripted installation. For IIS, the package manager can install the features locally. To install a basic IIS configuration, run the following script:

start /w pkgmgr /iu:IIS-WebServerRole;IIS-WebServerManagementTools;
IIS-ManagementService;IIS-Metabase;WAS-WindowsActivationService;
WAS-ProcessModel;WAS-NetFxEnvironment;WAS-ConfigurationAPI

The command provides little interaction and, by default, does not provide feedback of any type if an incorrect parameter is passed after the /iu parameter. Figure A shows IIS being added via the script.

Figure A

Figure A

Once the scripted task completes after a minute or so, and the Window Server 2008 Server Manager snap-in performs its next refresh, the Web server is listed as a role on the system and is running. Figure B shows an updated Server Manager snap-in with this basic IIS role.

Figure B

Figure B

Using this scripted install of IIS is a good way to ensure consistent server build configurations, and other Windows features can be automated through the package manager (pkgmgr). The package manager can also uninstall packages, which may be helpful for temporarily enabling a feature for a specified amount of time and for removing the feature from a scheduled task to ensure its decommissioning.

For more information on the package manager, read the TechNet article Package Manager Command-Line Options.

Stay on top of the latest Windows Server 2003 and Windows Server 2008 tips and tricks with our free Windows Server newsletter, delivered each Wednesday. Automatically sign up today!


  • Date: September 23rd, 2008
  • Author: Rick Vanover

Comments

Post a Comment

Popular posts from this blog

Use configSource attribute to manage Web.Config sections in ASP.Net 2.0

-
Different Sections in Web.Config can be managed by using external XML files, like Connection strings, Appsettings ..... Create a XML file with the respective settings and put that file in App_Data folder to protect <?xml version="1.0" standalone="yes"?> <connectionstrings> <!-- Connection String for SQL Server 2005 Express --> <add name=" SiteSqlServer " connectionstring=" Your Connection " providername=" System.Data.SqlClient " /> <!-- Connection String for SQL Server 2000/2005 <add name=" SiteSqlServer " connectionstring=" Your Connection " providername=" System.Data.SqlClient " /> --> </connectionstrings> Save the file in App_Data folder you need to change the Settings in Web.Config <connectionstrings configsource="App_Data\yourFileName.xml" /> You can manipulate the values by simply changing the respective XML files. No need to change the Web.Co
Read more

DevOps - Key Concepts - Roles & Responsibilities - Tools & Technologies

-
KEY CONCEPTS FUNDAMENTAL PRINCIPLES  ROLES & RESPONSIBILITIES  TOOLS & TECHNOLOGIES  VERSION CONTROL SYSTEMS (VCS) CONTINUOUS INTEGRATION AND CONTINUOUS DELIVERY (CI/CD)  CONFIGURATION MANAGEMENT  CONTAINERIZATION AND ORCHESTRATION  INFRASTRUCTURE AS CODE (IAC)  MONITORING AND LOGGING TOOLS  COLLABORATION AND COMMUNICATION TOOLS  TEST AUTOMATION TOOLS  CLOUD PLATFORMS AND SERVICES  DevOps  DevOps, short for Development and Operations, is a set of practices and principles that aims to foster collaboration, communication, and integration between development teams and operations teams. It focuses on improving the efficiency, speed, and quality of software development and delivery processes. Key Concepts Here are some key aspects of DevOps: ·          Culture: DevOps promotes a culture of collaboration, trust, and shared responsibility among development, operations, and other teams involved in the software development lifecycle. It emphasizes breaking down silos and fostering
Read more