Last updated: May 2003
This document provides instructions for installing Microsoft® Content Management Server (MCMS) 2002 on one computer (for example, for the development environment) and on multiple computers (for the production environment). It is recommended that you read through this document completely before installing MCMS 2002.
Note It is not possible to install MCMS 2002 unattended.
This section contains:
Viewing MCMS 2002 Documentation
Installing MCMS 2002 in a Single Computer Development Environment
Installing MCMS 2002 in a Multiple Computer Production Environment
Installing the WoodgroveNet Sample Site
Installing Authoring Connector
You can view MCMS 2002 Help without installing the entire product. MCMS 2002 Help is installed along with the MCMS 2002 Site Manager on the server computer only. Users of Authoring Connector and the Web Author can only access the documentation directly from the CD.
MCMS 2002 Help is now available for viewing.
Note If you have already installed the product, you can click Start, point to Programs, point to Microsoft Content Management Server, and then click MCMS Help.
To evaluate MCMS 2002, or if you are a developer working on an MCMS Web site, you have the option of installing all of MCMS 2002 and Microsoft SQL Server™ on a single computer, or you can choose to install MCMS and point to a shared SQL database. The information and instructions in this topic explain how to install all of MCMS and SQL on a single computer.
This section contains:
MCMS 2002 Hardware Requirements for a Single Computer Development Environment
MCMS 2002 Software Requirements for a Single Computer Development Environment
Configuring MCMS in a Single Computer Development Environment
Configuring the MCMS Content Server
The hardware requirements for installing MCMS 2002 in a development environment are as follows:
Note Hardware requirements for the evaluation version of MCMS 2002 are different because you can do a simple evaluation with a lower set of requirements. However, it is recommended that you use the requirements above.
This topic lists the software requirements for installing MCMS 2002 on a single computer in a development environment. The table lists only MCMS-specific installation requirements. Read the documentation accompanying each product for additional requirements. Before installing any prerequisite software, it is highly recommended that you read Windows 2000 documentation about how to ensure the security of your platform.
For information about software requirements for multiple computers in a production environment, see Installing MCMS 2002 in a Multiple Computer Production Environment.
Important Microsoft Professional Support Services only supports platforms that follow the hardware and software requirements listed in this document. You must install the software in the order indicated.
Note Installing MCMS on a domain controller computer is not recommended.
| Required/recommended software | MCMS-specific installation requirements |
| Microsoft Windows® 2000, Professional, Server or Advanced Server, or Windows XP
Note If you use Windows XP, be sure you use an edition of SQL Server 2000 that will run on that platform. For information on SQL requirements see http://go.microsoft.com/fwlink/?LinkId=16489. |
Observe the following requirements when installing Windows 2000 Server or Windows 2000 Advanced Server:
To run your development environment on Microsoft Windows® XP Professional, you must install Microsoft Windows XP Service Pack 1 at a minimum. |
| Microsoft Internet Explorer 6.0 | Download Microsoft Internet Explorer 6.0 at http://go.microsoft.com/fwlink/?LinkId=12037 |
| Microsoft Windows 2000 Service Pack 2 (Recommended: Service Pack 3) | Note It is recommended that you always check for the latest service packs and hotfixes.
Do the following to install Windows 2000 Service Pack 2:
Do the following to install Windows 2000 Service Pack 3:
|
Microsoft Internet Information Services (IIS) 5.0 components:
|
After you have completed installing the Windows 2000 Service Pack, enable IIS as follows:
Note These are the minimum requirements for MCMS. Additional components may be required for the other prerequisite software listed. |
| Cumulative Patch for IIS (Q319733) | Note If you have installed Microsoft Windows® 2000 Service Pack 3, you do not need to install this patch.
Do the following to install the Cumulative Patch for IIS (Q319733):
|
| Microsoft SQL Server™ 2000 (any edition)
Note If you are installing the MCMS trial software you can also use the SQL Server 2000 trial software. Note If you use Windows XP, be sure you use an edition of SQL Server 2000 that will run on that platform. For information on SQL requirements see http://go.microsoft.com/fwlink/?LinkId=16489. |
In a single computer environment, MCMS requires you to install both the server and client for Microsoft SQL Server 2000.
Note If you have SQL Server running on a LAN or WAN elsewhere in your organization, you do not have to install the server components of SQL Server 2000 on the same computer as MCMS 2002. MCMS 2002 does not support Microsoft SQL Server 7.0 configurations. During the installation of SQL Server note the following requirements on the pages specified below:
|
| Microsoft SQL Server 2000 Service Pack 3 (SP3) | Do the following to install SQL Server 2000 Service Pack 3:
|
| High Security Templates (Recommended) | Although the following security templates are not required software for an MCMS installation, it is recommended that you install them with the prerequisite software.
There are two security templates: the Windows High Security Template and the MCMS Template for the IIS Lockdown Tool. Windows High Security Template To install the Windows High Security Template (hisecws) Important The Windows High Security Template (hisecws) must be installed before you install the Microsoft .NET Framework (which is included in Microsoft Visual Studio .NET). If you apply this template after installing the .NET Framework, then the ASPNET_WP user privileges, such as access to the temp folder, will be removed.
Note Authentication issues exist regarding the configuration of the Windows NT® domain controller and installing the Windows High Security Template. For more information, see the following Microsoft Knowledge Base articles: http://go.microsoft.com/fwlink/?LinkId=9872 http://go.microsoft.com/fwlink/?LinkId=9873 IIS Lockdown Tool It is recommended that you use the IIS Lockdown Tool for increased security on your site. For more information about this tool, see http://go.microsoft.com/fwlink/?LinkId=9864. Certain versions of the tool do not contain instructions specifically for MCMS 2002, so you must install the MCMS-customized version of the tool from the MCMS CD. To install the MCMS-customized version of the IIS Lockdown Tool Note You must extract the iislockd.exe file as indicated in this procedure. Do not run the executable without extracting the files first.
|
| Microsoft Visual Studio® .NET | Microsoft Visual Studio .NET provides many developer tools for your use. (Visual Studio .NET is not required in a production environment.) Installing Visual Studio .NET will not reinstall the .NET Framework if you already have it installed.
Install Visual Studio .NET using the Visual Studio .NET product CD. Note Visual Studio .NET may require additional installation prerequisites. It is recommended that you read the Visual Studio .NET documentation. |
| Microsoft .NET Framework Service Pack 2 | Note Microsoft .NET Framework is installed when you install Microsoft Visual Studio .NET; therefore, you must install Service Pack 2.
Do the following to install Microsoft .NET Framework Service Pack 2 from the MCMS product CD:
|
| Microsoft Internet Explorer WebControls v.1.0 | The Microsoft Internet Explorer WebControls Version 1.0 of the ASP.NET Server Controls is available on the MCMS CD.
Do the following to install the WebControls:
|
Follow the installation steps in this section if you do not have a previous version of MCMS on your computer. The steps must be completed in the order in which they are presented.
If you have MCMS 2001 installed on your computer, you must follow a different set of steps to upgrade to MCMS 2002. For information about upgrading to MCMS 2002 from MCMS 2001, see the upgrading instructions at http://go.microsoft.com/fwlink/?LinkId=9919.
Note Before you install MCMS 2002, you must have first installed the required software. For a complete list of the required software and the order of installation, see MCMS 2002 Software Requirements for a Single Computer Development Environment.
To install MCMS 2002, you must be a member of the Microsoft Windows NT® administrators group on the destination server.
For information about managing a site, including creating rights groups and managing user access, see "Managing Site Structure and Workflow" in MCMS 2002 Help.
This section contains:
Enabling Windows Installer Logging
Step 1: Creating Windows NT User Accounts
Step 2: Creating the MCMS Database and Granting Rights
Step 3: Creating a Web Site for MCMS
Step 4: Installing MCMS 2002 Components
Step 5: Configuring the MCMS Database
It is recommended that you enable Windows Installer logging before you begin the MCMS installation process. The log file that Windows Installer creates will help you identify any installation issues and will also assist Product Support Services should you have any problems with the installation process.
If you have never run Windows Installer on your computer, you need to set up a key to enable Windows Installer logging. You must have local administrator rights to do this.
To set up a key to enable Windows Installer logging
A new value with the name Logging is created.
Note This procedure enables Windows Installer logging for all applications that use Windows Installer. To minimize disk impact, it is recommended that you disable logging after you have installed the components.
To disable logging, delete the value Logging that you created.
After you complete the MCMS configuration steps, you can check for the log file in the temporary folder (either type CD %TEMP% from a command prompt, or point to Start, click Run, in the Open box, type %temp%, and then click OK). The installation log files have a name format such as MSIc57af.LOG. Find the installation log file that was created last and open it to view the contents of the file.
You need two valid Windows NT accounts on the local computer: the MCMS initial administrator and the MCMS system account.
You can use an existing Windows NT user account for the MCMS initial administrator; however, it is recommended you create a new account for the MCMS system account.
MCMS initial administrator
The MCMS administrator sets up and manages publishing in the MCMS environment. MCMS administrators have full privileges (including the right to create, edit, and approve pages) in all MCMS 2002 containers. This initial administrator is the first administrator created by the Database Configuration Application (DCA) when a database is created or upgraded. In the beginning, this is the only user who can log on to Microsoft Content Management Server (MCMS) 2002 through the MCMS 2002 Site Manager.
MCMS system account
The system account is used to access resources such as those in Microsoft Active Directory® and SQL Server 2000. This account acts as an agent on behalf of all MCMS users when the MCMS Content Server accesses a resource. The system account must have permission on all the resources that it needs to access, such as organizational units, domains, containers, groups, and users in MCMS.
When setting up an MCMS system account, note the following:
Note There is a known issue with ASP.NET, domain controllers, and local accounts. On a domain controller all user accounts are domain accounts and are not local machine accounts. Therefore, ASP.NET fails to start because it cannot find a local account named localmachinename\ASPNET. To provide a valid user account on the domain controller, you must specify an explicit account in the <processModel> section of the Machine.config file, or you must use the system account. For more information, see the Microsoft Knowledge Base for article Q315158 at http://go.microsoft.com/fwlink/?LinkId=12910.
To create a MCMS system account
| Use this | To do this |
| User name | Type the name for the system account. This can be a local account. It does not have to be a domain account. |
| Password | Type the password. |
Once you have created the required Windows user accounts, proceed to "Step 2: Granting Rights to the MCMS Database."
After you have installed the prerequisite software, the first step in installing MCMS 2002 is to create a Microsoft SQL Server database and grant rights to it. The database is the Content Repository that MCMS uses to store content. MCMS creates the appropriate database schema and populates it with the required data during the installation process.
The MCMS Content Server uses the MCMS system account credentials to read and write data to the database.
Or
To grant MCMS system account rights to the database
A list of roles appears in the Permit in Database Role pane.
Note The db_ddladmin is only needed if you are using the import function in site deployment.
You have created a local database and have granted the MCMS system account rights to that database. Proceed to "Step 3: Creating a Web Site for MCMS."
You need two Web sites for MCMS. You need one site for MCMS and another site to serve as the entry point for the MCMS Server Configuration Application (SCA).
When you install Internet Information Services (IIS) with the common files, Internet Information Services Snap-In, and World Wide Web Server components, a default Web site is created. If you delete the default Web site or if you choose to have MCMS run on another Web site then you must create that site before installing MCMS. It is recommended you create a separate Web site as the SCA entry point. See Windows 2000 Professional and Windows XP Professional Help for more information about creating Web sites using IIS.
Note In Windows 2000 Professional and Windows XP Professional, you can only have one active Web site in IIS, so both the MCMS site and the SCA site will be the same.
Note If this site is the entry point for the SCA, deselect the box Allow anonymous access to the Web site.
Now you have created a Web site for MCMS. Proceed to "Step 4: Installing MCMS 2002 Components."
This step explains how to install MCMS 2002 components on a single computer. The components installed are MCMS Content Server, the developer tools, MCMS Site Manager, and MCMS Site Stager.
To install the MCMS components
Note Unless you plan to use Site Stager, you do not need to install it. Site Stager is a component of MCMS 2002 that produces static HTML or ASP copies of part or all of your Web site and enables you to host this content from another directory or server. Site Stager reduces browser traffic on your MCMS site by allowing you to host your site on platforms other than Windows 2000. Site Stager will not work with an ASP.NET-based MCMS site.
| Use this | To do this |
| User Name | Type the user name for your Administrator account. |
| Organization | Type the name of your company. |
Note To change the location of the cache folder, point to Change, browse to the new location, and then click OK. The default is <InstallDrive>:\Program Files\Microsoft Content Management Server\Server.
On the Ready to Install the Program page, select the Launch Database Configuration Application check box to have the Database Configuration Application (DCA) automatically start after the installation completes, and then click Install.
You have installed the MCMS components. The installation log file is saved in <InstallDrive>:\Program Files\Microsoft Content Management Server\LogFiles, which is the default location.
The DCA opens. Proceed to "Step 5: Configuring the MCMS Database."
Note It is recommended that you create the Web sites you will use for MCMS before starting this step (see Step 3: Creating a Web Site for MCMS).
To complete the MCMS installation and configure the MCMS database, use the Database Configuration Application (DCA). In this step, you specify the Web site for MCMS, a Web site for the SCA, select an MCMS system account and the initial site manager account, and finally select and populate your database.
The user running the DCA must have database owner (DBO) privileges on the database. However, if you are using SQL Server authentication then the SQL Server account you are using must have DBO privileges.
Note If you select the Cancel option while the DCA is running, your Internet Information Services (IIS) services will be restarted, but you must then restart the File Transfer Protocol (FTP) service manually and re-run the DCA to complete the configuration.
To manually restart the FTP service
1. Click Start, and then click Run.
2. In the Run dialog box, in the Open box, type inetmgr to load the IIS Manager, and then click OK.
3. In the Internet Information Services window, expand the node with the name of the local computer, right-click the FTP service that was not restarted, and then click Start.
4. The FTP service restarts.
5. Close the Internet Information Services window.
To configure the MCMS database
| Use this | To do this |
| ASP.NET Mode (this is recommended for new sites) | Restrict all read-only sites hosted by this MCMS server to ASP.NET-based content. Note that ASP-based content can still be accessed through any read/write site. |
| Mixed Mode | Enable MCMS to host both read-only and read/write sites hosted by the MCMS Content Server and to access ASP-based content. This option provides compatibility with MCMS 2001 sites. |
| Use this | To do this |
| Default Web Site | Select to use the default Web site, or a different MCMS site you created, as the primary Web entry point for MCMS. |
| Read/Write Site | Select to enable authoring on the MCMS site. |
| Use this | To do this |
| User | Type the MCMS system account user name in the form <local machine or domain>\<username>. The MCMS system account is used to read and write data to the database. |
| Password | Type the password you created for your MCMS system account. |
| Use this | To do this |
| Server | From the drop-down list, select local. |
| Options | Click to expand the dialog box. |
| Database | From the drop-down list, select the database you created in "Step 2: Creating the Database and Granting Rights." |
This action installs the data structure required to make the database an MCMS Content Repository (database).
When the database population operation is complete, a page appears that contains information about the database platform, login, and authentication.
| Use this | To do this |
| NT User (Domain\User) | Type the initial site manager (MCMS administrator) account name in the form <local machine or domain>\<username>. This account will be the only account to have access to Site Manager until additional users have been assigned rights. |
| Password | Type the password you created for your MCMS initial administrator account. |
The Committing changes page opens, the database saves the data, and then the MCMS Site Stager Access Configuration page opens.
You have completed the installation of MCMS on one computer. You can now move on to Configuring the MCMS Content Server, Installing the WoodgroveNet sample site that is included on the product CD, and Installing Authoring Connector.
Note If you encountered any issues during the configuration process, you can refer to the log file that you created by Enabling Windows Installer Logging.
You must configure the MCMS Content Server so that you can assign Windows user accounts on the MCMS server to MCMS rights groups. MCMS rights groups control the access of users to the MCMS applications and sites. You use the MCMS Server Configuration Application (SCA) to configure the MCMS server. The SCA is a utility used to configure individual or multiple servers. After a new installation, users can selectively configure, globally or on just one server, activities such as changing the MCMS 2002 system account, adding and removing supported Windows NT domains, and adding or removing Active Directory groups as the network topology changes or grows.
For information about adding users to rights groups, see the topic "Using the Server Configuration Application" in MCMS 2002 Help.
For your regular working environment, you need to install MCMS 2002 in a production environment that consists of multiple computers.
For information about setting up an environment with many developers, see "Setting Up a Multi-Developer Environment" in MCMS 2002 Help.
This section contains:
MCMS 2002 Hardware Requirements for a Multiple Computer Production Environment
MCMS 2002 Software Requirements for a Multiple Computer Production Environment
Configuring MCMS in a Multiple Computer Production Environment
The hardware requirements for installing Microsoft Content Management Server (MCMS) 2002 on each server in a multiple computer production environment are as follows:
The following is the list of software requirements for installing MCMS in a multiple computer production environment.
Important Microsoft Professional Support Services supports only the platforms outlined in this document.
For information about how to install the software required for a single computer development environment, see MCMS 2002 Software Requirements for a Single Computer Development Environment.
This section contains:
MCMS Content Server Software Requirements
MCMS Site Manager Computer Software Requirements
| Required/recommended software | MCMS-specific installation requirements |
| Microsoft Windows 2000, Professional, Server or Advanced Server, or Windows XP | Observe the following requirements when installing Windows 2000 Server or Windows 2000 Advanced Server:
To run your development environment on Microsoft Windows XP Professional, you must install Microsoft Windows XP Service Pack 1 at a minimum. |
| Microsoft Internet Explorer 6.0 | If you did not install Microsoft Internet Explorer 6.0 during the installation of Windows, you can download it at http://go.microsoft.com/fwlink/?LinkId=12037. |
| Microsoft Windows 2000 Service Pack 2 (Recommended: Service Pack 3) | Note It is recommended that you always check for the latest service packs and hotfixes.
Do the following to install Windows 2000 Service Pack 2:
Do the following to install Windows 2000 Service Pack 3:
|
Microsoft Internet Information Services (IIS) 5.0 components:
|
After you have completed installing the Windows 2000 Service Pack 2, enable IIS as follows:
|
| Cumulative Patch for IIS (Q319733) | Note If you have installed Microsoft Windows 2000 Service Pack 3, you do not need to install this patch.
Do the following to install the Cumulative Patch for IIS (Q319733):
|
| Microsoft SQL Server 2000 (Developer Edition) | Note MCMS 2002 does not support Microsoft SQL Server 7.0 configurations.
Only the client tools are installed on production environment computers. During the installation of SQL Server note the following requirements on the pages specified below:
|
| Microsoft SQL Server 2000 Service Pack 3 (SP3) | Do the following to install SQL Server 2000 Service Pack 3:
|
| Installing the Security Templates (Recommended) | Although the following security templates are not required software for an MCMS installation, it is highly recommended that you install them with the prerequisite software. For more information about security and deployment, see the white paper "MCMS 2002 Secure Deployment and Best Practices" at http://go.microsoft.com/fwlink/?LinkId=9615.
There are two security templates: the Windows High Security Template and the MCMS Template for the IIS Lockdown Tool. Windows High Security Template To install the Windows High Security Template (hisecws) Important The Windows High Security Template (hisecws) must be installed before you install the Microsoft .NET Framework (which is included in Microsoft Visual Studio .NET). If you apply this template after installing the .NET Framework, then the ASPNET_WP user privileges, such as access to the temp folder, will be removed.
http://go.microsoft.com/fwlink/?LinkId=9872 http://go.microsoft.com/fwlink/?LinkId=9873 IIS Lockdown Tool It is recommended that you use the IIS Lockdown Tool for increased security on your site. For more information about this tool, see http://go.microsoft.com/fwlink/?LinkId=9864. Certain versions of the tool do not contain instructions specifically for MCMS 2002, so you will need to install the MCMS-customized version of the tool from the MCMS CD. To install the MCMS-customized version of the IIS Lockdown Tool Note You must extract the iislockd.exe file as indicated in this procedure. Do not run the executable without extracting the files first.
|
| Microsoft .NET Framework | Do the following to install the Microsoft .NET Framework SDK from the MCMS product CD:
Important To use the Windows High Security Template, you must install it before you install the Microsoft .NET Framework. For instructions about installing the Windows High Security Template, see the preceding entry on this table ("Installing the Security Templates").
|
| Microsoft .NET Framework Service Pack 2 | Do the following to install Microsoft .NET Framework Service Pack 2 from the MCMS product CD:
|
| Microsoft Internet Explorer WebControls v.1.0 | The Microsoft Internet Explorer WebControls Version 1.0 of the ASP.NET Server Controls is available on the Microsoft Content Management Server (MCMS) CD.
Do the following to install the WebControls:
|
The following is the list of minimum and recommended software requirements for MCMS Site Manager.
For information about how to install the software required for the MCMS Site Manager computer, see the previous table.
You install MCMS 2002 on multiple computers in a production or testing environment. The steps must be completed in the order in which they are listed. Do the following before you install MCMS 2002.
For information about managing a site, including creating rights groups and managing user access, see "Managing Site Structure and Workflow" in MCMS 2002 Help.
This section contains:
Enabling Windows Installer Logging
Step 1: Creating Windows NT User Accounts
Step 2: Granting Rights to the MCMS Database
Step 3: Creating a Web Site for MCMS
Step 4: Installing Content Server
Step 5: Configuring the MCMS Database in a Multiple Computer Setup
Step 6: Installing Site Manager
It is recommended that you enable Windows Installer logging before you begin the MCMS installation process. The log file that Windows Installer creates will help you identify any installation issues and will also assist Product Support Services should you have any problems with the installation process.
After you complete the MCMS configuration steps, you can check for the log file in the temporary folder (either type CD %TEMP% from a command prompt, or point to Start, click Run, in the Open box, type %temp%, and then click OK). The installation log files have a name format such as MSIc57af.LOG. Find the installation log file that was created last and open it to view the contents of the file.
If you have never run Windows Installer on your computer, you need to set up a key to enable Windows Installer logging. You must have local administrator rights to do this.
To set up a key to enable Windows Installer logging
A new value with the name Logging is created.
Note This procedure enables Windows Installer logging for all modules. To minimize disk impact, it is recommended that you disable logging after you have installed the components.
To disable logging, delete the value Logging that you created.
You need two valid Windows NT accounts on the local computer: the MCMS initial administrator and the MCMS system account.
You can use an existing Windows NT user account for the MCMS initial administrator; however, it is recommended you create a new account for the MCMS system account.
MCMS initial administrator
The MCMS administrator sets up and manages publishing in the MCMS environment. MCMS administrators have full privileges (including the right to create, edit, and approve pages) in all MCMS 2002 containers. This initial administrator is the first administrator created by the Database Configuration Application (DCA) when a database is created or upgraded. In the beginning, this is the only user who can log on to Microsoft Content Management Server (MCMS) 2002 through the MCMS 2002 Site Manager.
MCMS system account
The system account is used to access resources such as those in Microsoft Active Directory® and SQL Server 2000. This account acts as an agent on behalf of all MCMS users when the MCMS content server accesses a resource. The system account must have permission on all the resources it needs to access, such as organizational units, domains, containers, groups, and users in MCMS.
When setting up a system account, note the following:
Note There is a known issue with ASP.NET, domain controllers, and local accounts. On a domain controller all user accounts are domain accounts and are not local computer accounts. Therefore, ASP.NET fails to start because it cannot find a local account named localmachinename\ASPNET. To provide a valid user account on the domain controller, you must specify an explicit account in the <processModel> section of the Machine.config file, or you must use the system account. For more information, see the Microsoft Knowledge Base for article Q315158 at http://go.microsoft.com/fwlink/?LinkId=12910.
To create a MCMS system account
| Use this | To do this |
| User name | Type the name for the system account. This can be a local account. It does not have to be a domain account. |
| Password | Type the password. |
Once you have created the required Windows user accounts, proceed to "Step 2: Granting Rights to the MCMS Database."
After you have installed the prerequisite software, the first step in installing MCMS 2002 is to create a Microsoft SQL Server database and grant rights to it. The database is the Content Repository that MCMS uses to store content. MCMS creates the appropriate database schema and populates it with the required data during the installation process.
The MCMS Content Server uses the MCMS system account credentials to read and write data to the database.
Note The db_ddladmin is only needed if you are using the import function in site deployment.
To grant the MCMS system account rights to the database
A list of roles appears in the Permit in Database Role pane.
You have created the database that MCMS will use as the Content Repository and have granted the MCMS system account rights to that database. Proceed to "Step 3: Creating a Web Site for MCMS."
You need two Web sites for MCMS. You need one site for MCMS and another site to serve as the entry point for the MCMS Server Configuration Application (SCA).
When you install Internet Information Services (IIS) with the common files, Internet Information Services Snap-In, and World Wide Web Server components, a default Web site is created. If you delete the default Web site or if you choose to have MCMS run on another Web site then you must create a site before installing MCMS. It is recommended you create a separate Web site as the SCA entry point.
Note See Windows 2000 Professional and Windows XP Professional Help for more information about creating Web sites using Internet Information Services.
Note If this site is the entry point for the SCA, deselect the box Allow anonymous access to the Web site.
You have now created a Web site for MCMS. Proceed to "Step 4: Installing Content Server."
You install Microsoft Content Management Server (MCMS) Content Server on your public Web server and your authoring Web server. The Content Server is the MCMS processing engine that receives incoming page requests, and then dynamically assembles the corresponding Web pages from its components in the Content Repository (database) and the file system.
To contribute content through the MCMS Web Author, you need only the hardware and software required to support Microsoft Internet Explorer 5.5 or later.
Note To see how much disk space is required to install the components you have selected, click Space to view the required space, and then click OK to return to previous page.
| Use this | To do this |
| User Name | Type the user name for your administrator account in the following form: <local machine or domain>\<username>. |
| Organization | Type the name of your company. |
The Database Configuration Application opens if it was previously selected.
You have installed Content Server. Proceed to "Step 5: Configuring the MCMS Database in a Multiple Computer Setup."
In this step, you select and populate your database, select a Microsoft Content Management Server (MCMS) system account and the initial site manager account, and specify the virtual Web site for MCMS.
The user running the Database Configuration Application (DCA) must have database owner (DBO) privileges on the database.
Note If you select the Cancel option while the DCA is running, your Internet Information Services (IIS) services will be restarted, but you must then restart the File Transfer Protocol (FTP) service manually and re-run the DCA to complete the configuration.
To manually restart the FTP service
1. Click Start, and then click Run.
2. In the Run dialog box, in the Open box, type inetmgr to load the IIS Manager, and then click OK.
3. In the Internet Information Services window, expand the node with the name of the local computer, right-click the FTP service that was not restarted, and then click Start.
4. The FTP service restarts.
5. Close the Internet Information Services window.
To configure the MCMS database
| Use this | To do this |
| ASP.NET Mode (this is recommended for new sites) | Restrict all read-only sites hosted by this MCMS server to ASP.NET-based content. However, ASP-based content can still be accessed through any read/write site. |
| Mixed Mode | Enable MCMS to host both read-only and read/write sites hosted by the MCMS Content Server and to access ASP-based content. This option provides compatibility with MCMS 2001 sites. |
| Use this | To do this |
| Read-Only Site | Enable the selected MCMS site to serve MCMS pages. No changes to content will be allowed through this site. |
| Read/Write Site | Enable the selected MCMS site to be used for all MCMS purposes, including development, authoring, managing, and deploying. |
| Use this | To do this |
| User Name | Type the MCMS system account user name in the form <local machine or domain>\<username>. The MCMS system account is used to read and write data to the database. |
| Password | Type the password you created for your MCMS system account. |
A message appears confirming IIS is stopped.
This action installs the data structure required to make the database an MCMS Content Repository.
| Use this | To do this |
| User Name | Type the initial site manager (MCMS administrator) account name in the form <local machine or domain>\<username>. This account will be the only account to have access to Site Manager until additional users have been assigned rights. |
| Password | Type the password you created for your MCMS initial administrator account. |
The database saves the data and the MCMS Site Stager Access Configuration page opens.
You have installed configured the database. Proceed to Step 6: Installing Site Manager.
Note If you encountered any issues during the configuration process, you can refer to the log file that you created by Enabling Windows Installer Logging.
Now you have configured the MCMS database. Proceed to "Step 6: Installing Site Manager."
You can install MCMS Site Manager on either a server or a client computer. Site Manager can be installed on multiple computers in your distributed network and can be installed on Windows 2000 Server, Advanced Server, or Windows XP Professional with Service Pack 1 or later.
| Use this | To do this |
| User Name | Type your name. |
| Organization | Type the name of your company. |
| Enter MCMS server to be managed | Type the name of the MCMS server that Site Manager will point to. This is the server that contains the data that Site Manager uses. |
Note Installing the WoodgroveNet sample site is not recommended in a production site environment.
The WoodgroveNet sample site is included with MCMS 2002. You can use this site to learn about developing your Web site to suit your requirements. WoodgroveNet is a unilingual, external ASP.NET-based site.
For information about other sample sites and code sample downloads, go to http://go.microsoft.com/fwlink/?LinkId=9920.
Note Before installing the WoodgroveNet sample site, you must install Content Server and Site Manager, and the MCMS system account must have database owner (DBO) rights to the Content Repository (database) to run site deployment. For more information about installing Content Server, see Step 4: Installing Content Server. For more information about installing Site Manager, see Step 6: Installing Site Manager.
To use Authoring Connector with the sample site, you must install the sample site before you install Authoring Connector.
To install the WoodgroveNet sample site
| Use this | To do this |
| User Name | Type the information for a user with site manager account rights using the form <local machine or domain\username>. |
| Password | Type the password. |
The installation status appears. Installation may take a few minutes.
Note After you have installed the WoodgroveNet sample site, the Web entry point for the WoodgroveNet sample site is http://localhost/woodgrovenet. This link works only on the server where you installed the WoodgroveNet sample site.
Important To make the WoodgroveNet sample site available to guest access, set the guest user to the Microsoft Internet Information Services (IIS) guest user, iusr_servername, using the System Configuration Application (SCA), and add that user to a subscribers group using Site Manager. For information about enabling guest access on the site, see "Enabling Guest Access" in MCMS 2002 Help.
A content provider uses Microsoft Content Management Server (MCMS) 2002 Authoring Connector to produce documents in Microsoft Word 2002 and then releases the documents to the MCMS Web site without having to leave the Word application. Authoring Connector is a wizard-based application.
Note To use Authoring Connector with the WoodgroveNet sample site, you must install the WoodgroveNet sample site before you install Authoring Connector.
Note MCMS 2002 Help is installed on the server only, with MCMS 2002 Site Manager. Users of the Authoring Connector and the Web Author must access the documentation directly from the CD. For more information see Viewing MCMS 2002 Documentation.
You install Authoring Connector on a client computer. Any user with rights to contribute content to an MCMS site can install Authoring Connector.
To install Authoring Connector, you must have the following software on your computer:
For information about installing the software required for Authoring Connector, see the table on installing prerequisite software earlier in this document (either MCMS Software Requirements for a Single Computer Development Environment or MCMS Software Requirements for a Multiple Computer Production Environment).
To install Authoring Connector
| Use this | To do this |
| User Name | Type your name. |
| Company Name | Type the name of your organization. |
| Install this application for | Select the appropriate option to make this copy of Authoring Connector available for anyone to use, or to limit it for your own use. |
The installation begins, and the Setup Status page displays until the installation is complete.
Important Site Stager works with the ASP-based sites and not with ASP.NET-based sites.
MCMS Site Stager is a stand-alone application that enables you to convert dynamic, database-driven MCMS sites to static, file-based (.htm and .asp) sites. The source computer contains the portion of the site that you stage. The destination computer contains the staged site.
The recommended configuration for installing Site Stager is to install on the destination computer. Site Stager pulls the portion of the site being staged to the destination computer.
Note You can only stage an MCMS site using Site Stager.
To install Site Stager only, you need the following software:
For information about installing the software required for Site Stager, see the table on installing prerequisite software earlier in this document (either MCMS Software Requirements for a Single Computer Development Environment or MCMS Software Requirements for a Multiple Computer Production Environment).
You should also consider how much disk space will be required for the site when it is staged.
Note To see how much disk space is required to install the components you have selected, click Space to view the required space, and then click OK to return to previous screen.
| Use this | To do this |
| User Name | Type your name. |
| Organization | Type the name of your company. |
You have completed the installation of Site Stager.
Users can author directly on the Web site using the MCMS Web Author, a dynamic editing feature. To use the Web Author, you must have Microsoft Internet Explorer 5.5 or later installed.
To activate the Web Author, the Read/Write Site option must have been selected during the MCMS installation.
Note MCMS 2002 Help is installed only on the server and with MCMS 2002 Site Manager. Authoring Connector and Web Author users must access the documentation directly from the CD. For more information, see Viewing MCMS 2002 Documentation.
To uninstall MCMS 2002 and its components, you must do the following steps in the order listed.
This section contains:
Do the following to uninstall the WoodgroveNet sample site.
Important You must uninstall the WoodgroveNet sample site before uninstalling MCMS 2002.
To uninstall the WoodgroveNet sample site
The uninstall proceeds without any further user action.
Do the following to uninstall MCMS Authoring Connector.
To uninstall Authoring Connector
Use the following procedure to uninstall an MCMS core component.
To uninstall an MCMS core component
The uninstallation process proceeds without any further user action.
Important When you uninstall the core components, files are removed. Any MCMS files that were directly modified will also be removed. However, if you have added new files to MCMS directories, for example, customized ASP files in the IIS_CMS folder, they will not be removed during the uninstall, but you will lose any virtual mappings that are inherited from MCMS. Also, any changes that you made to the database will not be uninstalled.
The uninstalling process is complete.
-----------------------------------------------------------------------------------------------------------
Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
© 1997-2003 Microsoft Corporation. All rights reserved.
Microsoft, Active Directory, JScript, MSDN, MS-DOS, MSN, Outlook, Verdana, Visual Basic, Visual C#, Visual C++, Visual SourceSafe, Visual Studio, Webdings, Win32, Win64, Windows, Windows Media, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.