Installing, Configuring and Managing SharePoint Services

Windows Server 2003 R2 includes Windows SharePoint Services. In this post, we will cover the basic installation and configuration steps needed in order to get a standalone Windows SharePoint Service 3.0 installation up and running on Windows Server 2003 system.

1. Install the Application Server (IIS) role on your Windows Server 2003 system.
2. Install the Mail server (POP3, SMTP) role on your system.
3. Download and install the Microsoft .NET Framework 3.0. Make sure to download the version (32-bit or 64-bit) that matches your operating system.
4. Verify that ASP.NET v2.0.50727 is allowed by opening the Internet Services Manager, choosing Web Services Extensions, choosing ASP .NET v2.0.50727, and clicking the Allow button.
5. Download Windows SharePoint Services 3.0 from Microsoft. Don't install Windows SharePoint Services through Add/Remove Programs, because this is not the latest version of the service. For the x64 version of SharePoint, go here.
6. Execute the downloaded file named SharePoint.exe.
7. When asked, choose a Basic installation. The Basic installation also includes a run-time database.

Figure 1

Choose an installation type.

8. Windows SharePoint Services 3.0 will install using the default configuration.
9. The Windows SharePoint Services configuration wizard will run. This step, among other things, creates a SharePoint configuration database, installs services, and creates sample data.

To utilize your new SharePoint site, open a Web browser and browse to your server's name.

This is a very short introduction of the installation procedure. A detailed Explanation, Installation and Configuration method is as follows.

What is Windows SharePoint Services?
Windows SharePoint Services is the little brother of Microsoft's SharePoint Portal Server. Although Windows SharePoint Services isn't quite as powerful as SharePoint Portal Server, it can really go a long way toward helping your company become better organized.

In addition to helping to archive documents, this Windows Server 2003 component also allows employees to build their own collaborative Web sites. Employees can use these Web sites for retrieving commonly used documents, discussing things going on within the department, and having online meetings. Perhaps the best part of Windows SharePoint Services, though, is that it's free for anyone running Windows Server 2003.

Before you begin
As you can see, Windows SharePoint Services is as powerful as it is useful. Before you can install the component, however, you need to do a little prep work.

For starters, you must locate a suitable server. The server must be running Windows Server 2003 Standard, Enterprise, Datacenter, or Web Edition. The server must also be running Microsoft's ASP.NET and IIS 6.0. As you may know, IIS has a lot of optional components. You must therefore verify that the common files, the Simple Mail Transfer Protocol (SMTP) Service, and the World Wide Web services are all installed and running. None of these components is installed by default.

It's very important to note that you should not install Windows SharePoint Services onto a server that is already hosting a Web site or running a Web application, including Microsoft Exchange. Previously existing Web applications will be disabled during the SharePoint Services installation. Furthermore, the installation process will also disable Kerberos authentication for IIS. Windows SharePoint Services uses NTLM authentication in lieu of Kerberos.

To install the necessary components, select the Add/Remove Programs command from Control Panel. When you do, Windows will display the Add Or Remove Programs dialog box. Click the Add/Remove Windows Components button. When you do, the Windows Components Wizard will appear.

At this point, scroll through the list of components until you find Application Server. Select Application Server, then click the Details button to reveal the individual Application Server components. Select ASP.NET. With the Application Server screen still open, select Internet Information Services (IIS) and click the Details button.

You'll see a list of the various IIS components. The Common Files and the World Wide Web Service should be selected by default, but you'll have to manually select SMTP Service and click OK to return to the Application Server screen. Click OK again to return to the Windows Components Wizard screen. Click Next, and Windows will install all of the necessary files.

Another requirement is that the server must be running a version of SQL Server 2000. Before you stop reading the article, I should tell you that Windows Server 2003 comes with it's own SQL Server engine. This means that smaller organizations don't have to go out and buy SQL Server. The built-in engine is called MSDE (Microsoft Database Engine). It is just like SQL Server, but it has some major limitations.

First, MSDE is designed to slow down significantly if it's used by more than five users simultaneously. In this way, it will work well for small offices, but bigger organizations will want to use a full-blown version of SQL. A second limitation is that it doesn't support databases over two gigabytes in size. This may sound like a big database, but if your users index a lot of documents, the database can grow to be larger than two gigabytes fairly quickly. The final limitation is that MSDE does not offer any administrative tools. If you want to do any administrative work at all on MSDE, you'll have to do it from either a command line or a script. As you can see, MSDE is great for small offices or for development environments, but larger organizations should use SQL Server. For the purposes of this article, we will use a normal copy of SQL Server 2000 running Microsoft SQL Server 2000 Developer Edition with Service Pack 3A.

Once SQL Server or MSDE is installed, there are a few other minor requirements. The server must be a part of a Windows NT, 2000, or 2003 domain, although it doesn't necessarily have to be a domain controller. The server must also have a Pentium III or higher processor, 512 MB of RAM, and 550 MB of free disk space.

Keep in mind, however, that these are only the requirements for installing Windows SharePoint Services. There is a good chance that the databases could grow to be several gigabytes in size, so plan your disk space requirements accordingly.

Finally, the clients will be accessing Windows SharePoint Services through a Web browser. It is therefore important that the clients are running a supported Web browser. Supported Web browsers include:

Internet Explorer 6

Internet Explorer 5.5 with Service Pack 2

Internet Explorer 5.01 with Service Pack 2

Netscape Navigator 6.2 or higher

Netscape Navigator is based on Mozilla 1.0, so Mozilla and Mozilla-based browsers such as Firebird may work. However, because Microsoft doesn't specifically support them, you may be on your own.

Acquiring Windows SharePoint Services
At the time that Windows Server 2003 was released, Windows SharePoint Services wasn't finished, so Microsoft decided to make the Windows SharePoint Services a downloadable feature pack. You can download Windows SharePoint Services from Microsoft's Windows SharePoint Services Web site. The download consists of a 34-MB, self-extracting executable file named STSV2.EXE.

Installing Windows SharePoint Services
Now that you've finished the necessary prep work, it's time to actually install SharePoint Services. To do so, copy the STSV2.EXE file that you downloaded earlier to an empty folder on your server and then double-click the file. When you do, Windows will extract the Setup files and launch the Setup program.

The Setup wizard's initial screen simply asks you to accept the end-user license agreement. Accept the agreement and click Next. The next screen asks whether you want to perform a typical installation or a server farm installation. If you choose to perform a typical installation, Setup will install SharePoint Services, configure IIS to make its default Web site a SharePoint team site, and install the SQL Server desktop engine (WMSDE, a version of MSDE). On the other hand, if you choose to perform a server farm installation, IIS will not be altered and WMSDE will not be installed. It will be up to you to manually set up the various Web sites and to specify the path to the SQL Server. For the purposes of this article, we will be performing a server farm installation.

Click Next and you'll see a summary of the options you have chosen. If the summary appears to be correct, click Install to begin the installation process. On my 2.8-GHz Pentium 4 test server, the file copy portion of the installation took less than a minute to complete. After the files had been copied, Setup ran a script to reconfigure IIS and then launched the configuration screen for the Windows SharePoint Services. In all, the entire process took about a minute and a half to complete.

Configuring Windows SharePoint Services

When Setup completed, it should have opened the Configure Administrative Virtual Server screen, shown in Figure A. This screen allows you to select which IIS application pool Windows SharePoint Services will use. Since this is a fresh install, we will configure my test server to use a brand new application pool.

Figure A

You must either select or create an application pool for IIS to use.

To create an application pool, select the Create New Application Pool radio button and enter a name for the pool. You must then tell SharePoint to use a predefined security account or you must specify the credentials for an account. Click OK to create the new application pool.

After creating the application pool, you'll see a message indicating that the application pool has been created, but that IIS must be restarted. Prior to clicking OK on this screen, you must open a Command Prompt window and enter the IISRESET command. IISRESET will stop and restart the IIS services. When the process completes, close the Command Prompt window, return to the Application Pool Changed screen, and click OK.

The next screen you'll see, shown in Figure B, allows you to configure the connection to the SQL database and to the Active Directory. Begin by entering the name of your SQL Server. In this particular case, I've installed SQL Server 2000 onto the same server that I'm using to run SharePoint Services, so I would enter that server's name.

Figure B

You must provide SharePoint Services with some database and Active Directory information.

The Configure Database section also asks for the name of the SQL Server database. Windows SharePoint Services tends to have problems recognizing any databases that you might have created ahead of time, so it's best to just let the configuration wizard create the database for you. Fill in the database name, but don't select the check box indicating that the database already exists. Just below the database name field, the configuration screen asks which type of authentication you want to use. I recommend using Windows authentication. SQL authentication is less secure and is typically used only by applications that don't support NTLM authentication.

Now that you've filled in all of the database-related fields, let's look at the Active Directory Account Creation section. I'm assuming that your server is already a part of a domain as outlined in the requirements earlier. If this is the case, the users should already have Active Directory accounts, so you can simply select the Users Already Have Domain Accounts radio button and click OK.

You'll now see the Windows SharePoint Services Central Administration screen, which is shown in Figure C. Make a note of the URL for this screen, because you can use this URL to access the Central Administration console in the future if you need to make changes to SharePoint Services.

Figure C

The Central Administration screen is used to configure virtually all aspects of SharePoint Services.

The Central Administration screen is broken down into several sections:

Virtual Server Configuration

Security Configuration

Server Configuration

Component Configuration

Generally speaking, the Virtual Server Configuration section is used to do things like installing SharePoint Services on a new virtual server, configuring settings across all virtual servers, or creating a top-level Web site. The Security Configuration section allows you to manage SharePoint users and administrators, block specific file types, and configure antivirus settings. The Server Configuration section lets you specify the e-mail, database, and Web servers. Finally, the Component Configuration section lets you manage components that work across all virtual servers, such as full-text searches, usage analysis, quotas, locks, and data retrieval services.

Creating a SharePoint Web site
In the real world, you would normally create a corporate-level SharePoint Web site. This would typically serve as your corporate Intranet, offering employees access to things like company news, HR forms, and maybe a calendar of events. You would then set some permissions that would allow individual departments to create their own collaborative Web sites. A full-scale deployment is beyond the scope of this article, but I want to at least show you how to create a corporate-level Web site and set some permissions.

Setting administrative permissions
Begin the process by specifying the SharePoint Administrator. You can do this by clicking the Set SharePoint Administrators Group link. Then enter the domain and user name for the user that you want to have administrative control over SharePoint Services. For example, I want to give administrative control to the Administrator account in the domain TEST, so I would enter TEST\Administrator into the Group Account Name field and click OK.

Creating a top-level Web site
The next step in the process is to create a top-level Web site. This corporate-level Web site should be accessible to all authenticated users. Begin by clicking the Create A Top Level Web Site link. A screen will prompt you to click the virtual server that you want to perform the task on. By default, the list will be empty, so click the Complete List link to populate it.

At this point, click the Default Web Site link. When you do, Windows will display the Extend Virtual Server screen. Verify that the virtual server name is Default Web Site and then click the Extend And Create A Content Database link. You'll now see the Extend And Create Content Database screen, shown in Figure D.

Figure D

The Extend And Create Content Database screen allows you to configure the virtual server.

The first thing you'll have to do is select or create an application pool for the virtual server. Just select the application pool that you created earlier. Now scroll down to the bottom half of the screen, shown in Figure E.

Figure E

This is the bottom half of the Extend And Create Content Database screen.

The next section is the Site Owner section. By default, the site owner is the local Administrator. You might want to change this to a domain administrator. You must also specify the site owner's e-mail address.

In the next section, you must enter the database server and database name, if appropriate. By default though, the Use Default Content Database Server check box is selected. If this check box is selected, you aren't required to fill in any of the fields in this section.

Next is the Custom URL section. Normally, you would have a main site name with sites created beneath it. For example, if your main site was called POSEY, and you wanted to create a new site called SITE1, you would enter /SITE1 into the Custom URL Path field. The URL for the new site would then be http://POSEY/SITE1. Since this is the default site, however, just enter / as the custom URL. You will enter real URL names only for future sites that fall beneath the default site.

The final two sections are the Quota Template and the Site Language sections. Leave the Quota Template set to No Quota and leave the Site Language set to English. Click OK to create the site.

After a couple of minutes, you'll see a message saying that the new site has been successfully created. Click the link in the message to open the site within a new browser window. When you attempt to open the site, you'll be asked to enter logon credentials. Enter the user name and password for the site owner and click OK. You'll now see the Template Selection screen, shown in Figure F. This allows you to select a template that will govern the overall look and feel of your Web site. (You can also exit the site on your own, but this is beyond the scope of this article.) Select a template that works for you and click OK.

Figure F

Select a template and click OK.

After you select a template and click OK, you'll see the Web site that you've just created, as shown in Figure G. As I mentioned earlier, everything that you see in Figure G is customizable, including the site name and logo.

Figure G

This is the newly created Web site.

I'll discuss site customizations in a future article. For now though, I want to show you how to grant access to the site that you've just created. Select the Modify This Workspace link in the site that you've just created, then select the Site Settings command. You'll now see the Site Settings page. Click the Manage Users link to view the Manage Users screen, which allows you to add or remove users and groups.

As you add users and groups, you can select the role that they are assigned. For example, an Administrator has full control of the Web site, while a Reader has read-only access to the site. A Contributor can add content to the site, while a Web Designer can create lists, document libraries, and even alter the pages within the site.

Tuning Sharepoint Services :

To configure WSPS, you need to start the administration tool at Start | Administrative Tools | SharePoint Central Administration. That will open the Windows that you see in Figure H.

Figure H

The SharePoint Central Administration tool is where you configure the system.

The purpose of WSPS is to provide your users with the ability to create shared workspaces. You can enable the ability for your users to create their own sites by enabling “self-service site creation.” This is accomplished by selecting the Select From Default Virtual Server option on the main administration screen. Next, click the name of your virtual server, in this case, Default Web Site, as shown in Figure I.

Figure I

Click the default virtual server to continue.

This actually opens up the Virtual Server Settings window (Figure J) where you can configure all options for this particular virtual server and the related Web site collections.

Figure J

Here is the virtual server configuration screen.

Click the Configure Self-Service Site Creation option on this screen to allow users to create their own top level Web site.

Figure K

Here is where you enable the Self-Service Site Creation option.

On the screen shown in Figure K, select the radio button to turn on this feature and click OK. Enabling this option adds an announcement to the selected site indicating that this feature is now enabled (Figure L). A link is added to allow users to carry out this operation.

Figure L

An announcement and a link is added to the Web site.

When a user follows the link provided, he is asked to fill out a form with details about what the new site will contain.

Windows SharePoint Services administrative overview
The top level SharePoint window has a number of options. Tables A-Dprovide an overview of what you can accomplish with these options.

Table A: Virtual Server Configuration options
Option	Description
Extend or upgrade virtual server	Allows you to make enhancements to a virtual server
Create a top-level Web site	Creates a new top level SharePoint site
Delete site collection	Deletes a top level site and all subsites of the selected site
Configure virtual server settings	Configures the settings related to the virtual server that is selected on the next page; security, collection management, e-mail settings, databases, and more are configurable from this option

Table B: Security Configuration options
Option	Description
Set SharePoint administration group	Allows you to specify a group in addition to the local Administrators group that can administer this SharePoint server
Manage site collection owners	Views and changes the owners for a site collection; in addition to having site collection administrator privileges, the selected users will receive quota or autodeletion notices
Manage Web site users	Adds new users to a SharePoint site
Manage blocked file types	Defines file extensions to restrict; SharePoint can be configured to disallow files of certain types to be stored in the collection
Configure antivirus settings	Configures the option that scans files being added to the collection (if required), if you have antivirus software installed on the server

Table C: Server Configuration
Option	Description
Configure default e-mail server settings	Provides e-mail server settings that will be used for all virtual servers
Manage Web server list	Manages servers in the farm using this page; you can remove servers from the list or click on a server name in the list to start the management process for that server
Set default content database server	Specifies which SharePoint server should be responsible for content management; content databases are created here unless otherwise specified
Set configuration database server	Specifies the server that will be responsible for storing SharePoint configuration information
Configure HTML Viewer	Configures service that allows Office files to be displayed in HTML; some SharePoint components require the use of the HTML Viewer
Configure virtual server for central administration	Changes the IIS application pool used by SharePoint

Table D: Component Configuration
Option	Description
Configure full-text search	Enables full-text searching if you are using a version of SQL Server that supports it
Configure usage analysis processing	Enables and configures usage analysis based on the log files
Manage quotas and locks	Limits the number of users allowed to access a site collection and the locks (quotas) on the collection
Configure data retrieval service settings	Allows you to configure data retrieval services such as OLAP and SOAP to access the SharePoint site

Team Web site overview
The default site installed by SharePoint provides a good glimpse into how this service works. Back in Figure G you can see the options in the left hand column: Documents, Pictures, Lists, Discussions and Surveys. Each option is aptly named and describes the function that it performs.

Documents
The documents option provides you with pseudo-document management capabilities. From here (Figure M), you can upload documents to the site repository, sign documents out, edit documents, discuss a document, view a document’s version history, and much more. Document workspaces can also be created for simplified collaboration.

Figure M

SharePoint has various document management capabilities.

Pictures
Likewise, a picture album can be created and the images manipulated, discussed, sorted, downloaded, mailed, etc. Pictures are uploaded using the Add Picture button and new folders are created with New Folder. Figure N shows a look at the Pictures screen.

Figure N

You can also manage Pictures in SharePoint.

Lists
SharePoint is a powerful way for workgroups to keep up with what’s going on. If the document management features weren’t enough, the lists section might convince you. In this section (Figure O), you can create new announcements that will be shown on the site home page; create a list of contacts used by your team; create events, calendar items and tasks for your team to focus on; and create a list of links to Web sites frequented by the team.

Figure O

Here are the lists available in SharePoint.

Discussions
Discussions are essential to meaningful team communication. SharePoint includes discussion board capability. You can add as many discussions as you like on any topic and use it to keep the ideas flowing between team members. Figure P shows an example.

Figure P

Discussion board functionality is also included.

Surveys
Discussions are great but sometimes you’ll want quicker feedback and want to get input from your team members on a specific topic. A survey is a great way to do that. WSPS includes the ability to create completely custom surveys with many different types of questions. Survey responses can be in the form of a free text field, multiple choice, rating scales, currency, date and time, database lookup, yes/no questions, and more.

Summary
As a free add-on to Windows Server 2003, Windows SharePoint Services provides a compelling reason to move to this operating system. With team work features such as document management, surveys, lists, and discussions, there is a lot of great stuff that teams can use to collaborate more effectively. Overall, this is an excellent system and is easily extended for greater functionality.

Create a New Web Site in IIS

You must create a new Web site for each security model that you want. For example, if you want to have both Anonymous access and Basic authentication, you must create two Web sites. On one site you would specify Anonymous access, and on the other site you would specify Basic authentication.

Note that you should not modify settings on the Default Web Site. Specifically, SharePoint Portal Server requires the Default Web Site to use port 80 as the TCP port. Do not change the port to an alternative HTTP port (such as 8000 or 8080) after installation. Ensure that port 80 is specified and remains as the primary port for the server.

To create a new Web site

1. On the taskbar, click Start, point to Programs, point to Administrative Tools, and then click Internet Services Manager.

2. Expand the node for the SharePoint Portal Server computer.

3. Right-click the name of the SharePoint Portal Server computer, point to New, and then click Web Site. The Web Site Creation Wizard appears.

4. Click Next, and then follow the instructions in the wizard:

· Type a description of the Web site, and then click Next. The description appears in the tree view of the console. For example, if this Web site is to be used for Anonymous access, you could type AdventureWorksAnon as the description.

· Select the IP address. Do not select (All Unassigned).

· Type 80 for the TCP port number.

· Type the external FQDN as the host header. The host header is of the form external_server_name.external_domain_name. For example, if the external server name for your SharePoint Portal Server computer is AdventureWorks, and the external domain name is adventure-works.com, you would type AdventureWorks.adventure-works.com as the host header.

· Click Next.

· Enter the path for your home directory. It is strongly recommended that the home directory be under the Inetpub directory. For example, the path can be C:\Inetpub\AdventureWorks. See “Test the Extranet from Your Intranet” in this paper for instructions on creating a default Web page.

· If you do not want to allow Anonymous access to SharePoint Portal Server, clear the Allow anonymous access to this Web site check box. For more detailed information about specifying security on the new Web site, see “Modify the Security Settings on the New Web Site” in this paper.

· Click Next.

· On the Web Site Access Permissions page, click Next. Do not change the default access permissions.

· Click Finish. The new Web site appears.

5. Expand Default Web Site, and then note the following five virtual directories (nodes on the tree): Exchweb, SharePoint Portal Server, Public, MSOffice, and YourWorkspace, where YourWorkspace represents the name of the virtual directory for your workspace. For example, if your workspace is named Marketing, look at the Marketing virtual directory. Write down the local path for each of these virtual directories (or use copy and paste while performing the steps). You need this path to complete steps 6 through 8. To find the local path, do this for each of the five virtual directories:

· Right-click the virtual directory, and then click Properties.

· On the Virtual Directory tab, note (or copy) the path shown in Local Path.

· Close the Properties page.

6. Right-click the new Web site that you created in step 4, point to New, and then click Virtual Directory. The Virtual Directory Creation Wizard appears.

7. Click Next, and then follow the instructions in the wizard:

· In Alias, type Exchweb and then click Next.

· In Directory, type (or paste) the path for Exchweb from step 5, and then click Next.

· On the Access Permissions page, click Next. Do not change the default access permissions.

· Click Finish.

8. Repeat steps 6 and 7 to create a virtual directory for SharePoint Portal Server, Public, MSOffice, and for YourWorkspace, where YourWorkspace represents the name of the virtual directory for your workspace.

Important The names of the new virtual directories must match exactly the names of the original virtual directories under the Default Web Site. Do not rename the virtual directories.

9. After creating the virtual directories, for the Public and YourWorkspace virtual directories on the new Web site that you created, do the following:

· Right-click the virtual directory, and then click Properties.

· Click the Virtual Directory tab.

· In Application Protection, select Low (IIS Process).

· On the Virtual Directory tab, click Configuration.

· On the App Mappings tab, click Add.

· In Executable, type the path to the msdmisap.dll file. You can also browse to the msdmisap.dll file. By default, this file is located in the SharePoint Portal Server \Bin directory. For example, if you installed SharePoint Portal Server to Program Files\SharePoint Portal Server, this file is in Program Files\SharePoint Portal Server\Bin.

Important In Executable, ensure that path entered follows the 8.3 naming convention. For example, if the msdmisap.dll file is in the Program Files\SharePoint Portal Server\Bin directory on drive D, type the path in Executable as D:\Progra~1\ShareP~1\Bin\msdmisap.dll

· In Extension, type * and then click OK.

· Clear the Check that file exists check box.

· Click OK to close Application Configuration.

· Click OK to close the Properties page.

10. For the YourWorkspace virtual directory on the Web site that you created, do the following:

· Right-click the virtual directory, and then click Properties.

· On the Virtual Directory tab, select the Write check box.

· Click the HTTP Headers tab, and then click Add.

· In Custom Header Name, type MicrosoftTahoeServer

· In Custom Header Value, type 1.0

· Click OK.

· Click OK to close the Properties page.

11. For the MSOffice virtual directory on the Web site that you created, do the following:

· Right-click the virtual directory, and then click Properties.

· Click the Virtual Directory tab.

· In Execute Permissions, select Scripts and Executables.

· Click OK to close the Properties page.

12. Right-click YourVirtualWeb, where YourVirtualWeb is the name of the new Web site you just created, and then click Start. If YourVirtualWeb is already started, omit this step.

Enable Discussions on the New Web Site

To use Web discussions on your SharePoint Portal Server computer from the Internet or extranet, you must modify the registry.

Use Web discussions to discuss a document with other users. Web discussions allow users to add remarks about a document without modifying the document itself. Discussions are threaded — replies to a discussion remark appear directly underneath the original remark. In addition, multiple discussions about the same document can occur at the same time. SharePoint Portal Server consolidates comments in a single location, allowing them to be easily reviewed.

To enable discussions on the new Web site

1. On the taskbar, click Start, and then click Run.

2. Type regedit, and then click OK.

Caution Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.

3. In Registry Editor, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\9.0\Web Server\1.

4. On the Registry menu, click Export Registry File.

5. Save the file as EnableDiscussions on your desktop.

6. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\9.0\Web Server\1.

7. Right-click 1 and then click Rename.

8. Type number and then press ENTER. Number is determined from the following procedure:

· On the taskbar, click Start, point to Programs, point to Accessories, and then click Command Prompt.

· Navigate to the directory where adsutil.vbs is located. Typically, this is in the Inetpub\AdminScripts directory on the operating system drive.

· Type cscript adsutil.vbs enum W3SVC/number, where number is 1, 2, etc. Type each number in order until the properties display the name of the new Web site. Typically, W3SVC/1 is the Default Web Site, W3SVC/2 is the Administration Web Site, and W3SVC/3 is the new Web site. If W3SVC/3 is the new Web site, you type 3 as number when renaming the registry key in this step.

9. Click Web Server.

10. On the Registry menu, click Import Registry File.

11. Import EnableDiscussions that you saved to the desktop previously.

12. Click OK.

13. Click 3, right-click Server Root Url in the right pane, and then click Modify.

14. In Value data, type the external FQDN of the server, and then click OK. For example, type http://AdventureWorks.adventure-works.com.

15. Close Registry Editor.

16. Restart the server.

Modify the Security Settings on the New Web Site

By default, SharePoint Portal Server uses NTLM authentication (on the Default Web Site in IIS). To use SharePoint Portal Server on the Internet or extranet, you must modify the security settings on the new Web site to Basic authentication or Anonymous.

Do not specify both Basic authentication and Anonymous access on the same Web site. If you want both Basic authentication and Anonymous access, create two Web sites.

For example, if you want to use both Basic authentication and Anonymous, configure the security settings as follows:

· For the Default Web Site in IIS, leave the default of NTLM authentication.

· Create a new Web Site in IIS and specify Basic authentication access.

· Create a second new Web Site in IIS and specify Anonymous access.

SharePoint Portal Server does not support both NTLM and Anonymous authentication on the same Web site.

In addition, if you modify the security setting to Anonymous, users cannot create subscriptions from the dashboard site.

Note that SharePoint Portal Server licensing requires that all devices accessing the server have a valid license. Nothing in this white paper is meant to waive or modify any rights or requirements under the end user license agreement or other applicable license agreement for SharePoint Portal Server.

Caution Do not run Windows 2000 Internet Server Security Tool (available for download from http://www.microsoft.com/TechNet/security/tools.asp) after installing SharePoint Portal Server. Running this tool may disable the dashboard site. For the latest information about implementing IIS security configurations to secure your server, see http://www.microsoft.com/SharePoint.

To modify the security settings on the new Web site

1. On the taskbar, click Start, point to Programs, point to Administrative Tools, and then click Internet Services Manager.

2. Expand the node for the SharePoint Portal Server computer.

3. Right-click YourVirtualWeb, where YourVirtualWeb is the name of the new Web site you created, and then click Properties.

4. Click the Directory Security tab.

5. In Anonymous access and authentication control, click Edit.

6. In Authentication Methods, select the authentication method you want for the new Web site:

· To enable Anonymous access, select the Anonymous access check box. Clear all other check boxes. Do not specify both Anonymous access and Basic authentication on the same Web site.

· To enable Basic authentication, select the Basic authentication (password is sent in clear text) check box, and then click Yes when prompted. Clear all other check boxes. Do not specify both Basic authentication and Anonymous access on the same Web site.

Note All information, including passwords, sent over the Internet is in a readable format. To secure your transmissions, use SSL. For more information, see “Enable SSL” in this paper.

7. Click OK.

8. Click OK to close the Properties page.

If you use Anonymous access, you must also assign the Internet Guest Access account to the reader role on each workspace for which you want Anonymous access. If you are configuring Basic authentication only, you do not need to assign the Internet Guest Access account to the reader role.

To assign the Internet Guest Access account to the reader role

1. On the taskbar, click Start, point to Programs, point to Administrative Tools, and then click SharePoint Portal Server Administration.

2. In the console tree, click to expand the server, and then select the workspace.

3. On the Action menu, click Properties.

You can also right-click the workspace name, and then click Properties on the shortcut menu.

4. Click the Security tab.

5. Click Add.

6. From Select Users or Groups, select the name of your server from Look in.

7. From the list of names, select the name IUSR_server_name, where server_name is the NetBIOS name of your server.

8. Click Add, and then click OK.

9. Click Apply. The account is added to the Reader role.

If you close the Properties page, open it, and then click the Security tab, the account you just entered is listed as Internet Guest Account.

Configure the Proxy Server

If you want to use SharePoint Portal Server on the Internet and you have a proxy server, you must:

· Ensure that the external IP address of your SharePoint Portal Server computer is added to the proxy server.

· Map the internal static IP address of the server to an external static IP address. If you are using Microsoft Internet Security and Acceleration (ISA) Server 2000, this is called server publishing. Permissions pass through and the host header file is not modified.

If you are not using ISA Server, you must configure your proxy server as follows:

· Password and authentication information must be passed through the proxy server to the SharePoint Portal Server computer inside the firewall.

· The host header name must stay intact when passing through.

· Do not use SSL bridging.

Before performing the following procedures, you must know the static external IP address assigned to your SharePoint Portal Server computer. This is not the same IP address as the static internal IP address for the server. You must also have a subnet mask. You receive a range of static external IP addresses and a subnet mask when you first establish Internet access through Network Solutions or through another company authorized by the ICANN.

The following procedures apply if you are using ISA Server as your proxy server. Note that the following steps assume that you have already enabled the firewall and reverse proxy for ISA Server. Additionally, your ISA Server must allow internal users to access the Internet by using the proxy without authentication. If you have a proxy server that requires a server to provide authentication to access the Internet from your intranet, you will not be able to download a Web part from the Internet. This is because the ServerXMLHTTP object cannot access the Internet if authentication is required.

To ensure that the external static IP address of your server is added to the proxy server

1. On the desktop on the proxy server, right-click My Network Places, and then click Properties.

2. Right click the NIC that is connected to the Internet, and then click Properties.

3. Under Components checked are used by this connection, click Internet Protocol (TCP/IP), and then click Properties.

4. Click Advanced.

5. Under IP addresses, scroll through the list of IP address to ensure that the external static IP address for the SharePoint Portal Server computer is listed. This is the same external static IP address used to create the DNS entry for the server.

6. If the IP address appears in the list, no further action is required. If the external static IP address does not appear in the list of IP addresses, you must complete steps 7 through 12.

7. Click Add. The TCP/IP Address dialog box appears.

8. In IP address, enter the external static IP address.

9. In Subnet mask, enter the subnet mask for the IP address.

10. Click Add to close the TCP/IP Address dialog box, and then click OK.

11. Click OK, and then click OK to close the Properties page.

12. Restart the server.

To map an external IP address to an internal IP address

1. On the taskbar, click Start, point to Programs, point to Microsoft ISA Server, and then click ISA Management.

2. Expand Servers and Arrays.

3. Expand the name of your proxy server.

4. Expand Publishing.

5. Right-Click Server Publishing Rules, point to View, and then click Taskpad.

6. Click Publish a Server. The New Server Publishing Rule Wizard appears.

7. In Server publishing rule name, type a name to identify the new publishing rule, and then click Next.

8. On the Address Mapping page, type the internal static IP address of the server in IP address of internal server.

9. On Address Mapping page, type the external static IP address in External IP address on ISA Server.

10. Click Next.

11. On the Protocol Settings page under Apply the rule to this protocol:

· Select HTTP Server if you have not enabled SSL.

· Select HTTPS Server if you have enabled SSL.

Note These protocols must be enabled on the proxy server. See the documentation for your proxy server for procedures to enable the protocols.

12. Click Next.

13. On the Client Type page, click Any request, and then click Next.

14. Click Finish.

15. Double-click the rule you just created, and on the General tab, ensure that the Enable check box is selected.

It may take up to 15 minutes for the mapping to be effective. If the mapping has not become effective after 15 minutes, do the following:

1. On the taskbar, click Start, point to Programs, point to Microsoft ISA Server, and then click ISA Management.

2. Expand Servers and Arrays.

3. Expand the name of your proxy server.

4. Expand Monitoring.

5. Right-Click Services, point to View, and then click Taskpad.

6. Select the Web proxy service, and then click Stop a Service.

7. Select the Firewall service, and then click Stop a Service.

8. Select the Web proxy service, and then click Start a Service.

9. Select the Firewall service, and then click Start a Service.

If the mapping has not taken affect within 30 minutes after this procedure, restart the proxy server.

Test the Extranet from Your Intranet

This step enables you to confirm that you have set up your server correctly to access it from the extranet or Internet.

Important Perform the following procedure from the server.

To test the extranet from your intranet

1. Create a test file in the home directory for the new Web site:

· Create default.htm and place it in the home directory. Your home directory should be under the Inetpub directory. For example, the home directory can be C:\Inetpub\AdventureWorks.

· Enter some text in default.htm and save the file. For example, enter

some text, such as the external FQDN

2. Create an entry in the hosts file on the server:

· Navigate to the hosts file. Typically, this file is located in WINNT\system32\drivers\etc on the operating system drive.

· Open hosts in Notepad.

· Add the SharePoint Portal Server computer (internal static) IP address along with the external name of your server to the hosts file. For example, 10.0.0.X AdventureWorks.adventure-works.com

· Save the file.

3. Modify the proxy settings for Internet Explorer on the server:

· Open Internet Explorer.

· On the Tools menu, click Internet Options.

· Click the Connections tab, and then click LAN Settings.

· Select the Use a proxy server and Bypass proxy server for local addresses check boxes.

· Type the address and port number for the proxy server, and then click Advanced.

· In Do not use proxy server for addresses beginning with, type *root_domain_name and then click OK. An example of a root domain name is adventure-works.com, so you would type *adventure-works.com.

· Click OK, and then click OK to close Internet Options.

4. In Internet Explorer, type http://external_server_name.external domain name in Address. You should see the text that you typed in default.htm. For example, if you typed AdventureWorks in default.htm, you should see AdventureWorks displayed.

If you can access the server, you have specified the external FQDN correctly.

If you cannot access the server, ensure that the Web site is started. To do this:

1. On the taskbar, click Start, point to Programs, point to Administrative Tools, and then click Internet Services Manager.

2. Expand the node for the SharePoint Portal Server computer.

3. Right-click YourVirtualWeb, where YourVirtualWeb is the name of the new Web site you created, and then click Start.

If you still cannot access the server, see “Troubleshooting” in this paper.

After you successfully access the extranet from your intranet, you should test access from the Internet.

Test the Extranet from the Internet

This step enables you to confirm that you have set up your server correctly to access it from the Internet.

Important Perform the following procedures from a computer that is not connected to your corporate local area network (LAN) or wide area network (WAN) (either directly or by dialing in to the network).

To test the extranet from the Internet

1. From the computer connected through an ISP to the Internet, type http://external_FQDN

For example, type http://AdventureWorks.adventure-works.com

The default Web page (default.htm) that you created during the previous section is displayed.

2. If the default Web page is displayed, type http://external_FQDN/workspace_name

For example, type http://AdventureWorks.adventure-works.com/Marketing

The dashboard site for the Marketing workspace is displayed.

If you cannot access the dashboard site, see “Troubleshooting” in this paper.