Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

WSS V3 Beta 2 installation instructions

  Asked By: Krista    Date: Aug 28    Category: Sharepoint    Views: 860

Here's the WSS V3 setup info:



Deploy Windows SharePoint Services version 3 (Beta 2) on a single server

Note This content is preliminary content for a preliminary software release. It might be incomplete and is subject to change.

You can publish a working SharePoint site in just minutes by deploying Microsoft Windows SharePoint Services (version 3) on a single server computer. A single-server configuration is useful if you want to evaluate Windows SharePoint Services version 3 features and capabilities, such as collaboration, document management, and search, but you do not want to spend a lot of time installing components and configuring settings. A single-server configuration is also useful if you are deploying a small number of Web sites and you want to minimize administrative overhead. When you deploy Windows SharePoint Services version 3 on a single server using the default settings, the Setup program automatically installs and configures Microsoft® Windows® Internal Database, and uses it to create the configuration database and content database for your SharePoint site. In addition, the Setup program installs SharePoint Central Administration and creates your first SharePoint site.

In this article

Hardware and software requirements

Security account requirements

Configure the server as a Web server

Install and configure Windows SharePoint Services with Windows Internal Database

After you install and configure Windows SharePoint Services with Windows Internal Database

Hardware and software requirements

Before you install and configure Windows SharePoint Services version 3, make sure your server computer has the recommended hardware and software. For a single-server deployment, your server computer must meet the following hardware and software requirements.

Hardware requirements

A dual-processor computer with processor clock speeds of 2.5 gigahertz (GHz) or higher. A minimum of 1 gigabyte (GB) of RAM; however, 2 GB of RAM is recommended for improved performance.

Software requirements

A computer running Microsoft Windows Server 2003 (Standard, Enterprise, Datacenter, or Web Edition) with Service Pack 1 (SP1), Microsoft Windows Workflow Foundation Runtime Components Beta 2.2 (Build 3807.7), and Microsoft .NET Framework 2.0. Instructions for installing the Windows Workflow Foundation Beta 2.2 and Microsoft .NET Framework 2.0 are provided later in this section. For more information about Microsoft .NET Framework 2.0, see the Microsoft .NET Framework Developer Center. For more information about the Windows Workflow Foundation Runtime Components Beta 2.2, see the Windows Workflow Foundation Web site.

The computer must be configured as a Web server running Microsoft Internet Information Services (IIS) in IIS 6.0 worker process isolation mode. Instructions for installing and configuring IIS are provided later in this section. For more information about IIS , see the Windows Server 2003 documentation.

The computer must be using the NTFS file system. Windows Server 2003 includes a conversion utility (Convert.exe) that you can use to convert an existing file allocation table (FAT) volume to NTFS without losing data.

In addition to these requirements, you must install Windows SharePoint Services version 3 on a clean installation of Windows Server 2003. If you uninstall a previous version of Windows SharePoint Services version 3, and then install Windows SharePoint Services version 3 (Beta 2), Setup might fail to create the configuration database and the installation process will fail.



Security account requirements

To install Windows SharePoint Services version 3 on a stand-alone server, you must be a member of the Administrators group on the computer, or you must be a member of a group that is a member of the Administrators group on the computer, such as the Domain Admins group.

Configure the server as a Web server

Before you install and configure Windows SharePoint Services version 3, you must install and configure the required software on each of your front-end servers. This includes installing and configuring IIS so your front-end servers act as Web servers, installing Windows .NET Framework 2.0, enabling ASP.NET 2.0, and installing Windows Workflow Foundation Runtime Components Beta 2.2 (build 3807.7).

Install and configure IIS

IIS is not installed or enabled by default in Windows Server 2003. To make your server a Web server, you must install and enable IIS, and you must make sure that IIS is running in IIS 6.0 worker process isolation mode.

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

2. On the Welcome to the Configure Your Server Wizard page, click Next.

3. On the Preliminary Steps page, click Next.

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

5. On the Application Server Options page, click Next.

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

7. Click Finish.

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

9. In the IIS Manager tree, click the plus sign (+) next to the server name, and then right-click the Web Sites folder and select Properties.

10. In the Web Sites 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 in IIS 5.0 isolation mode check box is only selected if you have upgraded to IIS 6.0 on Windows Server 2003 from IIS 5.0 on Microsoft Windows 2000. New installations of IIS 6.0 use IIS 6.0 worker process isolation mode by default.

Install Windows .NET Framework 2.0

1. Do one of the following:

· If you are running an x86-based computer, go to the Microsoft Download Center Web site, and on the Microsoft .NET Framework Version 2.0 Redistributable Package (x86) page, click Download.

· If you are running an x64-based computer, go to the Microsoft Download Center Web site, and on the Microsoft .NET Framework Version 2.0 Redistributable Package (x64) page, click Download.

2. In the File Download-Security Warning dialog box, click Run.

3. In the Internet Explorer-Security Warning dialog box, click Run and follow the instructions that appear on your screen.

Enable ASP.NET 2.0

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

2. In the IIS Manager tree, click the plus sign (+) next to the server name, and then click the Web Service Extensions folder.

3. In the details pane, click ASP.NET v2.0.50727, and then click Allow.

Install Windows Workflow Foundation Runtime Components Beta 2.2

Go to the Microsoft Download Center Web site, and on the Microsoft Windows Workflow Foundation Runtime Components Beta 2.2 and Visual Studio® 2005 Extensions for Windows Workflow Foundation Beta 2.2 page, follow the instructions for downloading and installing Windows Workflow Foundation Runtime Components Beta 2.2 (build 3807.7). There are separate downloads for x86-based computers and x64-based computers: be sure to download and install the appropriate version for your computer.

Install and configure Windows SharePoint Services with Windows Internal Database

Because you are installing to a single server, you can run the Setup program using the Basic option. This option uses the Setup program's default parameters to install Windows SharePoint Services version 3 and Windows Internal Database.

Run Windows SharePoint Services Setup

1. From the product disc, run Setup.exe, or from the product download, run Sharepoint.exe.

2. On the Read the Microsoft Software License Terms page, review the terms, select the I accept the terms of this agreement check box, and then click Continue.

3. On the Choose the installation you want page, click Basic.

4. When Setup finishes, a dialog appears telling you that you must complete the configuration of your server. Make sure that the Run the SharePoint Products and Technologies Configuration Wizard now check box is selected.

5. Click Close to start the configuration wizard.

Run the SharePoint Products and Technologies Configuration Wizard

1. On the Welcome to SharePoint Products and Technologies page, click Next.

2. In the warning dialog box notifying you that some services might need to be restarted or reset during configuration, click Yes.

3. On the Configuration Successful page, click Finish, and your new SharePoint site should open.

Notes

If you are prompted for your user name and password, you might need to add the site to the list of trusted sites and configure user authentication settings in Internet Explorer. Instructions for configuring these settings are provided in the next set of steps.

If you see a proxy server error message, you might need to configure your proxy server settings so that local addresses bypass the proxy server. Instructions for configuring this setting are provided later in this section.

Add the SharePoint site to the list of trusted sites

1. In Internet Explorer, on the Tools menu, click Internet Options.

2. On the Security tab, in the Select a Web content zone to specify its security settings box, click Trusted Sites, and then click Sites.

3. Clear the Require server verification (https:) for all sites in this zone check box.

4. In the Add this Web site to the zone box, type the URL to your site, and then click Add.

5. Select the Require server verification (https:) for all sites in this zone check box.

6. Click Close to close the Trusted Sites dialog box.

7. Click OK to close the Internet Options dialog box.

Configure user authentication settings for trusted sites

1. In Internet Explorer, on the Tools menu, click Internet Options.

2. On the Security tab, in the Select a Web content zone to specify its security settings box, click Trusted sites, and then click Custom Level.

3. In the Settings list box, under User Authentication, click Automatic logon with current username and password.

4. Click OK twice.

Note If you do not want to add your SharePoint site to the list of trusted sites, but you do not want to be prompted for your user name and password every time you access your SharePoint site, you can instead add your SharePoint site to the Local intranet zone. If you do this, you must enable the Automatic logon only in Intranet zone user authentication setting instead of the Automatic logon with current username and password user authentication setting.

Configure proxy server settings to bypass the proxy server for local addresses

1. In Internet Explorer, on the Tools menu, click Internet Options.

2. On the Connections tab, in the Local Area Network (LAN) Settings area, click LAN Settings.

3. In the Proxy Server area, select the Bypass proxy server for local addresses check box.

4. Click OK to close the Local Area Network (LAN) Settings dialog box.

5. Click OK again to close the Internet Options dialog box.

After you install and configure Windows SharePoint Services with Windows Internal Database

After Setup finishes, your browser window should be open to the home page of your new SharePoint site. Although you can start adding content to the site and you can start customizing the site, it is recommended that you perform the following administrative tasks using SharePoint Central Administration:

Configure incoming e-mail settings You can configure incoming e-mail settings so that SharePoint sites accept and archive incoming e-mail. You can also configure incoming e-mail settings so that SharePoint sites can archive e-mail discussions as they happen, save e-mailed documents, and show e-mailed meetings on site calendars. In addition, you can configure the SharePoint Directory Management Service to provide support for e-mail distribution list creation and management.

Configure outgoing e-mail settings You can configure outgoing e-mail settings so that your Simple Mail Transfer Protocol (SMTP) server sends e-mail alerts to site users and notifications to site administrators. You can configure both the "From" e-mail address and the "Reply" e-mail address that appears in outgoing alerts.

Create SharePoint sites When Setup finishes you have a single Web application that hosts a single SharePoint site. You can create more SharePoint sites and Web applications if your site design requires multiple sites or multiple Web applications.

Run the Best Practices Analyzer tool You can run the Best Practices Analyzer tool to check for common issues and best security practices. The tool generates a reqport that can help you optimize the configuration of your system. The tool can be run locally or from a server that is not attached to the server farm.

Configure diagnostic logging settings You can configure several diagnostic logging settings to help with troubleshooting. This includes enabling and configuring trace logs, event messages, user-mode error messages, and Customer Experience Improvement Program events.

Configure antivirus protection settings You can configure several antivirus settings if you have an antivirus program that is designed for Windows SharePoint Services version 3. Antivirus settings allow you to control whether documents are scanned on upload or download and whether users can download infected documents. You can also specify how long you want the antivirus program to run before it times out and you can specify how many execution threads the antivirus program can use on the server.

Configure administrative settings using SharePoint Central Administration

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

2. On the Central Administration home page, under Administrative Tasks, click the administrative task you want to perform.

3. On the Administrative Tasks page, next to Action, click the task.

Share: 

 

3 Answers Found

 
Answer #1    Answered By: Darrius Whitfield     Answered On: Aug 28

Deploy Windows SharePoint services  version 3 (Beta 2) in a server  farm environment

Note This content  is preliminary content for a preliminary software  release. It might be incomplete and is subject  to change.

You can deploy  Microsoft Windows SharePoint Services (version 3) in a server farm environment, which is useful if you are hosting a large number  of sites  or you want the scalability of a multi-tier topology. A server farm typically consists of a back-end database  server and one or more front-end servers that provide web  services and Windows SharePoint Services version  3 services, such as search  and indexing. When you deploy Microsoft Windows SharePoint Services (version 3)in a server farm environment, you can publish  an optimized SharePoint site  with a dedicated Microsoft® SQL Server database in minutes.

In this article

 hardware  and software requirements

Suggested topologies

 security  account requirements

 configure  the server as a Web server

 install  Windows SharePoint Services

Configure Windows SharePoint Services version 3Services

 create  and configure sites

After you install Windows SharePoint Services

Hardware and software requirements

Before you install and configure Windows SharePoint Services version 3, make sure your servers have the recommended  hardware and software. To deploy a server farm, you need at least one front-end server computer  acting as a Web server and an application server, and one back-end server computer acting as a database server. The server computers must meet  the following requirements.

Hardware requirements

Front-end Web server and application server computers: a dual-processor computer with processor clock  speeds of 2.5-gigahertz (GHz) or higher and a minimum  of 2 gigabytes (GB) of RAM.

Back-end database server computers: a dual-processor computer with processor clock speeds of 2.0 GHz or higher and a minimum of 2 GB of RAM.

Software requirements

The front-end server computers must be running  Microsoft Windows® Server 2003 (Standard, Enterprise, Datacenter, or Web Edition) with Service Pack 1 (SP1), and have Microsoft Windows Workflow Foundation Runtime Components beta  2.2 (Build 3807.7) and Microsoft .NET Framework 2.0 installed. instructions  for installing  Windows Workflow Foundation Runtime Components Beta 2.2 and Microsoft .NET Framework 2.0 are provided later in this section. For more information about Microsoft .NET Framework 2.0, see the Microsoft .NET Framework Developer Center. For more information about Windows Workflow Foundation Runtime Components Beta 2.2, see the Windows Workflow Foundation Web site.

The front-end server computers must be running Microsoft Internet Information Services (IIS) in IIS 6.0 worker process isolation mode. Instructions for installing and configuring  IIS are provided later in this section. For more information about IIS, see the Windows Server 2003 documentation.

The front-end server computers must be using the NTFS file system. Windows Server 2003 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 database server computer must be running Microsoft SQL Server 2005 or Microsoft SQL Server 2000 with Service Pack 3 (SP3) or later. It is assumed that you have installed and configured the database program  on the back-end server computer. You do not need to set up or create specific databases for Windows SharePoint Services version 3. The Windows SharePoint Services version 3 configuration  program will create the necessary databases when you install and configure Windows SharePoint Services version 3.

In addition  to these requirements, you must install Windows SharePoint Services version 3 on a clean installation  of Windows Server 2003. If you uninstall a previous version of Windows SharePoint Services version 3, and then install Windows SharePoint Services version 3 (Beta 2), Setup might fail to create the configuration database and the installation will fail.

Suggested topologies

A server farm typically consists of a back-end database server running either Microsoft SQL Server 2005 or Microsoft SQL Server 2000 with SP3 or later, and one or more front-end servers running Microsoft Internet Information Services (IIS) and Windows SharePoint Services version 3. In this configuration the front-end servers are configured as Web servers and application servers. The Web server role provides Web services to clients requesting Web pages; the application server role provides Windows SharePoint Services version 3 services such as search and indexing. In large server farm environments you typically have more than one database server in a clustered configuration and you have two or more front-end servers configured for network load balancing.

Security account  requirements

To deploy Windows SharePoint Services version 3 in a server farm environment you will need the following security accounts:

A user account that you can use to install Windows SharePoint Services version 3 and run the SharePoint Products and Technologies Configuration Wizard. This account must be:
A domain user account.
A member of the Administrators group on each of your front-end servers.
A member of the SQL Server Logins security group, which grants login access to your SQL Server database.
A member of the SQL Server Database Creator server role, which grants permission to create and alter datbases.
A member of the SQL Server Security Administrators server role, which grants permission to manage server logins.
A unique domain user account that you can specify as the Windows SharePoint Services version 3 service account. This user account is used to access your SharePoint configuration database. It also acts as the application pool identity for the SharePoint Central Administration application pool and it is the account under which the Windows SharePoint Services Timer service runs. The SharePoint Products and Technologies Configuration Wizard adds this account to the SQL Server Logins security group and the SQL Server Database Creator server role and the SQL Server Security Administrators server role. It is recommended that you follow the principle of least privilege and do not make this user account a member of any particular security group on your front-end servers or your back-end servers.
A unique domain user account under which the Windows SharePoint Services Search service can run. It is recommended that you follow the principle of least privilege and do not make this user account a member of any particular security group on your front-end servers or your back-end servers.
A unique domain user account that is used to crawl content on your sites and create indexes. It is recommended that you follow the principle of least privilege and select a unique user account that cannot modify content and does not have administrative  rights on your front-end servers or on your back-end database servers. This user account will be added to the Web application Full Read policy for your farm.
A unique domain user account that acts as the application pool identity for your site collection's Web application. It is recommended that you follow the principle of least privilege and select a unique user account that does not have administrative rights on your front-end servers or on your back-end database servers.
Configure the server as a Web server

Before you install and configure Windows SharePoint Services version 3, you must install and configure the required software on each of your front-end servers. This includes installing and configuring IIS so your front-end servers act as Web servers, installing Windows .NET Framework 2.0, enabling ASP.NET 2.0, and installing Windows Workflow Foundation Runtime Components Beta 2.2 (build 3807.7).

Install and configure IIS

IIS is not installed or enabled by default  in Windows Server 2003. To make your server a Web server, you must install and enable IIS, and you must make sure that IIS is running in IIS 6.0 worker process isolation mode.

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

2. On the Welcome to the Configure Your Server Wizard page, click Next.

3. On the Preliminary Steps page, click Next.

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

5. On the Application Server Options page, click Next.

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

7. Click Finish.

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

9. In the IIS Manager tree, click the plus sign (+) next to the server name, and then right-click the Web Sites folder and select Properties.

10. In the Web Sites 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 in IIS 5.0 isolation mode check box is only selected if you have upgraded to IIS 6.0 on Windows Server 2003 from IIS 5.0 on Microsoft Windows 2000. New installations of IIS 6.0 use IIS 6.0 worker process isolation mode by default.

Install Windows .NET Framework 2.0

1. Do one of the following:

· If you are running an x86-based computer, go to the Microsoft Download Center Web site, and on the Microsoft .NET Framework Version 2.0 Redistributable Package (x86) page, click Download.

· If you are running an x64-based computer, go to the Microsoft Download Center Web site, and on the Microsoft .NET Framework Version 2.0 Redistributable Package (x64) page, click Download.

2. In the File Download-Security Warning dialog box, click Run.

3. In the Internet Explorer-Security Warning dialog box, click Run and follow the instructions that appear on your screen.

Enable ASP.NET 2.0

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

2. In the IIS Manager tree, click the plus sign (+) next to the server name, and then click the Web Service Extensions folder.

3. In the details pane, click ASP.NET v2.0.50727, and then click Allow.

 
Answer #2    Answered By: Adrienne Greene     Answered On: Aug 28

Go to the Microsoft Download Center Web site, and on the Microsoft Windows Workflow Foundation Runtime Components beta  2.2 and Visual Studio® 2005 Extensions for Windows Workflow Foundation Beta 2.2 page, follow the instructions  for downloading and installing  Windows Workflow Foundation Runtime Components Beta 2.2 (build 3807.7). There are separate downloads for x86-based computers and x64-based computers: be sure to download and install  the appropriate version  for your computer.

Install and configure  Windows SharePoint Services

To deploy  Windows SharePoint services  version 3 in a server  farm environment, you must install and configure Windows SharePoint Services version 3 on each of your front-end servers before you configure Windows SharePoint Services version 3 services or create  sites. You must also have SQL Server running  on the back-end server before you install Windows SharePoint Services version 3 on your front-end servers.

Run Windows SharePoint Services Setup

1. From the product disc, run Setup.exe, or from the product download, run Sharepoint.exe on one of your front-end server computers.

2. On the Read the Microsoft Software License Terms page, review the terms, select the I accept the terms of this agreement check box, and then click Continue.

3. On the Choose the installation  you want page, click Advanced.

4. On the Server Type page, click Web Front End, and then click Install Now.

5. When Setup finishes, a dialog box appears telling you that you must complete the configuration  of your server. Make sure that the Run the SharePoint Products and Technologies Configuration Wizard now check box is selected.

6. Click Close to start the configuration wizard. Instructions for completing the wizard are provided in the next set of steps.

Run the SharePoint Products and Technologies Configuration Wizard

After Setup finishes, you can use the SharePoint Products and Technologies Configuration Wizard to configure Windows SharePoint Services version 3. The SharePoint Products and Technologies Configuration Wizard automates several configuration tasks, including: installing and configuring  the configuration database, installing and enablingWindows SharePoint Services version 3 services, and installing the SharePoint Central Administration Web application. Use the following instructions to run the SharePoint Products and Technologies Configuration Wizard.

1. On the Welcome to SharePoint Products and Technologies page, click Next.

2. Click Yes in the warning dialog box that appears notifying you that some services might need to be restarted during configuration.

3. On the Connect to a server farm page, do one of the following:

· If this is the first front-end server that you are configuring in your server farm, click No, I want to create a new server farm, and then click Next.

· If you have already configured your first front-end server in your server farm, click Yes, I want to connect to an existing server farm, and then click Next.

4. On the Specify Configuration Database settings  page, in database  server, type the name of the computer  that is running SQL Server.

5. Do one of the following:

· If this is the first front-end server that you are configuring in your server farm, do not change  the default  database name that appears in Database name.

· If you have already configured your first front-end server in your server farm, click Retrieve Database Names, and in Database name click the database name that you created when you configured the first front-end server in your server farm. The default name is SharePoint_Config.

6. In Username , type the user name of the account  used to connect to the computer running SQL Server (be sure to type the user name in the format DOMAIN\username).

Important This account is the Windows SharePoint Services version 3 service account under which several Windows SharePoint Services version 3 services run. The user account that you specify as the Windows SharePoint Services version 3 service account must be a domain user account, but it does not need to be a member of any specific security  group on your front-end servers or your back-end database servers. However, the user account that you specify must be a member of the following two SQL Server security roles on your back-end database servers: Database Creator and Security Administrator. It is recommended  that you follow the principle of least privilege and specify a user account that is not a member of the Administrators group as your Windows SharePoint Services version 3 service account.

7. In Password, type the user's password, and click Next.

8. Skip the next two steps if you have already configured your first front-end server in your server farm.

9. On the Configure SharePoint Central Administration Web Application page, select the Specify port number  check box and enter a port number if you want the SharePoint Central Administration Web application to use a specific port, or leave the Specify port number check box unchecked if you do not care which port number the SharePoint Central Administration Web application uses.

10. Do one of the following:

· If you want to use NTLM authentication (the default), click Next.

· If you want to use Kerberos authentication, click Negotiate (Kerberos), and then click Next.

Note In most cases, you should use the default setting (NTLM). Use Negotiate (Kerberos) only if Kerberos is supported in your environment. Using the Negotiate (Kerberos) option requires you to configure a Service Principal Name for the domain user account. To do this, you must be a member of the Domain Admins group. For more information about configuring Kerberos, see Microsoft Knowledge Base article  KB 832769: HOW TO: Configure Windows SharePoint Services to Use Kerberos Authentication.

11. On the Completing the SharePoint Products and Technologies Wizard page, verify your settings, and then click Next.

12. On the Configuration Successful page, click Finish, and the SharePoint Central Administration Web page opens.

Notes

If you are prompted for your user name and password, you might need to add the SharePoint Central Administration site  to the list of trusted sites  and configure user authentication settings in Internet Explorer. Instructions for configuring these settings are provided below.

If you see a proxy server error message, you might need to configure your proxy server settings so that local addresses bypass the proxy server. Instructions for configuring this setting are provided below.

Add the SharePoint Central Administration site to the list of trusted sites

1. In Internet Explorer, on the Tools menu, click Internet Options.

2. On the Security tab, in the Select a Web content  zone to specify its security settings box, click Trusted Sites, and then click Sites.

3. Clear the Require server verification (https:) for all sites in this zone check box.

4. In the Add this Web site to the zone box, type the URL for the SharePoint Central Administration site, and then click Add.

5. Select the Require server verification (https:) for all sites in this zone check box.

6. Click Close to close the Trusted Sites dialog box.

7. Click OK to close the Internet Options dialog box.

Configure user authentication settings for trusted sites

1. In Internet Explorer, on the Tools menu, click Internet Options.

2. On the Security tab, in the Select a Web content zone to specify its security settings box, click Trusted sites, and then click Custom Level.

3. In the Settings list box, under User Authentication, click Automatic logon with current username and password.

4. Click OK twice.

Note If you do not want to add the SharePoint Central Administration site to the list of trusted sites, but you do not want to be prompted for your user name and password every time  you access the SharePoint Central Administration site, you can instead add the SharePoint Central Administration site to the Local intranet zone. If you do this, you must enable the Automatic logon only in Intranet zone user authentication setting instead of the Automatic logon with current username and password user authentication setting

Configure proxy server settings to bypass the proxy server for local addresses

1. In Internet Explorer, on the Tools menu, click Internet Options.

2. On the Connections tab, in the Local Area Network (LAN) Settings area, click LAN Settings.

3. In the Proxy Server area, select the Bypass proxy server for local addresses check box.

4. Click OK to close the Local Area Network (LAN) Settings dialog box.

5. Click OK again to close the Internet Options dialog box.

Configure Windows SharePoint Services version 3 services

After you have installed and configured Windows SharePoint Services version 3 on all of your front-end servers, you must start the Windows SharePoint Services Search service on at least one of your front-end servers. You can start the Search service on any server in your server farm. If you want to start the Search service on more than one server in your server farm, you must specify which Search server you want to index the content database because the content database can be indexed by only one instance of the Search service (one Search server). If you start the Search service on more than one server, you can specify which server you want to index the content database by clicking the Application Management tab on the SharePoint Central Administration home page, and then clicking Content Databases in the SharePoint Web Application Management section.

Note You must start the Search service before you can create and extend the first Web application to host sites.

Start the Windows SharePoint Services Search service

1. On the SharePoint Central Administration home page, click the Operations tab on the top navigation bar.

2. In the Topology and Services section, click Servers in farm.

3. On the Server in Farm page, click the server on which you want to run the Search service.

4. On the Services on Server page, in the list of services, next to Windows SharePoint Services Help Search, click Start.

5. On the SharePoint Services Search Settings page, in the Indexing content databases section, select the Take over all non-indexed content databases check box.

6. In the Service Account section, click Configurable, and in User name and Password, type the user name and password for the user account under which you want the Search service to run. The user account does not have to be a member of any particular security group. It is recommended that you use the principle of least privilege and select a unique user account that does not have administrative  rights on your front-end servers or on your back-end database servers. You can use the user account that you specified as the Windows SharePoint Services version 3 service account; however, if that user account is a member of a security group that has administrative rights on your front-end servers or your back-end database servers, you will not be following the principle of least privilege. The user name must be in the format DOMAIN\username.

7. In the Content Access Account section, click Configurable, and in User name and Password, type the user name and password for the user account that you want to use to crawl content on your sites. It is recommended that you use the principle of least privilege and select a unique user account that cannot modify content and does not have administrative rights on your front-end servers or on your back-end database servers. You can use the user account that you specified as the Windows SharePoint Services version 3 service account; however, if that user account is a member of a security group that has administrative rights on your front-end servers or your back-end database servers, you will not be following the principle of least privilege. The user account that you specify will be added to the Full Read policy for all of your sites. The user name must be in the format DOMAIN\username.

8. In the Search Database section, do not modify the default settings.

9. In the Indexing Schedule section, do not modify the default settings.

10. Click Start.

 
Answer #3    Answered By: Joshuah Huber     Answered On: Aug 28

Create and configure  sites

After you install  and configure Windows SharePoint services  version 3, and configure services in your server  farm, you can create  a web  application and a site  collection. You should create the Web application on the first server on which you installed Windows SharePoint Services version  3 (in other words, the same server that is running  SharePoint Central Administration).

Create a Web application

1. From the SharePoint Central Administration site, click the Application Management tab in the top navigation bar.

2. On the Application Management page, in SharePoint Web Application Management, click Create or extend Web application.

3. On the Create or Extend Web Application page, click Create a new Web Application.

4. In the IIS Web Site section, click Create a new IIS web site, and then change  the port setting to 80. This will allow you to access your site by typing http://ServerName. If you use a nonstandard port number  you will have to include the port number in the URL to access your site (for example, http://ServerName:port).

5. In the security  Configuration section, under Authentication provider, select the appropriate authentication provider for your environment, and do not modify the default settings  in the remainder of this section.

Note By default, the authentication provider is set to NTLM. Use the Negotiate (Kerberos) setting only if Kerberos is supported in your environment. This option will require configuring  a Service Principal Name for the domain user account, for which you must have Domain Administrator credentials. For more information about configuring Kerberos, see Microsoft Knowledge Base article  KB 832769: HOW TO: Configure Windows SharePoint Services to Use Kerberos Authentication.

6. In the Load Balanced URL section, do not modify the default  settings.

7. In the Application Pool section, click Create new application pool.

8. In Application pool name, type the name of your application pool or use the default name.

9. Click Configurable, and in User name and Password, type the user name and password for the user account  under which you want the application pool to run. The user account does not have to be a member of any particular security group. It is recommended  that you use the principle of least privilege and select a unique user account that does not have administrative  rights on your front-end servers or on your back-end database  servers. You can use the user account that you specified as the Windows SharePoint Services version 3 service account; however, if that user account is a member of a security group that has administrative rights on your front-end servers or your back-end database servers, you will not be following the principle of least privilege. The user name must be in the format DOMAIN\username.

10. In the Database Name and Authentication section, verify the database information and click Windows Authentication.

11. In the Search Server section, specify the Search server you configured earlier, and then click OK.

12. After the Web application is created you should see an Application Created page.

13. If you chose to have the application pool run under a unique user account instead of the Windows SharePoint Services version 3 service account, do the following:

· Open the command prompt, type iisreset.exe /noforce, and then press ENTER.

14. Click Create a new Windows SharePoint Services site collection, and follow the instructions  below.

Create a site collection for your Web application

1. On the Create Site Collection page, in the Title and Description section, in Title, type a title for the new site.

2. In Description, type a description of the site collection.

3. In the Web Site Address section, click Create site at this URL, and then in URL path , click root.

If you want to specify a different URL, you can select a different path, or use the Create site under this URL option and specify a name and path.

4. In the Primary Site Collection Administrator section, in User name, type the user name of the site collection administrator. This can be the same user account that you specified as the Windows SharePoint Services version 3 service account.

5. In the Quota Template section, select a predefined quota template to limit resources used for this site collection. You can also select No Quota, thereby allowing this site collection to use any available resources.

6. In the Template Selection section, select a template for this site collection, for example, a Team Site.

7. Click OK to create the site collection with the attributes you specified.

Upon successful completion, a Top-Level Site Successfully Created page appears.

8. Click OK to return to the SharePoint Central Administration home page, or click the http://YourSiteName:Port link to go to the new site you created.

After you install Windows SharePoint Services

After you finish creating a site collection, your browser window should be open to the home page of your new SharePoint site. Although you can start adding content  to the site and you can start customizing the site, it is recommended that you perform several administrative tasks to ensure that your server farm is operating properly.

Configure alternate access mappings your Web applications

It is assumed that you installed and configured Windows SharePoint Services version 3 on all of your front-end servers before you created your first Web application and site collection. If you did, your front-end servers are mapped to your first Web application and site collection. In this case, when a user browses to one of your front-end servers by using http://servername, the browser will render the content that is in your Web application. However, if you add subsequent front-end servers to your server farm, the newly-added servers will not be mapped to your Web application. To map newly-added front-end servers to your existing Web application, you need to configure alternate access mappings.

 
Didn't find what you were looking for? Find more on WSS V3 Beta 2 installation instructions Or get search suggestion and latest updates.




Tagged: