16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 2: Installing Windows SharePoint Services 45<br />

Tip The default permissions, Read <strong>and</strong> Run Scripts (such as ASP), are<br />

recommended. The Execute (such as ISAPI applications or CGI) permission<br />

will be added automatically to the appropriate folders by Windows Share-<br />

Point Services.<br />

13. Click Finish.<br />

For more information about creating virtual servers, see the Adding Sites topic<br />

in the Help system for Internet Information Services.<br />

Now that the virtual server has been created, you can extend it with Windows<br />

SharePoint Services. You can use either the comm<strong>and</strong> line or the HTML Administration<br />

pages to extend the virtual server.<br />

To extend the virtual server from the comm<strong>and</strong> line<br />

1. Open a comm<strong>and</strong> prompt window, <strong>and</strong> navigate to the \Program Files\Common<br />

Files\<strong>Microsoft</strong> Shared\Web Server Extensions\60\bin folder.<br />

2. Run the following comm<strong>and</strong> to extend the virtual server:<br />

stsadm -o extendvs -url http://servername<br />

-ds [-du -dp <br />

-dn -ownerlogin <br />

-owneremail -ownername <br />

-donotcreatesite -apcreatenew -apidname <br />

-apidtype <br />

-apidlogin -apidpwd <br />

Be sure to use the -donotcreatesite parameter when you extend the virtual<br />

server. Without this parameter, a site is automatically created when you extend the<br />

virtual server, <strong>and</strong> the site will not be affiliated with a host name.<br />

Notice that the -du <strong>and</strong> -dp parameters are not needed if you are using Windows<br />

authentication to connect to SQL Server. It is recommended that you create a<br />

new application pool to use for your virtual servers so that they run in separate processes<br />

from the administrative virtual server. Use the same application pool for each<br />

server farm virtual server on each front-end Web server. This application pool<br />

should use a domain account, but it does not need to have database creation rights<br />

in SQL Server. The administration virtual server account will create any databases<br />

required.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!