Getting Started

  • Article
On This Page

MSCMS 2001 System Configurations Supported MSCMS 2001 System Configurations Supported
MSCMS 2001 Database Requirements MSCMS 2001 Database Requirements
MSCMS 2001 File System Requirements MSCMS 2001 File System Requirements
MSCMS 2001 Server Minimum Hardware Requirements MSCMS 2001 Server Minimum Hardware Requirements
MSCMS 2001 Server Software Requirements MSCMS 2001 Server Software Requirements
MSCMS 2001 Site Builder Hardware Requirements MSCMS 2001 Site Builder Hardware Requirements
MSCMS 2001 Site Builder Software Requirements MSCMS 2001 Site Builder Software Requirements
Microsoft Site Server LDAP Requirements Microsoft Site Server LDAP Requirements
Installation Scenarios Installation Scenarios
About the MSCMS 2001 System Account About the MSCMS 2001 System Account
Configuring User Access Configuring User Access
Cookie Authentication Across a Server Farm Cookie Authentication Across a Server Farm

MSCMS 2001 System Configurations Supported

You can install the Microsoft Content Management Server 2001 (MSCMS 2001) database on the same machine as the MSCMS 2001 server, or on a separate computer.

MSCMS 2001 Database Requirements

For Microsoft SQL Server, versions 7.0 SP2, SP3, and 2000 are supported.

MSCMS 2001 File System Requirements

You must have an NT File System (NTFS) as a prerequisite for installing MSCMS 2001. If your system is running with a File Allocation Table (FAT) system only, the installation will fail.

MSCMS 2001 Server Minimum Hardware Requirements

Although you can install Content Management Server 2001 with less than the minimum hardware and disk space requirements specified, we suggest you have the following minimum configuration for successful operation.

  • Pentium III 800 with 512 MB RAM and an Ultra SCSI drive, with 500 MB of space reserved for the server

  • 1 GB hard drive space for the database devices on the machine that will host the database

  • 150 MB of free disk space at all times. Also, you must have a minimum 50 MB for the cache folder.

Note The InstallShield Wizard stops during installation if there isn't enough space on the destination and system drives for the files created by the program. For a successful, complete installation, ensure there is enough space on the system drive, the Program Files drive (for shared files), the destination drive (main installation of MSCMS 2001 files), and the cache drive.

MSCMS 2001 Server Software Requirements

Note that the MSCMS 2001 server requires a machine that is configured to reside on a domain, rather than belonging to a workgroup.

Following are the MSCMS 2001 server software requirements. The "Supported versions" is the range of product versions, from the earliest version on which Content Management Server 2001 has been tested, to the most recently tested version. These are the versions on which you can install MSCMS 2001. There may be more recent released versions of the individual products, but we can't guarantee MSCMS 2001 will install properly on them.

Product Name

Suggested versions

Microsoft Windows Server

Windows 2000 (SP2) Server or Advanced Server

Microsoft Internet Information Server (IIS)

5.0. Note that IIS 5.0 is part of Windows 2000.

Microsoft Active Directory Service Interfaces (ADSI)

2.5

Microsoft SQL Server ODBC driver (included with MDAC)

3.7

Microsoft Data Access Components (MDAC)

MDAC 2.5 for Windows 2000.

Microsoft SQL Server (and Client Tools)

7.0 SP2, SP3; SQL 2000

Microsoft Internet Explorer

5.0, 5.5

Microsoft Visual Basic Scripting

5.1 or later (for viewing reports from the Site Deployment Manager). Installed as part of Internet Explorer. Or, download from Microsoft site https://msdn.microsoft.com/scripting/vbscript/download/vbsdown.htm.

MSCMS 2001 Site Builder Hardware Requirements

The minimum requirements for Content Management Server 2001 Site Builder computers are:

  • a Pentium II or equivalent processor

  • 128 MB RAM

  • 20 MB of disk space.

MSCMS 2001 Site Builder Software Requirements

Following are the software requirements for the Content Management Server 2001 Site Builder. The "Supported versions" is the range of product versions, from the earliest version to what we know to be the most recent version, on which you can install MSCMS 2001.

Product name

Supported versions

Microsoft Windows

Windows 98, Windows 2000 Professional, Windows ME

Microsoft Internet Explorer

5.0, 5.5

Microsoft Java Virtual Machine

5.0.2922.0. Note that Windows 2000 installs its own version of the JVM.

Subscribers to an MSCMS 2001 site can use any browser to view the site.

The MSCMS 2001 Web Author is compatible with: Windows 2000 Professional; Mac OS 8.6, 9.0; Sun Solaris 2.6; IE5.5; and Netscape 4.73.

We recommend that you not use Netscape on Solaris for working with the MSCMS 2001 Web Author.

Microsoft Site Server LDAP Requirements

Note Site Server is not supported in a server cluster (farm) environment.

Content Management Server 2001 can use Site Server's Membership Server to authenticate Lightweight Directory Access Protocol (LDAP) accounts. If your site is using the Site Server LDAP integration feature, you need the Personalization and Membership components of Microsoft Site Server on the computer hosting your MSCMS 2001 server. The LDAP server and MSCMS 2001 server can be installed on the same computer, or on separate machines.

Content Management Server 2001 supports Microsoft Site Server 3.0 SP3.

Installation Scenarios

This section describes the installation situations typically encountered with the MSCMS 2001 server. Further information about the steps is in the indicated chapters.

  • Chapter 3 : When you are working in a multiple-server environment (farm or cluster), you need to run the InstallShield Wizard and Database Configuration Application on each machine.

  • Chapters 4 : The Database Configuration Application (DCA) is a utility for selecting and populating a Microsoft SQL Server database. In addition, the DCA is used to select the virtual Web site (for the MSCMS 2001 server and Server Configuration Application), and to select an MSCMS 2001 System Account and the Initial MSCMS 2001 Administrator for a new installation. After you have used the DCA for a new installation, you can also use it to configure the database.

  • Chapter 5 : Several options and values that you set or change using the Server Configuration Application (SCA) utility can be applied globally—you can do this as a local administrator from a browser-based application.

New installation

For a first-time installation, do the following.

  1. Run the installation setup program (setup.exe): For a first-time installation, the files and registry keys settings are installed.

  2. Run the DCA: This sets up the Virtual Web site, configures security parameters, and installs and populates the SQL Server database.

  3. Run the SCA: Configures server parameters, such as setting up container viewing rights, changing cookie settings, or changing the size of the memory caches. Refer to Chapter 5, "Using the Server Configuration Application" for complete information about configuration settings.

Upgrade installation

To upgrade to a new release of this product, do the following.

  1. Run the installation setup program (setup.exe): Backs up existing files, verifies the database, and installs new files.

  2. Run the DCA: Upgrades the database and sets up the SCA.

  3. Run the SCA: Configures server parameters (as in the new installation procedure).

Note To change only the database or configure server parameters, run the DCA or SCA in standalone mode.

Silent mode installation

The MSCMS 2001 server installation program ships on the CD as a .MSI package that can be used for scripted installations with the Windows Installer service installed. Windows 2000 comes with the Windows Installer already installed.

Note The license agreement is automatically accepted when doing a Silent or Basic UI install.

Types of installs

You can install the MSCMS 2001 server in one of three modes:

  • Full UI mode

  • Basic mode

  • Silent mode.

With Silent mode, no user interface is displayed during the install—no user interaction is required to complete the installation. However you may still need to do configuration, but this would be done separately.

Windows Installer command line options

Because the MSCMS 2001 server installation was created as a Windows Installer package, there are several Windows Installer command line options to control the execution of the installation. Also, several properties specific to MSCMS 2001 server can be specified through the command line. This allows the MSCMS 2001 server installation to be scripted, and then executed in Silent or Basic UI mode. The result is a potential reduction in effort required to install many identical servers, for example a clustered configuration.

Some of the Windows Installers command line options that can be used to control the installation process are as follows:

  • /x - uninstalls the server

  • /qn - installs the server in Silent Install (no UI) mode

  • /qb - installs the server in Basic Install mode

  • /qf - installs the server in Full UI mode.

Server installation properties

Several MSCMS 2001 server installation properties (listed) can be passed to the installation program through the command line.

  • installation location

  • cache size and location

  • company name

  • user name

  • product license key.

These properties can also be set for a Full UI installation. In this case, the dialog boxes are populated with the values passed through the command line. The following table shows the status of the properties for the three install modes, where O is optional, M is mandatory, and N/A is not applicable.

Property name

Full

Basic

Silent

Default value if property not specified

INSTALLDIR

O

O

O

<%PROGRAM FILES%>\Microsoft Content Management Server\Server

SERVERLICENSEKEY

O

M

M

  

COMPANY NAME

O

O

O

  

USERNAME

O

O

O

User name for the operating system

CACHEDIR

O

O

O

<INSTALL DIR>\IIS_NR for a new install. For an upgrade, the existing cache directory path is preserved.

NR_CACHE_SIZE

O

O

O

50% of available disk space of <CACHEDIR> up to 2 GB for a new installation. For an upgrade, the existing cache size is preserved.

In the following table, the accepted value of the property is described as well as whether the parameter applies to a new install, an upgrade, or both.

Property name

Accepted value

Apply to New/Upgrade

Note

INSTALLDIR

Valid path format

New

MSCMS 2001 server must be installed on a local drive in NTFS format.

SERVERLICENSEKEY

Exactly as shown in product license key letter

Both

  

COMPANYNAME

Exactly as shown in product license key letter

Both

  

USERNAME

Alphanumeric - up to 50 characters

Both

  

CACHEDIR

Valid path format

New

NTFS format; local drive

NR_CACHE_SIZE

Numeric value

New

  
Example batch file

Here is an example of a batch file used to install MSCMS 2001 server in Silent mode. For our example, the company name is XYZ Corp, a license was purchased, 500 megabytes of cache space is required, and the installation program is on D: drive.

d:\MSCMS Server.msi /qn SERVERLICENSEKEY="ABCD-EFGH-IJKL-MNOP" 
COMPANYNAME="XYZ Corp" NR_CACHE_SIZE="500"

To uninstall, use the following: msiexec /x d:MSCMS Server.msi.

About the MSCMS 2001 System Account

Content Management Server 2001 uses a Windows 2000 domain user account to assign rights to security objects. During the MSCMS 2001 server installation, privileged rights to the Windows 2000 server machine are granted to a user account. Rights include access privileges required by the server and access to files on the hard drive. This account is referred to as the MSCMS 2001 System Account.

Because MSCMS 2001 is designed to work with a Windows 2000 domain's user accounts and must connect to a PDC emulator for Windows 2000 for information about users, the MSCMS 2001 server must be installed on a domain network environment. MSCMS 2001 does not support installation on non-domain network environments, such as peer-to-peer networks and workgroup networks. We recommend using an account on the same domain as the MSCMS 2001 computer for the MSCMS 2001 System Account.

The MSCMS 2001 System Account must have at least read privileges to all the domains, OUs, and containers, and the users within these that the system needs to authenticate. The MSCMS 2001 System Account must be a Windows 2000 domain user, and in an environment where the user is running Active Directory, the system administrator must enable NetBIOS over TCP/IP in order for the MSCMS 2001 install process to see the Windows 2000 domain users.

Refer to the section, "Requirements for installing the database" in Chapter 4 of this guide for information about assigning database user rights and roles.

Creating the domain user account for NT

Although you can choose any name, for convenience and clarity in the following procedure the domain user account is called "MSCMSUser."

  1. Open Windows NT "User Manager for Domains" from Administrative Tools.

  2. Create a Domain User named "MSCMSUser" and enter a password.

  3. Ensure this account has the "Access this computer from network" right on all Primary Domain Controllers (PDC) that will be used with MSCMS 2001. If the account does not have this right on a PDC, MSCMS 2001 will not be able to view the list of users in that domain.

  4. Changes to the Domain User name and password must be made through the Security function of the Server Configuration Application (SCA). Refer to Chapter 5, "Using the Server Configuration Application."

  5. Changes to the SQL Server login name and password must be made through the Database Configuration Application (DCA), described in Chapter 4, "Installing a Microsoft SQL Server Database."

Creating the domain user account for Windows 2000

  1. Open Windows 2000 "Active Directory Users and Computers" from Administrative Tools.

  2. Create a Domain User named "MSCMSUser" and enter a password.

  3. Ensure this account has the "Access this computer from network" right on all domain controllers (DC)* to be used with MSCMS 2001. If the account does not have this right on a DC, MSCMS 2001 can't view the list of users in that domain.

    * DC is the term used for Windows 2000 (in previous versions this was referred to as the Primary Domain Controller or PDC).

Configuring User Access

Content Management Server 2001 provides a secure work environment where the MSCMS 2001 administrator has explicit control over who can use what parts of the system.

Properly configured Windows 2000, Active Directory, and Site Server user accounts and working with MSCMS 2001 rights groups, allows you to control the level of access that users (both inside and outside of your organization) have to your site.

Selecting domains to use with MSCMS 2001

You can select domains with the Server Configuration Application (SCA). After the installation process, you can select users from the chosen domains, because any valid Windows 2000 user who can log on to the domain can be an MSCMS 2001 user.

Only domains in trust relationships with the Windows 2000 domain that the MSCMS 2001 System Account belongs to, can be authenticated by the MSCMS 2001 server when the system is running.

For NT users

Users from NT domains that don't have a trust relationship with the domain the MSCMS 2001 server is in, cannot be added as MSCMS 2001 users using the Site Builder, because the MSMCMS 2001 server won't be able to retrieve the list of users to add to the user role.

About the Initial MSCMS 2001 Administrator

When you are running the Database Configuration Application, you are prompted to browse for a Windows 2000 account to select as the Initial MSCMS 2001 Administrator in order to create a new database. You need to provide a password for this account. This administrator account is the only one with rights to log on to Content Management Server 2001 until other users are added through the Site Builder.

To view users on a domain, all MSCMS 2001 administrators, including the initial administrator, must have the "Access computer from network" right on that domain's DC. If your network includes several domains, the MSCMS 2001 administrators will require this right on the DC for each domain used with MSCMS 2001.

Before running the installation program, you should know the domain and name of your intended initial administrator. We recommend using separate accounts for the MSCMS 2001 System Account and the Initial MSCMS 2001 Administrator.

Creating a guest user account

A guest user account allows visitors from outside your Windows 2000 domain to view parts of your Web site.

To create a guest user account:

  1. Open Windows 2000 "Users and Passwords."

  2. Create a Domain User, using a name of your choice.

Using the Server Configuration Application (SCA), you can allow guest access to your site. Refer to Chapter 5, "Using the Server Configuration Application" for details.

Setting up the guest user account

After installing Content Management Server 2001, create a "Guest" subscriber rights group, add the guest user account to the group, and then give the group subscriber rights to the channels you want guests to have access to.

For more information on setting up rights groups, refer to the MSCMS 2001 Site Administrator's Guide.

After setting up a multiple-server environment (server farm or cluster), the person who installed the servers must synchronize a cookie encryption key across all computers in the same cluster, using an import and export program. This is done by exporting the cookie encryption key from one server in the cluster and then importing the key to all other servers in the cluster.

To run the program, use Windows Explorer to navigate to C:\Program Files\Microsoft Content Management Server\Server\Bin and double-click Managekey.exe. Or, use the command line to navigate to the C:\Program Files\Microsoft Content Management Server\Server\Bin directory and type Managekey.exe. 

  1. Export the cookie encryption key from one server by clicking the "Export Key" button. At the file dialog box, enter the file to save the key to. If you don't save to a diskette, you'll get a security alert. You'll get a confirmation if the key has been successfully saved.

  2. Go to the next server and using the "Import Key" command, select the file saved from step 1. The saved key is then imported to this server.

  3. Repeat step 2 for every server in the cluster.