Before you install SharePoint Portal Server, make sure that your computer meets the following recommended hardware and software requirements.
The following are the requirements for each server running SharePoint Portal Server:
Installing SharePoint Portal Server on a system that has been upgraded from Microsoft Windows NT® version 4 can cause install failures. It is recommended that you install SharePoint Portal Server on a clean Windows 2000 Server. If you are installing on a Windows 2000 system that was upgraded from Windows NT 4, manually register the Oledb32.dll file before installation to avoid installation failure. Go to the Program Files\Common Files\System\Ole DB folder and type regsvr32 oledb32.dll to register the file.
In addition to the requirements listed previously, install the following Windows 2000 updates before installing SharePoint Portal Server. These updates are available at http://support.microsoft.com/. These issues will be addressed in subsequent Windows 2000 service packs.
If you are installing on Windows 2000 Server with Service Pack 1, install the following updates:
For this hotfix, see Q291340: Token Handle Leak in LSASS Using Basic Authentication.
For this hotfix, see Q286360: GetEffectiveRightsFromAcl() Function Causes "ERROR_NO_SUCH_DOMAIN" Error Message.
If you are installing on Windows 2000 Server with Service Pack 2, install the following update:
For this hotfix, see Q291340: Token Handle Leak in LSASS Using Basic Authentication.
The following prerequisites must be met before installing SharePoint Portal Server:
The following software does not coexist with SharePoint Portal Server:
SharePoint Portal Server setup checks for the existence of this software and fails if this software is already installed. If you install this software after installing SharePoint Portal Server, SharePoint Portal Server will stop functioning properly.
SharePoint Portal Server is not supported in a clustered environment. You cannot install SharePoint Portal Server in a clustered environment, and you must not add the server to a clustered environment.
If you install SharePoint Portal Server on a computer running SQL Server 7 or SQL Server 2000, SharePoint Portal Server upgrades the existing Microsoft Search (MSSearch) service. In addition, SharePoint Portal Server upgrades the full-text index format of all of the existing indexes on that computer the next time that MSSearch starts. For the upgrade to succeed, there must be enough disk space on the computer to accommodate 120 percent of the size of the largest full-text index on the drive. Upgrading the full-text index format can take several hours, depending on the number and size of the existing indexes. During the SharePoint Portal Server setup, a message informs you that the service will be upgraded.
Because SharePoint Portal Server upgrades MSSearch and full-text indexes, do not install SharePoint Portal Server on a server that participates in a SQL Server clustering environment or add a computer running SharePoint Portal Server to a clustered environment.
You can install SQL Server on a computer already running SharePoint Portal Server. In this instance, SQL Server uses MSSearch installed by SharePoint Portal Server. If you remove SharePoint Portal Server from a computer that has SQL Server installed, SharePoint Portal Server will not remove the upgraded MSSearch because it is a shared service with SQL Server.
If SharePoint Team Services from Microsoft is installed on the computer on which you want to install SharePoint Portal Server, you must uninstall SharePoint Team Services before installing SharePoint Portal Server. In addition, you must delete the following registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Office\9.0\Web Server
Incorrectly editing the registry may severely damage your system. Back up the current version of the registry before making any changes. You should also back up any valued data on the computer.
If you install SharePoint Team Services after installing SharePoint Portal Server, you lose the following functionality from SharePoint Portal Server:
If you install SharePoint Portal Server on a domain controller:
You can rename a SharePoint Portal Server computer at any time. After renaming the server, you must restart it. In addition, SharePoint Portal Server Administration installed by setup prompts for authentication and displays an error before opening, after you rename the server. To remedy this situation, manually add the SharePoint Portal Server snap-in to Microsoft Management Console (MMC).
The following are the requirements for each computer running the client components of SharePoint Portal Server:
Accessing SharePoint Portal Server through the dashboard site does not require the user to install the client components. For the Windows operating system, you can use the following browsers:
Macintosh and Solaris operating systems are not supported.
In addition, you must enable Microsoft JScript® or Netscape JavaScript support in your browser for the dashboard site to function.
To use the dashboard site with Netscape Navigator, you must use Internet Services Manager to enable Basic authentication for the workspace node on the Default Web Site. To enable discussions to work when the browser is Netscape Navigator, you must also enable Basic authentication for the MSOffice node on the Default Web Site.
The following table summarizes the operating system and browser support for SharePoint Portal Server.
Operating System and Browser Support for SharePoint Portal Server
Operating system | Server support | Client support | Browser support (for dashboard site/Web access only) |
---|---|---|---|
Microsoft Windows 95 | No | No | Yes |
Windows 98 | No | Yes (limited)5 | Yes |
Windows NT 4 (SP6A) | No | Yes (limited)5 | Yes |
Windows 2000 Professional | No | Yes | Yes |
Windows 2000 Server or Windows 2000 Advanced Server | Yes (requires SP1) | Yes | Yes |
Windows 2000 Datacenter | No | No | Yes |
Windows Millennium Edition (includes Internet Explorer 5.5) | No | Yes (limited)5 | Yes |
Systems with Internet Explorer 5 or later | Yes | Yes | Yes |
Systems with Office XP | Yes | Yes | Yes |
Windows 98, Windows Millennium Edition, and Windows NT 4.x computers do not support coordinator functions such as scheduling updates and configuring content sources, tasks performed by using MMC, or Web views. In addition, on computers running Windows 98 or Windows NT 4.x, you cannot access User's Help from the workspace by using F1 or the Help menu. To access User's Help when using these operating systems, click the User's Help page in the workspace, and then click the User's Help link on that page.