Installing MOSS

By now, you have the necessary information to start the installation of MOSS. The following section describes the exact steps required to install Microsoft Office SharePoint Server 2007. If you have other web applications installed on the same server, please make a backup before you start, to be prepared for the unlikely possibility that something goes wrong and the server gets messed up beyond repair!

When installing MOSS in Advanced mode, you have a choice of which web application to use for the portal and team sites. When you select the virtual IIS server for this web application, it is automatically extended, and you do not need to do this manually.

Important 

In the following sections are three complete sets of step-by-step instructions on how to install MOSS. You only have to read the description for the particular type of installation you are about to do. To get the MOSS 2007 installation CD, you typically order it from your favorite software vendor.

Installing on a Stand-Alone Server with SQL Express

Installing a MOSS using a local SQL Express database is very straightforward and easy. You can do it within 10 minutes without much hassle. Remember that you cannot perform this type of installation on a domain controller, since it will not allow the SQL Express database! Follow the steps in the Try It Out to install both the MOSS application and the SQL Express database on the same server.

Try It Out Install MOSS and SQL Express on a Stand-Alone Server

1. Log on as an administrator to the Windows 2003 server you will use for your MOSS and SQL Express installation.

2. Make sure that Windows 2003 Server has the latest service packs and security patches installed by going to Start All Programs Windows Update.

3. Verify that you have ASP.NET, and the .NET Framework 3.0 package installed on this server, as previously described in the "Software Requirements" section.

4. Start the installation by mounting the MOSS CD-ROM. You can also choose to start it via SETUP.EXE on the CD-ROM directly.

5. The first page asks about the product key. Note that this key will decide if you are installing Standard or Enterprise edition of MOSS. If you install the Standard Edition, you can later upgrade to Enterprise, but not the other way around! Enter the product key and click Continue.

   Important 

   Microsoft provides free product keys for a 180-day trial period. One product key is for the MOSS Standard Edition, and one is for the Enterprise Edition. This installation can later be converted to a fully licensed MOSS server simply by entering a real production key. If you do so, everything stored in the servers is retained, and there is no need for a reinstallation of MOSS.

6. On the next page, choose the type of installation you want. Since you will be installing a standalone server, click Basic. The installation now starts and runs from 5 to 15 minutes, depending on the server hardware.

7. After the installation, you will be prompted to run the SharePoint Product and Technologies Configuration Wizard. Click Close to close the installation program and start the Configuration Wizard.

8. On the welcome page, click Next, then click Yes to accept that the IIS will be restarted during the configuration. This process now starts, and takes about 5 to 15 minutes, depending on the server hardware.

9. When the configuration is completed, click Finish. The intranet portal that the Configuration Wizard created automatically for you is now displayed and ready to be used (see Figure 4-1).

Figure 4-1

After the Installation of the Stand-Alone Server

There are many things to do directly after the installation, but some of these need immediate attention, and other things will be taken care of when appropriate. For a single-server installation of MOSS, you should now do these two things:

• q Download and install the latest service pack for MOSS and WSS. You start by installing the WSS service pack and then the MOSS service pack. Good places to start looking for these service packs are http://www.microsoft.com/technet/windowsserver/sharepoint for WSS and http://www.microsoft.com/office/sharepoint for MOSS. You may also find these service packs using Microsoft Update.

• q Do a full backup of the MOSS server environment with the backup utility that comes with MOSS (see the end of this chapter) or your ordinary backup program, if it is SharePoint-aware.

Checking the New Folder and Applications

The portal site is now up and running, and you will very soon check it out. But first take a look at what has changed in the Windows 2003 server. You have several new file directories used by MOSS and the underlying WSS environment:

• q C:\Program Files\Common Files\Microsoft Shared\web server extensions\12: (Where 12 is the internal version number of MOSS.) This folder has several new directories, including a Bin directory where several tools for WSS are stored. All these files and folders are identical to a pure WSS installation.

• q C:\Program Files\Microsoft Office Servers\12.0: This location has several folders and files specific for the MOSS application. There is a Bin directory that contains all the DLL files for MOSS. In the Data folder you will find index files, and in the Log folder are installation log files and other log files that you can view from within the MOSS administrative tool.

• q C:\Program Files\Microsoft Microsoft Office Servers\12.0\Data\MSSQL: This folder structure stores the SQL Express information; the Data folder stores the actual SQL database files; the Log folder stores the MS SQL transaction log files and error log files.

There are also two new application links listed in the Start All Programs Microsoft Office Server node. By default you will see these links there:

• q SharePoint 3.0 Central Administration: This is the administrative tool for SharePoint. This is simply a link to the web site in the virtual IIS server "SharePoint Central Administration."

• q SharePoint Products and Technologies Configuration Wizard: This is the online help manual for SharePoint. You can also find help inside the user portal site almost anywhere.

Important 

You can also start both of these two tools from Start Administrative Tools.

Checking the New Virtual IIS Server Settings

Finally, you will find that a number of web applications (such as virtual IIS web servers) that have been both created and extended by the installation program and the Configuration Wizard. Since MOSS is much more advanced than WSS, you will find more web applications in the IIS Web Sites node. To see them, open the IIS manager: Start Administration Tools Internet Information Service (IIS) Manager. Then expand the node Web Sites. Note that you have a number of IIS virtual web servers there:

• q SharePoint Central Administration v3: Used by SharePoint for the administration web site. This virtual server was created during the initial phase of the MOSS installation, before the portal site was created.

• q SharePoint – 80: This is the virtual server that hosts the site collection used by the portal site.

• q SharePoint – nnn : (nnn = a randomly created TCP port number). This virtual server is used by the Shared Service Provider, and its first instance, SharedServices1; you will learn more about the Shared Service Provider later in this chapter

• q Office Server Web Services: This is a general service for enabling MOSS and other Office Server applications to use the Web service technique to retrieve or store data from SharePoint's database.

Right-click on SharePoint – 80 and select Properties. Switch to the Home Directory tab. Note the application pool name this virtual server is using; by default it will be SharePoint – 80, the same name as the virtual IIS server itself. The other virtual IIS server, SharePoint Central Administration v3, will by default use the application pool SharePoint Central Administration v3. Expand the node Application Pools (located directly above the Web Sites node), right-click on either of the two application pools mentioned above, and switch to the Identity tab. Note that the security account this application pool is using is the built-in Network Service account, which is fine since this installation is using a local SQL Express database.

To summarize: MOSS uses four virtual IIS servers for a stand-alone installation, one for the web sites that your SharePoint users utilize and three others for the administration of SharePoint. All of these virtual servers use separate application pools. But all these application pools use the same security account, that is, Network Service.

Important 

The following section describes how to install MOSS using the MS SQL Server database, instead of the SQL Express database; You can skip this section if it does not match your required installation procedure. However, if you want to know how to install MOSS in advanced mode using the full SQL Server product, be sure to read the following section.

Installing a MOSS Using the MS SQL Database

One of the most common installation scenarios for small- and medium-sized organizations is a MOSS that uses a MS SQL Server; this SQL server may be installed on the SharePoint server, i.e., a single server, or a remote server, i.e., a small farm. Many of the following steps are identical to the previous installation scenario using a local SQL Express database, except for these important things:

• q You need to install MS SQL Server before installing MOSS. If you are using SQL Server 2000, you must install Service Pack 3a or later. If you are using SQL Server 2005, install Service Pack 2 or later.

• q You will need to define more service accounts. An example is the user account that MOSS will use when communicating with the MS SQL server (also used as the Application Pool Identity account).

Important 

SQL Server 2000 runs with just 64 MB of memory, while SQL Server 2005 needs at least 192 MB. For a stand-alone server, you may want to use the old SQL Server 2000, due to its lower memory requirements.

If this is the first time you install MOSS, you may need some assistance on how to set up SQL Server as well. Follow these steps to install both MS SQL 2000 + SP3a and MOSS 2007 on the same server:

Try It Out Install MS SQL Server 2000 and Service Pack 4

1. Log on as an administrator on the Windows 2003 server you will use for your MOSS and MS SQL installation.

2. Make sure that Windows 2003 Server has the latest service packs and security patches installed by going to Start All Programs Windows Update.

3. Verify that you have ASP.NET and the .NET Framework 3.0 package is installed, as described in the "Software Requirements" section in this chapter.

4. Mount the CD with the MS SQL 2000 Server. On the Welcome page, click Next.

5. Computer name page: Select Local Computer, and click Next.

6. Installation Selection page: Select Create a new instance of SQL Server, or install Client Tools, then click Next.

7. User Information page: Enter the registered owner of the SQL 2000 license, and click Next.

8. Software license agreement page: Read the agreement and if you accept it, click Yes to continue.

9. Installation Definition page: Select Server and Client Tools, and click Next.

10. Instance page: Make sure that the Default option is checked, and click Next.

11. Setup Type page: Choose the option Typical, and click Next.

12. Service Account page: Accept the default option, "Use the same account for each service. Auto start SQL Server Service." Then select the user account that will be used by the SQL services. For a local installation you can select the option Use the Local System account. If you select another account, make sure that it is a member of the computer's local Power Users group or the local Administrators group. Click Next to continue.

13. Authentication Mode page: Accept the default, Windows Authentication Mode, and click Next.

14. Start Copying Files page: Click Next to continue.

15. Choose License Mode page: Select the type of license you have, then click Continue to start the actual installation.

16. Setup Complete page: Click Finish to complete the installation of MS SQL Server 2000.

17. The next step is to install the service pack for MS SQL Server 2000. SharePoint requires at least Service Pack 3a, but you should install Service Pack 4 or later. You can get this service pack from the following URL: http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads. Look for the latest service pack for MS SQL Server 2000. Download it and expand it, then start the installation file Setup.bat.

18. Welcome page: Click Next.

19. Software License Agreement page: Read it and if you accept it, click Yes to continue.

20. Instance Name page: Click Next.

21. Connect to Server page: Accept the default option, "The Windows account information I use to log on to my computer with (Windows authentication)," and click Next.

22. SA Password Warning page: Enter a password for the SQL account SA. Make sure to store it in a safe place. Then click OK.

23. SQL Server 2000 Service Pack 4 Setup page: Check the option "Upgrade Microsoft Search and apply SQL Server 2000 SP4 (required)," then click Continue.

24. Error Reporting page: If you want to activate this feature, check this box. Click OK.

25. Start Copying Files page: Click Next. This step will take several minutes to complete.

26. When the installation is done, you will see a dialog box reminding you to make a backup. Click OK and then Finish to complete the installation of the service pack.

Important 

The SQL Server service MSSQLSERVER has not started at this point. You may have to start it manually or restart the server before installing MOSS.

This concludes the MS SQL Server 2000 installation. Since you are configuring a single-server installation, the next step will be to install MOSS on the same server. During this installation you will be asked about several service accounts for SharePoint. One of these is the configuration database administration user account. In previous versions of SharePoint, you had to manually grant this account the proper permission to the SQL Server, that is, Security Administrators and Database Creators; this is now done automatically by SharePoint's Configuration Wizard. If you later want to check this manually, follow the steps in the Try It Out below. But remember that at this stage you have not installed MOSS, so you will not find any MOSS service accounts yet.

Try It Out Checking Accounts Given Permissions to SQL

1. Log on as an administrator to the MS SQL server.

2. Start the SQL management tool by going to Start All Programs Microsoft SQL Server Enterprise Manager.

3. Expand the nodes: Microsoft SQL Servers SQL Server Group (local) (Windows NT).

   Important 

   A red dot at the server icon (in the system tray) indicates that the SQL Server service is not yet started. If you see this red dot, right-click on the server node and select Start now.

4. Expand the Security node, and click Logins to see all accounts given permissions to the SQL server. Double-click on the user account you want to check, and open the Server Role tab to see its given permissions. Then click OK to save and close it.

5. Close the SQL Server Enterprise Manager.

SQL Server 2000 is now ready for the MOSS server. Follow the steps in the next Try It Out to install MOSS.

Try It Out Install MOSS 2007 Using a SQL Server

1. Log on as an administrator to the Windows 2003 server you will use for your MOSS and SQL Express installation.

2. Make sure that Windows 2003 Server has the latest service packs and security patches installed by going to Start All Programs Windows Update.

3. Verify that you have ASP.NET and the .NET Framework 3.0 package installed on this server, as previously described in the "Software Requirements" section.

4. Start the installation by mounting the MOSS CD-ROM. You can also choose to start by using SETUP.EXE on the CD-ROM directly.

5. The first page asks about the product key. Note that this key will indicate if you are installing the Standard or Enterprise Edition of MOSS. If you install the Standard Edition, you can later upgrade to Enterprise, but not the other way around! Enter the product key and click Continue.

   Important 

   Microsoft provides free product keys for a 180-day trial period. One product key is for the MOSS Standard Edition and one is for the Enterprise Edition. This installation can later be converted to a fully licensed MOSS server simply by entering a real product key. If you do so, everything stored in the server is retained, and there is no need for a reinstallation of MOSS.

6. On the next page, choose the type of installation you want; since you will install a single-server configuration, click Advanced. Next, you can choose from three types of installations:

   • q Complete: Installs all components on the same server. You can later add more servers to form a SharePoint farm. This requires a preinstalled version SQL Server.

   • q Web Front End: Installs only the components necessary to display Web content in HTML to the users. You can later add more servers to form a SharePoint farm. This requires a preinstalled SQL Server.

   • q Stand-alone: Installs all components, plus the SQL Express database on this computer; that is, it performs the same type of installation as Basic, but allows the administrator to configure more settings, such as the file locations. You cannot add servers later to this setup.

7. Select Complete installation, then switch to the File Location tab and choose where the SharePoint files will be installed. For the best performance, use a physical disk other than the Windows boot disk. Click Install Now when all the settings are okay, and you are ready to start the installation.

8. After the installation, you will be prompted to run the SharePoint Product and Technologies Configuration Wizard. Click Close to close the installation program and start the Configuration Wizard.

9. On the Welcome page, click Next, then click Yes to agree that the IIS will be restarted during the configuration. This process now starts, and takes about 5 to 15 minutes, depending on the server hardware.

10. On the Connect to a server farm page, you can choose between connect to an existing SharePoint farm or create a new one. Since this is the first server you are installing, you must select No, I want to create a new server farm, and then click Next.

11. On the Specify Configuration Database Settings page (see Figure 4-2), you can define which SQL server this SharePoint server will use, plus the name of the configuration database, and the database access user account. Enter the name of the database server (i.e., the local server for a stand-alone installation or a separate server for a small farm). Accept the default name for the configuration database, then enter the user account that SharePoint will use whenever it communicates with the SQL Server. Click Next to continue.

    
    Figure 4-2

    Important 

    The user account defined as the Database Access Account will automatically be granted permissions as Security Admins and Database Creators in the SQL Server, by the Configuration Wizard.

12. On the Configure SharePoint Central Administration Web Application page, you will define the TCP port number used by the web application (i.e., an extended virtual IIS server) that will host the Central Administration tool. By default, this TCP port number is randomly chosen, but a good tip is to set this number to something easier to remember, for example 5000. You must also choose the type of authentication provider. Unless you have configured the Kerberos settings in your Windows domain, select NTLM, and click Next to continue to next page.

13. On the Completing the SharePoint Products and Technologies Configuration Wizard page, you will see a summary of your chosen settings. If something is wrong, then click Back and correct the error. If all is okay, click Next to start the configuration process, which will create the Central Administration tool, and the virtual IIS servers and applications pools, just to mention a few things.

14. When the Configuration Wizard is completed, click Finish to close this page. Next, the Central Administration tool will open.

15. The installation and basic configuration is completed, but you will need to perform several more steps before the new SharePoint server has a user site up and running. Just look at the text in red on the left side of this page, saying "Server Farm Configuration Not Complete!" To assist you, SharePoint displays a task list on the home page of its Central Administration tool, which you should follow in the given order. Start by clicking on READ FIRST for deployment instructions. On the page with the task details is a description of this task and what you are supposed to do next. Click the link in the Action field, to see the Quick Start Guide. Next click Delete Item and then Yes to remove this item from the task list.

16. The next task is Initial deployment: Add servers to farm. This task should take you to the Operations page, and its link Servers in farm. If it does not; simply open the Operations page and click the Servers in farm link manually. On that page you will see a summary of all SharePoint servers in the farm, and it will consist of just one single server for now, since this is the first server in the farm. This server is also running several services, such as the Central Administration service, the Windows SharePoint Services database, and Windows SharePoint Services web application. At this time, there is nothing to change on this page, so click Home on the top menu bar to return to the task list, then delete this task, as described in the previous step.

17. The next task is Initial deployment: Assign services to servers. This task will take you to the Operations page, and its Services on server link. Here, you can see a list of all services for the farm. Select the Single Server or Web Server for small server farms option at the top of the page (see Figure 4-3), then look at the list of services below. If there is any service with the comment Required on Farm that is not running, click the Start link in the Action column. By default, none of these services is running:

    
    Figure 4-3

    1. Click Start for the Excel Calculation Services.

    2. Click Start for the Office SharePoint Server Search. This will open a new page (see Figure 4-4) where you can configure the search settings. You can choose if this server will be running the indexing service and/or the Search Query service. Check both of these options to have this server run both indexing and search queries. This is the way that you define what SharePoint role a specific server have when there is more than one SharePoint server in this farm. Add an e-mail address that will receive any messages about the Search service. Next, enter the user name and password for the Farm Search Service Account. This account will be used by the Windows 2003 Office Search Service. For a simple installation of MOSS, you can use the same account here as for the other service accounts (sp_service). You can see the file location for the index files listed here, but you cannot change it. Select indexer performance if necessary, or keep the default setting, Partly reduced. Finally, you can select one particular server that will be responsible for running the indexing process. Since this is a very CPU-intensive task, it may be a good idea to have a separate server dedicated to index crawling. Click Start to save and close this page.

       
       Figure 4-4

    3. Click Start for the Windows SharePoint Services Search. This is also a long configuration page (see Figure 4-5). Use this page to configure how WSS Search will index the help files (but not the WSS content) in SharePoint. Enter a user name to be used as the service account, plus its password. Do not use built-in accounts for this setting. For simple installations, you can use the same account here as for other services (such as sp_service)! Then enter a user name and password to be used as the Content Access Account (which account this service will use when indexing content). Accept the default database server name and its database table name, and then define how often this content will be indexed; the default is once every five minutes. Click Start when ready.

    
    Figure 4-5

18. The Services on Server opens again. Notice that there is no service marked as "Required on Farm not running" any more. Although there are some services not yet started, at this time you do not need them. Later, you will come back to this page again. Click Home to return to the Administrators task list. Delete this task now.

19. The final task is to create a Shared Service Provider (SSP). You will learn more about this SSP in Chapter 5, but for now, open this task, and click its Action link, Configure server farm's shared services. On the next page, you will configure a number of settings:

    Important 

    During the following procedure, you will start with one web page, then temporarily switch to another page to create web applications, then go back to the first page again. This may happen several times, depending on your configuration.

    1. SSP Name: Note the name of this SSP: SharedServices1. Here, you configure the web application that the SSP will use. Click Create a new Web Application. A second page will now show up; this page is very long with lots of settings. Use it to define the new web application for the SSP. Start by changing the Port number to something like 5001 (if you want to continue with the same number series you used for the web application utilized by the Central Administration tool). Notice that the Description name for the new IIS web site will change to reflect the TCP port number chosen. Accept the other default settings, but further down on this page you will see an Application Pool section. Make sure that the name here also contains the TCP port number, to make it easy to understand that this application pool is connected to the virtual IIS web site above. Enter a user account and its password, to be used by the application pool; for example, sp_service. Note that this account will automatically be granted permission to the SQL Server database as Security Admins and Database Creators. Then click OK to save and close this page. You will now be back at the previous page, the SSP configuration page. If you see a warning stating "You must specify a value for this required field," it can be ignored, since you have not yet completed this page.

    2. You have just created the web application for the SSP itself. The next step is to define what web application users' personal sites, My Site, will use. You can create a separate web application for the My Site or use an existing web application. To create a new web application, click Create a new Web application. This opens the web page where you define the new web application. In the IIS Web Site section, select Create a new IIS web site, and set the port number to something easy to remember, for example 6000. Then in the Application Pool section, select Create new application pool;" notice that the name of this application pool is identical to that of the virtual IIS web site above. This is smart, since it will make it easier to understand which application pool is used by which virtual IIS web site. Next select Configurable, and enter the user account for the application pool. In most installations, you will do fine with the same user account that you used for the SSP application pool you created in step a above. Click OK to close and save the web application creation page. Once again, you are taken back to the SSP configuration page.

       Important 

       Note that if you want to use the same web application for both the portal web site and My Site, then you must create the web application and the site collection for the portal site before you define what web application My Site will have!

    3. The next section on this SSP configuration page is SSP Service Credentials. Enter the user name and password that this service will use for interservice communications and for running SSP-scoped timer jobs. You can use the same user account that you used for steps a and b above.

    4. Note the database names to be used for the SSP Database, and the Search Database; accept the settings for these two sections.

    5. Note the name of the listed index server. If you have more than one index server you could choose which one that will crawl the content for all web applications associated with this SSP. Here, you can set the exact file location to be used for the index files.

    6. If you want to configure Secure Socket Layer (SSL) to be used when communicating with Web services for this SSP, select Yes in this section; otherwise, select No. Be sure that you have installed the necessary SSL certificate before you activate SSL.

    7. Click OK to save and start creating this Shared Service Provider. This step may take several minutes, depending on your server hardware.

Let's summarize what you have at this stage: MOSS is installed, using Advanced installation mode. You have configured the required services, such as the search service, and you have just completed the installation and configuration of a Shared Service Provider instance, named SharedServices1, which among several other things, also contains the users' My Site configuration. The next time you open the home page in Central Administration, there is no longer a warning that your server is not yet configured. Instead of the previous Administrator's Tasks list with 4 items, you know see a new list with 10 new items. In Chapter 5, you will learn more about these tasks items, but for now you can let them be.

Just to make sure that your SharePoint installation really works, let's create the first portal web site. If you tried the Basic installation mode described earlier, you may remember that it automatically created a portal site for you. So, why not create the same portal site manually this time? It is simple, just follow the steps below:

1. Open the SharePoint Central Administration tool, then switch to the Application Manager page.

2. Just like any SharePoint site, user web sites, such as the portal site, must have a web application that hosts its site collection. First, you create the web application:

   1. Click Create or extend web application in the SharePoint Web Application Management section.

   2. Click Create a new Web application. (You will recognize the next page from when you created the Shared Service Provider.)

   3. In the IIS Web Site section, you define what virtual IIS server this new web application will use. Since it will later be used to create a user site, you really need to have a virtual IIS web site using TCP port 80. So, either select "Use an existing IIS web site" and select Default Web Site, or create a new IIS web site using port 80 (make sure to stop or remove the default web site, in this case).

   4. In the Application Pool section, you define what application pool the virtual IIS web site will use. You can use one that SharePoint is already using, but the best practice is to create a separate application pool for the users' web site: Click Create new application pool and enter the user account for this application pool. As before, it is okay in most situations to use the same account that you used for the other SharePoint application pools.

   5. In the Database Name and Authentication section, you will see the default database name for this web application. Since this will be the database used for storing user web sites, it should have a name that is easy to recognize. Change it to anything meaningful to you; for example, WSS_ Content. Click OK to save and close this page and create the new web application.

3. After creating a web application, the next step is to create the site collection, and thus also its top site. The exact look and feel of this new site is dependent on the site template you choose. Since the purpose of this exercise is to create the same portal site structure that the Basic installation mode did, you will choose the Collaboration Portal site template, as described next:

   1. Make sure that the Application Management page is open, then click Create site collection, in the SharePoint Site Management section.

   2. Check that the web application listed at the top of this web form is the one you just created in step 2 above; if not, click on the current name, and select Change Web Application.

   3. Enter the Title for this new portal site, and enter a description.

   4. Notice the URL; you will use it to open this portal.

   5. In the Template Selection section, open the Publishing tab, and select Collaboration Portal.

   6. In the Primary Site Collection Administrator section, enter the user account that will be the full administrator for this site collection.

   7. In the Secondary Site Collection Administrator section, enter the user account that will be a secondary administrator for this site collection, if any.

   8. Click OK to close this page and start creating this site collection. Note that the Collaboration Portal site template is rather complex, and therefore it will take some time to complete this step. When it is done, you will have one top site, and five subsites, each based on the advanced content management functionality that SharePoint calls a Publishing Page.

   9. When done, click the link on the next page to open the new collaboration portal site. It should look similar to Figure 4-1 earlier in this chapter.

After the Installation of MOSS Using the MS SQL Server

Two things you should do immediately after the installation of MOSS 2003 has completed:

• q Download and install the latest service pack for MOSS and WSS, if any.

• q Do a full backup of the SharePoint Portal Server environment with the backup utility that comes with MOSS (see the end of this chapter for a quick guide) or with your ordinary backup program, if it is SharePoint-aware.

Checking the New Folder and Applications

The portal site is now up and running. Take a look at what has changed in the Windows 2003 server. You have several new file directories used by MOSS and the underlying WSS environment. For example, you will find that a number of newly created web applications, for example, a virtual IIS server that has been both created and extended by the installation program and the Configuration Wizard. Since MOSS is much more advanced than WSS, you will find more web applications in the IIS Web Sites node. To see them, open the IIS manager: Start Administration Tools Internet Information Service (IIS) Manager. Then expand the node Web Sites. Note that you have a number of IIS virtual servers here, usually with names like these:

• q SharePoint Central Administration v3: Used by SharePoint for the administration web site. This virtual IIS web server was created during the initial phase of the MOSS installation, before the portal site was created.

• q Default Web Site: This is the virtual IIS web server that is used by the Collaboration Portal site collection.

• q SharePoint – nnn : (nnn = the TCP port number selected by you.) This virtual IIS web server is used by the Shared Service Provider and its first instance, SharedServices1.

• q SharePoint – nnn : (nnn = the TCP port number selected by you.) This virtual IIS web server is used by the My Site site collection, unless you chose to install My Site on an existing web application.

• q Office Server Web Services: This is a general service that enables MOSS and other Office Server applications to use Web service techniques to retrieve or store data from SharePoint's database.

Right-click on the virtual IIS server SharePoint Central Administration v3, and open its properties. It will, by default, use the application pool SharePoint Central Administration v3. Expand the Application Pools node (located directly above the Web Sites node), right-click on either of the two application pools mentioned above, and switch to the Identity tab. Note that the security account that this application pool is using is the user account chosen by you when you installed MOSS. This user account is also granted permission to the SQL Server 2000 database.

To summarize this type of installation: MOSS uses up to five virtual IIS web servers for an Advanced installation, one for the web sites that your SharePoint users utilize and up to four others for the administration of SharePoint. All of these virtual servers use separate application pools, and each of them can have its own security account, or you can configure them to use the same account.