Microsoft Content Management Server 2002 Evaluation Guide
Collapse the table of content
Expand the table of content

Microsoft Content Management Server 2002 Evaluation Guide

Content Management Server

Microsoft Corporation

June 2003

Applies to:
    Microsoft® Content Management Server 2002

Summary: Evaluate the new features and functionality of Microsoft Content Management Server 2002 by reading this guide and walking through some of the common procedures for developers, administrators, and business users.

For more detailed information about MCMS, see MCMS 2002 Help, which includes a set of tutorials, and see the other MCMS resources listed in the "For More Information" section at the end of this guide. (50 printed pages)

Download a copy of this document from the Microsoft Download Center (


How to Use This Guide
Product Overview
Features at a Glance
Architectural Overview
Installing MCMS for Evaluation
Pre-Installation Steps
Administering MCMS
Authoring Content
A Developer's Perspective
For More Information


Microsoft® Content Management Server (MCMS) 2002 provides a fast and cost-effective way to create, deploy and maintain mission-critical, content-rich Web sites.

Business users can create and publish Web content from the browser or directly from within Microsoft Word 2002 through a seamless integration that connects directly into the MCMS workflow process.

Developers and system administrators can quickly build and deploy ASP.NET Web sites and Web services by leveraging the integration of MCMS with Visual Studio®.NET and other Microsoft servers such as Commerce Server, SharePoint™ Portal Server and Application Center.

How to Use This Guide

This guide has the following sections. For best results, review these sections in order, because each section builds on the concepts in preceding sections.

Product Overview
Highlights key features of MCMS 2002, and describes how these features can benefit organizations that build and manage content-rich Web sites.
Features at a Glance
Lists the MCMS features for developing and deploying an MCMS Web site, and for managing Web content.
Architectural Overview
Describes the logical architecture of an MCMS Web site (channels, templates, and resource galleries), and the component architecture (browser, Content Repository, Content Server, and so on.).
Installing MCMS for Evaluation
Provides step by step instructions for installing MCMS in a single computer development environment so that you can evaluate product features.
Administering MCMS
Introduces the Site Manager and the Server Configuration (SCA) application and provides some sample procedures for administering your site with these tools.
Authoring Content
Introduces the tools and procedures for authoring and publishing content.
A Developer's Perspective
Introduces the tools that developers use to build MCMS Web sites.
For More Information
Provides links to more information about MCMS, such as white papers, community sites, and the MCMS Support Web site.

Product Overview

MCMS 2002 provides many enhancements to the MCMS 2001 product. This section contains an overview of the following enhancements and new features:

  • Enhanced content authoring capabilities
  • Enhanced site deployment capabilities
  • Enhanced distributed administration capabilities
  • Visual Studio .NET integration
  • Support for source code management
  • ASP.NET architecture
  • MCMS Web server controls
  • Support for XML content
  • Support for Web services

Enhanced Content Authoring Capabilities

MCMS 2002 provides tight integration with Microsoft Word 2002 through the new MCMS Authoring Connector.

The MCMS Authoring Connector is a wizard-based plug-in to Word 2002 that enables you to create richly formatted content in Word—including support for embedded objects such as images, video files, and Excel spreadsheets—and to publish that content directly to MCMS without leaving the Word environment.

Using the Authoring Connector, you can do the following:

  • Publish content as an attachment and/or convert it directly to an HMTL page
  • Set automatic publication and archival schedules
  • Select pre-defined publishing tasks to automate redundant steps in the process
  • Submit the content directly into the MCMS workflow system

Enhanced Site Deployment Capabilities

MCMS 2002 provides an integrated deployment solution that leverages the capabilities of Microsoft Application Center. Using Application Center, you can deploy MCMS Web sites throughout the development cycle. You can deploy Web sites through firewalls and across server farms more easily than you could with MCMS 2001. You can also move applications from development computers, to test computers, to staging computers, to production computers, resulting in a streamlined development process and site life cycle.

When you integrate MCMS with Application Center, you can leverage scheduled automatic deployments, automatic registration of server control components, incremental deployments, and transactional deployments. You can also use the open deployment API for building highly customized deployment solutions.

Enhanced Distributed Administration Capabilities

Complimenting the MCMS distributed authoring and publishing capabilities, the new Channel Manager role enables you to optimize the management of global Web sites as well as to manage multiple Web sites within the same Content Server. This new role enables you to delegate certain administrative capabilities to specific users, and for specific areas, within the system.

Visual Studio .NET Integration

MCMS 2002 offers you a unified development experience when building or extending your online business solutions. All MCMS developer tools and resources are now integrated with the Visual Studio .NET integrated development environment (IDE). This integration provides you with a single, familiar development environment, where creating a new MCMS-based application in Visual Studio .NET is as easy as selecting File->New Content Management Server Project.

When you open an MCMS project in Visual Studio .NET, you are in a rich MCMS development environment that provides access to the MCMS object model. The development environment includes drag-and-drop galleries of MCMS controls and template creation and management features, and it gives you access to all of the richness of Visual Studio .NET, such as great code debugging.

Together, MCMS and Microsoft Visual Studio® .NET form a dynamic Web site programming environment where powerful, Web services-enabled online business solutions can be built or easily extended. MCMS is the natural complement to Visual Studio .NET, extending its rapid application development capabilities into enterprise e-business.

Support for Source Code Management

The new MCMS 2002 template architecture manages the template source code and Web site application code on the file system so that you can manage your source code in Microsoft Visual SourceSafe®, or any other source code management system.

With this new support, MCMS offers you the best content management and publishing environment, and the best application development and management environment, all in one integrated environment that you manage using familiar tools.

ASP.NET Architecture

MCMS enables you to use ASP.NET to create MCMS applications while at the same time enabling you to benefit from the reliability, performance, and scalability built into ASP.NET.

The MCMS .NET Class Library fully leverages the .NET Framework programming model but also extends it in areas such as output caching and Web site authentication. .NET Framework support provides developers with a consistent and intuitive experience while developing their e-business applications; greater productivity through the use of Web server controls; and requires fewer lines of code, while providing greater manageability, through the separation of code and content.

MCMS Web Server Controls

The new MCMS development environment includes a gallery of pre-built MCMS server and user controls that provide for drag-and-drop assembly of dynamic Web sites. For example, MCMS includes a Woodgrove sample site that demonstrates:

  • HTML and XML placeholder controls
  • Dynamic navigation
  • Breadcrumb navigation
  • Dynamic summary pages

You can use the Woodgrove controls, or you can use a number of MCMS APIs to build your own controls to support the special needs of your Web sites. And with the drag-and-drop control gallery in Visual Studio .NET, assembling dynamic Web sites has never been faster!

Support for XML Content

MCMS 2002 provides the standards-based interoperability that companies need to integrate Web sites and content with their legacy systems, line of business applications, and partners' systems. With the new XML placeholder object, you can create and store XML as well as apply XSLT style sheets for rendering and XSD for execution of data validation rules.

With this native support for XML, you can build applications using open standards that will support more efficient connections with other data systems, and flexibility for future use of the content.

Support for Web Services

The enhanced support in MCMS 2002 for Web services enables you to integrate your Web sites and content with other applications without the restrictions of earlier technologies, and without the limitations of heterogeneous platforms and development languages. This enables you to build powerful distributed solutions spanning internal users, business partners, and/or customers, using open standards and keeping implementation costs low.

Features at a Glance

Table 1. Comprehensive Solution for Managing Web Content

Feature Description
MCMS Web Author client Empower business users to create and publish rich Web content directly from within their browsers.
Template-based publishing Centrally control branding, page and navigation layout and corporate publishing standards through authoring and presentation templates.
Authoring Connector for Office Empower business users to create and publish rich content directly from within Word 2002.
Publishing tasks Streamline the publishing process with tasks that automate repetitive steps.
Workflow Ensure content is properly reviewed and approved prior to publishing through multi-step role-based workflow.
Content scheduling Ensure content is always published on time and is never out of date by automating its publishing and archival schedule.
Real-time site updates Streamline the content deployment process by enabling business users to safely publish content into the development environment, the staging environment, or directly onto the production Web servers.
Page revision history Enable users to perform content audits and compare revisions through automatic storage of content revisions and page versions.
Object-based repository Ensure maximum flexibility for your content by storing it as individual content objects in SQL Server that are separate from the application code and design elements of the Web site. This provides for dynamic use of content such as personalization, and flexibility for re-use in future applications.
Dynamic page assembly Use dynamically assembled pages for personalization of content based on user profile, click-through analysis, browsing device, and language preference.
Dynamic template switching Switch templates on the fly to serve content using different styling and layout to support diverse sets of browsing devices.
Connected content pages Easily share content across multiple pages within the Web site.

Table 2. Faster Time to Deploy and Lower Total Cost of Ownership

Feature Description
Visual Studio .NET integration Build content management applications quickly and easily in Visual Studio .NET with integrated MCMS projects, template manager, solution explorer and drag-and-drop server controls gallery.
ASP.NET architecture Leverage the full power of .NET in content management applications through support for the .NET Framework.
Extensions to ASP.NET output caching Build Web sites that are scalable and high performance with ASP.NET output caching support and MCMS extensions to the .NET caching model.
Extensions to ASP.NET authentication model Use existing authentication model or integrate custom models using ASP.NET authentication support and MCMS extensions to the .NET authentication model.
Content management server controls Build applications faster with pre-built content management developer controls.
MCMS managed Publishing API Build custom publishing applications and functionality into your Web sites by accessing the MCMS capabilities and content programmatically through the managed Publishing API.
MCMS managed Deployment API Extend the integrated deployment solution for highly customized deployment operations using the managed Deployment API.
Source code management support Support for source code versioning, branching, archival and team-based development with the ability to use industry-leading source code management tools, such as Visual SourceSafe, to manage application code.
Integration with SQL Server Integrated with Microsoft SQL Server™ for scalable and reliable content storage.
Integration with Commerce Server Integrated with Microsoft Commerce Server for building content-rich sites with integrated e-commerce functionality, content profiling and personalization, and Web site analysis and reporting tools.
Integration with SharePoint Portal Server Integrated with Microsoft SharePoint™ Portal Server for building content-rich Web sites with integrated search, document management, and knowledge worker portal services.
Integration with Microsoft Office Integrated with Microsoft Office for empowering non-technical business users to create and publish rich Web content directly from within Microsoft Word 2002.
Integration with Application Center Integration scripts are provided that leverage Microsoft Application Center's deployment capabilities and provide system administrators with a deployment solution that supports scheduled and automated deployments, incremental deployments for maximum performance, and transactional deployments for roll-back support in case of hardware failure.
Easy to integrate with BizTalk Server Integrate data from legacy systems using Microsoft BizTalk® and over 300 back-end system adapters.
MSIB Solution Site Build end-to-end solutions quickly with this pre-built, production quality solution site.
MSIB prescriptive architecture guidance Build end-to-end solutions right the first time with Microsoft's prescriptive best practices for building e-business Web sites.
MSIB services Leverage Microsoft global network of implementation partners who have been trained on building and deploying e-business Web sites using Microsoft prescriptive best practices.

Table 3. Mission Critical

Feature Description
Windows Network Load Balancer (NLB) support Support for load-balanced Web farms for maximum scalability and availability using Microsoft NLB.
Support for industry-standard load balancing software and hardware Support for load-balanced Web farms for maximum scalability and availability using any industry standard software or hardware-based load balancing technology.
Symmetric multiprocessor (SMP) support Scale up with your hardware through direct support for multiple CPUs within the same physical server.
Caching Achieve maximum page serving performance with caching of both static and dynamic content.
XML placeholder object Native support for managing content in XML format.
XSLT style sheet support Support for content styling through standard XSLT style sheets.
XSD validation support Support for content validation through XSD definitions.
Web services support Support for exposing content and functionality within the system as standard Web services.
Distributed administration Optimized management of multiple sites within the same server or highly distributed Web sites with support for delegation of certain administrator capabilities to the Channel Manager role.

Table 4. Windows Active Directory Services (ADS) Integration

Feature Description
Integration with Application Center for deployment Leverage Application Center deployment capabilities and provide system administrators with a deployment solution that supports scheduled and automated deployments, incremental deployments for maximum performance and transactional deployments for roll-back support in case of hardware failure.

See the white paper on deploying content with Application Center, and download the integration scripts from

MCMS Site Deployment Manager Import and export content and templates for deployment and replication between servers.
MCMS Site Manager Easily create and manage the site map, template galleries, roles, and permissions in the Site Manager.

Table 5. MCMS Server Configuration Application (SCA)

Feature Description
Extensible workflow Extend the workflow to integrate tightly with your existing business processes and workflow systems using the workflow hooks event model.
Extensible server controls Extend the MCMS development environment by customizing pre-built controls or by adding your own custom controls.
Extensible publishing client Extend the publishing environment to support your existing business processes and for integration with existing publishing applications.
Extensible deployment solution Extend the integrated deployment solution for highly customized deployment operations using the managed Deployment API.
Extensible object properties Extend the properties on content objects for content integration with other data systems.

Architectural Overview

This section describes the components of an MCMS system and an MCMS Web site. It also describes the tools you use to develop and manage your MCMS Web site.

This section contains:

  • Components of an MCMS Web site
  • Components of an MCMS environment
  • User roles and rights
  • MCMS tools

Components of an MCMS Web Site

This section introduces you to the terminology that is used to describe the components of an MCMS Web site.

An MCMS Web site is comprised of two types of objects:

  • Templates. An ASPX, ASP, or ASCX source file that you create to define the overall appearance for a set of pages in an MCMS Web site and that contains the executable code. Templates are the primary source of information about a particular set of pages that are said to be based on that template.
  • Containers. Virtual storage spaces that you use to organize your Web pages and content.

MCMS has three types of containers: channels, templates galleries and resource galleries.

  • Channel. A container used to store the structure of the pages of an MCMS Web site.
  • Template Gallery. A container used to manage access to templates.
  • Resource Galleries. A container used to store graphics, audio, and video files accessed by a user on an MCMS site.

Each container can contain child containers, forming a tree-like structure, as shown in the following figure.

Figure 1.

Components of an MCMS Environment

The components of an MCMS environment can be categorized as follows:

  • Developer tools and components
  • Authoring tools
  • Other Microsoft technologies

The following figure shows all of these components in one Microsoft® Content Management Server (MCMS) environment.

Figure 2.

Developer Tools and Components

When you build an MCMS Web site, you work with the following MCMS tools and components:

  • Visual Studio .NET client. Microsoft Visual Studio .NET extensions installed with MCMS, such as the Template Explorer and custom collection editors, provide MCMS-specific functionality. You can create and manage templates and template galleries from within the Visual Studio .NET integrated development environment (IDE).
  • Site Manager. In MCMS 2001, the Site Manager tool was known as Site Builder. Site Manager is now a non-authoring tool. You use this tool to create and maintain MCMS Web sites.
  • ASPX template file. The code for a template is now stored on the file system as an ASP.NET ASPX file or an ASP file.
  • Content Repository. The Content Repository component stores information about the structure and content of an MCMS Web site in a Microsoft SQL Server™ database.
  • Content Server. The Content Server component is the core engine of the MCMS Web site. This includes the MCMS Publishing application programming interface (API) and the Internet Server API (ISAPI).
  • Placeholder Controls. Placeholders are used to display content on an MCMS Web page. Placeholder code is now implemented using ASP.NET server controls, called placeholder controls. There are individual placeholder controls for the different types of content, such as text, images, and attachments.

Authoring Tools

When you or other users author content and publish it to your MCMS Web site, you use the following authoring tools:

  • Web Author. The Web Author component is the main authoring application within MCMS. It enables authors and editors to provide content for an MCMS Web site using the Internet Explorer browser.
  • Authoring Connector. The Author Connector component enables authors to create and submit content to an MCMS Web site using Microsoft Word 2002. Content can be displayed in both text and attachment placeholders.
  • Browser. The browser component is used to view and maintain the Web site, using the Web Author.

Other Microsoft Technologies

MCMS works with the following Microsoft technologies:

  • SQL Server 2000. Microsoft SQL Server 2000 is used as the Content Repository for an MCMS Web site.
  • Content Connector and Commerce Server. Microsoft Solution for Internet Business (MSIB) 2002 Content Connector is a feature provided by MSIB 2.0 that enables you to merge the .NET capabilities of MCMS 2002 and Commerce Server 2002. Using Content Connector, you can do the following:
    • Edit Commerce Server product catalog data from MCMS-based Web pages.
    • Associate a page profile with any MCMS page using the Commerce Server profile service features.
    • Personalize sites by targeting content to specific users on selected pages.
  • Microsoft Word 2002. By using the MCMS Authoring Connector, you can author content in Microsoft Word 2002 and publish it to the MCMS Web site.

User Roles and Rights

To enable you to determine who has permission to perform a given management or authoring task on your Web site, MCMS provides rights groups and roles.

  • Rights group. A group of users who are granted or denied access rights to one or more MCMS containers. Each rights group corresponds to one of the roles, and users within those rights groups have the rights that are assigned to a given role.
  • Roles. Every MCMS 2002 user, from the subscriber who browses your Web pages, to an administrator who sets up the site, is assigned a role. There are eight roles as shown in the table below.

The following table lists the eight MCMS roles and their associated rights in the publishing and managing process.

Table 6.

User Role Tasks Performed
Subscriber Browses the site.
Author Creates, edits, and submits content.
Editor Approves or declines content.
Moderator Edits, approves, or declines content.
Resource Manager Deletes, replaces, and creates shared resources.
Template Designer Creates channels, resource galleries, template galleries and templates.
Channel Manager Creates channels, resource galleries, and template galleries.
Administrator Has rights to perform all of the above tasks, and can create rights groups and assign users to them.

Each of the eight roles is assigned certain rights. These rights are given to rights groups. In addition to encapsulating the rights of a particular role, the rights group determines which channels or galleries the members of that group can access. For instance, if there are two channels, A and B, the administrator can create an editors rights group for channel A, and a different editors rights group, with different members, for channel B. Both groups have the rights specified by the editor role, but the rights groups specify where those rights apply.

MCMS Tools

MCMS 2002 provides a comprehensive set of tools, for both business managers and developers, to develop and manage MCMS Web sites. Using these tools, MCMS enables you to do the following:

  • Build scalable and dynamic Web sites using extensible MCMS controls.
  • Empower your business users to create, publish, and manage their own Web content.
  • Enable multiple site authors with the appropriate rights to create and update many parts of a Web site simultaneously by effectively separating content from format.

The figure below shows the MCMS tools for managing a production site: Authoring Connector, Web Author, Site Manager, and Site Stager.

Figure 3.

These tools are used by the following MCMS users:

  • Site authors can use the MCMS Web Author and Authoring Connector to produce content for their Web sites with little need to understand the technical aspects of site development.
  • Administrators use the Site Manager to manage site content and workflow, and optionally, the Site Stager, to transform their Web sites.
  • Developers can take advantage of various .NET-based technologies, such as Microsoft Windows Forms and ASP.NET. They can use the MCMS Publishing application programming interface (API) to customize Web sites. MCMS integration with Visual Studio .NET enhances developer productivity and supports parallel efforts by multiple developers.

Installing MCMS for Evaluation

For the purpose of this guide you will configure a typical development environment by installing all of the required software on one computer. This will make it easy for you to move straight into the following exercises.

For the complete MCMS installation instructions, you can download the Installation Guide at

Hardware Requirements

The following list contains the recommended hardware to install and run MCMS 2002 on a single computer for evaluation.

  • PC with Pentium III-compatible or higher processor
  • 1GB RAM
  • 2GB free disk space (MCMS only)
  • CD-ROM drive
  • Network Interface Card

Software Requirements

The following table lists the minimum and recommended software required to install and run MCMS on a single computer. To perform the steps in this guide, it is assumed that you are using Microsoft Windows® 2000 Server. To perform the procedures that introduce the MCMS Authoring Connector, you must install Microsoft Office XP or Word 2002.

Table 7.

Minimum Recommended
Microsoft Windows 2000 Pro/Server/Advanced Server, 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
Microsoft Windows 2000 Pro/Server/Advanced Server, Windows XP
Microsoft Internet Explorer 6.0 Microsoft Internet Explorer 6.0
Microsoft Windows 2000 Service Pack 3 or Windows XP Service Pack 1 Microsoft Windows 2000 Service Pack 3 or Windows XP Service Pack 1
Microsoft IIS 5.0 Components:
  • Common Files
  • IIS Snap-In
  • WWW Server
  • FrontPage Extensions
Microsoft IIS 5.0 Components:
  • Common Files
  • IIS Snap-In
  • WWW Server
  • FrontPage Extensions
Microsoft SQL Server 2000
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
Microsoft SQL Server 2000
Microsoft SQL Server 2000 Service Pack 3 Microsoft SQL Server 2000 Service Pack 3
  High Security Templates

These are not required for Evaluation purposes, but in a real installation they are recommended. See the MCMS Installation Guide at for more details.

Microsoft .NET Framework, version 1.0
Note   This is automatically installed when you install Visual Studio .NET so you do not need to install it if you are going to install Visual Studio .NET.
Microsoft .NET Framework, version 1.0
Microsoft Visual Studio .NET All versions
Microsoft .NET Framework Service Pack 2 Microsoft .NET Framework Service Pack 2
Microsoft Internet Explorer WebControls v1.0 Microsoft Internet Explorer WebControls v1.0

Pre-Installation Steps

Before installing MCMS 2002, you must install and configure the software required to support it. Because the order of installation is important, please follow the steps below to assure that your evaluation system works properly. It is assumed that you are already familiar with these packages, so this guide only notes special settings or options necessary for use in an MCMS environment.

Installing Windows 2000 Server Core Components

  1. At the Windows 2000 Components page, make sure that the following Internet Information Server (IIS) sub-components are all selected:
    • Common Files
    • FrontPage Server Extensions
    • IIS Snap-In
    • World Wide Web Server

    It is fine to configure your system as a stand-alone server, or a member of a domain if you have one in place, but do not make it a domain controller.

  2. Create two additional user accounts. You will use them to act in various MCMS user roles during the exercises.
  3. Install Internet Explorer 6.0.
  4. Install Windows 2000 Service Pack 3.

Installing SQL Server 2000

  1. On the Installation Selection page, select the Create a new instance of SQL Server, or Install Client Tools option.
  2. On the Installation Definition page, select the Server and Client Tools option.
  3. On the Setup Type page, select Custom.
  4. On the Select Components page, in the Sub-Components section, make sure Full-Text Search is selected.
  5. For the SQL Server Service Accounts, use Same for each service, and set it to Use the Local System account. The Authentication Mode should be set to Windows Authentication Mode.
  6. On the Collation page, be sure to use the following settings: dictionary order, case-insensitive, for use with 1252 Character Set. (This is the default setting.)
  7. On the Network Libraries page both the Named Pipes and TCP/IP Sockets check boxes should be selected.
  8. After you have SQL Server 2000 installed, install SQL Server 2000 Service Pack 3.

This point in the process is where you would normally install the Windows High Security Templates and the MCMS-specific template for the IIS Lockdown Tool. These templates are recommended for all production environments, but because we are not installing a production system, we'll skip these steps to save time.

Installing Visual Studio .NET

There are no special requirements for installing Visual Studio .NET. Be sure to install the Microsoft Visual C# .NET modules, as some parts of this walk-through will make use of them.

After you've completed the Visual Studio .NET installation you must install the Microsoft .NET Framework Service Pack 2. To do this, run the file dotnetfxSP2.exe, which is located in the Support\Dotnet folder on the MCMS CD-ROM.

Figure 4.

Installing Internet Explorer WebControls

  • Locate the file iewebcontrols.msi in the WebControls folder of the MCMS CD and double-click to install it.

    Figure 5.

Creating the MCMS System Account

You must create two local user accounts (not domain accounts) for MCMS:

  • MCMS Initial Administrator Account sets up and manages publishing in the MCMS environment. For simplicity, you'll use your existing Windows Administrator account for the MCMS initial administrator.
  • MCMS System Account is used to access resources and to act as an agent on behalf of all MCMS users; it must have permissions on all the resources that it needs to access.

Using the Computer Management administrative tool, add a new local user for the MCMS System Account.

Figure 6.

Creating the MCMS Database

With the System Account defined, you now need to add a new SQL 2000 database to act as the repository for all of the MCMS information.

Note   The SQL Server database contains table definitions and stored procedures that are used by MCMS to persist most of its data. Information about the structure of a site, its content, and its resources reside here.
  1. From SQL Server's Enterprise Manager, expand the local computer tree, right-click the Databases folder, and select New Database. Give the database a name (such as MCMS), and then click OK.

    Figure 7.

  2. Next, expand the Security folder, right-click Logins, and choose New Login. Browse the local computer and select the account you previously created for the MCMS System Account.
  3. From the Database drop-down box, select your new MCMS database.

    Figure 8.

  4. Click the Database Access tab, select the boxes next to db_dlladmin, db_datareader, and db_datawriter, and then click OK to save the settings.

Creating the MCMS Web Sites

Two Web sites are required for MCMS. One acts as the public site that users and authors access. The other is used as the entry point for the MCMS Server Configuration Application (SCA). This guide will step through the site creation now.

Note   Before you add the new sites, it's recommended that you change the TCP Port number of the Default Web Site that IIS installs. This is necessary to avoid a conflict with your public MCMS site. (Alternatively, you can either add a second IP address to your server and bind each virtual site to a different IP address, or simply disable the Default Site. Please consult the IIS documentation for details on how to do this).

Let's create the public site first.

  1. Start Internet Information Services Manager, right-click on your server, and choose New, and then Web Site.
  2. Using the Web Site Creation Wizard, enter a description for the site. At the IP Address and Port Settings page, leave the default.
  3. Specify the folder Inetpub\wwwroot for the Web site home directory. Since this will be the public MCMS site, leave Allow anonymous access selected.
  4. On the Web Site Access Permissions dialog, leave the settings at the defaults of Read and Run scripts.

To create the SCA entry point, repeat the steps above with two minor changes:

  • In Step 2, change the TCP Port to a port that won't conflict with any other ports (for example, 8080).
  • In Step 3, deselect Allow anonymous access.

Installing Core MCMS Components

With the prior steps completed, you're now ready to install MCMS 2002, the WoodgroveNet sample site, and the Authoring Connector.

  1. Insert the MCMS CD into your CD-ROM drive. The main setup menu will appear. Please take the time to look over the Release Notes and MCMS 2002 Help (click Installing MCMS 2002 to see the Help) which contain valuable information that will make it easier to get up to speed with the product.
  2. Click Install Components, and then Install MCMS Components. At the Welcome page, click Next. Accept the license agreement terms and click Next once more.
  3. On the Custom Setup page, adjust the settings to install both Site Manager and Developer Tools (under the CMS Server option). Do not select Site Stager, as we won't be covering it in this guide.

    Figure 9.

  4. Follow through the rest of the setup menus, accepting the defaults. Be sure to leave the Launch Database Configuration Application check box selected before you click the Install button.
  5. Once the MCMS installation completes, click the Finish button to start the Database Configuration Application (DCA).

Using the Database Configuration Application

The Database Configuration Application (DCA) utility is used to select and populate a SQL Server database with tables and data required by an MCMS 2002 Content Server. During a new installation of MCMS 2002, the DCA is also used to select the virtual Web sites, and to designate the MCMS system and initial administrator accounts.

  1. After clicking Next on the first page, you're asked to select the ASP Compatibility mode for this installation. Your choice here won't affect these exercises: However, because this setting cannot be changed after installation, it's important in MCMS production environments. Click Next.
  2. Now you must assign a virtual Web site for use as the public MCMS location. You should see one or two default entries created by IIS, and the two you created in the previous section. Highlight your public MCMS site, make sure Read/Write Site is selected, and click Next.
  3. The next page asks you to pick the SCA Web entry point. Highlight the site you defined for this role and click Next .

    Figure 10.

  4. If you receive a warning referring to one or more properties not recommended for an SCA virtual site, click Yes.
  5. When entering the username and password for the MCMS System Account, remember to use the local server name for the domain name.

    Figure 11.

  6. When asked to stop the IIS service, click Yes.
  7. You've reached the point where a database must be chosen, so press the Select Database button. When presented with the SQL Server Login, set the Server name to (local), click the Options button, and then select your MCMS database. Finally, click OK.

    Figure 12.

  8. Once you're returned to the Select Database page, click Next. When told the database is empty, click Yes to install the MCMS schema.
  9. Click Next once more on the Database Population page.
  10. Enter your system administrator information for the Initial MCMS Administrator, and remember to use the local server name for the domain name.
  11. Leave the default setting on the Site Stager Access screen and click Next.
  12. When asked if you want to start the SQL Server Agent, click Yes.
  13. You're at the final DCA setup screen now. We're going to cover SCA in the management section that follows so clear the Launch the SCA Now option and click the Finish button.

Installing the WoodgroveNet Sample Site

Included with MCMS 2002 is a sample Web site called WoodgroveNet. When you perform the procedures in this guide to explore MCMS functionality, you will work on the WoodgroveNet sample site. WoodgroveNet is a unilingual, external ASP.NET-based site.

  1. From the main MCMS setup screen, click Install Components, and then click Install Sample Site. (Note: If the option is grayed out, exit MCMS setup and restart.) At the Wizard Welcome page, click Next.
  2. The installer will do a quick check to assure all prerequisites are installed. Click Next when it finishes.
  3. This is the first time the data is being imported, so leave the box selected on the Import Sample Data page and click Next.
  4. Now enter the name and password for your MCMS administrator account. Remember to use the local server name for the domain name. Click Next.

    Figure 13.

  5. At the Ready to Install page, click the Install button. Once the data is successfully imported you'll be at the Completion page, so click Finish.

Installing the Authoring Connector

Authoring Connector is a wizard-based application that enables you to produce documents in Microsoft Word 2002 and submit them directly to the MCMS Web site without leaving Word.

Note   To use Authoring Connector with the WoodgroveNet sample site, you must install the WoodgroveNet sample site before you install Authoring Connector.
  1. From the main MCMS setup screen, click Install Components, and then click Install Authoring Connector. At the Wizard Welcome screen, click Next.
  2. Leave the application setting at all users and click Next.
  3. Accept the default destination folder and click Next.
  4. Now you're asked to provide the name of the MCMS 2002 server that Authoring Connector will access. In this development scenario (in which all applications are installed on a single system), you can leave localhost as the name, and click Next.
  5. On the Settings Review page, click the Install button.
  6. When the installation is done, click Finish. Your MCMS 2002 installation is complete.

Administering MCMS

This section introduces you to the following procedures and tools for administering MCMS:

  • Configuring servers: the Server Configuration Application
  • Managing an MCMS Web site: Site Manager

Configuring Servers: the Server Configuration Application

You use MCMS Server Configuration Application (SCA) to configure individual or multiple servers. After a new installation, you can—globally or just on one server—make changes to the MCMS 2002 system account, add or remove supported Windows NT domains, and add or remove Microsoft Active Directory® groups as the network topology changes or grows.

To support multiple servers, MCMS separates configuration properties into the following properties:

  • Entry-point properties affect one entry point of a server. You can put the SCA on a secure port.
  • Local properties affect all of the entry points to the local server.
  • Global properties affect all servers that point to a particular database.
  • Global defaults stored in a database affect all servers that point to that database, unless they are individually overridden with a local setting.

Perform the following steps to explore the Server Configuration Application.

  1. Start the SCA from the MCMS programs menu. By clicking the Configure button on the General tab you can change the URL format (Hierarchical or Unique ID), and map channel names to host header names.
    Note   You can specify how MCMS identifies (or references) your pages using one of the following URL formats:
    • Hierarchical – Duplicates the channel structure in Site Manager to identify pages.
    • Unique ID-based – Assigns random numbers and letters to identify pages.

      Figure 14.

  2. Click the Cache tab and you can flush the local cache, and change its size or location. You can also set global cache properties.
  3. Click the Web tab and you can display a list of all Web sites on your local computer, their IP address and TCP port settings, and their MCMS site type (Read/Write or Read-Only). Click the Configure button to change these attributes.
  4. To enable guest access to the WoodgroveNet Web site (which you will use later on) you need to make one change here and another in Site Manager. Click the Security tab, and then click the Configure button.
  5. Change Allow Guests On Site to Yes, and then click the Browse button.

    Figure 15.

  6. At the warning screen, click OK.
  7. Next, using the Windows NT Domain drop-down box, select your local server's name. Once the user names are displayed, click on the IIS user account (normally IUSER_<server name>), and then click OK twice to save your changes.

    Figure 16.

    Figure 17.

  8. Finally, to exit the SCA, click the Close Application button, and then click Yes.

Now you move on to the Site Manager to enable guest access to the WoodgroveNet Web site.

Managing an MCMS Web Site: the Site Manager

In this section, you will explore the features of the Site Manager tool. You will enable guest access to the WoodgroveNet sample site.

When you manage a site, you use Site Manager to:

  • Create and manage the site's channels and galleries.
  • Manage user roles and rights groups.
  • Deploy the site.

Managing User Roles & Rights Groups

MCMS supports a total of five levels of workflow control based on user roles. The five roles are shown in the following diagram.

Figure 18.

In this exercise, you will add users to three of these roles: subscriber, author, and editor.

First, you will use Site Manager to permit unrestricted browsing access to the WoodgroveNet Web site. You will make the IIS anonymous user account a part of the site's CMS Guest rights group.

  1. From the Start menu, click Programs, click Content Management Server and then click Site Manager. Leave Log on as Administrator selected and click Start.
  2. Click the User Roles icon. Next, in the middle (User Roles) pane, click the Subscribers group. Now right-click the CMS Guest subscribers rights group and choose Properties.

    Figure 19.

  3. On the CMS Guest Properties dialog, click the Group Members tab, and then click the Modify button to bring up the Modify Members dialog box.
  4. Under NT Domains, click your server name. Next, use the drop-down box to set the display to show all users and groups for selection.

    Figure 20.

  5. When the list of user and group names on your server appears, double-click the IIS anonymous user account (IUSER_<server name>). Lastly, click OK.

    Figure 21.

  6. Before closing the CMS Guest Properties dialog box, click the Group Rights tab and expand the branches under the Channels, Resources, and Templates containers. Note the green arrows, which indicate those elements to which the group is granted rights. Click OK.
  7. Back at the Site Manager console, under User Roles, click Authors. Using the steps above, add one of the user accounts that you created during setup, to the Small Business rights group.
  8. Repeat Step 7 for a second user, but this time add them to the Small Business rights group of the Editors User Role.

You have successfully added the following three users to Site Manager:

  • Anonymous IIS account: member of Subscribers\CMS Guest
  • User 1: member of Authors\Small Business
  • User 2: member of Editors\Small Business

Deploying Sites

MCMS 2002 provides new capabilities and a new approach for deploying your content-based sites. Site Deployment APIs support new capabilities that optimize import/export operations done programmatically or through Site Manager. In addition, the import/export of template objects have been modified.

Figure 22.

Although template objects are included in export and import operations, the template files themselves are now deployed separately to the MCMS 2002 database. This, and other changes, has led to a new format for the site deployment files. These files are now known as site deployment objects, and are identified by the .sdo file extension.

In this exercise you explore the process of exporting the site deployment package and you view a sample report.

  1. From the File menu, choose Package and then Export. You can export entire containers, sub-containers, or individual items. Go ahead and select several items or containers; click the Include button to add them to the list.

    Figure 23.

  2. Next, click the Rights Options tab, and select both the Export Rights Groups and Export Users boxes. Lastly, choose Export Preview from the Report menu. (You won't actually run the export operation, but you can view the item definitions that would be stored in the .sdo file.)
    Note   A rights group can be exported with or without its members. If the destination server and the source server use a common domain, you can export the rights group and its members to the object file being exported. If the domains are different then you should not export the members, since the user information isn't relevant in the destination environment.

    Figure 24.

  3. Scrolling through the report, you see a breakdown by container of the export package contents.

    Figure 25.

  4. The MCMS 2002 package import function provides site administrators full control over how new container objects and user objects are merged into their existing site's structure.

    Figure 26.

Authoring Content

This section introduces you to the WoodgroveNet sample site, and guides you through steps to author content and then publish it to the site. It introduces you to the following authoring tools:

  • Web Author. A tool that enables authors, editors, and moderators to create and approve pages from a Web browser.
  • Authoring Connector. A Microsoft Content Management Server (MCMS) 2002 feature that enables users to author, edit, and submit content from a Microsoft Word 2002 document to an MCMS Web site.

Using these tools, you will perform the following procedures to update content on the WoodgroveNet sample site:

  • Edit pages and submit content
  • View revisions and approve content for publication
  • Use Microsoft Word 2002 to update content

WoodgroveNet Site Topology

Before you start editing the WoodgroveNet sample site, take a few minutes to review the site topology. The following block-diagram shows how the WoodgroveNet channel hierarchies are structured.

Figure 27.

The WoodgroveNet site contains three top-level channels, each containing a number of sub-channels:

  • About Us. The About Us channel has two sub-channels that contain information about careers in the company and company press releases.
  • Partner. The Partner channel contains information for, and services available to, the bank's partners.
  • Small Business. The Small Business channel has two sub-channels containing case studies and information about the bank's services.

Template and resource galleries have been created to mirror the channels of the site, making it easier for users to find templates and resources that relate to the area of the site they are creating content for.

Web Author

You will use the Web Author to edit the WoodgroveNet sample site.

The Web Author controls the content postings and the console actions for each page in your MCMS 2002 site. The Web Authoring framework controls which postings your users can view, and also enables your authors to create new pages, or edit existing pages. Furthermore, it enables editors and moderators to approve, publish, or decline content submitted by authors.

The Web Author has two modes, one for customers visiting your site, and one for authors updating your site.

  • Presentation Mode. Typical users browse your site in presentation mode. The Web Author only provides links to published content in presentation mode, and will display only the approved published content.
  • Authoring Mode. Authors, editors, and moderators typically work in authoring mode. This mode enables authors to create and submit new content, edit previously published content, or delete existing postings. This mode also enables editors and moderators to approve or decline postings submitted by authors.

The following figure shows a typical authoring console. Note how both action controls and status controls are contained within the console. Although they are hidden from the user, the Site Mode containers are also embedded in the console—they control which action controls and status controls are displayed in each specific mode.

Figure 28.

Before editing the WoodgroveNet sample site, perform the following procedures to explore the site and the Web Author.

  1. Start Internet Explorer and enter the URL http://localhost/woodgrovenet. Because we enabled anonymous access earlier, no password is required to browse the site.
  2. Let's login to the site now. Click the word Login on the upper right side of the page. When prompted for credentials, enter account information for the user that you added to the Authors group in the Site Manager exercise. For the Domain field, enter your server's name. Click the Continue button to login.
  3. Navigate to the Case Studies page under Small Business, and click the link to Blue Yonder Airlines. Finally, click Switch To Edit Site.
  4. Note the options available to you in the Web Author console. This is because you are logged in as a member of the authors group for this page. Go ahead and click the Careers link below About Us. Note how the console changes to show the more restricted rights you have to that channel.

Editing Pages and Submitting Content

  1. Return to the Blue Yonder Airlines page and then click Edit in the Web Author console. In the upper placeholder, add the word "The" in front of the word "Sky's." The small T in the upper right corner indicates that this is a plain-text only placeholder.

    Figure 29.

  2. Next you add a hyperlink. Highlight the word Alaska in the Customer Description placeholder, and then click the Edit Hyperlink button on the Toolbar. Enter the URL for the hyperlink address. The ToolTip is used like an ALT tag for the link, while the Name defines an anchor point. Be sure to change the Open Link In option to New Unnamed Window, and then click OK.

    Figure 30.

  3. With your changes complete, click Save and Exit. The page is saved, and relevant information about the page status and the version being displayed is shown at the top of the Web Author console.
  4. In real-world environments it is likely that Web authors will work on multiple parts of a site at the same time. Clicking on the Production Manager link in the Web Author console lets authors track the pages they own, view their current status, and preview them.

    Figure 31.

  5. Return to the Blue Yonder Airlines page and click the Submit link. Note how the Page Status changed to WaitingforEditorApproval. Click Logoff to sign out of the site as an author.

    Figure 32.

Viewing Revisions and Approving Content

Even though an author has submitted page revisions, the changes do not "go live" until someone with editing privileges on the channel approves it. You review that process next.

  1. Click Login again, enter the credentials for the account you added to the Editors User Role, and then click Continue.
  2. MCMS 2002 makes it easy for editors to view page modifications before they approve the changes. You can do this by clicking the Revision History link. Select the boxes under the Latest Unapproved and Approved Revisions, and then click Compare.

    Figure 33.

  3. The first page uses color-coding to identify changed elements.

    Figure 34.

  4. Clicking the Source tab reveals the page's underlying HTML, with the changes once again color-coded for clarity and easy identification.

    Figure 35.

  5. Close the Revision History windows.
  6. If, as the editor, you are satisfied with the page, you just click the Approve link. In a production site, you are likely to need to approve multiple pages. This is when you would want to click the Approval Assistant link. From the sortable list, editors can check those items they wish to sign off on, and then click the Approve button to publish the pages as a group.

    Figure 36.

Word 2002 and Authoring Connector

Using a familiar tool—Microsoft Word 2002—you can create and publish content without the need to know or learn about MCMS or Web page design. Using the MCMS Authoring Connector, you can easily publish Word documents to your Web site.

When you submit a Word document to MCMS, Authoring Connector converts the body of the document to HTML, making it ready for publication on the Web site.

Figure 37.

An Authoring Connector template can contain a document content placeholder, an attachment placeholder, or both. If the template contains both placeholder types, Authoring Connector submits the document to both placeholders. A link to the Web page is stored in the submitted document. This link allows an author to update the Web page by editing the original document and resubmitting it.

Authoring Connector facilitates task-oriented publishing. Task-oriented publishing makes it easier for users with no knowledge of Web publishing to publish content. Users only need to pick a predefined task to be able to publish content to the Web site. End users don't need to worry about, or even be aware of, which channel and template their submission is targeted toward, because the selected task already defines the channel and template to utilize. These tasks are defined by the developer in an XML file.

Using Word 2002 and the Authoring Connector

Perform the following steps to publish content using Word 2002 and the Authoring Connector.

  1. Start Word 2002 and create a simple document. Add a graphic to the page, and a few paragraphs of text. Save the document.
  2. Now open the File menu and select Send to MCMS, and then Create New Page. The Authoring Connector Wizard opens.
  3. On the Welcome page, click Next. Now you'll see the publishing task list. (There is only one defined in the sample site.) Click on it and then click Next.
  4. Fill in the basic page information and then click Next.
  5. Leave the default settings on the Publishing Dates and Times page and click Next.

    This brings you to the Page Submission dialog. As you can see, the Channel, Template, and document-related settings are all preset for the user. Don't click the Preview Page button because you're only one step away from being done. Click Next.

  6. On the final Wizard page, select the box next to Launch MCMS Web Author and then click Finish.
  7. When prompted to login to the WoodgroveNet site, enter the credentials for the account with editor rights. Once the newly created page is displayed, you can just click the Approve link in the Web Author and the page will go "live".

For detailed information about how MCMS templates respond to varying content types submitted through the Authoring Connector, see the white paper, Customizing the Authoring Connector, at

A Developer's Perspective

There are two basic building blocks for an MCMS developer: templates and placeholders.

This section introduces you to these building blocks and shows you how to add them to the WoodgroveNet sample site.

This section contains:

  • Templates
  • Placeholders
  • MCMS Content Repository
  • Adding a placeholder definition
  • Adding a new placeholder control


A template is the framework that you use to control the way that page content is presented. You can design a template to ensure that a consistent look is achieved throughout the site, or several templates can be used to apply different looks to different areas of the site. Every MCMS page has a template assigned to it.

Templates are composed of template files and template objects. A template file is an ASPX, ASP, or ASCX source file that defines an overall appearance for a set of pages in an MCMS Web site and contains the executable code associated with a template object in MCMS. Certain areas of the template file are predefined for all pages based on the template file; others areas, known as placeholder definitions, are reserved for custom content in each page based on the template file.

Template files are stored in the file system making it easy to use familiar source control systems, such as Microsoft Visual SourceSafe®, to manage revisions to template files. Template objects are stored in the Content Repository and reference the template file to be used to render content, the placeholder definitions to be used to contain content, and the custom property collection.


Placeholders are found within templates and contain the page content that can be edited by users. Placeholders keep the page content separate from the page design. The type of content and formatting options in a placeholder are set by the template designer.

In MCMS 2002, placeholders are implemented as .NET server controls, and are referred to as placeholder controls. Because these controls bring their code with them, when they are dragged into an ASPX template file, they become part of the page.

Placeholders are governed by the placeholder definitions in the corresponding template. Placeholders have a number of properties that can be modified using the Visual Studio .NET Properties window. These properties can be set differently for a given placeholder in each template file that the placeholder is associated with because each template file has its own copy of the placeholder control.

The MCMS 2002 placeholder architecture is open and extensible, so you can build your own controls to suit your particular business requirements. Placeholder controls are simply ASP.NET server controls that interact with MCMS 2002. Placeholders enable authors to submit content to the site, and users to browse that content.

Placeholders consist of the following three parts:

  • Placeholder Definitions. Placeholder definitions are defined in MCMS 2002 templates. They form part of the overall page definition by specifying the content to be saved or retrieved and rendered to the MCMS 2002 Content Repository.
  • Placeholder Objects. Placeholder objects actually perform the saving and retrieval of content to and from the MCMS 2002 Content Repository. The Publishing API exposes placeholder objects so you can directly manipulate the saving and retrieval of content.
  • Placeholder Controls. Placeholder controls interact with placeholder objects. In presentation mode, they render the content on the Web page, and in authoring mode they allow authors, editors, and moderators to submit new content or edit existing postings.

MCMS Content Repository

The MCMS 2002 Content Repository stores the Web page definitions, with their placeholder definitions included. It also stores the content that has been submitted by authors. The placeholder objects manage this content.

Figure 38.

The actual template files are stored by the operating system, and include placeholder controls that bind to the placeholder objects for rendering content and allowing authoring actions on that content.

Adding a Placeholder Definition

In this section, you add a placeholder definition and placeholder control to the WoodgroveNet solution file, and observe the effects. This exercise assumes that you are familiar with Visual Studio .NET.

Note   MCMS 2002 Help contains a set of tutorials to expand your understanding of the processes and procedures required for successful site deployment and management.
  1. From the Visual Studio .NET File menu, choose Open Solution. Next, locate and open the WoodgroveNet folder. You will find it in the path: <system_drive>:\ Program Files\Microsoft Content Management Server\Sample Data.
  2. Double-click the solution file WoodgroveNet.sln.
  3. Now let's take advantage of the MCMS integration with Visual Studio .NET to quickly locate the template we want to modify. From the View menu, choose Other Windows and then MCMS Template Explorer.

    Figure 39.

  4. Your Visual Studio .NET workspace should look like the one below. Expand the Small Business Net branch, and then double-click Case Studies ASPX.

    Figure 40.

    In previous releases of MCMS, templates were published to the MCMS Web site. With MCMS 2002, templates are no longer published; instead they are checked in and out of a template gallery. Thus, there is only one master copy of a template.

    You must check out a template gallery item before you can modify the definitions for the template. While you have a template gallery item checked out, you will see the Web site using the template that you are modifying, but a visitor will view the site using the last checked in version of the template. After a template is checked back in, the changes are immediately reflected on the site.

  5. As explained above, you need to check the template out of the system before beginning to work on it in design view. You do this by right-clicking the Case Studies ASPX template and then choosing Check Out. A red check mark will appear on the icon.
  6. In the MCMS Template Explorer, right-click the Case Studies ASPX icon and choose Properties.
  7. Now click where it says (Collection) to the right of PlaceholderDefinitions and then click the ellipsis (...).

    Figure 41.

  8. Click the little arrow to the right of the Add button and choose HtmlPlaceholderDefinition.

    Figure 42.

  9. Using the drop-down box, set the HTML Formatting option to FullFormatting. Go ahead and change the Name and Description fields to something meaningful too. Leave the other settings at their defaults and click OK.

    Figure 43.

Adding a New Placeholder Control

  1. From the View menu, choose Toolbox and then click the Content Management Server tab. Drag and drop a new HtmlPlaceholderControl from the Toolbox to right above Details of Solution.

    Figure 44.

  2. Right-click your new placeholder control and choose Properties. Use the drop-down box next to PlaceholderToBind and pick the name you assigned to the placeholder definition in step 9 of the previous procedure. Leave the rest of the settings alone and close the Properties box.
  3. Right-click Case Studies ASPX in the MCMS Template Explorer and choose Check In.
  4. Your last step will be to rebuild the site. Click Build on the Toolbar and choose Rebuild Solution. When prompted to save the changes, click Yes.
  5. After selecting the build output window to be sure all went well, close Visual Studio .NET.
  6. Open the WoodgroveNet Web site in your browser and login under your authoring account. Navigate to the Fabrikam or Blue Yonder case studies and then click Edit. Scroll down the page and you'll find the newly added placeholder control ready to use.

    Figure 45.

  7. When you've finished adjusting the content in your placeholder, click the Preview link in Web Author to view the final product.

    Figure 46.

For More Information

  • The Microsoft Content Management Server (MCMS) 2002 Web site at features the latest news and information about MCMS, including product information, case studies, white papers, information about related technologies, and more.
  • A trial version of MCMS 2002 is available for download at
  • White papers covering topics that are relevant to developers, such as creating MCMS solutions, can be found at the MSDN® Web site at
  • White papers covering topics that are relevant to IT professionals, such as architecting, sizing, and managing an MCMS solution, can be found at the TechNet site at
  • The MCMS Community site is a great place to participate in the newsgroups, view WebCasts, and participate in live chats. Visit it at
  • To find MCMS training in your area, see the MCMS training site at
  • The MCMS Support Web site provides developers and customers with technical support. It is located at
© 2016 Microsoft