• Article

Lab Scenario 1: Built-in Authentication

Microsoft Office Communications Server 2007 and Microsoft Office Communications Server 2007 R2 will reach end of support on January 9, 2018. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.

This topic provides an introduction to Lab Scenario 1 in the Introduction to Microsoft Office Communicator Web Access (2007 Release) Guide to Lab Deployment.

Overview

In Lab Scenario 1, you will deploy Communicator Web Access (2007 release) with built-in authentication in a lab setting that employs a single-forest, single-domain topology. The resulting environment supports testing of the new Unified Communications JavaScript Libraries, the new Unified Communications AJAX API, and automatic sign-in scenarios other than SSO-enabled ISA Server 2006 scenarios. The environment simulates a corporate Windows network with users for which Microsoft Office Communicator 2007 is not an option. These users might include:

  • Macintosh users

  • UNIX users

  • Users of supported Windows platforms who are not authorized to install the Microsoft Office Communicator 2007 client

Communicator Web Access provides users with an installation-free solution for accessing the instant messaging, presence features, and other features of Microsoft Office Communications Server 2007 that you deploy and enable.

In Lab Scenario 1, you will set up a development lab environment for a single-forest, single-domain topology in which Communicator Web Access (2007 release) is deployed. In this simulated corporate user environment, you can perform the following tasks:

  • Set up Communicator Web Access

  • Sign in to Communicator Web Access

  • Search for users to add to the Contact List

  • Add contacts to, and delete them from, the Contact List

  • Send an instant message by using Communicator Web Access

  • Change presence status

  • Set presence status to Do Not Disturb

In this scenario, the fictitious Contoso Corporation network includes the following:

  • A domain controller that runs Microsoft Active Directory® Domain Services, DNS Server, and a private certification authority

  • A server that runs Microsoft Office Communications Server 2007, Standard Edition

    Important

    Running Office Communications Server 2007 on a domain controller is not supported.

  • A Communicator Web Access (2007 release) server

  • One hub

  • Two clients

    Note

    Installing Communicator Web Access (2007 release) and any server role of Office Communications Server 2007 on the same physical server is not supported.

Figure 1. Topology for Lab Scenario 1

42eafe7c-24a8-4623-8612-b6d4087a7fc1

Tasks in this Lab Scenario

  1. Set up contosodc.contoso.com. This server functions as the Active Directory domain controller, the DNS Server, and the Microsoft Windows Server® 2003 SP1 enterprise root certification authority (CA).

  2. Set up ocs2k7.contoso.com. This server runs Microsoft Office Communications Server 2007, Standard Edition.

    Note

    Running Office Communications Server 2007 on a domain controller is not supported.

  3. Set up cwaserver.contoso.com. This server functions as the Communicator Web Access server.

  4. Prepare the clients. Each client computer connects to Communicator Web Access through a browser.

  5. Perform Lab scenario 1 exercises. The lab exercises demonstrate end-user tasks such as adding contacts, sending instant messages, and changing presence.