Microsoft Windows SharePoint Services
HomeBackForwardPrint

Show AllShow All

Extend a virtual server

Extend a virtual server

Before extending a virtual server, you must first make sure that you've created it in Internet Information Services (IIS). Also, if you are adding a server to a farm, you must connect the content database to the virtual server before extending.

Note  To complete this procedure, 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.

Create a virtual server in IIS

If you are adding a new virtual server to an existing server, you must create the virtual server in IIS first. To do this, create a folder on your hard disk (usually under the \Inetpub folder) to store the virtual server's files and then add the virtual server in IIS.

How?

  1. Click Start, point to All Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
  2. Click the plus sign (+) next to the server name to which you want to add a virtual server.
  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, select the IP address that you want to use, or use the default (All Unassigned).
  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 Microsoft Windows SharePoint Services handles the hosting.

  8. Click Next.
  9. In the Path box, type (or browse to) the path on your hard disk where the site content will reside.
  10. To disallow 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. Windows SharePoint Services adds the Execute (such as ISAPI applications or CGI) permission automatically to the appropriate folders.

  13. Click Finish.

For more information about creating Web sites on servers running the Microsoft Windows Server 2003, see Help for IIS.

Connecting to a configuration database (server farm only)

If you are adding a server to a server farm, and provisioning the first virtual server for that server, you must connect to the configuration database for your server farm before you can extend the virtual server. To connect to a configuration database, use the Set Configuration Database Server page. For more information, see Specifying configuration database settings. After you have connected to the configuration database, you can extend the virtual server.

Remove FrontPage Server Extensions (if installed)

Note  If you wish to preserve the content from your FrontPage 2002 Server Extensions-based site, use the Microsoft SharePoint Migration tool (smigrate.exe) to migrate the content to your new Windows SharePoint Services-based site before uninstalling. For information on smigrate, see About migrating Web sites.

  1. Click Start, and then click Run.
  2. In the Run window, type cmd and then click OK.
  3. Change to the directory where FrontPage Server Extensions are installed. For example:

    cd ..\..\program files\common files\microsoft shared\web server extensions\50\bin

  4. Type the owsadm.exe command to uninstall FrontPage Server Extensions:

    owsadm.exe -o fulluninstall -p <port number>

    Where "<port number>" represents the port number used by the virtual server running FrontPage Server Extensions.

Extend and create a content database by using SharePoint Central Administration

  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 either Use an existing application pool or Create a new application pool.

    Notes

    • When using Windows SharePoint Services with SharePoint Portal Server, re-use the MSSharePointPortalServerAppPool application pool created by SharePoint Portal Server. This application pool can be managed by clicking on Configure Server Farm Account Settings in SharePoint Portal Server Central Administration.
    • In most other installations, it is recommended that you create a new application pool for each virtual server, so that they run in separate processes. This application pool should use a domain account, but it does not need to have database creation rights in Microsoft SQL Server — the administration virtual server account creates any databases that are required.

  5. If you selected Use an existing application pool, select the application pool to use. If you selected Create a new application pool, type the new application pool name, user name, and password to use.

  6. In the Site Owner section, in the User 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).
  7. In the E-mail box, type the e-mail address that corresponds to the account.
  8. In the Database Information section, type the following database connection information or select the Use default content database server check box:
    • In the Database server box, type the server name for your server computer.
    • In the Database name box, type the name to use for your content database.
  9. To specify a path for the URL, in the Custom URL path box, type the path to use.
  10. If you are using quotas, select a template in the Select a quota template box of the Quota Settings section.
  11. In the Site Language section, select the language to use.
  12. Click OK.

The virtual server is extended, a site is created at the root of the virtual server, and the browser window returns to the Virtual Server Settings page, where you can configure default settings for new top-level Web sites.

When you connect to an existing content database, you do not need to create a top-level Web site. After you extend the virtual server, the virtual server hosts the existing sites in the database.

Extend and connect to an existing content database by using SharePoint Central Administration

  1. Click Start, point to All Programs, point to Administrative 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 that 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 either Use an existing application pool or Create a new application pool.

    Notes

    • When using Windows SharePoint Services with SharePoint Portal Server, re-use the MSSharePointPortalServerAppPool application pool created by SharePoint Portal Server. This application pool can be managed by clicking on Configure Server Farm Account Settings in SharePoint Portal Server Central Administration.
    • In most other installations, it is recommended that you create a new application pool for each virtual server, so that they run in separate processes. This application pool should use a domain account, but it does not need to have database creation rights in Microsoft SQL Server — the administration virtual server account creates any databases that are required.

  7. If you selected Use an existing application pool, select the application pool to use. If you selected Create a new application pool, type the new application pool name, user name, and password to use.

  8. Click Submit.

The virtual server is extended and can now provide the same content as the other virtual servers pointing to that content database. You can add a new top-level Web site to the virtual server if you need to, and it will be hosted by any virtual server that is connected to the content database.

Extending a virtual server from the command line

You can extend virtual servers from the command line by using the extendvs operation. The extendvs operation allows you to extend a virtual server and either connect to an existing content database or create a new content database, specify the language for the top-level Web site, and specify a template to use for the top-level Web site. The extendvs operation takes the following required parameters: url, ownerlogin, owneremail and the following optional parameters: ownername, databaseserver (ds), databaseuser (du), databasepassword (dp), databasename (dn), lcid, sitetemplate, donotcreatesite, apcreatenew, apidname, apidtype, apidlogin, and apidpwd.

The lcid parameter allows you to specify a language to use for the default top-level Web site. For example, to specify U.S. English as the language to use, type -lcid 1033 on the command line. If you do not specify a locale ID (LCID) by using the lcid parameter, the language of the server is used for the default top-level Web site.

The donotcreatesite parameter allows you to extend a virtual server and create a content database without a top-level Web site. Use this parameter when you are setting up a server farm and hosting sites with URLs like http://server_name/site1, http://server_name/site2, and so on. (To use this site naming scheme, you must create a wildcard inclusion for the path under which you create the sites. For more information about inclusions, see About managed paths.)

The sitetemplate parameter allows you to extend a virtual server, create a top-level Web site, and apply a site template to the top-level Web site during site creation. If you do not use the sitetemplate parameter, the site owner can choose a site template when he or she first goes to the site.

To extend a virtual server and use the default content database server and default application pool, use the following syntax:

Stsadm –o extendvs -url <url> -ownerlogin DOMAIN\username -owneremail 
 someone@example.com [-ownername <full name>]

To extend a virtual server, specify a content database name and server, and create a new application pool, use the following syntax:

stsadm -o extendvs -url <url> -ownerlogin DOMAIN\user -owneremail 
 someone@example.com [-ownername <full name>] -ds <database server name> 
 [-du <database user name> -dp <password>] -dn <database name> 
 -lcid <lcid> -sitetemplate sts -apcreatenew -apidname <application pool name> 
 -apidtype <configurableid/NetworkService/LocalService/LocalSystem> 
 -apidlogin <DOMAIN\name> -apidpwd <password>

Note that you do not need the -du and -dp parameters if you are using Windows authentication to connect to the SQL Server databases.

To extend a virtual server and create a new application pool, use the following syntax:

stsadm -o extendvs -url <url> -ds <database server name> 
 [-du <database user name> -dp <password>] -dn <database name> 
 -ownerlogin <owner login as DOMAIN\username> -owneremail <e-mail address 
 as someone@example.com> -ownername <owner's full name as "Owner 
 Name"> -lcid <lcid>

If you are in a server farm environment, you can use the extendvsinwebfarm operation. The extendvsinwebfarm operation uses the following syntax:

stsadm -o extendvsinwebfarm -url <url> -vsname <virtualservername>
 [-apcreatenew] [-apidname <app pool id>]
 [-apidtype <configurableid/NetworkService/LocalService/LocalSystem>]
 [-apidlogin <app pool user account>]
 [-apidpwd <app pool password>]

Related Topics

Specify configuration database settings
Specify content database settings
Configure a virtual server
Create a site
©2003 Microsoft Corporation. All rights reserved.