The purpose of this document is to provide comprehensive information on how to prepare Windows 2000 servers for the installation of H-Sphere components. It covers the following topics:

1. Hardware and Partitioning requirements.
2. Software requirements.

Note: We don't install H-Sphere on live servers.

Hardware and Partitioning Requirements

For better functioning we recommend to have not less than 256RAM. And as for partitions it's better to brake it into two:

• C:\ for system files and program files - at least 5 GB.
• D:\ for users' content - the rest of the HDD.
  
  Important: partition containing users' content must be NTFS formated to support disk space quota.

Software Requirements

Before installing H-Sphere to Windows platform, make sure your system complies with the following software requirements:

• Windows 2000 Server or Windows 2000 Advanced Server, should not be the PDC (Primary Domain Controller);
• Terminal Service or pcAnywhere for remote access to the computer;
• Both, the system disk and the one with user homes, should have NTFS file system;
• External IP
• IIS (Internet Information Server) service set up for WWW service and FTP service
• FrontPage extensions version 4 or higher;
• The following ports should be open:
  - 20, 21 (FTP)
  - 80 (HTTP)
  - 443 (HTTPS)
  - 873 (Rsync)
• These are the default ports for * SQL servers to be open if your customers connect to them via ODBC:
  • MySQL - 3306
  • PostgreSQL - 5432
  • MS SQL-1433
  Note: If *SQL server is put on any port other than the default ones, don't forget to open it.
  To access Windows boxes via pcAnywhere or Terminal Service, the ports 5631 and 3389 corespondingly should be open.

Third party commercial products are purchased separately and should be installed prior to H-Sphere:

• MS SQL server
• Real Server
• ColdFusion
• Miva

The following noncommercial third party products should also be set up prior to the H-Sphere installation:

• webalizer
• ASP.NET (see also ASP.NET Support)
• ActivePerl
• PHP Make sure to install the complete version of PHP. This is required by the latest version of Webshell. Plus, your customers would enjoy the fullness of PHP functionality.

  * Important: Upon the completion of ActivePerl and PHP installation, please check whether the read/launch permissions for built-in IUSR and IWAM accounts have been set on the destination directories and their content. This is done so the respective libraries can be run when Perl or PHP scripts are requested via http.
  Also, read/launch permissions for built-in IUSR and IWAM accounts should be set to the winnt\system32 directory, as this directory contains libraries to work with ASP.