Export (0) Print
Expand All
ABS
AND
ASC
COS
DAY
DDB
EXP
FV
IF
INT
LEN
LN
LOG
MAX
Me
MID
MIN
MOD
NOT
IS
NPV
ODD
OR
PI
PMT
PV
SIN
SLN
SUM
SYD
T
TAN
VAR
Expand Minimize

Configuring Two Virtual Servers to Host the Same Content

Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

You can install and configure Microsoft to allow your server farm to provide the same content to two sites. In this scenario, the content is shared by the two sites, not duplicated. For example, this type of configuration would be helpful when setting up an intranet and extranet configuration. This topic discusses configuring virtual servers to share content, using an intranet/extranet deployment as an example.

Important: This example does not contain explicit information about setting up firewalls or other methods of safeguarding data or resources in an extranet. To set up a more secure extranet, follow the guidelines in the Internet Information Services and Microsoft documentation.

Note: This is only one of several hosting choices for . For more information about hosting choices, see "Structuring the URL namespace" in Windows SharePoint Services Architecture .

Preparing the Servers

Before you can install and configure for both an intranet and an extranet, you must be sure you meet the hardware and software requirements. The following sections help you review the requirements.

Hardware and Software Requirements

To be able to set up in an intranet and extranet configuration, you must meet the following criteria:

  • The Web front-end servers must be running Microsoft (Standard, Enterprise, Datacenter, or Web Edition). Note that the hardware requirements for are the same as the installation requirements.

    • The Web front-end servers must be configured as Web servers (running Internet Information Services in IIS 6.0 worker process isolation mode) and must be running ASP.NET. For more information about installing and configuring IIS and ASP.NET, see the Family documentation.

    • The Web front-end servers must be using the NTFS file system. Microsoft Windows includes a conversion utility (Convert.exe) that you can use to convert an existing file allocation table (FAT) volume to NTFS without losing data.

  • The back-end servers must be running Microsoft SQL Server 2000 Service Pack 3 or later.

  • The client computers must be running Microsoft Internet Explorer 5 or later (best results with Microsoft Internet Explorer 5.5 or later) or Netscape Navigator 6.2 or later to use Web site features.

  • To complete the procedures that involve SQL Server in the following sections, you must be logged on using an account that is a member of the db_owner role in SQL Server.

  • To complete the procedures that involve IIS in the following sections, you must be logged on as a member of the Administrators group on the local computer, or you must be logged on using an account that is both a member of the SharePoint administrators group and that has been granted permissions to administer IIS.

For a complete list of hardware and software requirements, see Hardware and Software Requirements .

Planning for Scale

You can use the same Web front-end server to host both your intranet and extranet virtual servers, or you can split them across two separate servers. If you anticipate a heavy load on either your intranet or extranet, it is recommended that you use separate Web front-end servers for each environment, so that heavy use of your extranet server does not affect the availability of your intranet server and vice versa. This topic describes the steps to use separate Web front-end servers for each environment. You can also use multiple Web front-end servers to host both virtual servers, as in a standard server farm, to reduce potential downtime. For more information about server farms, see Server Farm with Multiple Host Names Deployment .

Preparing the Database Back-end Servers

To set up your database back-end servers, you must perform the following steps.

  • Install SQL Server 2000, Service Pack 3.

    You can use SQL Server 2000 Standard or Enterprise edition with . For more information about installing SQL Server, see the SQL Server 2000 documentation.

  • Set a strong password for your SQL Server administration account.

    You must know both the administrator user account and password to be able to connect between on the Web front-end servers and SQL Server on the back-end servers. It is recommended that you set a strong password for the administration account. If you are using Windows Authentication (recommended), then you should use a domain account with permissions to create databases in SQL Server. If you are using SQL Server authentication, this means that the "sa" account should have a strong password. For more information about setting the administrator username and password, see the SQL Server 2000 documentation.

  • Configure the authentication method for connections between the Web servers and SQL Server.

    For better security in your server farm, it is recommended that you use Windows NT authentication, rather than SQL Server authentication, for connections between your Web front-end servers and the database back-end servers. Windows NT authentication uses a domain user account to control access to SQL Server, rather than storing credentials in the registry and passing them across the network as in SQL Server authentication.

You configure the authentication method for SQL Server by using the SQL Server Enterprise Manager.

Configure Authentication for SQL Server

  1. On the database back end servers, click Start , point to All Programs , point to Microsoft SQL Server , and then click Enterprise Manager .

  2. Click the plus sign (+) next to Microsoft SQL Servers .

  3. Click the plus sign (+) next to SQL Server Group .

  4. Right-click the SQL server name, and click Properties .

  5. In the Properties dialog, click the Security tab.

  6. Under Authentication , click Windows only , and then click OK .

Configuring the Intranet Front-end Server

To configure your intranet Web front-end server, you must perform the following steps.

  • Configure the intranet server as a Web server.

    You must be running Internet Information Services (IIS) 6.0 on your Web server, and you must set it to run in IIS 6.0 worker process isolation mode instead of IIS 5.0 isolation mode. To communicate with SQL Server 2000 on the back-end servers, you must also configure the front-end Web server to use the TCP/IP protocol, rather than Named Pipes (the default).

  • Create the intranet virtual server and configure the authentication method.

    If you are not using the default virtual server in IIS, you must create a new virtual server and map it to the host name of the server that will provide the content. The simplest way to set up an extranet is to use the default virtual server in IIS. Whichever method you choose, you must specify the authentication method (Integrated Windows authentication in this case) to use for the virtual server.

  • Install in the server farm configuration and create the administration virtual server and configuration database.

    You must install on each Web front-end server. Using the remote SQL Server option allows you to install without also installing Microsoft SQL Server 2000 Desktop Engine (Windows) (WMSDE). You must also create the administration virtual server and configuration database. You only need to create the configuration database when you configure the first Web front-end server; for subsequent front-end servers (including the extranet server), you can simply connect to the database.

  • Extend the intranet virtual server.

    Before you can create sites, you must extend the intranet virtual server. The intranet virtual server is connected to the same content databases as the extranet virtual server, so that they provide the same site content.

To perform these steps for a server farm, it is recommended that you use the command-line administration tool, Stsadm.exe. For more information about using Stsadm.exe, see Introducing the Administration Tools for .

Configuring the Intranet Server as a Web Server

IIS is not enabled by default in . To make your front-end server into a Web server, you must enable IIS.

Enable IIS and Configure it to use IIS 6.0 worker process isolation mode

  1. Click Start , point to All Programs , point to Administrative Tools , and then click Manage Your Server .

  2. On the Manage Your Server page, click Add or remove a role .

  3. On the Preliminary Steps pane, click Next .

  4. On the Server Role pane, click Application server (IIS, ASP.NET) , and then click Next .

  5. On the Web Application Server Options pane, accept the default of ASP.Net and then click Next .

  6. On the Summary of Selections pane, click Next .

  7. Click Finish .

  8. Click Start , point to All Programs , point to Administrative Tools , and then click Internet Information Services (IIS) .

  9. In Internet Information Services manager, click the plus sign next to the server name, and then right-click the Web Sites folder and select Properties .

  10. In the Properties dialog box, click the Service tab.

  11. In the Isolation mode section, clear the Run WWW service in IIS 5.0 isolation mode check box, and then click OK .

    Note: The Run WWW service in IIS 5.0 isolation mode checkbox is only selected if you have upgraded to IIS 6.0 on from IIS 5.0 on Windows 2000. New installations of IIS 6.0 use IIS 6.0 worker process isolation mode by default.

Creating the Intranet Virtual Server and Configuring Authentication

When IIS is configured and ready to work with SQL Server, you can create the virtual server you need to host the intranet sites.

Create a Virtual Server

  1. Click Start , point to Programs , point to Administration Tools , and then click Internet Information Services .

  2. Click the plus sign (+) next to the server name you want to add a virtual server to.

  3. Right-click the Web Sites folder, click New , and then click Web site .

  4. Click Next .

  5. In the Description box, type the description of your virtual server, and then click Next .

  6. In the Enter the IP address to use for this Web site box, click All Unassigned .

    Note: You can create multiple virtual servers by using IIS Host Headers with All Unassigned if necessary, but IP-bound virtual servers are not supported.

  7. In the TCP port this web site should use (Default: 80) box, type the port number to assign to the virtual server.

    You do not need to assign a host header, because the hosting is being handled through .

  8. Click Next .

  9. In the Path box, type or browse to the path on your hard disk where the site content will go.

  10. If you do not want to allow anonymous access to your virtual server, clear the Allow anonymous access to this Web site check box.

  11. Click Next .

  12. On the Permissions panel, select the permissions to use, and then click Next .

    The default permissions, Read and Run Scripts (such as ASP) , are recommended. The Execute (such as ISAPI applications or CGI) permission will be added automatically to the appropriate folders by .

  13. Click Finish .

Now you can configure the authentication method to use for the intranet virtual server.

Configure the Authentication Method for the Intranet Virtual Server

  1. On the intranet Web front-end server, in Internet Information Services , right-click the virtual server that will be used for the intranet site, and then click Properties .

  2. On the Directory Security tab, under Authentication and access control , click Edit .

  3. Select the Integrated Windows authentication check box, and clear all other authentication method check boxes.

  4. Click OK to close the Authentication Methods dialog box.

  5. Click OK again to close the Properties dialog box.

Installing and Configuring on the Intranet Web Front-end Server

You must install in the server farm configuration. To do so, you use setupsts.exe command with the remotesql property on the command line.

Install with the Remote SQL Server Option

  1. Download STSV2.exe to your computer.

    You can download STSV2.exe from the Microsoft Web site.

  2. Run STSV2.exe to extract the installation files.

  3. When the installation starts, click Cancel .

  4. Click Start , and then click Run .

  5. In the Open box, type c:\folder\setupsts.exe remotesql=yes (where c:\folder is the path to the Setupsts.exe file on your local computer).

    For example, if you installed the US English version of STSV2.exe, then the folder is c:\program files\STS2Setup_1033.

  6. Click OK .

    The Setup program opens.

  7. On the End-User License Agreement page, review the terms, and then select the I accept the terms in the License Agreement check box, and then click Next .

  8. On the Type of Installation page, click Server Farm , and then click Next .

  9. On the Summary page, verify that only will be installed, and then click Install .

  10. Setup runs and installs .

  11. Follow the prompts to install using the Server Farm installation option.

After setup, you can create the administration virtual server and configuration database. If you want to set up a server farm environment, you can use the command line administration tool to create the configuration database and include the -hh parameter. This is an advanced scenario, and is not covered in this topic. For more information, see Server Farm with Multiple Host Names Deployment .

Create the Administration Virtual Server from the Command Line

  1. Open a command prompt window, and navigate to the \Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\bin folder.

  2. Run the following command to create the administration virtual server:

    stsadm.exe -o setadminport -port <port> -admapcreatenew -admapidname <id for application pool> -admapidtype <configurableid/NetworkService/LocalService/LocalSystem> -admapidlogin <user account for the application pool> -admapidpwd <password>
    

    Note that you can use any unused port between 1023 and 32767. The application pool account must have database owner (DBO) rights to the SQL Server computer to be able to create the configuration database. It is recommended that you use a dedicated domain account for this account, rather than a user's login account. Also, it is recommended that you use the same account for each application pool that hosts the same content.

If you have used a domain account that does not already have database creation rights in SQL Server, you can give the account this access in SQL Server Enterprise Manager. This is a one-time only change. Once you have granted database creation permissions to the account used by the administration virtual server, this account can create any subsequent databases. You do not need database creation rights to connect to a configuration database, which you will do when you set up the Web front-end server for the extranet.

Grant Database Creation Rights in SQL Server

  1. On your SQL Server computer, click Start , point to Programs , point to Microsoft SQL Server , and then click Enterprise Manager .

  2. In Enterprise Manager , click the plus sign (+) next to Microsoft SQL Servers , click the plus sign (+) next to SQL Server Group , and then click the plus sign next to your SQL Server.

  3. Click the plus sign (+) next to Security , and then right-click Logins , and click New Login .

  4. In the Name box, type the account in the form DOMAIN\name.

  5. Click the Server Roles tab.

  6. In the Server Role list, select the Security Administrators and Database Creators check boxes, and then click OK .

After you configure the administrative virtual server (and grant SQL Server rights to the new application pool account, if necessary), you must restart Internet Information Services (IIS), by typing iisreset on the command line. After IIS is reset, you can continue configuring to work with your remote SQL Server.

Create the Configuration Database from the Command Line

  • Run the following command to create the configuration database:

    stsadm.exe -o setconfigdb -ds <database server name> -dn sts_config
    

The syntax above is for Windows authentication. If you are using SQL Server authentication, you must also specify the -du and -dp parameters with the database username and password. To connect to the configuration database from subsequent Web front-end servers, use the following syntax:

stsadm.exe -o setconfigdb -ds <database server name> [-du <database user>-dp <password>] -dn sts_config

Create the Administration Application Pool and Configuration Database using HTML Administration Pages

  1. When Setup finishes, you are taken to the Configure Admin Virtual Server page.

  2. In the Application Pool section, select Create a new application pool .

  3. Under Select a security account for this application pool , select Configurable .

  4. In the User name box, type the domain account to use for the application pool.

    This account must have database owner (DBO) rights to the SQL Server computer to be able to create the configuration database. It is recommended that you use a dedicated account for this account, rather than a user's login account. Also, it is recommended that you use the same account for each application pool that hosts the same content.

  5. In the Password box, type the password for the account, and then confirm it, and click OK .

    The application pool is created, and you are taken to a confirmation page. You must restart IIS to accept the change.

  6. After restarting IIS, click the link to continue, and on the Create Configuration Database page, in the Configuration Database section, enter the server name and database name to use.

  7. Select Use Windows integrated authentication (more secure, recommended) .

  8. In the Active Directory Account Creation section, select Users already have domain accounts if you are using a Windows domain, or Automatically create active directory accounts for users of this site if you are using Active Directory outside of a Windows domain.

  9. If you selected Automatically create active directory accounts for users of this site, you must fill in the Active Directory Domain and Organization Unit information.

  10. Click Submit .

  11. On the SharePoint Central Administration page, under Server Configuration , click Set default content database server .

  12. On the Content Database Server page, in the Content Database Server section, enter the server name, administrator account username, and password.

  13. Click Submit .

Extending the Intranet Virtual Server

With the administration virtual server and configuration database in place, you can extend the virtual server to host the intranet sites. You can use either the command line or HTML Administration pages to extend the virtual server.

Extend the Virtual Server using the Command Line

  1. Open a command prompt window, and navigate to the \Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\bin folder.

  2. Run the following command to extend the intranet virtual server:

    stsadm.exe -o extendvs -url http://servername -ownerlogin <DOMAIN\username> -owneremail <e-mail address> [-du <database user> -ds <database server> -dn <database name> -dp <database password> -lcid <locale ID> -sitetemplate <template name> -apcreatenew -apidname <application pool name> -apidtype <configurableid/NetworkService/LocalService/LocalSystem> -apidlogin <DOMAIN\username> -apidpwd <password>]
    

Note that while the apid... parameters are optional, it is recommended that you create a new application pool for the virtual server. Use a dedicated application pool account, not a user login account. The application pool account for a virtual server does not need database owner rights on the SQL Server computer. Note that the -du and -dp parameters are not needed if you are using Windows authentication to connect to SQL Server.

Extend the Virtual Server using HTML Administration Pages

  1. On the SharePoint Central Administration page click Extend or upgrade virtual server .

  2. On the Virtual Server List page, click the name of the virtual server to extend.

  3. On the Extend Virtual Server page, in the Provisioning Options section, select Extend and create a content database .

  4. In the Application Pool section, select Create a new application pool .

  5. Under Select a security account for this application pool , select Configurable .

  6. In the User name box, type the domain account to use for the application pool.

    It is recommended that you use a dedicated account for this account, rather than a user's login account. Also, it is recommended that you use the same account for each application pool that hosts the same content.

  7. In the Password box, type the password for the account, and then confirm it.

  8. In the Site Owner section, in the Account name box, type the user name for the site owner (in the format DOMAIN\username if the username is part of a Windows domain group).

  9. In the E-mail address box, type the e-mail address that corresponds to the account.

  10. In the Database Settings section, enter the following database connection information:

    • In the Database server box, type the server name for your SQL Server.

    • In the Database name box, type the name to use for your content database.

  11. If you want to specify a path for the URL, in the Custom URL path box, type the path to use.

  12. If you are using quotas, select a template in the Select a quota template box of the Quota Settings section.

  13. In the Site Language section, select the language to use.

  14. Click OK .

Note: For a basic test scenario where you are hosting the same content from two virtual servers, you can create a second virtual server on the intranet front-end server and extend it using the Extend and connect to an existing content database . On the Extend and Connect to an Existing Content Database page, select the first virtual server you extended. When you click OK , the content will be hosted from both virtual servers.

Configuring the Extranet Front-end Server

To configure your extranet Web front-end server, you must perform the following steps.

  • Configure the server as a Web server.

    You must be running Internet Information Services (IIS) 6.0 on your Web server, and you must set it to run in IIS 6.0 worker process isolation mode instead of IIS 5.0 isolation mode.

  • Switch to using the TCP/IP protocol for the connections between the Web servers and SQL Server.

    To communicate with SQL Server 2000 on the back-end servers, you must configure the front-end Web servers to use the TCP/IP protocol, rather than Named Pipes (the default).

  • Create a virtual server and configure the authentication method.

    Before you can create sites for your extranet, you must create the virtual server to contain them in IIS, and specify the authentication method to use (Basic authentication with Secure Sockets Layer in this case).

  • Install in the server farm configuration.

    You must install on each Web front-end server. Using the remote SQL Server option allows you to install without also installing Microsoft SQL Server 2000 Desktop Engine (Windows) (WMSDE). You must also create an application pool for the extranet sites and connect to the configuration database after installation.

  • Extend the virtual server.

    Before you can create sites, you must extend the extranet virtual server. The extranet virtual server is connected to the same content databases as the intranet virtual server, so that they provide the same site content.

To perform these steps for a server farm, it is recommended that you use the command-line administration tool, Stsadm.exe. For more information about using Stsadm.exe, see Introducing the Administration Tools for .

IIS is not enabled by default in . To make your front-end servers into Web servers, you must enable IIS.

Enable IIS and configure it to use IIS 6.0 worker process isolation mode

  1. Click Start and then click Manage Your Server .

  2. On the Manage Your Server page, click Add or remove a role .

  3. On the Preliminary Steps pane, click Next .

  4. On the Server Role pane, click Application server (IIS, ASP.NET) , and then click Next .

  5. On the Web Application Server Options pane, accept the default of ASP.Net and then click Next .

  6. On the Summary of Selections pane, click Next .

  7. Click Finish .

  8. Click Start , point to Administrative Tools , and then click Internet Information Services (IIS) .

  9. In Internet Information Services manager, click the plus sign next to the server name, and then right-click the Web Sites folder and select Properties .

  10. In the Properties dialog box, click the Service tab.

  11. In the Isolation mode section, clear the Run WWW service in IIS 5.0 isolation mode check box, and then click OK .

When IIS is configured and ready to work with SQL Server, you can create the virtual server you need to host the extranet sites.

Create a Virtual Server

  1. Click Start , point to Programs , point to Administration Tools , and then click Internet Information Services .

  2. Click the plus sign (+) next to the server name you want to add a virtual server to.

  3. Right-click the Web Sites folder, click New , and then click Web site .

  4. Click Next .

  5. In the Description box, type the description of your virtual server, and then click Next .

  6. In the Enter the IP address to use for this Web site box, choose All Unassigned .

    Note: You can create multiple virtual servers using IIS Host Headers with All Unassigned if necessary, but IP bound virtual servers are not supported.

  7. In the TCP port this web site should use (Default: 80) box, type the port number to assign to the virtual server.

  8. In the Host Header for this site (Default: None) box, type the header you want to use, and then click Next .

  9. In the Path box, type or browse to the path on your hard disk where the site content will go.

  10. Clear the Allow anonymous access to this Web site check box, and then click Next .

  11. On the Permissions panel, select the permissions to use, and then click Next .

    If other users are allowed to contribute to the site, you must select at least the Read , Write , and Browse check boxes. If your virtual server allows scripts to be run, you must also select the Run scripts (such as ASP) check box. If you want to allow Internet Server Application Programming Interface (ISAPI) applications or Common Gateway Interface (CGI) scripts to be used on your virtual server, you must also select the Execute (such as ISAPI applications or CGI) check box.

  12. Click Finish .

Now you can configure the authentication method to use for the extranet virtual server.

Configure the Authentication Method for the Extranet Virtual Server

  1. On the extranet Web front-end server, in Internet Information Services , right-click the virtual server that will be used for the extranet site, and then click Properties .

  2. On the Directory Security tab, under Authentication and access control , click Edit .

  3. Select the Basic authentication check box, and clear all other authentication method check boxes.

  4. Click OK to close the Authentication Methods dialog box.

  5. On the Directory Security tab, under Secure communications , click Edit .

  6. On the Secure Communications dialog box, select the Require secure channel (SSL) check box, and then click OK .

  7. Click OK again to close the Properties dialog box.

Note: You must have a certificate before you can enable SSL. For more information about SSL certificates, see the topics About Certificates and Setting Up SSL on Your Server in IIS 6.0 online Help. For more information about IIS authentication methods, see the topic About authentication in IIS 6.0 online Help.

After you have configured the authentication method, you can install .

Installing and Configuring on the Extranet Web Front-end Server

You must install in the server farm configuration. To do so, you use setupsts.exe command with the remotesql property on the command line.

Install with the Remote SQL Server Option

  1. Download STSV2.exe to your computer.

    You can download STSV2.exe from the Microsoft Web site.

  2. Run STSV2.exe to extract the installation files.

  3. When the installation starts, click Cancel .

  4. Click Start , and then click Run .

  5. In the Open box, type c:\folder\setupsts.exe remotesql=yes (where c:\folder is the path to the Setupsts.exe file on your local computer).

    For example, if you installed the US English version of STSV2.exe, then the folder is c:\program files\STS2Setup_1033.

  6. Click OK .

    The Setup program opens.

  7. On the End-User License Agreement page, review the terms, and then select the I accept the terms in the License Agreement check box, and then click Next .

  8. On the Type of Installation page, click Server Farm , and then click Next .

  9. On the Summary page, verify that only will be installed, and then click Install .

  10. Setup runs and installs .

After setup, you can create the administration virtual server and connect to the configuration database. You can use either the command line or HTML Administration pages to create the administration virtual server and connect to the configuration database.

Set the Application Pool for the Administration Virtual Server and Connect to the Configuration Database from the Command Line

  1. Open a command prompt window, and navigate to the \Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\bin folder.

  2. Run the following command to create the administration virtual server:

    stsadm.exe -o setadminport -port <port> -admapcreatenew -admapidname <id for application pool> -admapidtype configurableid -admapidlogin <DOMAIN\username> -admapidpwd <password>
    

    Note that you can use any unused port between 1023 and 32767. It is recommended that you use a dedicated account for the application pool account, rather than a user's login account. Also, it is recommended that you use the same account for each application pool that hosts the same content.

  3. Restart IIS by running iisreset on the command line.

  4. Run the following command to connect to the configuration database:

    stsadm.exe -o setconfigdb -ds <database server name> [-du <database user> -dp <password>] -dn sts_config
    

The syntax above is for Windows authentication. If you are using SQL Server authentication, you must also specify the -du and -dp parameters with the database username and password.

Set the Application Pool for the Administration Virtual Server and Connect to the Configuration Database using HTML Administration Pages

  1. When Setup finishes, you are taken to the Security and Configuration Database page.

  2. In the Application Pool section, select Define a new application pool .

  3. Under Select a security account for this application pool, select Configurable .

  4. In the User name box, type the domain account to use for the application pool.

    This account must have database owner (DBO) rights to the SQL Server computer to be able to create the configuration database. It is recommended that you use a dedicated account for this account, rather than a user's login account. Also, it is recommended that you use the same account for each application pool that hosts the same content.

  5. In the Password box, type the password for the account, and then confirm it, and click OK .

    The application pool is created, and you are taken to a confirmation page. You must restart IIS to accept the change. To restart IIS, type iisreset on the command line.

  6. After restarting IIS, click the link to continue, and on the Create Configuration Database page, in the Configuration Database section, enter the server name and database name for the existing configuration database.

  7. Select Use Windows integrated authentication (more secure, recommended) .

  8. Select the Connect to existing database check box.

  9. In the Active Directory Account Creation section, select Users already have domain accounts if you are using a Windows domain, or Automatically create active directory accounts for users of this site if you are using Active Directory outside of a Windows domain.

  10. If you selected Automatically create active directory accounts for users of this site, you must fill in the Active Directory Domain and Organization Unit information.

  11. Click Submit .

  12. On the SharePoint Central Administration page, under Central Configuration Settings and Defaults , click Set default content database server .

  13. On the Content Database Server page, in the Content Database Server section, enter the server name, administrator account username, and password.

  14. Click Submit .

Extending the Extranet Virtual Server

With the administration virtual server and configuration database in place, you can extend the virtual server to host the extranet sites. You can use either the command line or HTML Administration pages to extend the virtual server.

Extend the extranet virtual server

  1. Open a command prompt window, and navigate to the \Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\bin folder.

  2. Run the following command to extend the extranet virtual server.

    stsadm.exe -o extendvsinwebfarm -url https://www.servername.extranet.com -vsname <virtual server name> [-apcreatenew -adpidname <application pool name> -apidtype configurableid -apidlogin <DOMAIN\name> -apidpwd <password>]
    

    The -vsname parameter is the IIS name of the internal virtual server you extended earlier. For example, if you are using a site named "mysite" in IIS, then the -vsname value would be mysite . It is recommended that you create a new application pool for the virtual server. Use a dedicated application pool account, not a user login account. The application pool account for a virtual server does not need database owner rights on the SQL Server computer. Note that the -du and -dp parameters are not needed if you are using Windows authentication to connect to SQL Server.

Extend the Virtual Server using HTML Administration Pages

  1. Click Start , point to Programs , point to Administration Tools , and then click SharePoint Central Administration .

  2. Click Extend or upgrade virtual server .

  3. On the Virtual Server List page, click the virtual server you want to extend.

  4. On the Extend Virtual Server page, click Extend and connect to existing content database .

  5. On the Extend and Connect to Existing Content Database page, in the Server Mapping section, in the Host name or IIS virtual server name box, select the name of the host or virtual server that you want to use.

  6. In the Application Pool section, select Create a new application pool .

  7. Under Select a security account for this application pool , select Configurable .

  8. In the User name box, type the domain account to use for the application pool.

    It is recommended that you use a dedicated account for this account, rather than a user's login account. Also, it is recommended that you use the same account for each application pool that hosts the same content.

  9. In the Password box, type the password for the account, and then confirm it.

  10. Click Submit .

Creating Sites

After following the steps above, you are ready to create sites for your users. This is the last step in the process for setting up your intranet/extranet server farm. After this step, you can start adding users and managing the sites.

Create a Site

  1. Open a command prompt window, and navigate to the \Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\bin folder.

  2. Run the following command to create a site:

    stsadm.exe -o createsite -url <url> -ownerlogin <DOMAIN\username> -owneremail <email address> [-ownername <display name> -lcid <lcid> -sitetemplate <site template> -title <title> -description <site description>]
    

Repeat this step for every site you want to create. Note that because both your intranet and extranet virtual servers connect to the same content database, the same sites are available in each environment.

Next Steps

Your server farm is now set up for serving the same content on both an intranet and extranet. You can start adding users and managing sites, or you can perform the following optional, but recommended steps:

  • It is recommended that you help protect your administration virtual server by either using a firewall to block access, or by using Secure Sockets Layer (SSL) for the port. For more information, see Configuring Authentication .

  • As your sites increase in number and size, you will want to be able to add content databases or change connections to the content databases. For more information about content databases, see content databases.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft