You are on page 1of 17

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
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
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
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.
Figure 2

The SharePoint Team Site window

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

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

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

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

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 Allows you to make enhancements to a virtual server
Create a top-
Creates a new top level SharePoint site
level Web site
Delete site
Deletes a top level site and all subsites of the selected site
Configures the settings related to the virtual server that is
Configure virtual selected on the next page; security, collection management, e-
server settings mail settings, databases, and more are configurable from this

Table B: Security Configuration options

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

Table C: Server Configuration

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

Table D: Component Configuration

Option Description
Enables full-text searching if you are using a version of
Configure full-text search
SQL Server that supports it
Configure usage analysis Enables and configures usage analysis based on the
processing log files
Manage quotas and Limits the number of users allowed to access a site
locks collection and the locks (quotas) on the collection
Configure data retrieval Allows you to configure data retrieval services such as
service settings 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.

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.

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.

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 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.

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.

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.