Install Windows SharePoint Services 3.0 on a stand-alone computer

Install Windows SharePoint Services 3.0 on a stand-alone computer

In this article:

•	Hardware and software requirements
•	Configure the server as a Web server
•	Install and configure Windows SharePoint Services 3.0 with Windows Internal Database
•	Post-installation steps
•	Important This document discusses how to install Windows SharePoint Services 3.0 on a single computer as a stand-alone installation. It does not cover installing Windows SharePoint Services 3.0 in a farm environment, upgrading from previous releases of Windows SharePoint Services 3.0, or how to upgrade from SharePoint Portal Server 2003. For information about how to do this, see the following articles: Simple farm deployment (Windows SharePoint Services 3.0) Upgrading to Windows SharePoint Services 3.0

You can quickly publish a SharePoint site by deploying Windows SharePoint Services 3.0 on a single server computer. A stand-alone configuration is useful if you want to evaluate Windows SharePoint Services 3.0 features and capabilities, such as collaboration, document management, and search. A stand-alone 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 3.0 on a single server using the default settings, the Setup program automatically installs SQL Server 2005 Express Edition and uses it to create the configuration database and content database for your SharePoint sites. In addition, Setup installs the SharePoint Central Administration Web site and creates your first SharePoint site collection and site.

	Note:
	There is no direct upgrade from a stand-alone installation to a farm installation.

0 Hardware and software requirements

Before you install and configure Windows SharePoint Services 3.0, be sure that your servers have the required hardware and software. For more information about these requirements, see Determine hardware and software requirements (Windows SharePoint Services).

Top of page

1 Configure the server as a Web server

Before you install and configure Windows SharePoint Services 3.0, you must install and configure the required software. This includes installing and configuring Internet Information Services (IIS) so your computer acts as a Web server, installing the Microsoft .NET Framework version 3.0, and enabling ASP.NET 2.0.

Install and configure IIS

Internet Information Services (IIS) is not installed or enabled by default in the Microsoft Windows Server 2003 operating system. To make your server a Web server, you must install and enable IIS, and you must ensure that IIS is running in IIS 6.0 worker process isolation mode.

Install and configure IIS

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, right-click the Web Sites folder, and then click 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 the Microsoft .NET Framework version 3.0

Go to the Microsoft Download Center Web site (http://go.microsoft.com/fwlink/?LinkID=72322&clcid=0x409), and on the Microsoft .NET Framework 3.0 Redistributable Package page, follow the instructions for downloading and installing the .NET Framework version 3.0. There are separate downloads for x86-based computers and x64-based computers. Be sure to download and install the appropriate version for your computer. The .NET Framework version 3.0 download contains the Windows Workflow Foundation technology, which is required by workflow features.

Enable ASP.NET 2.0

ASP.NET 2.0 is required for proper functioning of Web content, the Central Administration Web Site, and many other features and functions of Windows SharePoint Services 3.0.

	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 Internet Information Services tree, click the plus sign (+) next to the server name, and then click the Web Service Extensions folder. 3. In the details pane, right-click ASP.NET v2.0.50727, and then click Allow.

Top of page

2 Install and configure Windows SharePoint Services 3.0 with Windows Internal Database

When you install Windows SharePoint Services 3.0 on a single server, run the Setup program using the Basic option. This option uses the Setup program's default parameters to install Windows SharePoint Services 3.0 and Windows Internal Database. Windows Internal Database uses SQL Server technology as a relational data store for Windows roles and features only, such as Windows SharePoint Services, Active Directory Rights Management Services, UDDI Services, Windows Server Update Services, and Windows System Resources Manager.

Note:

If you uninstall Windows SharePoint Services 3.0, and then later install on the same computer, the Setup program could fail when creating the configuration database causing the entire installation process to fail. You can prevent this failure by either deleting all the existing Windows SharePoint Services 3.0 databases on the computer or by creating a new configuration database. You can create a new configuration database by running the following command: psconfig -cmd configdb -create -database

Run Setup

1. 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. 2. On the Choose the installation you want page, click Basic to install to the default location. To install to a different location, click Advanced, and then on the Data Location tab, specify the location you want to install to and finish the installation. 3. When Setup finishes, a dialog box prompts you to complete the configuration of your server. Be sure that the Run the SharePoint Products and Technologies Configuration Wizard now check box is selected. 4. 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 dialog box that notifies you that some services might need to be restarted or reset during configuration, click Yes. 3. On the Configuration Successful page, click Finish. Your new SharePoint site opens. Note: If you are prompted for your user name and password, you might need to add the SharePoint site to the list of trusted sites and configure user authentication settings in Internet Explorer. Instructions for configuring these settings are provided in the following procedure. Note: 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 proxy server settings 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. Click Close to close the Trusted Sites dialog box. 6. Click OK to close the Internet Options dialog box.

If you are using a proxy server in your organization, use the following steps to configure Internet Explorer to bypass the proxy server for local addresses.

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 Automatic configuration section, clear the Automatically detect settings check box. 4. In the Proxy Server section, select the Use a proxy server for your LAN check box. 5. Type the address of the proxy server in the Address box. 6. Type the port number of the proxy server in the Port box. 7. Select the Bypass proxy server for local addresses check box. 8. Click OK to close the Local Area Network (LAN) Settings dialog box. 9. Click OK to close the Internet Options dialog box.

Top of page

3 Post-installation steps

After Setup finishes, your browser window opens to the home page of your new SharePoint site. Although you can start adding content to the site or you can start customizing the site, we recommend that you perform the following administrative tasks by using the SharePoint Central Administration Web site.

•	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. For more information, see Configure incoming e-mail settings
•	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 appear in outgoing alerts. For more information, see Configure outgoing e-mail settings
•	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. For more information, see Configure diagnostic logging settings
•	Configure antivirus protection settings You can configure several antivirus settings if you have an antivirus program that is designed for Windows SharePoint Services 3.0. Antivirus settings enable 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. For more information, see Configure antivirus protection .
•	Create SharePoint sites When Setup finishes, you have a single Web application that contains a single SharePoint site collection that hosts a SharePoint site. You can create more SharePoint sites collections, sites, and Web applications if your site design requires multiple sites or multiple Web applications. For more information, see Deploy and configure SharePoint sites (Windows SharePoint Services)

	Perform administrator tasks by using the Central Administration site
	1. Click Start, point to All Programs, point to Administrator Tools, and then click SharePoint 3.0 Central Administration. 2. On the Central Administration home page, under Administrator Tasks, click the task you want to perform. 3. On the Administrator Tasks page, next to Action, click the task.

Top of page

Operations for Office SharePoint Server 2007

Office SharePoint Server 2007 Administration Office SharePoint Server 2007 Backup and Restore	Office SharePoint Server 2007 Monitoring

http://technet2.microsoft.com/Office/en-us/library/604431c9-de72-43b9-a3a9-3b0c3bf3444e1033.mspx?mfr=true

Announcing the RTW of WSS and Office SharePoint Server 2007 Standard and Enterprise Evaluation!

http://blogs.msdn.com/sharepoint/archive/2006/11/16/announcing-the-rtw-of-wss-and-office-sharepoint-server-2007-standard-and-enterprise-evaluation.aspx

Announcing the RTW of WSS and Office SharePoint Server 2007 Standard and Enterprise Evaluation!

It is my pleasure to announce the RTW of WSS 3.0 and Office SharePoint Server 2007. Please read the all information on the details page.

Note: Installing Microsoft Windows SharePoint Services 3.0 over any beta or trial edition of Microsoft Office SharePoint Server 2007 is not supported.

Links to download the RTW versions:

Microsoft Office SharePoint Server 2007 x86 English Evaluation

Windows SharePoint Services 3.0

Here are the Product Keys you will need when installing SharePoint Server 2007

SharePoint Server Standard Trial: XJMKW-8T7PR-76XT6-RTC8G-VVWCQ
SharePoint Server Enterprise Trial: F2JBW-4PDJC-HKXTJ-YCKRP-T2J9D (corrected)

Installation Instructions and ReadMe

• Known Issues/ReadMe articles
• Install MOSS on a single server
• Install MOSS on a server farm
• Install WSS on a single server
• Install WSS on a server farm
• Installing Microsoft Office SharePoint Server 2007 by Bill English (SharePoint MVP)

Build to Build Upgrade Resources

• Upgrading from Office SharePoint Server 2007 Beta 2 Technical Refresh to Release Version
• Step by Step Instructions (with Screenshots) Office SharePoint Services B2TR to Release by Shane Young (SharePoint MVP)
• Upgrading from Windows SharePoint Services 3.0 Beta 2 Technical Refresh to Release Version
• Upgrading from Office Forms Server 2007 Beta 2 Technical Refresh to Release Version
• Upgrading from Beta 2 to B2TR for WSS and MOSS 2007 (prerequiste to B2TR to RTM)

Version to Version Upgrade & Migration

• Upgrade to SharePoint Server 2007 (IT Pro)
• Upgrade WSS 2.0 to WSS 3.0 (IT Pro)
• CMS 2002 to SharePoint Server 2007 (Developer)

Related Resources:

• Build to Build Supportability
• Version to Version Supported Paths
• Features comparison, Edition comparison, and Differences
• Other Version to Version Upgrade Resources

Joel Oleson
Product Manager
Office SharePoint Server

Upgrading from Windows SharePoint Services 3.0 Beta 2 Technical Refresh to Release Version

Follow the instructions in this article carefully when you upgrade from Microsoft Windows SharePoint Services 3.0 Beta 2 Technical Refresh to the release version.

During upgrade, your farm will be offline for a period of time while the databases are upgraded to the release version of the product. Be sure to notify your customers in advance.

In this article:

•	Prepare for upgrade
•	Uninstall Windows SharePoint Services 3.0 Beta 2 Technical Refresh
•	Install the release version of Windows SharePoint Services 3.0
•	Uninstall and reinstall Microsoft .NET Framework 3.0

Prepare for upgrade

Perform the procedures in this section on every server computer in your farm.

	Delete failed timer jobs
	1. Open SharePoint 3.0 Central Administration. 2. On the top navigation bar, click Operations. 3. In the Global Configuration section, click Timer job definitions. 4. On the Timer Job Definitions page, look for backup and restore or upgrade timer jobs in the list. If any exist, delete them by clicking the timer job and then clicking Delete on the page that appears.

Record current server information

1. Record the name of every server computer that hosts SharePoint 3.0 Central Administration. 2. Record the following information for each server computer: • Server type When you install the release version, you will need to specify the same server type that you have currently installed for each server computer in your farm. Note: The server type of a computer is located in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\WSS\ServerRole registry subkey. The values are singleserver for Basic installations or WFE for Advanced (farm) installations. • Central Administration account and password You will need to use the same account and password when you install the release version.

	Stop Windows SharePoint Services Search in a Basic installation
	1. Open SharePoint 3.0 Central Administration. 2. On the top navigation bar, click Operations. 3. In the Topology and Services section, click Services on Server. Stop Windows SharePoint Services Search.

Stop Windows SharePoint Services Search in an Advanced (farm) installation

1. On the Start menu, click Run. In the Open box, type cmd and then click OK. 2. At the command prompt, type cd %Programfiles%\Common Files\Microsoft Shared\web server extensions\12\bin 3. At the command prompt, type stsadm -o spsearch -action list > SearchServerList.txt 4. Open SharePoint 3.0 Central Administration. 5. On the top navigation bar, click Operations. 6. In the Topology and Services section, click Services on Server. 7. On every server, stop Windows SharePoint Services Search if it is not already stopped. To easily check the status of the search service on each server, click the server name in the Server list.

Modify the registry setting for the configuration database connection

1. On the Start menu, click Run. In the Open box, type regedit and then click OK. 2. In the Registry Editor, navigate to and click the following subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Secure\ConfigDB 3. On the File menu, click Export, and in the File name box, typeSharePointRegKeyBackupThis backs up the subkey so you can restore it to your registry later, if necessary. 4. Under the registry subkey, right-click the dsn value, and then click Rename. 5. Type dsn2 for the name, and then press ENTER to save your changes. Caution: Be sure to check that you have renamed the registry key to dsn2. If you fail to perform this step, upgrade will fail and you will have to manually upgrade the content databases to a new installation. This step is required for the installation process to detect and upgrade Beta 2 Technical Refresh to the release version. 6. Close the Registry Editor.

	Delete existing SharePoint Products and Technologies Configuration Wizard logs
	1. Open a command window. 2. At the command prompt, type cd "%programfiles%\common files\microsoft shared\web server extensions\12\logs" and then press ENTER. 3. At the command prompt, type del psc*.log and then press ENTER.

Top of page

Uninstall Beta 2 Technical Refresh

Perform the procedure in this section on all server computers in your farm. You can perform the steps in parallel across all server computers, or complete the procedure on each computer before moving to the next. You do not need to uninstall .NET Framework or Windows Workflow Foundation from these computers.

Uninstall Beta 2 Technical Refresh

1. In Control Panel, double-click Add or Remove Programs. 2. Uninstall all Microsoft Windows SharePoint Services 3.0 Language Packages. Caution: You must uninstall all language packs before you uninstall Windows SharePoint Services 3.0 Beta 2 Technical Refresh. If you do not uninstall all language packs at this point, you will be unable to install the release version of Windows SharePoint Services 3.0. 3. A message box appears to remind you to run the SharePoint Products and Technologies Configuration Wizard after uninstalling the language packs. You can ignore this reminder; click OK. 4. Select Microsoft Windows SharePoint Services 3.0, and then click Remove. 5. In the first message box that asks you to confirm that you want to uninstall, click Yes. 6. In the second message box that asks you to confirm that you want to uninstall, click OK. 7. If you are prompted to restart the computer, do so.

Top of page

Install the release version of Windows SharePoint Services 3.0

The procedure in this section must first be performed on a front-end Web server that hosted the Central Administration Web application in your Beta 2 Technical Refresh installation, which you noted under "Record current server information," earlier in this article. After you successfully complete this procedure on that server computer, perform it on all the other server computers in the farm, one at a time.

	Note:
	If upgrade fails on any server computer, do not run this procedure on any other computer in the farm until you have fixed the problem. After you have fixed the problem, run the SharePoint Products and Technologies Configuration Wizard again to resume upgrade.

Install Windows SharePoint Services 3.0 release version

1. Run Setup for the release version of Windows SharePoint Services 3.0. 2. Follow the steps to install the product. If the Upgrade Earlier Versions dialog box is displayed, choose No, do not upgrade at this time, and then click Install Now. 3. On the welcome page of the SharePoint Products and Technologies Configuration Wizard, click Cancel, and then click Yes in the dialog box that appears. 4. If you are using a Basic installation, perform the following steps: 1. In Control Panel, double-click Administrative Tools, and then double-click Services. 2. Double-click SQL Server 2005 Embedded Edition (MICROSOFT##SSEE). 3. In the Startup type list, click Automatic, and then click OK. 4. Click Start the service. 5. On the Start menu, click Run. In the Open box, type regedit and then click OK. 6. In the Registry Editor, navigate to the following subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\WSS 7. Under the registry subkey, double-click the Server Role value, change the value to SINGLESERVER, and then click OK. 8. Close the Registry Editor. 5. Install any Microsoft Windows SharePoint Services 3.0 Language Packages. At the end of every language pack installation, cancel the SharePoint Products and Technologies Configuration Wizard when it opens. 6. Run the SharePoint Products and Technologies Configuration Wizard. Use the Central Administration account and password that you noted under "Record current server information," earlier in this article. Be sure you select the same server type you previously used for this server, which you also noted under "Record current server information." A message box appears to remind you that services will be started; click Yes. A message box appears to remind you to run the wizard on each server in the farm; click OK. Note: Upgrade may only be run on one server computer in the farm at a time. Ignore the warning that is briefly displayed in the wizard that reads Failed to start search service SPSearchServiceInstance on this server after completing upgrade. Please start it manually. You will start this service in step 10. 7. If you are performing a Basic installation and the SharePoint Products and Technologies Configuration Wizard fails with the error message …is blocked because the signature is not valid, do the following: 1. On the Start menu, click Run. In the Open box, type regedit and then click OK. 2. In the Registry Editor, navigate to the following subkey, and then delete it: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\WSS\Services\Microsoft.SharePoint.Search.Administration.SPSearchService 3. Run the SharePoint Products and Technologies Configuration Wizard again. 8. Wait until upgrade has been completed successfully on this server computer before you start upgrade on any other server computer. 9. Open the file SearchServerList.txt, which you created in step 3 of "Stop Windows SharePoint Services Search in an Advanced (farm) installation," earlier in this article. 10. On every server listed with Status:Online, do the following: 1. On the Start menu, click Run. In the Open box, type cmd and then click OK. 2. At the command prompt, type cd %Programfiles%\Common Files\Microsoft Shared\web server extensions\12\bin 3. At the command prompt, type stsadm -o spsearch -action start -farmserviceaccount DoMAIN\name -farmservicepassword password -databaseserver searchdatabaseserver -databasename WSS_Search_NewDB 11. After starting search, you need to associate content databases to search servers. If a content database is not associated with a search server and you attempt a search on a site in the content database, the following message will be displayed: Your search cannot be completed because this site is not assigned to an indexer. Perform the following steps: 1. Open SharePoint 3.0 Central Administration, click Application Management, and then click Content Databases. 2. Click the content database for a Web application, and for Search Server choose a Windows SharePoint Services Search Server. 3. Repeat these steps for each content database for each Web application.

If the Search service is not functional, perform the following procedures for both Basic and Advanced (farm) installations.

On each and every server that has an online ("started") Windows SharePoint Services Search service, do the following:

1.	Open a command prompt window on the server, and change directory to Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN.
2.	Type stsadm -o spsearch –action list This will output the current association of content databases to search servers.
3.	Type stsadm -o spsearch -action stop This stops the Windows SharePoint Services Search service (this action throws away the search index).

If you encounter a problem or error, do the following:

1.	Type net stop sptimerv3 net stop spsearch

If the service does not stop, do the following:

1.	Open a command prompt window, and type run tasklist /svc
2.	Find "SPSearch" in the output and note the process ID .
3.	At the command prompt, type run taskkill /f /pid
4.	At the command prompt, type stsadm -o spsearch -action stop net start sptimerv3

Top of page

Uninstall and reinstall Microsoft .NET Framework 3.0

After you have successfully installed the release version and verified that the search service is functional, perform this procedure on every server computer in your farm.

	Uninstall and reinstall Microsoft .NET Framework 3.0
	1. In Control Panel, click Add or Remove Programs, select Microsoft .NET Framework 3.0, and then remove it. 2. Install Microsoft .NET Framework 3.0 (http://www.microsoft.com/downloads/details.aspx?FamilyId=10CC340B-F857-4A14-83F5-25634C3BF043&displaylang=en).

Windows SharePoint Services 3.0 Ready to Download!

Windows SharePoint Services 3.0 Ready to Download!

Thursday, November 16, 2006. Remember this day as the day that SharePoint 2007 was released! You can download Windows SharePoint Service 3.0 (WSSv3) from the Microsoft Download site (for free of course).

[Update] Required reading: the official announcement on the SharePoint Team blog. Joel posts the required product keys for the trial and links to several upgrade/installation guides.

Windows SharePoint Services 3.0 Windows SharePoint Services is a versatile technology that organizations and business units of all sizes can use to increase the efficiency of business processes and improve team productivity. With tools for collaboration that help people stay connected across organizational and geographic boundaries, Windows SharePoint Services gives people access to information they need.

Built on Microsoft Windows Server 2003, Windows SharePoint Services also provides a foundation platform for building Web-based business applications that can flex and scale easily to meet the changing and growing needs of your business. Robust administrative controls for managing storage and Web infrastructure give IT departments a cost-effective way to implement and manage a high-performance collaboration environment. With a familiar, Web-based interface and close integration with everyday tools including the 2007 Microsoft Office system, Windows SharePoint Server is easy to use and can be deployed rapidly.

[Update] more SharePoint related downloads:

• Windows SharePoint Services 3.0 Language Pack
• Windows SharePoint Services 3.0 x64
• Windows SharePoint Services 3.0 Language Pack x64
• Microsoft Office SharePoint Server 2007 Trial Version

Installing SharePoint 2007

Installing a New Microsoft Office SharePoint Server 2007 Portal: Step-by-Step Instructions

In this post, I'll demonstrate with words and screen shots how to install and get working a portal using Microsoft Office SharePoint Server 2007. Installing this product is not difficult, but it does require some forethought and planning. You can use this post as a reference for getting your version of MOSS 2007 installed.

You need to have downloaded the software from Microsoft's site. For information on how to do that, please go here. Once you have registered and downloaded the software, you're ready to start.

First, you'll need Windows 2003 Server, fully patched and ready to go. I believe I've seen blog postings recently that indicate that you can install MOSS07 on a Vista server. I'll leave that discussion for other threads and posts.

Once you have the operating system ready to go, you'll want to start by running the setup.exe for MOSS 2007. Figure 1 illustrates that after you start the installation process, you'll need to enter a valid product identification key code. This key code can be found on the download site and should have been a part of what you did to get the software in the first place.

Figure 1: Product Identification Key Code Input Screen

After entering the product identification key code, click Continue. The next screen is the licensing agreement screen. Now, I always recommend that you read the licensing agreement since it is a legal document and you are bound by its' terms. But I also recognize that in the 10+ years I've been in this industry, I've never seen an agreement that I didn't agree with.............if you get my drift.

Figure 2: Licensing Agreement Screen.

Be sure to select the "I accept the terms of this agreement" check box and then click Continue.

The next screen will give you the chance to select which type of installation you wish to commit. The Basic installation is used for those who:

• Need to install everything on a single server

• Do not need to grow into a multi-server farm

• Need a quick, easy deployment during installation with lead administrative effort

The Advanced option is selected by those who wish to install MOSS 2007 selecting some of the customizable features. In this illustration, we'll select the Advanced option and follow that route.

Figure 3: Installation Type Selection Screen

After clicking on the Advanced button, you'll find that the selections default to StandAlone (Figure 4). However, we'll choose Complete. The meaning of the three options is as follows:

• Complete: Enables all of the options for one server to offer the entire range of MOSS 2007 services and features to the network. You can scale out this deployment, start and stop services on this server and use a SQL server to host your databases.

• Web Front End: Enables only those options that allows the server to run as a web front end server. What this means is that server is merely the entry and exit point (or one of them among the other WFE servers) for the farm. The actual servers that users will consume will be hosted on other servers (presumably). This cannot be the first choice of a farm unless you plan on installing other servers in the farm to offer the services and features that users will want to consume.

• Stand-Alone: Similar to complete, this option enables all of the services and features for the MOSS 2007 farm, but assumes that there is no SQL server, so the MSDE engine is installed locally on this server. You cannot scale out this server into a larger MOSS 2007 farm.

Note that in reality, all of the MOSS 2007 binaries are installed in all three choices. All these choices really do is (pragmatically, not technically) turn on and off the code that is required for the server to fulfill the functions that have been assigned to it. Note also that you can select the location where the binaries should be installed in the File Location tab and then sign up to give feedback directly to Microsoft if you'd like to do this.

Make your selections, then click Install Now.

Figure 4: Server Type Selection Screen

During the installation, you'll be presented with a status bar that is illustrated in Figure 5.

Figure 5: Installation Status Screen

After installation has completed, you'll be given the chance to run through the SharePoint Products and Technologies Configuration Wizard (Figure 6). You'll use this wizard to commit the initial configuration options for your new SharePoint farm.

Figure 6: Entry screen to the SPPT Configuration Wizard. Note that you can come back to this screen using the Administration menus that automatically install with the SharePoint Server binaries

One you start the SPPT wizard, you'll receive a pop-up box (Figure 7) that will inform you that certain services are going to be stopped. Be sure it is a good time to stop these services before moving on with the configuration options for your farm.

Figure 7: Informational Pop-Up Box

The following set of screens in the SPPT Configuration Wizard are design to help you setup the farm. In Figure 8, you'll be able to create a new farm or join and existing farm. Farm membership, at the server level, is determined by which servers are using the same configuration database in SQL and which servers are not. In my illustration, I want to create a new farm, so I select the "No, I want to create a new server farm" radio button. If I had wanted to connect to an existing farm, I would have selected the other radio button.

Figure 8: Connect to a server farm configuration screen in the SPPT Wizard

After making our selection in Figure 8 and then clicking Next, I'm taken to the next screen illustrated in Figure 9. On this screen, I can enter the following configuration values:

• The SQL database server name. I'm not clear if this is the host name or netbios name, but I suspect this is the host name. However, you don't need the FQDN here, but you do need name resolution to this server or SQL Instance.

• The farm configuration database name is needed in the next input box. Note that the screen just asks for a name, but you need to understand you're entering the most persistent database name for the entire farm - the farm configuration database name. Be sure this name supports your database naming convention. You should decide the name of this database in advance of getting to this screen

• The database access account will need to be a member of the local admins group on each SharePoint server along with having db_creator and db_security permissions in SQL. I would suggest you have an account setup just for this purpose in your Active Directory and that you have a strong password associated with this account.

Figure 9: Configuration Database Settings Screen in the SPPT Wizard

in Figure 10, you'll be asked to decide which type of security settings you want to use for your farm. First, you can specify a pre-selected port number for central administration to run on or you can allow the wizard to randomly assign a port number. As you can see, this instance of the wizard randomly selected 17386 as the port number for Central Administration (CA). If you want CA to run on a different port, then select the check box and enter the desired port number.

The issue of NTLM vs. Kerberos is one that you may at some point wish to consider. Do you want the CA application to run using NTLM (NT Lan Manager) for security authentication or Kerberos? If the latter, there are some special configurations you'll need to complete for your Active Directory (AD) before Kerberos will work. I'm finding that most administrators are happy with NTLM, though those in a larger and more secure implementations are increasingly using Kerberos. For purposes of my illustration here, I'm selecting NTLM.

Figure 10: Configure SharePoint Web Application configuration screen in SPPT Wizard

After you click Next, you'll be given a status bar that indicates how the SharePoint configuration is going. Depending on the type of server you're installing and the options you're installing, you could have as few as seven tasks or as many as eleven. Figure 11 illustrates the progress screen. Note that the caption below the status bar will inform you about the configuration actions that are being executed during this process.

Figure 11: Configuration status bar screen in the SPPT Wizard

After the configurations have been executed and committed to the SQL Server database, we finally get to CA where we can further configure our farm. We can start and stop services (Figure 12) on this server and then create web applications. In order to have portal, you'll first need to start the Office SharePoint Server Search service and then create a Shared Services Provider (SSP). I'll start the search service.

Figure 12: Services configuration screen in CA

When the search service is started, you're presented with another web page for search configuration administration that needs to be completed before the search service can start. The configuration options are pretty clear. Out of the shoot, you'll use this server for both indexing and servicing queries from users until you can get enough servers in your farm to quarantine those options in your farm. Select a location that has enough disk space for your indexes. You should plan on a space allotment of 20% relative to the amount of information you wish to index. You'll also need to input an email address, a service account and whether or not there is a dedicated WFE for all crawling activities. For now, in my illustration, since this is the first server in the farm, I'll accept the defaults and click OK.

Figure 13: Search configuration screen

After starting the search service, the next thing I need to do is create a SSP. In order to do this, I'll navigate to the Application tab in CA, click Create or Extend a Web Application, then click Create a New Web Application, then make the configurations necessary that you see in Figure 14. Most of this is pretty self-explanatory, so I won't go through each input in detail. Suffice to say that I've done two things not illustrated here. First, after creating this web application, I then web back into CA, selected the Create or Configure Core Farm Services, then selected New SSP (Figure 15) and then filled in the configuration information for the new SSP. All of the options on that page are self-explanatory, except that you must select an Index server for the SSP to operate.

Backtracking just a bit, you can't have an Index server unless the Search services is started. So, that's why I illustrated starting the search services first, then creating an SSP, then creating a portal.

Figure 14: Configuring the new web application to host the portal

Figure 15: Illustration of the SSP management interface where you can select to create a New SSP.

Once the SSP is created and the web application for the portal has been created, you can then create the portal. The way to do this is to navigate to CA and then click Create Site Collection. Be sure the http://portal is selected in the drop down list in the upper right-hand portion of the screen (Figure 16). Note that on this screen, you'll need to ensure that you are creating the site collection at the root by selecting the "Create Site at this URL" where the URL path is "root", not in the Sites managed path. Also, if you scroll down, you'll need to select the Corporate Intranet Site under the Publishing tab. Microsoft has renamed the Portal to Corporate Intranet Site and placed it under the Publishing tab for web content publishing purposes. BTW, even though I don't illustrate it here, be sure to give the site a title.

Figure 16: Create Site Collection Screen

At this point, you should now have a new portal, ready to aggregate, organize and present content for your enterprise, division or department.

Bill

posted on Tuesday, June 27, 2006 1:03 PM