Server Installation

You can install SharePoint Portal Server by running the SharePoint Portal Server Setup Wizard. The wizard guides you through the installation process. Before running the setup wizard on your server, plan how you will use SharePoint Portal Server in your organization. For more information about planning your deployment, see Appendix B, For More Information.

To install SharePoint Portal Server on the server:

  1. Review the server hardware and software requirements, including coexistence issues, outlined earlier in this chapter.
  2. Install SharePoint Portal Server on the server by running the SharePoint Portal Server Setup Wizard.
  3. Create a workspace on the server.

If you have Terminal Services, you can use it in remote administration mode to install SharePoint Portal Server. If you are running in Terminal Services in application mode, run chgusr /install in Command Prompt before attempting to install SharePoint Portal Server.

You can also use group policy to install the server in attended or unattended mode by using ZAP files. For more information about using ZAP files, see the following resources:

  • Knowledge Base Article Q231747: How to Publish non-MSI Programs with .zap Files (http://support.microsoft.com/support/kb/articles/Q231/7/47.ASP)
  • Microsoft Windows 2000 Server Resource Kit (http://mspress.microsoft.com/prod/books/1394.htm)
  • "Step-by-Step Guide to Software Installation and Maintenance" on Microsoft TechNet (http://www.microsoft.com/TechNet/win2000/instmain.asp)

If you want to install SharePoint Portal Server on the server in unattended mode, see Using Unattended Server Installation later in this section. If you want to uninstall or repair a SharePoint Portal Server computer, see Uninstalling or Repairing SharePoint Portal Server later in this section.

Installing SharePoint Portal Server

To install SharePoint Portal Server:

  1. Log on to the computer running Windows 2000 Server or Advanced Server as a local or domain administrator.
  2. Stop all anti-virus software. If anti-virus software is running during SharePoint Portal Server installation, the workspace creation step at the end of the setup process fails.
  3. Ensure that there is at least one free network drive letter on the computer. The setup process requires at least one free network drive letter on the computer.
  4. Configure the proxy server settings for Internet access:
    • On the taskbar, click Start, point to Settings, and then click Control Panel.
    • Double-click Internet Options. The Internet Properties dialog box appears.
    • Click the Connections tab, and then click LAN Settings.
    • Clear both check boxes under Automatic configuration.
    • If you use a proxy server, select the Use a proxy server check box, type a valid proxy server address and port number, and then select the Bypass proxy server for local addresses check box. If you do not use a proxy server, clear all check boxes.
    • Click OK to apply the changes, and then click OK to close Internet Properties.
  5. Insert the SharePoint Portal Server CD into your CD-ROM drive.
  6. Click Server Installation. The SharePoint Portal Server Setup Wizard appears. You can also go to the Server folder on the CD, and then double-click Setup.exe.
  7. Follow the instructions that appear in the setup wizard.
  8. On the Product Identification page, type the CD Key in the spaces provided. The CD Key uniquely identifies your copy of SharePoint Portal Server and enables you to receive technical support. The CD Key is located on the back of your SharePoint Portal Server CD case. If the number that you type is not accepted, check the following:
    • If you are using the keypad to the right of your keyboard, ensure that NUM LOCK is on.
    • Ensure that you are not using the letter I for the number one.
    • Ensure that you are not using the letter O for the number zero.
  9. On the SharePoint Portal Server Installation Folders page, specify the location on the server's disk where you want to install the SharePoint Portal Server program files and data files. You can change the installation location for these files by clicking Change Folder. SharePoint Portal Server also installs additional required files on the operating system drive. Click Disk Information for information about the amount of disk space required and the amount remaining. If there are existing files in the installation paths, setup removes these files. Note the following restrictions for the path:
    • The path name can have a maximum length of 100 characters.
    • The path name can contain only characters in the lower ASCII range.
    • The path cannot point to a root directory. For example, E:\ is not allowed, but E:\Installation is allowed.
  10. On the SharePoint Portal Server Indexing Settings page, specify the default content access account and the Gatherer e-mail address. SharePoint Portal Server uses the default content access account to crawl content sources. The Gatherer e-mail address is an e-mail address that an external site administrator can contact if problems occur when SharePoint Portal Server crawls the external site. SharePoint Portal Server uses these settings to crawl content stored outside the workspace and include it in an index. If you choose not to specify these settings during installation, you can specify them later by using the Properties page of the server in SharePoint Portal Server Administration.

Administrators can manage servers and workspaces from SharePoint Portal Server Administration. To open SharePoint Portal Server Administration, click Start, point to Programs, point to Administrative Tools, and then click SharePoint Portal Server Administration.

Creating a Workspace on the Server

After you run SharePoint Portal Server setup, the New Workspace Wizard appears. This wizard helps you create a workspace. If you click Cancel to close the New Workspace Wizard, you can create a workspace later by using SharePoint Portal Server Administration.

To create a workspace by using the New Workspace Wizard:

  1. Stop all anti-virus software. If anti-virus software is running during workspace creation, the process may fail.
  2. On the first page of the wizard, click Next.
  3. On the Workspace Definition page:
    • In the Workspace name box, type the name of the workspace that you are creating. Workspace names can consist of characters from lower ASCII except for the following:

      # : \ ? * < > % / | " { } ~ [ ] Space ! ( ) = ; . , @ & +

      The lower ASCII code set includes the characters with codes 32–127. The workspace name cannot exceed 25 characters in length.

      The wizard verifies that the workspace name is unique and does not conflict with any other workspace names or propagated index names on the server. If the name is already in use, the wizard prompts you to enter a unique name. You cannot edit a workspace name after you create the workspace. If you are creating an index workspace, the name of the workspace that you are creating must be different from that of the destination workspace.

    • In the Description box, type an optional description of the workspace.
  4. If you are not creating an index workspace, omit this step. If you are creating an index workspace, click Advanced. Select the Configure as an index workspace check box. In the Specify the destination workspace address box, type the destination workspace for the propagated index. The name of the destination workspace is http://server_name/workspace_name. Click OK. The wizard prompts you to provide the name of a propagation access account, which is required before you can propagate an index. This account must have local administrator permissions on the destination server.

    The destination workspace must exist before you create the index workspace. The wizard ensures that a workspace with the same name as the index workspace does not already exist on the destination. You cannot change the destination workspace after you have created the index workspace. If the destination server is not a SharePoint Portal Server computer, the wizard logs an error in the Application Log in Windows 2000 Event Viewer (commonly referred to as the Windows 2000 event log).

    You can create index workspaces with the same name (and propagating to the same destination) on multiple servers dedicated to creating and updating indexes. The last index to propagate has its index active on the destination. You can use this setup to continually update the destination by appropriately scheduling the crawls for each index workspace.

    It is recommended that you maintain a list of index workspace names, the servers on which they are stored, and the servers and workspaces to which they are propagated.

    Note that to use fully qualified domain names and index workspace propagation together, both the server dedicated to indexes and the destination server must be in Windows 2000 domains.

  5. Click Next.
  6. On the Workspace Contact page:
    • In the Workspace contact name box, type the name of the user or group that you are assigning as the workspace contact. The workspace contact is the individual user or group with overall responsibility for the workspace.
    • In the Workspace contact e-mail address box, type the e-mail address for the work-space contact. The contact e-mail address can be that of an individual user or a group.
    • Click Next.
  7. Click Finish to complete the wizard and create the new workspace. After SharePoint Portal Server creates the workspace, it displays a message stating that the wizard will open the workspace and create a link to it in My Network Places.
  8. Click OK. The link is created, the Configure Your Workspace page opens, and the dashboard site opens. For index workspaces, an introduction page opens and the link points to the Content Sources folder within the workspace.

After you create the workspace, you must configure security on the workspace node by using SharePoint Portal Server Administration or Web folders. The Windows 2000 local Administrators group has permission to read documents and configure security on any folder or document in a workspace.

The SharePoint Portal Server Setup Wizard automatically installs the client components. After installing the client, you must add a Web folder that points to the workspace. The address of the workspace is http://server_name/workspace_name.

Using Unattended Server Installation

If you are installing a large number of servers or want to customize your installation, you can run SharePoint Portal Server setup in unattended mode by using an .ini file. When you install SharePoint Portal Server by using an .ini file (also called silent install), no dialog boxes or error messages that require user intervention are displayed unless prerequisites are missing. This setup lets you install identical configurations of SharePoint Portal Server on multiple computers.

Before running this unattended setup, you must create an .ini file that contains the default installation settings that you want to use, such as the installation directory. After you create the .ini file, you can edit it by using a text editor. By editing the .ini file, you specify additional options and gain more control over your installation.

To create the .ini file used for unattended setup, you must run the SharePoint Portal Server Setup Wizard. However, instead of installing SharePoint Portal Server, the wizard stores the settings that you specify in the .ini file.

Double-byte character set (DBCS) or high-ASCII characters cannot be used in installation paths when performing an unattended installation. If you use these characters, the installation fails. In addition, no path in the .ini file should be longer than 140 characters.

To install SharePoint Portal Server by using an .ini file:

  1. Create an .ini file:
    • On the taskbar, click Start, and then click Run.
    • In the Open box, type path_to_server_setup_file setup /CreateUnattend path filename.ini where filename is the name of the .ini file that you want to create. For example, if the setup file is in the Setup directory on drive D and you want to create sample.ini on drive E, type D:\Setup\setup /CreateUnattend E:\sample.ini
    • Click OK.
    • Follow the instructions that appear in the SharePoint Portal Server Setup Wizard. All settings that you choose are included in the .ini file that you create.
    • One additional parameter is available for use with /CreateUnattend: /EncryptedMode. This parameter enables you to create an .ini file with the password for the default content access account hidden. To do this, type: path_to_server_setup_file setup /CreateUnattend path file_name.ini /EncryptedMode
  2. Edit the .ini file:
    • In a text editor, such as Microsoft WordPad, open filename.ini where filename is the name of the .ini file that you created.
    • Modify parameters in the file for the settings that you want SharePoint Portal Server setup to use.

      If you plan to use an unattended installation file on servers with varying storage configurations, ensure that hard-coded paths are valid for each server configuration before starting the installation. An example of a hard-coded path reference is "C:\." You can force the installer to automatically choose the correct default path by removing an entry line completely.

      You can modify only the following paths:

      • InstallDirectory. You can specify the installation location for SharePoint Portal Server program files. By default, the program files are stored on the operating system drive in Program Files\SharePoint Portal Server.

        There are two other InstallDirectory paths. One path is for the Microsoft Web Storage System and the other is for MSSearch. Altering these paths is not recommended. This is the recommended option for the MSSearch and Web Storage System installation directories:

        InstallDirectory=operating_system_drive\Program Files\Common Files\Microsoft Shared\Web Storage System

        InstallDirectory=operating_system_drive\Program Files\Common Files\Microsoft Shared\MSSearch

        By default, the Microsoft Web Storage System files are stored on the operating system drive in Program Files\Common Files\Microsoft Shared\Web Storage System. However, if you are running unattended server installation and you delete all lines containing a hard-coded path reference, the location defaults to Program Files\Exchsrvr on the operating system drive.

    • Search Gatherer Log Directory. Each time that SharePoint Portal Server creates an index, it creates a log file for that workspace. This log file contains data about crawling content sources and records access errors. After installation, you can use SharePoint Portal Server Administration to change this path. By default, the log is stored on the operating system drive in Program Files\SharePoint Portal Server\Data\FTData\SharePointPortalServer\GatherLogs.

      The Gatherer log contains data about URLs that SharePoint Portal Server accesses while it creates an index. The file records successful accesses, access errors, and accesses disallowed by rules (in case the user needs to debug the index restrictions). Coordinators can view this log from a user-friendly Active Server Pages (ASP) page in the workspace.

    • Search Index Directory. When creating a workspace, SharePoint Portal Server creates an index under this root node. SharePoint Portal Server also creates all indexes propagated to the server under this root node. After installation, you can use SharePoint Portal Server Administration to change this path. By default, the indexes are stored on the operating system drive in Program Files\SharePoint Portal Server\Data\FTData\SharePointPortalServer\Projects. If you want to move existing indexes to a new location, you must use a tool that is included on the SharePoint Portal Server CD. For more information, see ToolsHowTo.txt in the Support\Tools directory on the SharePoint Portal Server CD.
    • Search Property Store Database Directory. You can specify the location of the property store file. The property store file contains the metadata from documents. After installation, you cannot modify the file location by using SharePoint Portal Server Administration. By default, the property store file is stored on the operating system drive in Program Files\SharePoint Portal Server\Data\FTData\SharePointPortalServer. To modify the file location, you must use a tool that is included on the SharePoint Portal Server CD. For more information on ToolsHowTo.txt, see ToolsHowTo.txt in the Support\Tools directory on the SharePoint Portal Server CD. For optimal performance, the property store and property store log files should be on dedicated physical volumes. SharePoint Portal Server shares this file across all workspaces.
    • Search Property Store Log Directory. You can specify the location of the property store log files. The property store log files are the log files for the property store. After installation, you cannot modify the location of these files by using SharePoint Portal Server Administration. By default, the property store log files are stored on the operating system drive in Program Files\SharePoint Portal Server\Data\FTData\SharePointPortalServer. To modify the file location, you must use a tool that is included on the SharePoint Portal Server CD. For more information on ToolsHowTo.txt, see ToolsHowTo.txt in the Support\Tools directory on the SharePoint Portal Server CD. For optimal performance, the property store and property store log files should be on separate dedicated physical volumes. SharePoint Portal Server shares these files across all workspaces.
    • Web Storage System Database Directory. You can specify the location of the Web Storage System Database file. Every SharePoint Portal Server computer contains one public store (wss.mdb). All workspaces hosted on the server reside on the Web Storage System. After installation, you can use SharePoint Portal Server Administration to change this path. If this location changes, the existing file moves to the new location. By default, the database file is stored on the operating system drive in Program Files\SharePoint Portal Server\Data\Web Storage System.
    • Web Storage System Streaming Database Directory. You can specify the location of the WSS-Streaming Database file. Used for streaming files, the WSS-Streaming Database file (wss.stm) contains data and is a companion to the WSS-Database file (wss.mdb). Together, these two files form the database. SharePoint Portal Server document streams make up a sizable part of the total amount of data. You might want to move this file to a larger drive (ideally a dynamic disk that you can easily resize) because it can increase substantially over time. After installation, you can use SharePoint Portal Server Administration to change this path. If this location changes, the existing file moves to the new location. By default, the streaming database file is stored on the operating system drive in Program Files\SharePoint Portal Server\Data\Web Storage System.
    • Web Storage System Database Log Directory. You can specify the location of the WSS-Database Log files. These are the log files for the Web Storage System. For optimal performance, place the log files on a dedicated physical volume. After installation, you can use SharePoint Portal Server Administration to change this path. If this location changes, the existing files move to the new location. By default, the log files are stored on the operating system drive in Program Files\SharePoint Portal Server\Data\Web Storage System.

      Do not modify other paths.

    You can modify the parameter "apply indexing settings" in the .ini file to set the default content access account and Gatherer e-mail address during the unattended installation. SharePoint Portal Server uses the default content access account to crawl content outside the workspace. SharePoint Portal Server provides the Gatherer e-mail address to each Web site it crawls when creating an index. If a problem occurs while crawling (for example, the crawler is hitting the site too much), the Web site's administrator can contact this address.

    If the "apply indexing settings" parameter is equal to zero (0), the default content access account and Gatherer e-mail address are not set when you run the unattended installation. You can set these options after installation by using SharePoint Portal Server Administration.

    To specify the account and e-mail address:

    • Set apply indexing settings=1
    • Set Default Content Access Account=user_name,domain,password
    • Set gatherer e-mail address=someone@microsoft.com
  3. Run setup by performing the following tasks:
    • On the taskbar, from the server on which you want to run setup, click Start, and then click Run.
    • In the Open box, type path_to_server_setup_file setup /UnattendFile path filename.ini where filename is the name of the .ini file that you created.
    • Click OK. You do not see the finish page or the New Workspace Wizard page.

Uninstalling or Repairing SharePoint Portal Server

The SharePoint Portal Server Setup Wizard installs the client components of SharePoint Portal Server. If you uninstall SharePoint Portal Server, it removes the client components. If you repair SharePoint Portal Server, it repairs the client components as well.

If you remove SharePoint Portal Server from a computer that has SQL Server installed, SharePoint Portal Server does not remove the upgraded MSSearch because it is a shared service with SQL Server.

During the uninstall process, SharePoint Portal Server requires access to the original installation point to uninstall the Microsoft Embedded Exchange files. If the original installation point has moved, you can insert the SharePoint Portal Server CD into the CD-ROM drive to continue uninstalling. You can also point to the Server\Web Storage System directory at the installation point.

Before uninstalling SharePoint Portal Server, you must:

  • Verify that all command prompts are closed.
  • Remove any additional virtual roots mapped to the Web Storage System drive. The Web Storage System is mapped to network drive M by default.

    If network drive M is already in use when you install SharePoint Portal Server, the Web Storage System is mapped to another network drive.

    By default, this drive is disabled (it is not visible in My Computer). For more information about enabling this drive, see Using the IFS Drive and the Microsoft Web Storage System later in this chapter.

When you uninstall SharePoint Portal Server, all files and folders located in the installation directories are removed, including any user-created or modified files. The uninstall process also removes all workspaces. It is highly recommended that you restart the server after you uninstall SharePoint Portal Server.

The repair process requires at least one free network drive letter on the computer. If no drive is available, repair fails.

You can uninstall or repair a server by running SharePoint Portal Server setup. Alternatively, you can use Add/Remove Programs in the Control Panel.



Microsoft Sharepoint Portal Server 2001 Resource Kit
Microsoft SharePoint(TM) Portal Server 2001 Resource Kit (Examples & Explanations Series)
ISBN: 0735615624
EAN: 2147483647
Year: 2001
Pages: 231

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net