Export (0) Print
Expand All

Extendvsinwebfarm: Stsadm operation (Windows SharePoint Services)

Office 2007

Updated: November 29, 2007

Applies To: Windows SharePoint Services 3.0

 

Topic Last Modified: 2009-03-10

Extend a Windows SharePoint Services 3.0 Web application for use in a server farm. This operation does not create a new content database, but allows you to connect to an existing virtual server when the vsname parameter is used and use the same 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.

stsadm -o extendvsinwebfarm

   -url <URL name>

   -vsname <Web application name>

   [-exclusivelyusentlm]

   [-apidname <application pool name>]

   [-apidtype {configurableID | NetworkService}]

   [-apidlogin] <domain\name>]

   [-apidpwd <application pool password>]

   [-allowanonymous]

 

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.

vsname

A valid name such as, "My Web application"

Yes

The text name of the Web application.

exclusivelyusentlm

<none>

No

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

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 the 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. The default 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.

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