Export (0) Print
Expand All
0 out of 1 rated this helpful - Rate this topic

Extendvs: Stsadm operation (Windows SharePoint Services)

SharePoint 2007

Updated: January 10, 2008

Applies To: Windows SharePoint Services 3.0

Updated: 2008-01-10

Operation name: Extendvs

Description

Extends a Windows SharePoint Services 3.0 Web application and creates a new content database.

ImportantImportant:

The account that you use to run the Stsadm command-line tool must be a member of the Administrators group on the local computer. Because this operation affects a content or configuration database, you must also be a member of the following fixed server roles in SQL Server: dbcreator.

Syntax

stsadm -o extendvs

   -url <URL name>

   -ownerlogin <domain\name>

   -owneremail <someone@example.com>

   [-exclusivelyusentlm]

   [-ownername <display name>]

   [-databaseuser <database user name>]

   [-databaseserver <database server name>]

   [-databasename <database name>]

   [-databasepassword <database password>]

   [-lcid <language>]

   [-sitetemplate <site template>]

   [-donotcreatesite]

   [-description]

   [-sethostheader]

   [-apidname <application pool name>]

   [-apidtype {configurableID | NetworkService}]

   [-apidlogin <domain\name>]

   [-apidpwd <application pool password>]

   [-allowanonymous]

Parameters

Parameter name and (short form) Value Required? Description

url

A valid URL name, such as http://server_name

Yes

The name of the Web application.

ownerlogin

A valid Windows user name that must be qualified with a domain name, for example, domain\name

Yes

The site owner's user account.

owneremail

A valid e-mail address, in the form someone@example.com

Yes

The site owner's e-mail address.

exclusivelyusentlm

<none>

No

Specifies to exclusively use NTLM authentication instead of Negotiate (Kerberos). Kerberos requires the application pool account to be a network service and to be configured by the domain administrator. NTLM authentication works with any application pool account and the default domain configuration.

ownername

A valid display name, such as "John Smith"

No

The display name of the Web application owner.

databaseuser (du)

A valid user name, such as domain\username

No

The administrator user name for the Microsoft SQL Server database.

databaseserver (ds)

A valid database server, such as "DS"

No

The server on which to create the content database. The default value is the local computer name.

databasename (dn)

A valid database name, such as "DN"

No

The name of the SQL Server database used for Windows SharePoint Services data.

databasepassword (dp)

A valid password that adheres to your business policy

No

The password that corresponds to the administrator user name for the SQL Server database.

lcid

A valid locale ID, such as "1033" for English

No

The local language ID.

NoteNote:

You must specify this parameter when using a non-English template.

sitetemplate (st)

Valid values available in a default installation include:

  • STS#0: Team Site

  • STS#1: Blank Site

  • STS#2: Document Workspace

  • MPS#0: Basic Meeting Workspace

  • MPS#1: Blank Meeting Workspace

  • MPS#2: Decision Meeting Workspace

  • MPS#3: Social Meeting Workspace

  • MPS#4: Multipage Meeting Workspace

    NoteNote:

    If you added a template to the central template gallery, you must specify the template name as _GLOBAL_#number, where number refers to the template ID.

No

Specifies the type of template to be used by the newly created site.

The value must be in the form name#configuration. If you do not specify the configuration, configuration 0 is the default (for example, STS#0). The list of available templates can be customized to include templates you create.

donotcreatesite

<none>

No

If this parameter is present, no corresponding site collection will be created for the Web application.

description

A valid text string, such as "This is a description"

No

Description of the site collection.

sethostheader

<none>

No

Works in conjunction with the url parameter.

When a new Web application is created, Windows SharePoint Services 3.0 looks at the URL value that is specified using the url parameter. Windows SharePoint Services 3.0 only uses the port number to create a new IIS Web site. However, the host name portion of the URL is ignored and Windows SharePoint Services 3.0 does not create a host header binding for the IIS Web site. To create a Web application with an IIS Web site that includes a host header binding, use the sethostheader parameter. This enables Windows SharePoint Services 3.0 to use the host name portion of URL and create an IIS Web site that also includes the host name from the URL as a host header binding.

apidname

A valid application pool name, such as "Test1"

No

The application pool ID.

The application pool defines the account and credentials that are used by the Web application.

apidtype

One of the following types:

  • NetworkService

  • ConfigurableID

    NoteNote:

    If the ConfigurableID value is used, you must use the apidlogin parameter to specify a user name and password.

No

The identity type to use for the application pool.

NoteNote:

You cannot use the same application pool that you used for Windows SharePoint Services 2.0.

You can use the same user account, but you must create a new application pool, or use an application pool that you already created for your upgraded sites.

apidlogin (apl)

A valid user name in the form domain\username

No

The user name to use for running processes in the application pool.

This parameter must be a Windows user name, and must be qualified with a domain name.

apidpwd

A valid Windows password to the application pool

No

The password that is used in conjunction with the apidlogin parameter.

allowanonymous

<none>

No

Specifies the default state for anonymous access during virtual server provisioning. By default this setting is off, regardless of the current IIS setting. The administrator needs to explicitly turn on anonymous access.

IIS anonymous access must be on for pluggable authentication. Anonymous requests must make it through IIS to get to the ASP.NET authentication system.

There is no anonymous access choice when provisioning with forms-based authentication.

NoteNote:

Allowing anonymous access in IIS does not automatically make all Windows SharePoint Services 3.0 sites anonymously accessible. There is Web-level anonymous access control as well, which is also off by default. However, disabling anonymous access in IIS does disable anonymous access to all Windows SharePoint Services 3.0 sites on the Web application because IIS rejects the request before code even runs.

See Also

Concepts

Authentication

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.