Microsoft Internet Information Server (IIS)

Views: 2.4k  |  Created: 07/05/2004

Average Rating: 0
Internet Information Server (IIS) has 1 inventory records, 1 Questions, 1 Blogs and 6 links. Please help add to this by sharing more!

Deployment Tips (12)

Most Common Setup Type
Not Determined
Average Package Difficulty Rating
Rated 4 / 5 (Somewhat Difficult) based on 2 ratings
Most Commonly Reported Deployment Method
Vendor Provided Command Line (answer file driven)
or cancel
118
Note

If installing IIS via SMS, you may wish to check that the installation account / machine has access to the I386 source files.

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Note
IIS Import/Export Web Sites and FTP Sites Configuration Scripts

Once the initial IIS 6.0 installation is complete, settings can be applied to the IIS instance using the Internet Information Services (IIS) Manager and then exported to an XML file. The XML files contain IIS metabase entries that can then be imported to other machines running IIS. It is important to remove all machine specific data from the exported XML file prior to importing onto another machine.

Export IIS Configuration

Web Sites: The following command is an example to export the base configuration for “Web Sites” to the c:\temp\Microsoft\IIS\6.0 directory naming the file wwwBaseConfig.xml:

%SystemRoot%\system32\cscript.exe %SystemRoot%\system32\iiscnfg.vbs /export /f c:\temp\Microsoft\IIS\6.0\wwwBaseConfig.xml /sp /LM/W3SVC /children

• /f specifies a unique name and location for the export file.
• /sp specifies the metabase keys to export. The parameter immediately after the /sp specifies the path of the Web site to export.
• /children exports all subkeys of the configuration.

FTP Sites: The following command is an example to export the base configuration for “FTP Sites” to the c:\temp\Microsoft\IIS\6.0 directory naming the file ftpBaseConfig.xml:

%SystemRoot%\system32\cscript.exe %SystemRoot%\system32\iiscnfg.vbs /export /f c:\temp\Microsoft\IIS\6.0\ftpBaseConfig.xml /sp /lm/MSFTPSVC /children

• /f specifies a unique name and location for the export file.
• /sp specifies the metabase keys to export. The parameter immediately after the /sp specifies the path of the ftp site to export.
• /children exports all subkeys of the configuration.

Import Configuration

Web Sites: The following command is an example to import the base configuration from the c:\temp\Microsoft\IIS\6.0\wwwBaseConfig.xml file to the /LM/W3SVC metabase location and subkeys.

%SystemRoot%\system32\cscript %SystemRoot%\system32\iiscnfg.vbs /import /f c:\temp\Microsoft\IIS\6.0\wwwBaseConfig.xml /sp /lm/W3SVC /dp /lm/W3SVC /children /merge

• /f specifies the path and file name of the XML source file.
• /sp specifies the location in the XML file of the keys being imported.
• /dp specifies where in the metabase the imported keys are placed.
• /children recursively imports the subkeys of the specified key.
• /merge combines the keys in the XML file with the existing metabase keys.

FTP Sites: The following command is an example to import the base configuration from the c:\temp\Microsoft\IIS\6.0\ftpBaseConfig.xml file to the /LM/MSFTPSVC metabase location and subkeys.

%SystemRoot%\system32\cscript %SystemRoot%\system32\iiscnfg.vbs /import /f c:\temp\Microsoft\IIS\6.0\ftpBaseConfig.xml /sp /lm/MSFTPSVC /dp /lm/MSFTPSVC /children /merge

• /f specifies the path and file name of the XML source file.
• /sp specifies the location in the XML file of the keys being imported.
• /dp specifies where in the metabase the imported keys are placed.
• /children recursively imports the subkeys of the specified key.
• /merge combines the keys in the XML file with the existing metabase keys.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Note
Windows SP2 and IIS 5.1 & 6.0

When you install SP2, Windows Firewall is enabled by default to help improve security. As a result, Web servers running Windows XP with SP2 will no longer be accessible from remote computers. For example, you will be unable to use Microsoft FrontPage® Server Extensions or SharePoint™ Team Services from Microsoft to browse or update Web sites.

You can make these applications accessible by opening the Internet Information Services (IIS) port TCP 80 on your computer.

To do this, at the command line, enter the following:

netsh firewall ipv4 set portopening proto=tcp port=XX WebServer_Description

XX represents the port number for the Web server. By default, this is 80.


See: http://www.microsoft.com/technet/prodtechnol/winxppro/deploy/relnsp2.mspx?pf=true
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Note
Common Files iis_common = on/off
File Transport Protocol (FTP) Services iis_ftp = on/off
FrontPage 2002 Server Extensions fp_extensions = on/off
IIS Manager iis_inetmgr = on/off
NNTP Service iis_nntp = on/off
SMTP Service iis_smtp = on/off
World Wide Web Publishing Service n/a (A parent object in OCM)
Active Server Pages iis_asp = on/off
Internet Data Connector iis_internetdataconnector = on/off
Remote Administration (HTML) *# sakit_web = on/off
Remote Desktop Web Connection tswebclient = on/off
Server-Side Includes iis_serversideincludes = on/off
WebDAV Publishing iis_webdav = on/off
WWW Service iis_www = on/off
Application Server Console appsrv_console = on/off


Example IIS 6.0 answer file:

[Components]
aspnet = off
complusnetwork = off
dtcnetwork = off
bitsserverextensionsisapi = off
bitsserverextensionsmanager = off
iis_common = on
iis_ftp = on
fp_extensions = off
iis_inetmgr = on
iis_nntp = off
iis_smtp = on
iis_asp = on
iis_internetdataconnector = off
sakit_web = off
tswebclient = off
iis_serversideincludes = off
iis_webdav = off
iis_www = on
appsrv_console = on

[NetOptionalComponents]

[InternetServer]
PathFTPRoot=D:\Inetpub\Ftproot
PathWWWRoot=D:\Inetpub\Wwwroot

The above settings can be save to a text file (IIS60Config.txt in this example) and can be called with the following command:

Sysocmgr.exe /i:sysoc.inf /u:<SourceDir>\IIS60Config.txt /r /q


Removal: In order to uninstall the IIS 6.0 installation, create an answer file (IIS60Remove.txt in this example):

[Components]
aspnet = off
complusnetwork = off
dtcnetwork = off
bitsserverextensionsisapi = off
bitsserverextensionsmanager = off
iis_common = off
iis_ftp = off
fp_extensions = off
iis_inetmgr = off
iis_nntp = off
iis_smtp = off
iis_asp = off
iis_internetdataconnector = off
sakit_web = off
tswebclient = off
iis_serversideincludes = off
iis_webdav = off
iis_www = off
appsrv_console = off

[NetOptionalComponents]

The above settings were saved in a text file called IIS60Config.txt and can be called with the following command:

Sysocmgr.exe /i:sysoc.inf /u:<SourceDir>\IIS60Remove.txt /r /q
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Command Line
Sysocmgr.exe /?

/i:<master_oc_inf> - (required) Specifies the name of the master.inf. The installation source path is taken from here.

/u:<unattend_spec> - Specifies unattended operation parameters.

/r - Suppress reboot

/z - Indicates that args that follow are not OC args and should be passed to components

/n - Forces the specified master inf to be treated as new

/f - Indicates that all component installation states should be initialized as if their installers had never been run.

/c - Disallow cancel during final installation phase.

/x - Suppresses the 'initializing' banner.

/q - for use with /u. Runs the unattended installation without UI.

/w - for use with /u. If a reboot is required, prompt the user instead of automatically rebooting.

/l - Multi-Language aware installation.

Example:

This example will launch the installation in unattended mode suppressing a reboot.

Sysocmgr.exe /i:sysoc.inf /u:<SourceDir>\answer.txt /r /q
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Note
Create FTP Site

A FTP site can be created automatically by using the IIS FTP Site Management Script (iisftp.vbs).

Example:

This example will create a site called ftproot that points to the D:\ftp root directory.

%SystemRoot%\System32\cscript.exe //T:360 %SystemRoot%\System32\iisftp.vbs /create D:\ftp ftproot

Iisftp.vbs: IIS FTP site management script
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Command Line
Delete FTP Site:

The following command will delete the Default FTP site using the IIS FTP Site Management Script (iisftp.vbs).

%SystemRoot%\System32\cscript.exe //T:360 %SystemRoot%\System32\iisftp.vbs /delete "Default FTP Site"
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Command Line
Delete Default Web Site:

The following command will delete the Default Web Site using the IIS Web Site Management Script (iisweb.vbs).

%SystemRoot%\system32\cscript.exe //T:360 %SystemRoot%\system32\iisweb.vbs /delete "Default Web Site"
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Note
IIS Import/Export Web Sites and FTP Sites Configuration Scripts

Once the initial IIS 6.0 installation is complete, settings can be applied to the IIS instance using the Internet Information Services (IIS) Manager and then exported to an XML file. The XML files contain IIS metabase entries that can then be imported to other machines running IIS. It is important to remove all machine specific data from the exported XML file prior to importing onto another machine.

Export IIS Configuration

Web Sites: The following command is an example to export the base configuration for “Web Sites” to the c:\temp\Microsoft\IIS\6.0 directory naming the file wwwBaseConfig.xml:

%SystemRoot%\system32\cscript.exe %SystemRoot%\system32\iiscnfg.vbs /export /f c:\temp\Microsoft\IIS\6.0\wwwBaseConfig.xml /sp /LM/W3SVC /children

• /f specifies a unique name and location for the export file.
• /sp specifies the metabase keys to export. The parameter immediately after the /sp specifies the path of the Web site to export.
• /children exports all subkeys of the configuration.

FTP Sites: The following command is an example to export the base configuration for “FTP Sites” to the c:\temp\Microsoft\IIS\6.0 directory naming the file ftpBaseConfig.xml:

%SystemRoot%\system32\cscript.exe %SystemRoot%\system32\iiscnfg.vbs /export /f c:\temp\Microsoft\IIS\6.0\ftpBaseConfig.xml /sp /lm/MSFTPSVC /children

• /f specifies a unique name and location for the export file.
• /sp specifies the metabase keys to export. The parameter immediately after the /sp specifies the path of the ftp site to export.
• /children exports all subkeys of the configuration.

Import Configuration

Web Sites: The following command is an example to import the base configuration from the c:\temp\Microsoft\IIS\6.0\wwwBaseConfig.xml file to the /LM/W3SVC metabase location and subkeys.

%SystemRoot%\system32\cscript %SystemRoot%\system32\iiscnfg.vbs /import /f c:\temp\Microsoft\IIS\6.0\wwwBaseConfig.xml /sp /lm/W3SVC /dp /lm/W3SVC /children /merge

• /f specifies the path and file name of the XML source file.
• /sp specifies the location in the XML file of the keys being imported.
• /dp specifies where in the metabase the imported keys are placed.
• /children recursively imports the subkeys of the specified key.
• /merge combines the keys in the XML file with the existing metabase keys.

FTP Sites: The following command is an example to import the base configuration from the c:\temp\Microsoft\IIS\6.0\ftpBaseConfig.xml file to the /LM/MSFTPSVC metabase location and subkeys.

%SystemRoot%\system32\cscript %SystemRoot%\system32\iiscnfg.vbs /import /f c:\temp\Microsoft\IIS\6.0\ftpBaseConfig.xml /sp /lm/MSFTPSVC /dp /lm/MSFTPSVC /children /merge

• /f specifies the path and file name of the XML source file.
• /sp specifies the location in the XML file of the keys being imported.
• /dp specifies where in the metabase the imported keys are placed.
• /children recursively imports the subkeys of the specified key.
• /merge combines the keys in the XML file with the existing metabase keys.
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Note

Removing Machine Specific Data from XML Configuration Files:

When importing a metabase element to another computer, you must change or remove machine-specific and system-specific information in the import file before you use it, otherwise IIS cannot use these values.

Important

Never include password properties in import files. If you use an import file with a blank password property, the new computer subsequently stores encrypted properties as plain text.

Metabase properties that contain paths to resources in the file system might not match the paths on other computers. For example, the following properties might be written in the import file in the following way:

LogFileDirectory = "c:\windows\system32\logfiles"

Path = "c:\inetpub\ftproot"

HttpErrors = "400,*,FILE,c:\windows\help\iishelp\common\400.htm

more HTTP errors

InProcessIsapiApps = "c:\windows\system32\inetsrv\httpext.dll

more ISAPI applications

ScriptMaps = ".asp,c:\windows\system32\inetsrv\asp.dll,1,GET,HEAD,POST,TRACE

more script maps

Change the paths in bold above to the path used by the computer to which you want to import the metabase element. Search for other paths in your import file before using it.

Metabase properties that specify the IWAM and IUSR accounts might not match the user accounts used by other computers. If your import file contains these properties, delete or alter them so that their values do not overwrite the existing valid properties. These properties might be written in the import file in the following way:

<IIsWebService

Location = "/LM/MSFTPSVC"

WAMUserName = "AccountName"

AnonymousUserName = "AccountName">

The ServerBindings property, which is used to configure the port number for a site, might not be set the same way on another computer. However, you might want to import these settings to the new computer so that the computers will be configured the same way. The ServerBindings property is set at the site level, and can be written in the import file in the following way:

<IIsFtpServer

Location = "/LM/MSFTPSVC/1"

ServerBindings = ":21:" >

<IIsWebServer

Location = "/LM/W3SVC/1"

ServerBindings = ":80:">

Metabase properties that contain ACLs cannot be moved to another computer. If your import file contains these properties, delete them so that their values do not overwrite the existing valid properties. These properties might be written in the import file in the following way:

AdminACL = "LongNumber"

Metabase properties that contain passwords cannot be moved to another computer. If your import file contains properties with passwords, delete them so that their values do not overwrite the existing valid properties. These properties might be written in the import file in the following way:

<IIsWebService

Location = "/LM/W3SVC"

WAMUserPass = "LongNumber"

AnonymousUserPass = "LongNumber"

LogOdbcPassword = "LongNumber">

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Note
Windows SP2 and IIS 5.1 & 6.0

When you install SP2, Windows Firewall is enabled by default to help improve security. As a result, Web servers running Windows XP with SP2 will no longer be accessible from remote computers. For example, you will be unable to use Microsoft FrontPage® Server Extensions or SharePoint™ Team Services from Microsoft to browse or update Web sites.

You can make these applications accessible by opening the Internet Information Services (IIS) port TCP 80 on your computer.

To do this, at the command line, enter the following:

netsh firewall ipv4 set portopening proto=tcp port=XX WebServer_Description

XX represents the port number for the Web server. By default, this is 80.


See: http://www.microsoft.com/technet/prodtechnol/winxppro/deploy/relnsp2.mspx?pf=true
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment
117
Security
If you need to lock down the IIS download the IISlockdown tool from MS at: http://download.microsoft.com/download/iis50/Utility/2.1/NT45XP/EN-US/iislockd.exe

Use the command:
iislockd.exe /C /T:c:\temp\iislock to unpack the files to the temporary location.

Change the line UNATTEND=FALSE to UNATTEND=TRUE in the file called iislockd.ini (located in c:\temp\iislock\).

Run the file called iislockd.exe (it now runs silently).

You might want to change specific setting in the ini-file specific to your environment...!

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
Please log in to comment

Inventory Records (1)

View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.

Versions

Internet Information Server (IIS)

Version

6

Questions & Answers (1)

Questions & Answers related to Microsoft Internet Information Server (IIS)

2
ANSWERS

Blogs (1)

Blog posts related to Microsoft Internet Information Server (IIS)

Reviews (0)

Reviews related to Microsoft Internet Information Server (IIS)