Cwa Isvquickstart
This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA
Overview
Download & View Cwa Isvquickstart as PDF for free.
More details
- Words: 6,778
- Pages: 32
Microsoft Office Communicator Web Access (2007 release, Public Beta) Guide to Lab Deployment Published: March 2007
This document supports a preliminary release of a software product that may be changed substantially prior to final commercial release. This document is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in this document. Information in this document, including URL and other Internet Web site references, is subject to change without notice. The entire risk of the use or the results from the use of this document remains with the user. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. 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.
© 2007 Microsoft Corporation. All rights reserved.
Microsoft, MS-DOS, Windows, Windows Mobile, Windows Server, Windows Vista, Active Directory, Internet Explorer, Visual Studio, and Win32 are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
All other trademarks are property of their respective owners.
Contents
Contents............................................................. ..............................3 Introduction..................................................................................... ..1 Overview of Lab Scenario...................................................... .......1 Supported Browsers.................................................. ...................1 Lab Scenario 1: Built-in Authentication Mode...............................2 Lab 1 System Requirements............................................... .....4 Setting up contosodc.contoso.com...................................... ....7 Setting up webserver3.contoso.com.......................................9 Configuring the Client Computers.........................................17 Performing Lab 1 Exercises...................................................20
Introduction Microsoft® Office Communicator Web Access (2007 release) provides browser-based client access to Microsoft Office Communications Server 2007. Office Communications Server 2007 and Communicator Web Access (2007 release) build upon the foundation established by Live Communications Server 2005 with SP1 and Communicator Web Access (2005 release). This document describes the steps necessary to deploy Communicator Web Access (2007 release) in a lab environment with a single-forest, single-domain topology.
Overview of Lab Scenario This Quick Start contains the following lab scenario: •
Lab Scenario 1: Built-in authentication mode Lab scenario 1 demonstrates the requirements and installation steps for deploying Communicator Web Access in Built-in authentication mode. You use built-in authentication mode for testing Communicator Web Access (2007 release) Controls and the new Microsoft Office Communicator Web Access (2007 release) AJAX Service API. Built-in authentication does not support single sign-on (SSO). For information about SSO, see the Communicator Web Access (2007 release) Authentication Guide. For information about the Communicator Web Access (2007 release) AJAX Service API and the Communicator Web Access (2007 release) Controls, see the Communicator Web Access (2007 release) Software Development Kit (SDK). Note: The deployment scenario described in this document is intended for test-lab purposes only. It might not be suitable for a production environment.
Supported Browsers Supported browsers for Communicator Web Access (2007 release) are: Table 1: Supported Browsers Operating System
Internet Browser
Authentication Mechanism
Microsoft Windows® 2000 SP4
Microsoft Internet Explorer® 6 SP1
Forms-based NTLM Custom
Windows XP SP2
Internet Explorer 6 SP2 Internet Explorer 7 Firefox 2.0.latest
Forms-based NTLM Kerberos Custom
2 Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment
Windows Vista™
Internet Explorer 7 Firefox 2.0.latest
Forms-based NTLM Kerberos Custom
Mac OS X 10.3.9
Safari 1.3.2
Forms-based Kerberos Custom
Firefox 2.0.latest
Forms-based NTLM Kerberos Custom
Safari 2.0.latest
Forms-based Kerberos Custom
Firefox 2.0.latest
Forms-based NTLM Kerberos Custom
Mac OS X 10.4.8
Lab Scenario 1: Built-in Authentication Mode In Lab Scenario 1, you will deploy Communicator Web Access (2007 release) in built-in authentication mode in a lab setting with a single-forest, single-domain topology. The resulting environment supports testing of the new Communicator Web Access UI controls, the new Communicator Web Access AJAX Service API, and for testing automatic logon 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 Microsoft Windows® operating systems prior to Windows 2000 SP4, which are not supported by Office Communicator 2007
•
Locked-down, insufficiently privileged users of supported Windows platforms
Communicator Web Access provides users with an installation-free solution for accessing instant messaging and presence features and for accessing features implemented in your solutions. In Lab Scenario 1, you will set up a development lab environment for a single-forest, singledomain 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.
Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment 3
•
Sign in to Communicator Web Access.
•
Search for users to add to the Contacts list.
•
Add contacts to, and delete them from, the Contacts list.
•
Send an instant message by using Communicator Web Access.
•
Change presence status.
•
Set presence status to Do Not Disturb.
•
Create and test a sample enhanced presence solution containing code that accesses the new Communicator Web Access AJAX Service API and Communicator Web Access Controls.
In this scenario, the Contoso Corporation network includes the following: •
A domain controller that runs Microsoft Active Directory® Domain Services, DNS Server, a private certification authority, and Microsoft Office Communications Server 2007, Standard Edition
Caution Running Office Communications Server 2007 on a Domain Controller is not recommended or supported in a production environment.
•
A Communicator Web Access (2007 release) server
•
One hub
•
Two clients
Figure 1: Lab 1
In this lab scenario, you will perform the following tasks:
4 Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment
1. Set up contosodc.contoso.com. This server will function as the Active Directory domain controller, the DNS Server, the Microsoft Windows Server® 2003 SP1 enterprise root certification authority (CA), and the Office Communications Server 2007, Standard Edition server.
Caution Running Office Communications Server 2007 on a Domain Controller is not recommended or supported for a production environment
2. Set up webserver3.contoso.com. This server will function as the Communicator Web Access server. 3. Prepare the clients. Each client computer will connect to Communicator Web Access client through a browser. 4. Perform Lab 1 exercises. The lab exercises will demonstrate end user tasks such as adding contacts, sending instant messages, and changing presence. ISV application developer tasks are also demonstrated.
Lab 1 System Requirements You will need two “bare-metal” servers, two client computers, and one hub, as shown previously in Figure 1.
Server: contosodc.contoso.com Table 2 shows the system requirements for contosodc.contoso.com. For this lab, the root CA issues certificates required for secure communications in Office Communications Server 2007, Standard Edition and Communicator Web Access. Table 2: contosodc.contoso.com Minimum Requirements Component
Requirement
contosodc.contoso.com - Domain Controller: IP Address = 10.10.10.1/24 Software Operating System
Windows Server 2003 SP1 (Standard Edition, Enterprise Edition or Datacenter Edition)
Directory Service
Active Directory
Name Resolution
DNS Server
PKI Infrastructure
Windows Server 2003 SP1 Enterprise Root CA
Office Communications Server 2007
Office Communications Server 2007,Standard Edition
Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment 5
Certificate services Web enrollment and Office Communications Server 2007 Web Components support
IIS 6.0
Other software required for Office Communications Server 2007
.NET Framework Version 2.0 or greater
QFEs
KB 915066 http://support.microsoft.com/kb/915066
ASP.NET 2.0
KB913297 http://support.microsoft.com/kb/913297 KB 917283 http://support.microsoft.com/kb/917283 KB 922770 http://support.microsoft.com/kb/922770 Group memberships
DomainAdmins Administrators
Hardware Processor
Dual 3.2 GHz CPU
Networking
1 Gigabit Ethernet network adapter
Memory
4 GB RAM (Recommended)
Disk Space
2 × 36 GB NTFS-formatted Hard Drives
For details about installing Office Communications Server, Standard Edition, see the Office Communications Server 2007, Standard Edition Deployment Guide available on the Office Communications Server 2007 installation media. You install IIS 6.0 by using the Windows Control Panel. For details, see the Windows Server documentation. To download Service Pack 1for Windows Server 2003, go to: http://www.microsoft.com/windowsserver2003/downloads/servicepacks/sp1/default.mspx. To download the .NET Framework, go to: http://www.microsoft.com/downloads/details.aspx?familyid=0856EACB-4362-4B0D-8EDDAAB15C5E04F5&displaylang=en
Server: webserver3.contoso.com Table 3 shows the system requirements for webserver3.contoso.com. On this server, you will install Communicator Web Access. Table 3: webserver3.contoso.com Minimum Requirements Component
Requirement
6 Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment
webserver3.contoso.com - Member Server contoso.com - IP Address = 10.10.10.35/24 Software Disk format
NTFS
Operating System
Windows Server 2003 SP1 (Standard Edition, Enterprise Edition or Datacenter Edition)
Other software required for Communicator Web Access
.NET Framework Version 2.0 or greater IIS 6.0 ASP.NET 2.0 Communicator Web Access
Hardware Processor
Dual 3.2 GHz CPU
Networking
1 Gigabit Ethernet network adapter
Memory
4 GB RAM (Recommended)
Disk Space
1 × 36 GB NTFS-formatted Hard Drives
Group memberships To install Communicator Web Access
User must be a member of local Administrators group.
To activate Communicator Web Access
User must be a member of the DomainAdmins group.
To create a virtual server
User must be a member of local Administrators group.
Client computers Each client computer runs the Microsoft Windows® XP or Windows 2000 Server with SP4 operating system with the Internet Explorer® 6.0 SP1 Internet browser. You can optionally add Office Communicator 2007 to one or both of the client computers. Table 4: Client 1 and Client 2 Minimum Requirements Component
Requirement
Client 1 - Member client; name=Client1; IP Address=10.10.10.4/24 Client 2 - Member client; name=Client2; IP Address= 10.10.10.5/24 Software Operating System
Windows XP with the latest service pack1
Browser/Client
Internet Explorer 6.01
Other software
Office Communicator 2007
Hardware
Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment 7
Processor
300 MHz
Networking
1 network adapter
Memory
128 MB RAM
Disk space
20 GB
1
Other operating systems or browsers may be used. For a list of supported operating systems and browsers, see the Microsoft Communicator Web Access (2007 release) Planning and Deployment Guide.
Setting up contosodc.contoso.com Preparing contosodc.contoso.com consists of the following steps: 1. Configure a static IP Address. 2. Prepare Active Directory using dcpromo and configure DNS. 3. Configure server as a Windows Server 2003 SP1 Enterprise Root CA. 4. Install and configure Office Communications Server 2007, Standard Edition.
Caution Running Office Communications Server 2007 on a Domain Controller is not recommended or supported for a production environment
5. Request and configure certificates for Office Communications Server 2007. The following sections explain these steps in detail.
Configure Static IP Address for contosodc Connect the Server to Hub 1, and then configure the server with a static IP address.
To configure a static IP address for contosodc 1. Click Start, point to Settings, and then click Network Connections. 2. Right-click the connection for which you want to configure a static IP address, and then click Properties. 3. Click Internet Protocol (TCP/IP), and then click Properties. 4. In the Internet Protocol (TCP/IP) Properties dialog box, click Use the following IP address. 5. In the IP address box, type 10.10.10.1. 6. In the Subnet mask box, type 255.255.255.0. 7. Click Use the following DNS server addresses. 8. In the Preferred DNS server box, type 10.10.10.1. 9. Click OK twice, and then close the Network Connections window.
8 Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment
Prepare Active Directory by using dcpromo and configure DNS Use Dcpromo to install Active Directory and promote contosodc.contoso.com to a domain controller, and then configure DNS. You will need your Windows Server 2003 installation media.
To prepare Active Directory using dcpromo and configure DNS 1. Click Start, and then click Run. In the Open box, type dcpromo, and then click OK. 2. On the Active Directory Installation Wizard Welcome page, click Next. 3. On the Operating System Compatibility page, click Next. 4. On the Domain Controller Type page, accept the default Domain controller for a new domain, and then click Next. 5. On the Create New Domain page, accept the default Domain in a new forest, and then click Next. 6. On the New Domain Name page, enter contoso.com in the text box, and then click Next. 7. On the NetBIOS Domain Name page, accept the default CONTOSO, and then click Next. 8. On the Database and Log Folders page, accept the default locations, and then click Next. 9. On the Shared System Volume page, accept the default location, and then click Next. 10. On the DNS Registration Diagnostics page, click the middle button, Install and configure the DNS server on this computer, and set this computer to use this DNS server as its preferred DNS server, and then click Next. 11. On the Permissions page, accept the default, Permissions compatible only with Windows 2000 or Windows Server 2003 operating systems, and then click Next. Office Communications Server 2007 requires native mode. 12. On the Directory Services Restore Mode Administration Password page, enter the same password in both text boxes, and then click Next. 13. On the Summary page, click Next. 14. If prompted, type the full path to the Windows Server 2003 installation folder or CD, and then click Continue. 15. Click Finish. 16. Ensure that the domain controller is in native mode.
Configure contosodc.contoso.com as a Windows Server 2003 SP1 Enterprise Root CA Install certificate services and configure the server as an Enterprise Root Certification Authority.
To install certificate services and configure the server as an Enterprise root CA 1. Click Start, point to Settings, click Control Panel, and then click Add or Remove Programs. 2. Click Add or Remove Windows Components. 3. In the Windows Components Wizard, click Certificate Services.
Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment 9
4. On the Microsoft Certificate Services page, click Yes, and then click Next. 5. On the CA Type page, click Enterprise root CA, and then click Next. 6. On the CA Identifying Information page, in the Common name for this CA box, type webserver3, and then click Next. 7. On the Certificate Database Settings page, click Next. 8. If prompted, type the full path to the Windows Server 2003 installation folder or CD, and then click Continue. 9. In the Microsoft Certificate Services message, click Yes to allow IIS to be temporarily stopped. 10. In the Microsoft Certificate Services message, click Yes to enable ASP and IIS. After you have installed Microsoft Certificate Services, prepare the CA for issuing certificates by duplicating the web server certificate template. During this procedure, you must grant Enroll and Auto enroll permissions for the following groups in all domains: AuthenticatedUsers, DomainAdmins, DomainComputers, and EnterpriseAdmins.
Request Certificates for Office Communications Server 2007, Standard Edition See the Office Communications Server 2007, Standard Edition Quick Start.
Caution The certificates for both Office Communications Server 2007 Standard Edition and Communicator Web Access must be issued from the same certification authority (CA) and must use a duplicated Web server template in which the Mark keys as exportable option has been enabled.
Install and Configure Office Communications Server 2007, Standard Edition See the Office Communications Server 2007, Standard Edition Quick Start.
Setting up webserver3.contoso.com For this lab, webserver3.contoso.com will function as the Communicator Web Access server. Preparing the webserver3 for this role consists of the following steps: 1. Configure a static IP address and name resolution. 2. Add webserver3 to the contoso.com domain. 3. Request the required certificates for Communicator Web Access. 4. Install and Configure Communicator Web Access. The following sections describe these steps in detail.
Configure Static IP Address Connect webserver3 to Hub1, and then configure webserver3 with a static IP address.
10 Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment
To configure webserver3 with a static IP address 1. Click Start, point to Settings, and click Network Connections. 2. Right-click the connection for which you want to configure a static IP address, and then click Properties. 3. In the Properties dialog box, click Internet Protocol (TCP/IP), and then click Properties. 4. In the Internet Protocol (TCP/IP) Properties dialog box, click Use the following IP address. 5. In the IP address box, type 10.10.10.35. 6. In the Subnet mask box, type 255.255.255.0. 7. Click Use the following DNS server addresses. 8. In the Preferred DNS server box, type 10.10.10.1. 9. Click OK twice, and then close the Network Connections window.
Add webserver3 to contoso domain. webserver3 must be a member server in the contoso.com domain.
To add webserver3 to the contoso domain 1. Right-click My Computer, and click Properties. 2. In the System Properties dialog box, click the Computer Name tab, and then click Change. 3. In the Computer Name Change dialog box, click Domain. In the Domain box, type contoso.com, and then click OK. 4. In the Authentication dialog box, type the user name and password of a member of the DomainAdmins group, and then click OK. 5. On the Computer Name Changes authentication page, type the Domain Admin credentials, and then click OK. 6. In the Confirmation/Welcome dialog box, click OK. 7. In the Restart notification dialog box, click OK. 8. In the Restart confirmation dialog box, click OK to restart the server.
Request a certificate Because you have set up contosodc.contoso.com as a Windows Server 2003 Enterprise CA and enabled autoenrollment, webserver3.contoso.com will receive the enterprise CA certificate chain when it is added to the domain. However, you will need to request a Web Server certificate with the FQDN (fully qualified domain name) webserver3.contoso.com. You will be asked to choose this certificate during the Communicator Web Access setup process.
Caution The certificates for Office Communications Server 2007, Standard Edition and Communicator Web Access must be issued from the same certification authority (CA) and must use a duplicated web server template in which the Mark keys as exportable option has been enabled. See the Office Communications Server 2007 Quick Start for the procedure detailing how to do this.
Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment 11
Note Lab Scenario 1 uses the Microsoft Certification Authority (CA) that you set up on contosodc.contoso.com, and the procedures in this document assume the use of an internal CA. You can use an External CA for this lab scenario, but you may need to modify the certificate procedures to comply with the requirements of the External CA, in addition to the certification requirements of Office Communications Server 2007 and Communicator Web Access. For details about configuring certificates, see Office Communications Server 2007 Configuring Certificates at http://office.microsoft.com/enus/FX011526591033.aspx.
The Communicator Web Access server requires a Mutual TLS (MTLS) certificate and an SSL IIS certificate. For this Lab, you can use the same certificate for both. The Communicator Web Access certificate requirements for this lab are as follows: •
Certificates must be issued from the same CA from which the Office Communications Server 2007, Standard Edition certificates were issued.
•
Certificates must use a duplicated web server template in which the Mark keys as exportable option has been enabled
For this lab, in which the FQDN of the server is webserver3.contoso.com, the certificate FQDN is webserver3.contoso.com. However, if the server name differs for your deployment, use a certificate with the FQDN of the server on which you are installing Communicator Web Access. The following procedure assumes that webserver3.contoso.com and the logged on user have permission to access the internal CA on contosodc.contoso.com by using the physical network and Certificate Services Web enrollment feature.
To request the certificate 1. On webserver3.contoso.com, open a Web browser. In the Address box, type http://contosodc.contoso.com/certsrv, and then press ENTER. 2. Click Request a Certificate. 3. Click Advanced certificate request. 4. Click Create and submit a request to this CA. 5. In the Certificate Template list, select the name of the duplicated Web Server template that you created for the Office Communications Server 2007, Standard Edition certificates. 6. In the Identifying Information for Offline Template box, type webserver3.contoso.com. 7. The Mark keys as exportable check box must be checked, which is the default for the duplicated Web Server template. Do not proceed unless this check box is selected. If the check box is cleared and is unavailable, you have not duplicated the web server template. You must do this before continuing.
12 Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment
8. In the Key Options area, select the Store certificate in the local computer certificate store check box. 9. Click Submit. 10. If a potential scripting violation warning appears, and you understand and accept the implications, click Yes. Now that you have requested the certificate, you can install it.
To install the certificate on the computer 1. Click Install this certificate. If a potential scripting violation warning appears, and you understand and accept the implications, click Yes. 2. Click Start, click Run, type mmc, and then click OK. 3. On the File menu, click Add/Remove Snap-in. 4. In the Add/Remove Snap-in dialog box, click Add. 5. In the list of Available Standalone Snap-ins, click Certificates. 6. Click Add. 7. Click Computer account, and then click Next. 8. In the Select Computer dialog box, ensure that the Local computer: (the computer this console is running on) check box is selected, and then click Finish. 9. Click Close, and then click OK. 10. In the left pane of the Certificates console, expand Certificates (Local Computer), expand Trusted Root Certification Authorities, and then click Certificates. 11. Confirm that the certificate that you just requested and installed and that contains an FQDN of webserver3.contoso.com and is located in this folder. If it is not, copy it from the Certificates folder under the Personal folder node, just above.
Install and Configure Communicator Web Access Installing and configuring Communicator Web Access involves the following procedures: 1. Install Communicator Web Access. 2. Activate the Communicator Web Access server. 3. Create the Communicator Web Access virtual server.
Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment 13
To install Communicator Web Access on webserver3.contoso.com 1. Log on to webserver3.contoso.com as a member of the Administrators group. 2. From the Office Communications Server 2007 installation media, double click SetupSE.exe. 3. On the Office Communications Server 2007, Standard Edition Deployment page, click Deploy Other Server Roles.
4. On the Deploy Other Server Roles page, click Deploy Communicator Web Access.
14 Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment
5. On the Deploy Microsoft Office Communicator Web Access page, under Step 1: Install Communicator Web Access, click Install.
6. On the Welcome page, click Next. 7. On the License Agreement page, click I accept, and then click Next. 8. On the Customer Information page, in User Name and Organization, type a name and organization, and then click Next. 9. On the Ready to install page, accept the default location, and then click Next. 10. On the Ready to install page, click Install. 11. On the Setup complete page, click Finish. Do not close the window. Continue directly with the next procedure.
To Activate the Communicator Web Access Server Note Activating the server creates the account CWAService in Active Directory.
1. Under Step 2: Activate Communicator Web Access, click Activate. 2. On the Welcome page, click Next. 3. On the Select domain service account page, accept the default Account name, in the Password box and the Confirm password box, create and type identically, a strong password to be used for the account, and then click Next. 4. On the Select Server Certificate page, click Select Certificate. 5. On the Select Certificate page, in the Issued to column, click webserver3.contoso.com. 6. On the Select Server Certificate page, click Next. Verify that the Issued to box contains CN=webserver3.contoso.com. 7. On the Ready to activate Communicator Web Access page, click Next.
Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment 15
8. On the Success page, click Finish. Do not close the window. Continue directly with the next procedure.
To create the Communicator Web Access virtual server Note The first virtual server is created during this step. You can create additional virtual server in Communicator Web Access Manager (2007 release).
1. Under Step 3: Create a Virtual Server, click Create. 2. On the Welcome page, click Next. 3. On the Select Virtual Server Type page, accept Internal, and then click Next.
4. On the Select Authentication Type page, Use built-in authentication is selected by default. Click Next.
16 Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment
5. On the Select authentication method page, accept the default, and click Next.
6. On the Select Browser Connection Type, accept the default of HTTPS (recommended), and then click Select Certificate.
7. On the Select Certificate page, click the certificate with the FQDN of webserver3.contoso.com, or the server name that you are using, and then click OK. 8. On the Select Browser Connection Type page, click Next.
Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment 17
9. On the Select IP address and port setting page, accept all defaults, and click Next.
10. On the Name the Virtual Server page, accept the default name Communicator Web Access and click Next. 11. On the Automatically Start Virtual Server page, accept the default and click Next. 12. On the Review Settings page, click Next. 13. On the Success page, click Finish.
Configuring the Client Computers For Lab Scenario 1, each client computer will connect to Communicator Web Access through a supported browser. The clients can also host the Office Communicator 2007 client (optional). Installing both Communicator Web Access and Office Communicator 2007 provides you with the opportunity to contrast and compare each client’s features. To prepare each client computer for this role, do the following: 1. Configure Static IP address and Name Resolution for both client computers. 2. Install Office Communicator 2007 on one or both client computers. 3. Configure users for each client computer in Active Directory on contosodc.contoso.com.
Configure Static IP address and Name Resolution for both client computers You will need to follow this procedure for each client computer, entering the IP address noted for each one. When you have configured the static IP address, connect the client to the Hub.
To configure static IP address and name resolution 1. Click Start, point to Settings, and click Network Connections. 2. Right-click the connection for which you want to configure a static IP address, and then click Properties. 3. On the General tab, click Internet Protocol (TCP/IP), and then click Properties. 4. In the Internet Protocol (TCP/IP) Properties dialog box, click Use the following IP address.
18 Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment
5. In the IP address box, type the IP address for the client: a.
For Client 1, type 10.10.10.4
b.
For Client 2, type 10.10.10.5
6. In the Subnet mask box, type 255.255.255.0. 7. Click Use the following DNS server addresses. 8. In the Preferred DNS server box, type 10.10.10.1. 9. Click Advanced. 10. In the Advanced TCP/IP Settings dialog box, click the DNS tab. 11. On the DNS tab, click Append primary and connection specific DNS suffixes, and then click Append parent suffixes of the primary DNS suffix. 12. In the DNS suffix for this connection box, type contoso.com. Select the Register this connection’s addresses in DNS check box, and then select the Use this connection’s DNS suffix in DNS registration check box. 13. Click OK twice, and click Close twice to close the Network Connections window. 14. Connect the client to Hub.
Install Office Communicator 2007 for one or both clients (Optional) This step is optional. Install Office Communicator 2007 if you want to compare Communicator Web Access with Office Communicator 2007.
Add the client computers to the domain Join both client computers to the domain.
To join a client computer to the domain 1. Click Start, right-click My Computer, and then click Properties. 2. Click the Computer Name tab, and then click Change. 3. In the Computer Name Changes dialog box, click Domain. Under Domain, type contoso.com, and then click OK. 4. In the Authentication dialog box, enter the credentials of a member of the DomainAdmins group, and then click OK. 5. On the Confirmation/Welcome page, click OK. 6. On the Restart notification page, click OK.
Configure users for each client in Active Directory on contosodc.contoso.com Add the users Bob and Alice to Active Directory so that you have two users to use during testing. Grant each user the permission to access Office Communications Server 2007, Standard Edition, and therefore, Communicator Web Access.
To configure a user in Active Directory 1. On contosodc.contoso.com, open the Active Directory Users and Computers snap-in.
Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment 19
2. In the tree view pane, expand contoso.com, expand Users, right-click Users, point to New, and then click User. 3. In the First name and Last name boxes, type the user's first name and last name. In the User logon name box, type the user's network logon name. Click Next. 4. Set the password policy for the user. 5. In the Password field and in the Confirm Password box, type the same password, click Next, and then click Finish. 6. In the Active Directory Users and Computers snap-in, in the tree view pane, under Users, right click the user, and then click Properties. 7. Click the Communications tab, and then select the Enable Communications for this user check box. Type a Sign-in name, and select a domain in the @ field. (This can only be done from a machine with Office Communications Server 2007 administrative tools installed.)
8. In the Server or pool field, click the arrow, select contosodc.contoso.com from the list, and then click Configure. 9. On the Other Options page, select the Enable remote user check box, and click OK. 10. Click Apply, and then click OK.
Sign in to Communicator Web Access To test the deployment, sign in to Communicator Web Access by performing the following procedure on each client.
To sign in to Communicator Web Access 1. On the client1.contoso.com computer, open a supported browser. 2. In the Address box of the browser, type https://webserver3.contoso.com.
20 Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment
3. In the Security Alert message box, click Yes if you understand the implications and are comfortable with them. 4. On the Communicator Web Access sign-in page, set a presence level and sign in as [email protected]. 5. The Contacts list will appear. 6. On Client 2, repeat this procedure for [email protected].
Performing Lab 1 Exercises To test Communicator Web Access features and meet the objectives of this lab, perform the following Lab 1 Exercises: 1. Log on to Client 1 and sign in to Communicator Web Access as Bob, and log on to Client 2 and sign in to Communicator Web Access as Alice. 2. From Bob’s account, add Alice to the Contacts list, and from Alice’s account, add Bob to the Contacts list. 3. Send an instant message from Bob to Alice. 4. Send a response from Alice to Bob. 5. Change Bob’s presence status, and note the change on Alice’s Contacts list. 6. Set Alice’s presence status to Do Not Disturb, and try to send an IM from Bob to Alice. 7. Remove Alice from Bob’s Contacts list. 8. Test your solution. Table 4 shows the procedures for these lab exercises. Table 4: Lab 1 Exercises (1-7) Step
Action
Result
Exercise 1: Sign in as [email protected] on Client 1 and [email protected] on Client 2 1
Sign-in to Client 1 as Bob.
Signed-in with a contact list window and presence that is set in the sign-in page of the user
2
Start Internet Explorer. In the Address box, type https://webserver3.contoso.com, and then click Go.
The Security Alert appears.
3
Click Yes in the Security Alert.
The Communicator Web Access Sign-in page appears.
4
Type [email protected] and then click Sign In.
The authentication dialog box appears.
5
Enter [email protected] and Bob’s password in the authentication dialog box, and click OK.
The Communicator Web Access main page appears.
6
Repeat for [email protected] on Client 2.
See above.
Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment 21
Step
Action
Result
Exercise 2: Add Alice to Bob’s contact list 1
With both client computers running, on Bob’s computer, in the Find box of the Communicator Web Access client, type Alice.
N/A
2
Click Find.
Alice should appear just below the Find text box
3
Right-click Alice, point to Add Contact To, and then click Other Contacts.
Alice is added to Bob’s contact list. Alice is also sent a message informing her that Bob has added her to his contact list and giving Alice the option of adding Bob to her Contacts list. Accept the option.
Exercise 3: Send an IM from Bob to Alice. 1
From Bob’s computer, in the Contacts list, double-click Alice.
The Alice - Conversation dialog box opens.
2
From Bob’s computer, type a message in the message box just under the toolbar with Font, and to the left of the Send button. Click Send.
The message appears in the message box as you type. When you click Send, the message is sent to Alice, which causes a desktop alert to pop up in the notification area of Alice’s computer.
Exercise 4: Send an IM response from Alice to Bob. 1
From Alice’s computer, click the desktop alert that pops up as a result of Bob sending an IM.
The Bob-Conversation dialog box appears.
2
From Alice’s computer, type an IM response in the text box of the Conversation dialog box.
The message appears in the text box as you type. When you click Send, Alice’s response appears in the Alice - Conversation dialog box on Bob’s computer.
Exercise 5: Change Bob’s presence status. 1
On Bob’s computer, close the Alice Conversation window.
Alice is notified that the conversation has been terminated by Bob.
2
On Bob’s computer, click Bob at the top of the Communicator Web Access main page, and then click Away.
Bob’s presence is shown as Away on both client computers.
Exercise 6: Set Alice’s presence status to Do Not Disturb, and then send an IM from Bob to Alice. 1
On Alice’s computer, close the Bob Conversation window.
N/A
22 Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment
Step
Action
Result
2
On Alice’s computer, click Alice at the top of the Communicator Web Access main page, and then click Do Not Disturb.
Alice’s presence is shown as Do Not Disturb on both client computers.
3
From Bob’s computer, send Alice an IM as described previously.
A message in Bob’s Communicator Web Access page indicates that Alice’s status is Do Not Disturb.
Exercise 7: Remove Alice from Bob’s contact list 1
On Bob’s computer, on the main Communicator Web Access page, under Other Contacts, right-click Alice, and then click Remove from Contact List.
Bob is prompted to confirm that he wants to remove Alice from his contact list.
2
In the confirmation message, click OK.
Alice is removed from Bob’s contact list.
Exercise 8: Testing your Solution, Communicator Web Access Controls, and the Communicator Web Access AJAX Service API Lab 1 exercises 1 through 7 confirm that the Communicator Web Access deployment is complete and configured correctly. The lab environment is now ready to evaluate the new Communicator Web Access Controls, Communicator Web Access AJAX Service API, automatic logon features, and your custom programs that take advantage of these features. Lab 1 enables all automatic logon scenarios, other than Custom Authentication including SSO, and provides an environment for testing the Communicator Web Access Controls and the Communicator Web Access AJAX Service API. For a high-level discussion of Custom Authentication including SSO, see the Communicator Web Access (2007 release) Authentication Guide. The Communicator Web Access (2007 release) AJAX Service SDK contains information and code snippets to help you develop custom solutions. The SDK comes with Web-based samples and samples based on the Microsoft Win32® application programming interface. To install the SDK, repeat steps 1 through 5 of the To install Communicator Web Access procedure. On the Deploy Microsoft Office Communicator Web Access page, click the Download the Communicator Web Access SDK link, and follow the instructions. The SDK default installation folder is:\Program Files\Office Communications Server 2007\Communicator Web Access\SDK\. Two subfolders are installed here, Docs and Samples. Also see the Office Live Communications Server 2005 Developer Center at: http://r.office.microsoft.com/r/rlidCWA?clid=1033&p1=SDKSite Running the WebControls Sample in the SDK You can use IIS 6.0 to create a Web site on webserver3.contoso.com that points to the WebControls sample. You can then open the samples in the Microsoft Visual Studio® 2005 integrated development environment (IDE), which is shown in the next figure.
Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment 23
Note The screen illustrations in this section were made in an environment other than Lab 1 of this Guide to Lab Deployment. If you run the samples in the environment created in Lab 1, what you see on your screen will differ from the illustrations that follow, in the way described in the next table.
Table 5: Name Mapping Screen illustrations
Password
Your screen
https://cwa2k7.conto so.com
N/A
https://webserver3.cont oso.com
ISVUser1
Pass.Word1
alice
ISVUser2
Pass.Word2
bob
[email protected] Pass.Word1 m
[email protected]
[email protected] Pass.Word2 m
[email protected]
See the ReadMe file with the samples for detailed instructions, but the general steps are: 1. Add 2 users to Active Directory and enable for Communicator Web Access remote access, for example: 2. User name: ISVUser1 Password: Pass.Word1 3. User name: ISVUser2 Password: Pass.Word2 4. Add the WebControls folder into the:\Program Files\Office Communications Server 2007\Communicator Web Access\Server\cwa\Client directory 5. Create the Application name in IIS 6.0 6. Require SSL cert if Communicator Web Access is using SSL (same protocol as the CWA site required) 7. Load the project into the IDE 8. Add CwaWebPages.dll as a reference to the project 9. Set Logon.htm as the start page 10. Edit the following files for your environment: 11. Logon.htm 12. SampleConfig.js 13. Turn of ASP.NET debugging in the IDE 14. Build
24 Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment
15. Log users into Communicator Web Access 16. Run the WebControls project, either from within the IDE or from a supported browser. Figure 2: WebControls SDK Sample
Follow the directions in the readme files included with the SDK for configuring the samples for your ISV Lab environment. To run the WebControls sample in the environment created in Lab 1 described in this Quick Start, you will need to edit the SampleConfig.js file as follows: // ISV needs to change following configuration // Sip domain for each user. For example, if user's sip uri is // sip:[email protected] // and the sip domain is contoso.com // then var L_CWA_SipDomain = "contoso.com"; var L_CWA_SipDomain = "contoso.com"; // Domain which hosts users. //var L_CWA_Domain = "contoso"; var L_CWA_Domain = "contoso"; // URL of CWA Server //var L_CWA_URL = "https://webserver3.contoso.com";
Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment 25 var L_CWA_URL = "https://webserver3.contoso.com";
Important If you use the Microsoft Visual Studio® 2005 integrated development environment, disable ASP.NET debugging on the Start Options tab of the Property Pages for this example.
Figure 3: The Visual Studio 2005 Properties Start Options Page
If you edited the Logon.htm file with ISVUser1 and Pass.Word1, you see the following:
26 Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment
Figure 4: The Sample Logon Page
Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment 27
The next figure shows the WebControls example with four users enabled for Office Communications Server 2007 and each user logged on to Communicator Web Access with a different status. Figure 5: SDK Sample Web Control
Running the CwaApiViewer Sample The CwaApiViewer SDK sample is a Win32® API sample, and is not Web-based, though it does access the Communicator Web Access Web site. In the LoginForm.cs file, modify the this.Account, this.Uri, this.Server, this.Domain, and this.Password variables for your deployment. Build the project, save it, and then run the program. Figure 6 shows the CwaApiViewer SDK sample in the Microsoft Visual Studio® 2005 integrated development environment. Figure 7 shows the CwaApiViewer SDK sample connected to Communicator Web Access (2007 release) using domain credentials for isvuser1, who has been granted access to Office Communications Server 2007 and Communicator Web Access.
28 Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment
Figure 6: The CwaApiViewer SDK Sample in Visual Studio 2005
Figure 7 shows the running CwaApiViewer SDK sample. Figure 7: The CwaApiViewer
This document supports a preliminary release of a software product that may be changed substantially prior to final commercial release. This document is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in this document. Information in this document, including URL and other Internet Web site references, is subject to change without notice. The entire risk of the use or the results from the use of this document remains with the user. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. 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.
© 2007 Microsoft Corporation. All rights reserved.
Microsoft, MS-DOS, Windows, Windows Mobile, Windows Server, Windows Vista, Active Directory, Internet Explorer, Visual Studio, and Win32 are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
All other trademarks are property of their respective owners.
Contents
Contents............................................................. ..............................3 Introduction..................................................................................... ..1 Overview of Lab Scenario...................................................... .......1 Supported Browsers.................................................. ...................1 Lab Scenario 1: Built-in Authentication Mode...............................2 Lab 1 System Requirements............................................... .....4 Setting up contosodc.contoso.com...................................... ....7 Setting up webserver3.contoso.com.......................................9 Configuring the Client Computers.........................................17 Performing Lab 1 Exercises...................................................20
Introduction Microsoft® Office Communicator Web Access (2007 release) provides browser-based client access to Microsoft Office Communications Server 2007. Office Communications Server 2007 and Communicator Web Access (2007 release) build upon the foundation established by Live Communications Server 2005 with SP1 and Communicator Web Access (2005 release). This document describes the steps necessary to deploy Communicator Web Access (2007 release) in a lab environment with a single-forest, single-domain topology.
Overview of Lab Scenario This Quick Start contains the following lab scenario: •
Lab Scenario 1: Built-in authentication mode Lab scenario 1 demonstrates the requirements and installation steps for deploying Communicator Web Access in Built-in authentication mode. You use built-in authentication mode for testing Communicator Web Access (2007 release) Controls and the new Microsoft Office Communicator Web Access (2007 release) AJAX Service API. Built-in authentication does not support single sign-on (SSO). For information about SSO, see the Communicator Web Access (2007 release) Authentication Guide. For information about the Communicator Web Access (2007 release) AJAX Service API and the Communicator Web Access (2007 release) Controls, see the Communicator Web Access (2007 release) Software Development Kit (SDK). Note: The deployment scenario described in this document is intended for test-lab purposes only. It might not be suitable for a production environment.
Supported Browsers Supported browsers for Communicator Web Access (2007 release) are: Table 1: Supported Browsers Operating System
Internet Browser
Authentication Mechanism
Microsoft Windows® 2000 SP4
Microsoft Internet Explorer® 6 SP1
Forms-based NTLM Custom
Windows XP SP2
Internet Explorer 6 SP2 Internet Explorer 7 Firefox 2.0.latest
Forms-based NTLM Kerberos Custom
2 Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment
Windows Vista™
Internet Explorer 7 Firefox 2.0.latest
Forms-based NTLM Kerberos Custom
Mac OS X 10.3.9
Safari 1.3.2
Forms-based Kerberos Custom
Firefox 2.0.latest
Forms-based NTLM Kerberos Custom
Safari 2.0.latest
Forms-based Kerberos Custom
Firefox 2.0.latest
Forms-based NTLM Kerberos Custom
Mac OS X 10.4.8
Lab Scenario 1: Built-in Authentication Mode In Lab Scenario 1, you will deploy Communicator Web Access (2007 release) in built-in authentication mode in a lab setting with a single-forest, single-domain topology. The resulting environment supports testing of the new Communicator Web Access UI controls, the new Communicator Web Access AJAX Service API, and for testing automatic logon 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 Microsoft Windows® operating systems prior to Windows 2000 SP4, which are not supported by Office Communicator 2007
•
Locked-down, insufficiently privileged users of supported Windows platforms
Communicator Web Access provides users with an installation-free solution for accessing instant messaging and presence features and for accessing features implemented in your solutions. In Lab Scenario 1, you will set up a development lab environment for a single-forest, singledomain 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.
Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment 3
•
Sign in to Communicator Web Access.
•
Search for users to add to the Contacts list.
•
Add contacts to, and delete them from, the Contacts list.
•
Send an instant message by using Communicator Web Access.
•
Change presence status.
•
Set presence status to Do Not Disturb.
•
Create and test a sample enhanced presence solution containing code that accesses the new Communicator Web Access AJAX Service API and Communicator Web Access Controls.
In this scenario, the Contoso Corporation network includes the following: •
A domain controller that runs Microsoft Active Directory® Domain Services, DNS Server, a private certification authority, and Microsoft Office Communications Server 2007, Standard Edition
Caution Running Office Communications Server 2007 on a Domain Controller is not recommended or supported in a production environment.
•
A Communicator Web Access (2007 release) server
•
One hub
•
Two clients
Figure 1: Lab 1
In this lab scenario, you will perform the following tasks:
4 Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment
1. Set up contosodc.contoso.com. This server will function as the Active Directory domain controller, the DNS Server, the Microsoft Windows Server® 2003 SP1 enterprise root certification authority (CA), and the Office Communications Server 2007, Standard Edition server.
Caution Running Office Communications Server 2007 on a Domain Controller is not recommended or supported for a production environment
2. Set up webserver3.contoso.com. This server will function as the Communicator Web Access server. 3. Prepare the clients. Each client computer will connect to Communicator Web Access client through a browser. 4. Perform Lab 1 exercises. The lab exercises will demonstrate end user tasks such as adding contacts, sending instant messages, and changing presence. ISV application developer tasks are also demonstrated.
Lab 1 System Requirements You will need two “bare-metal” servers, two client computers, and one hub, as shown previously in Figure 1.
Server: contosodc.contoso.com Table 2 shows the system requirements for contosodc.contoso.com. For this lab, the root CA issues certificates required for secure communications in Office Communications Server 2007, Standard Edition and Communicator Web Access. Table 2: contosodc.contoso.com Minimum Requirements Component
Requirement
contosodc.contoso.com - Domain Controller: IP Address = 10.10.10.1/24 Software Operating System
Windows Server 2003 SP1 (Standard Edition, Enterprise Edition or Datacenter Edition)
Directory Service
Active Directory
Name Resolution
DNS Server
PKI Infrastructure
Windows Server 2003 SP1 Enterprise Root CA
Office Communications Server 2007
Office Communications Server 2007,Standard Edition
Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment 5
Certificate services Web enrollment and Office Communications Server 2007 Web Components support
IIS 6.0
Other software required for Office Communications Server 2007
.NET Framework Version 2.0 or greater
QFEs
KB 915066 http://support.microsoft.com/kb/915066
ASP.NET 2.0
KB913297 http://support.microsoft.com/kb/913297 KB 917283 http://support.microsoft.com/kb/917283 KB 922770 http://support.microsoft.com/kb/922770 Group memberships
DomainAdmins Administrators
Hardware Processor
Dual 3.2 GHz CPU
Networking
1 Gigabit Ethernet network adapter
Memory
4 GB RAM (Recommended)
Disk Space
2 × 36 GB NTFS-formatted Hard Drives
For details about installing Office Communications Server, Standard Edition, see the Office Communications Server 2007, Standard Edition Deployment Guide available on the Office Communications Server 2007 installation media. You install IIS 6.0 by using the Windows Control Panel. For details, see the Windows Server documentation. To download Service Pack 1for Windows Server 2003, go to: http://www.microsoft.com/windowsserver2003/downloads/servicepacks/sp1/default.mspx. To download the .NET Framework, go to: http://www.microsoft.com/downloads/details.aspx?familyid=0856EACB-4362-4B0D-8EDDAAB15C5E04F5&displaylang=en
Server: webserver3.contoso.com Table 3 shows the system requirements for webserver3.contoso.com. On this server, you will install Communicator Web Access. Table 3: webserver3.contoso.com Minimum Requirements Component
Requirement
6 Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment
webserver3.contoso.com - Member Server contoso.com - IP Address = 10.10.10.35/24 Software Disk format
NTFS
Operating System
Windows Server 2003 SP1 (Standard Edition, Enterprise Edition or Datacenter Edition)
Other software required for Communicator Web Access
.NET Framework Version 2.0 or greater IIS 6.0 ASP.NET 2.0 Communicator Web Access
Hardware Processor
Dual 3.2 GHz CPU
Networking
1 Gigabit Ethernet network adapter
Memory
4 GB RAM (Recommended)
Disk Space
1 × 36 GB NTFS-formatted Hard Drives
Group memberships To install Communicator Web Access
User must be a member of local Administrators group.
To activate Communicator Web Access
User must be a member of the DomainAdmins group.
To create a virtual server
User must be a member of local Administrators group.
Client computers Each client computer runs the Microsoft Windows® XP or Windows 2000 Server with SP4 operating system with the Internet Explorer® 6.0 SP1 Internet browser. You can optionally add Office Communicator 2007 to one or both of the client computers. Table 4: Client 1 and Client 2 Minimum Requirements Component
Requirement
Client 1 - Member client; name=Client1; IP Address=10.10.10.4/24 Client 2 - Member client; name=Client2; IP Address= 10.10.10.5/24 Software Operating System
Windows XP with the latest service pack1
Browser/Client
Internet Explorer 6.01
Other software
Office Communicator 2007
Hardware
Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment 7
Processor
300 MHz
Networking
1 network adapter
Memory
128 MB RAM
Disk space
20 GB
1
Other operating systems or browsers may be used. For a list of supported operating systems and browsers, see the Microsoft Communicator Web Access (2007 release) Planning and Deployment Guide.
Setting up contosodc.contoso.com Preparing contosodc.contoso.com consists of the following steps: 1. Configure a static IP Address. 2. Prepare Active Directory using dcpromo and configure DNS. 3. Configure server as a Windows Server 2003 SP1 Enterprise Root CA. 4. Install and configure Office Communications Server 2007, Standard Edition.
Caution Running Office Communications Server 2007 on a Domain Controller is not recommended or supported for a production environment
5. Request and configure certificates for Office Communications Server 2007. The following sections explain these steps in detail.
Configure Static IP Address for contosodc Connect the Server to Hub 1, and then configure the server with a static IP address.
To configure a static IP address for contosodc 1. Click Start, point to Settings, and then click Network Connections. 2. Right-click the connection for which you want to configure a static IP address, and then click Properties. 3. Click Internet Protocol (TCP/IP), and then click Properties. 4. In the Internet Protocol (TCP/IP) Properties dialog box, click Use the following IP address. 5. In the IP address box, type 10.10.10.1. 6. In the Subnet mask box, type 255.255.255.0. 7. Click Use the following DNS server addresses. 8. In the Preferred DNS server box, type 10.10.10.1. 9. Click OK twice, and then close the Network Connections window.
8 Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment
Prepare Active Directory by using dcpromo and configure DNS Use Dcpromo to install Active Directory and promote contosodc.contoso.com to a domain controller, and then configure DNS. You will need your Windows Server 2003 installation media.
To prepare Active Directory using dcpromo and configure DNS 1. Click Start, and then click Run. In the Open box, type dcpromo, and then click OK. 2. On the Active Directory Installation Wizard Welcome page, click Next. 3. On the Operating System Compatibility page, click Next. 4. On the Domain Controller Type page, accept the default Domain controller for a new domain, and then click Next. 5. On the Create New Domain page, accept the default Domain in a new forest, and then click Next. 6. On the New Domain Name page, enter contoso.com in the text box, and then click Next. 7. On the NetBIOS Domain Name page, accept the default CONTOSO, and then click Next. 8. On the Database and Log Folders page, accept the default locations, and then click Next. 9. On the Shared System Volume page, accept the default location, and then click Next. 10. On the DNS Registration Diagnostics page, click the middle button, Install and configure the DNS server on this computer, and set this computer to use this DNS server as its preferred DNS server, and then click Next. 11. On the Permissions page, accept the default, Permissions compatible only with Windows 2000 or Windows Server 2003 operating systems, and then click Next. Office Communications Server 2007 requires native mode. 12. On the Directory Services Restore Mode Administration Password page, enter the same password in both text boxes, and then click Next. 13. On the Summary page, click Next. 14. If prompted, type the full path to the Windows Server 2003 installation folder or CD, and then click Continue. 15. Click Finish. 16. Ensure that the domain controller is in native mode.
Configure contosodc.contoso.com as a Windows Server 2003 SP1 Enterprise Root CA Install certificate services and configure the server as an Enterprise Root Certification Authority.
To install certificate services and configure the server as an Enterprise root CA 1. Click Start, point to Settings, click Control Panel, and then click Add or Remove Programs. 2. Click Add or Remove Windows Components. 3. In the Windows Components Wizard, click Certificate Services.
Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment 9
4. On the Microsoft Certificate Services page, click Yes, and then click Next. 5. On the CA Type page, click Enterprise root CA, and then click Next. 6. On the CA Identifying Information page, in the Common name for this CA box, type webserver3, and then click Next. 7. On the Certificate Database Settings page, click Next. 8. If prompted, type the full path to the Windows Server 2003 installation folder or CD, and then click Continue. 9. In the Microsoft Certificate Services message, click Yes to allow IIS to be temporarily stopped. 10. In the Microsoft Certificate Services message, click Yes to enable ASP and IIS. After you have installed Microsoft Certificate Services, prepare the CA for issuing certificates by duplicating the web server certificate template. During this procedure, you must grant Enroll and Auto enroll permissions for the following groups in all domains: AuthenticatedUsers, DomainAdmins, DomainComputers, and EnterpriseAdmins.
Request Certificates for Office Communications Server 2007, Standard Edition See the Office Communications Server 2007, Standard Edition Quick Start.
Caution The certificates for both Office Communications Server 2007 Standard Edition and Communicator Web Access must be issued from the same certification authority (CA) and must use a duplicated Web server template in which the Mark keys as exportable option has been enabled.
Install and Configure Office Communications Server 2007, Standard Edition See the Office Communications Server 2007, Standard Edition Quick Start.
Setting up webserver3.contoso.com For this lab, webserver3.contoso.com will function as the Communicator Web Access server. Preparing the webserver3 for this role consists of the following steps: 1. Configure a static IP address and name resolution. 2. Add webserver3 to the contoso.com domain. 3. Request the required certificates for Communicator Web Access. 4. Install and Configure Communicator Web Access. The following sections describe these steps in detail.
Configure Static IP Address Connect webserver3 to Hub1, and then configure webserver3 with a static IP address.
10 Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment
To configure webserver3 with a static IP address 1. Click Start, point to Settings, and click Network Connections. 2. Right-click the connection for which you want to configure a static IP address, and then click Properties. 3. In the Properties dialog box, click Internet Protocol (TCP/IP), and then click Properties. 4. In the Internet Protocol (TCP/IP) Properties dialog box, click Use the following IP address. 5. In the IP address box, type 10.10.10.35. 6. In the Subnet mask box, type 255.255.255.0. 7. Click Use the following DNS server addresses. 8. In the Preferred DNS server box, type 10.10.10.1. 9. Click OK twice, and then close the Network Connections window.
Add webserver3 to contoso domain. webserver3 must be a member server in the contoso.com domain.
To add webserver3 to the contoso domain 1. Right-click My Computer, and click Properties. 2. In the System Properties dialog box, click the Computer Name tab, and then click Change. 3. In the Computer Name Change dialog box, click Domain. In the Domain box, type contoso.com, and then click OK. 4. In the Authentication dialog box, type the user name and password of a member of the DomainAdmins group, and then click OK. 5. On the Computer Name Changes authentication page, type the Domain Admin credentials, and then click OK. 6. In the Confirmation/Welcome dialog box, click OK. 7. In the Restart notification dialog box, click OK. 8. In the Restart confirmation dialog box, click OK to restart the server.
Request a certificate Because you have set up contosodc.contoso.com as a Windows Server 2003 Enterprise CA and enabled autoenrollment, webserver3.contoso.com will receive the enterprise CA certificate chain when it is added to the domain. However, you will need to request a Web Server certificate with the FQDN (fully qualified domain name) webserver3.contoso.com. You will be asked to choose this certificate during the Communicator Web Access setup process.
Caution The certificates for Office Communications Server 2007, Standard Edition and Communicator Web Access must be issued from the same certification authority (CA) and must use a duplicated web server template in which the Mark keys as exportable option has been enabled. See the Office Communications Server 2007 Quick Start for the procedure detailing how to do this.
Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment 11
Note Lab Scenario 1 uses the Microsoft Certification Authority (CA) that you set up on contosodc.contoso.com, and the procedures in this document assume the use of an internal CA. You can use an External CA for this lab scenario, but you may need to modify the certificate procedures to comply with the requirements of the External CA, in addition to the certification requirements of Office Communications Server 2007 and Communicator Web Access. For details about configuring certificates, see Office Communications Server 2007 Configuring Certificates at http://office.microsoft.com/enus/FX011526591033.aspx.
The Communicator Web Access server requires a Mutual TLS (MTLS) certificate and an SSL IIS certificate. For this Lab, you can use the same certificate for both. The Communicator Web Access certificate requirements for this lab are as follows: •
Certificates must be issued from the same CA from which the Office Communications Server 2007, Standard Edition certificates were issued.
•
Certificates must use a duplicated web server template in which the Mark keys as exportable option has been enabled
For this lab, in which the FQDN of the server is webserver3.contoso.com, the certificate FQDN is webserver3.contoso.com. However, if the server name differs for your deployment, use a certificate with the FQDN of the server on which you are installing Communicator Web Access. The following procedure assumes that webserver3.contoso.com and the logged on user have permission to access the internal CA on contosodc.contoso.com by using the physical network and Certificate Services Web enrollment feature.
To request the certificate 1. On webserver3.contoso.com, open a Web browser. In the Address box, type http://contosodc.contoso.com/certsrv, and then press ENTER. 2. Click Request a Certificate. 3. Click Advanced certificate request. 4. Click Create and submit a request to this CA. 5. In the Certificate Template list, select the name of the duplicated Web Server template that you created for the Office Communications Server 2007, Standard Edition certificates. 6. In the Identifying Information for Offline Template box, type webserver3.contoso.com. 7. The Mark keys as exportable check box must be checked, which is the default for the duplicated Web Server template. Do not proceed unless this check box is selected. If the check box is cleared and is unavailable, you have not duplicated the web server template. You must do this before continuing.
12 Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment
8. In the Key Options area, select the Store certificate in the local computer certificate store check box. 9. Click Submit. 10. If a potential scripting violation warning appears, and you understand and accept the implications, click Yes. Now that you have requested the certificate, you can install it.
To install the certificate on the computer 1. Click Install this certificate. If a potential scripting violation warning appears, and you understand and accept the implications, click Yes. 2. Click Start, click Run, type mmc, and then click OK. 3. On the File menu, click Add/Remove Snap-in. 4. In the Add/Remove Snap-in dialog box, click Add. 5. In the list of Available Standalone Snap-ins, click Certificates. 6. Click Add. 7. Click Computer account, and then click Next. 8. In the Select Computer dialog box, ensure that the Local computer: (the computer this console is running on) check box is selected, and then click Finish. 9. Click Close, and then click OK. 10. In the left pane of the Certificates console, expand Certificates (Local Computer), expand Trusted Root Certification Authorities, and then click Certificates. 11. Confirm that the certificate that you just requested and installed and that contains an FQDN of webserver3.contoso.com and is located in this folder. If it is not, copy it from the Certificates folder under the Personal folder node, just above.
Install and Configure Communicator Web Access Installing and configuring Communicator Web Access involves the following procedures: 1. Install Communicator Web Access. 2. Activate the Communicator Web Access server. 3. Create the Communicator Web Access virtual server.
Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment 13
To install Communicator Web Access on webserver3.contoso.com 1. Log on to webserver3.contoso.com as a member of the Administrators group. 2. From the Office Communications Server 2007 installation media, double click SetupSE.exe. 3. On the Office Communications Server 2007, Standard Edition Deployment page, click Deploy Other Server Roles.
4. On the Deploy Other Server Roles page, click Deploy Communicator Web Access.
14 Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment
5. On the Deploy Microsoft Office Communicator Web Access page, under Step 1: Install Communicator Web Access, click Install.
6. On the Welcome page, click Next. 7. On the License Agreement page, click I accept, and then click Next. 8. On the Customer Information page, in User Name and Organization, type a name and organization, and then click Next. 9. On the Ready to install page, accept the default location, and then click Next. 10. On the Ready to install page, click Install. 11. On the Setup complete page, click Finish. Do not close the window. Continue directly with the next procedure.
To Activate the Communicator Web Access Server Note Activating the server creates the account CWAService in Active Directory.
1. Under Step 2: Activate Communicator Web Access, click Activate. 2. On the Welcome page, click Next. 3. On the Select domain service account page, accept the default Account name, in the Password box and the Confirm password box, create and type identically, a strong password to be used for the account, and then click Next. 4. On the Select Server Certificate page, click Select Certificate. 5. On the Select Certificate page, in the Issued to column, click webserver3.contoso.com. 6. On the Select Server Certificate page, click Next. Verify that the Issued to box contains CN=webserver3.contoso.com. 7. On the Ready to activate Communicator Web Access page, click Next.
Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment 15
8. On the Success page, click Finish. Do not close the window. Continue directly with the next procedure.
To create the Communicator Web Access virtual server Note The first virtual server is created during this step. You can create additional virtual server in Communicator Web Access Manager (2007 release).
1. Under Step 3: Create a Virtual Server, click Create. 2. On the Welcome page, click Next. 3. On the Select Virtual Server Type page, accept Internal, and then click Next.
4. On the Select Authentication Type page, Use built-in authentication is selected by default. Click Next.
16 Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment
5. On the Select authentication method page, accept the default, and click Next.
6. On the Select Browser Connection Type, accept the default of HTTPS (recommended), and then click Select Certificate.
7. On the Select Certificate page, click the certificate with the FQDN of webserver3.contoso.com, or the server name that you are using, and then click OK. 8. On the Select Browser Connection Type page, click Next.
Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment 17
9. On the Select IP address and port setting page, accept all defaults, and click Next.
10. On the Name the Virtual Server page, accept the default name Communicator Web Access and click Next. 11. On the Automatically Start Virtual Server page, accept the default and click Next. 12. On the Review Settings page, click Next. 13. On the Success page, click Finish.
Configuring the Client Computers For Lab Scenario 1, each client computer will connect to Communicator Web Access through a supported browser. The clients can also host the Office Communicator 2007 client (optional). Installing both Communicator Web Access and Office Communicator 2007 provides you with the opportunity to contrast and compare each client’s features. To prepare each client computer for this role, do the following: 1. Configure Static IP address and Name Resolution for both client computers. 2. Install Office Communicator 2007 on one or both client computers. 3. Configure users for each client computer in Active Directory on contosodc.contoso.com.
Configure Static IP address and Name Resolution for both client computers You will need to follow this procedure for each client computer, entering the IP address noted for each one. When you have configured the static IP address, connect the client to the Hub.
To configure static IP address and name resolution 1. Click Start, point to Settings, and click Network Connections. 2. Right-click the connection for which you want to configure a static IP address, and then click Properties. 3. On the General tab, click Internet Protocol (TCP/IP), and then click Properties. 4. In the Internet Protocol (TCP/IP) Properties dialog box, click Use the following IP address.
18 Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment
5. In the IP address box, type the IP address for the client: a.
For Client 1, type 10.10.10.4
b.
For Client 2, type 10.10.10.5
6. In the Subnet mask box, type 255.255.255.0. 7. Click Use the following DNS server addresses. 8. In the Preferred DNS server box, type 10.10.10.1. 9. Click Advanced. 10. In the Advanced TCP/IP Settings dialog box, click the DNS tab. 11. On the DNS tab, click Append primary and connection specific DNS suffixes, and then click Append parent suffixes of the primary DNS suffix. 12. In the DNS suffix for this connection box, type contoso.com. Select the Register this connection’s addresses in DNS check box, and then select the Use this connection’s DNS suffix in DNS registration check box. 13. Click OK twice, and click Close twice to close the Network Connections window. 14. Connect the client to Hub.
Install Office Communicator 2007 for one or both clients (Optional) This step is optional. Install Office Communicator 2007 if you want to compare Communicator Web Access with Office Communicator 2007.
Add the client computers to the domain Join both client computers to the domain.
To join a client computer to the domain 1. Click Start, right-click My Computer, and then click Properties. 2. Click the Computer Name tab, and then click Change. 3. In the Computer Name Changes dialog box, click Domain. Under Domain, type contoso.com, and then click OK. 4. In the Authentication dialog box, enter the credentials of a member of the DomainAdmins group, and then click OK. 5. On the Confirmation/Welcome page, click OK. 6. On the Restart notification page, click OK.
Configure users for each client in Active Directory on contosodc.contoso.com Add the users Bob and Alice to Active Directory so that you have two users to use during testing. Grant each user the permission to access Office Communications Server 2007, Standard Edition, and therefore, Communicator Web Access.
To configure a user in Active Directory 1. On contosodc.contoso.com, open the Active Directory Users and Computers snap-in.
Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment 19
2. In the tree view pane, expand contoso.com, expand Users, right-click Users, point to New, and then click User. 3. In the First name and Last name boxes, type the user's first name and last name. In the User logon name box, type the user's network logon name. Click Next. 4. Set the password policy for the user. 5. In the Password field and in the Confirm Password box, type the same password, click Next, and then click Finish. 6. In the Active Directory Users and Computers snap-in, in the tree view pane, under Users, right click the user, and then click Properties. 7. Click the Communications tab, and then select the Enable Communications for this user check box. Type a Sign-in name, and select a domain in the @ field. (This can only be done from a machine with Office Communications Server 2007 administrative tools installed.)
8. In the Server or pool field, click the arrow, select contosodc.contoso.com from the list, and then click Configure. 9. On the Other Options page, select the Enable remote user check box, and click OK. 10. Click Apply, and then click OK.
Sign in to Communicator Web Access To test the deployment, sign in to Communicator Web Access by performing the following procedure on each client.
To sign in to Communicator Web Access 1. On the client1.contoso.com computer, open a supported browser. 2. In the Address box of the browser, type https://webserver3.contoso.com.
20 Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment
3. In the Security Alert message box, click Yes if you understand the implications and are comfortable with them. 4. On the Communicator Web Access sign-in page, set a presence level and sign in as [email protected]. 5. The Contacts list will appear. 6. On Client 2, repeat this procedure for [email protected].
Performing Lab 1 Exercises To test Communicator Web Access features and meet the objectives of this lab, perform the following Lab 1 Exercises: 1. Log on to Client 1 and sign in to Communicator Web Access as Bob, and log on to Client 2 and sign in to Communicator Web Access as Alice. 2. From Bob’s account, add Alice to the Contacts list, and from Alice’s account, add Bob to the Contacts list. 3. Send an instant message from Bob to Alice. 4. Send a response from Alice to Bob. 5. Change Bob’s presence status, and note the change on Alice’s Contacts list. 6. Set Alice’s presence status to Do Not Disturb, and try to send an IM from Bob to Alice. 7. Remove Alice from Bob’s Contacts list. 8. Test your solution. Table 4 shows the procedures for these lab exercises. Table 4: Lab 1 Exercises (1-7) Step
Action
Result
Exercise 1: Sign in as [email protected] on Client 1 and [email protected] on Client 2 1
Sign-in to Client 1 as Bob.
Signed-in with a contact list window and presence that is set in the sign-in page of the user
2
Start Internet Explorer. In the Address box, type https://webserver3.contoso.com, and then click Go.
The Security Alert appears.
3
Click Yes in the Security Alert.
The Communicator Web Access Sign-in page appears.
4
Type [email protected] and then click Sign In.
The authentication dialog box appears.
5
Enter [email protected] and Bob’s password in the authentication dialog box, and click OK.
The Communicator Web Access main page appears.
6
Repeat for [email protected] on Client 2.
See above.
Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment 21
Step
Action
Result
Exercise 2: Add Alice to Bob’s contact list 1
With both client computers running, on Bob’s computer, in the Find box of the Communicator Web Access client, type Alice.
N/A
2
Click Find.
Alice should appear just below the Find text box
3
Right-click Alice, point to Add Contact To, and then click Other Contacts.
Alice is added to Bob’s contact list. Alice is also sent a message informing her that Bob has added her to his contact list and giving Alice the option of adding Bob to her Contacts list. Accept the option.
Exercise 3: Send an IM from Bob to Alice. 1
From Bob’s computer, in the Contacts list, double-click Alice.
The Alice - Conversation dialog box opens.
2
From Bob’s computer, type a message in the message box just under the toolbar with Font, and to the left of the Send button. Click Send.
The message appears in the message box as you type. When you click Send, the message is sent to Alice, which causes a desktop alert to pop up in the notification area of Alice’s computer.
Exercise 4: Send an IM response from Alice to Bob. 1
From Alice’s computer, click the desktop alert that pops up as a result of Bob sending an IM.
The Bob-Conversation dialog box appears.
2
From Alice’s computer, type an IM response in the text box of the Conversation dialog box.
The message appears in the text box as you type. When you click Send, Alice’s response appears in the Alice - Conversation dialog box on Bob’s computer.
Exercise 5: Change Bob’s presence status. 1
On Bob’s computer, close the Alice Conversation window.
Alice is notified that the conversation has been terminated by Bob.
2
On Bob’s computer, click Bob at the top of the Communicator Web Access main page, and then click Away.
Bob’s presence is shown as Away on both client computers.
Exercise 6: Set Alice’s presence status to Do Not Disturb, and then send an IM from Bob to Alice. 1
On Alice’s computer, close the Bob Conversation window.
N/A
22 Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment
Step
Action
Result
2
On Alice’s computer, click Alice at the top of the Communicator Web Access main page, and then click Do Not Disturb.
Alice’s presence is shown as Do Not Disturb on both client computers.
3
From Bob’s computer, send Alice an IM as described previously.
A message in Bob’s Communicator Web Access page indicates that Alice’s status is Do Not Disturb.
Exercise 7: Remove Alice from Bob’s contact list 1
On Bob’s computer, on the main Communicator Web Access page, under Other Contacts, right-click Alice, and then click Remove from Contact List.
Bob is prompted to confirm that he wants to remove Alice from his contact list.
2
In the confirmation message, click OK.
Alice is removed from Bob’s contact list.
Exercise 8: Testing your Solution, Communicator Web Access Controls, and the Communicator Web Access AJAX Service API Lab 1 exercises 1 through 7 confirm that the Communicator Web Access deployment is complete and configured correctly. The lab environment is now ready to evaluate the new Communicator Web Access Controls, Communicator Web Access AJAX Service API, automatic logon features, and your custom programs that take advantage of these features. Lab 1 enables all automatic logon scenarios, other than Custom Authentication including SSO, and provides an environment for testing the Communicator Web Access Controls and the Communicator Web Access AJAX Service API. For a high-level discussion of Custom Authentication including SSO, see the Communicator Web Access (2007 release) Authentication Guide. The Communicator Web Access (2007 release) AJAX Service SDK contains information and code snippets to help you develop custom solutions. The SDK comes with Web-based samples and samples based on the Microsoft Win32® application programming interface. To install the SDK, repeat steps 1 through 5 of the To install Communicator Web Access procedure. On the Deploy Microsoft Office Communicator Web Access page, click the Download the Communicator Web Access SDK link, and follow the instructions. The SDK default installation folder is
Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment 23
Note The screen illustrations in this section were made in an environment other than Lab 1 of this Guide to Lab Deployment. If you run the samples in the environment created in Lab 1, what you see on your screen will differ from the illustrations that follow, in the way described in the next table.
Table 5: Name Mapping Screen illustrations
Password
Your screen
https://cwa2k7.conto so.com
N/A
https://webserver3.cont oso.com
ISVUser1
Pass.Word1
alice
ISVUser2
Pass.Word2
bob
[email protected] Pass.Word1 m
[email protected]
[email protected] Pass.Word2 m
[email protected]
See the ReadMe file with the samples for detailed instructions, but the general steps are: 1. Add 2 users to Active Directory and enable for Communicator Web Access remote access, for example: 2. User name: ISVUser1 Password: Pass.Word1 3. User name: ISVUser2 Password: Pass.Word2 4. Add the WebControls folder into the
24 Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment
15. Log users into Communicator Web Access 16. Run the WebControls project, either from within the IDE or from a supported browser. Figure 2: WebControls SDK Sample
Follow the directions in the readme files included with the SDK for configuring the samples for your ISV Lab environment. To run the WebControls sample in the environment created in Lab 1 described in this Quick Start, you will need to edit the SampleConfig.js file as follows: // ISV needs to change following configuration // Sip domain for each user. For example, if user's sip uri is // sip:[email protected] // and the sip domain is contoso.com // then var L_CWA_SipDomain = "contoso.com"; var L_CWA_SipDomain = "contoso.com"; // Domain which hosts users. //var L_CWA_Domain = "contoso"; var L_CWA_Domain = "contoso"; // URL of CWA Server //var L_CWA_URL = "https://webserver3.contoso.com";
Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment 25 var L_CWA_URL = "https://webserver3.contoso.com";
Important If you use the Microsoft Visual Studio® 2005 integrated development environment, disable ASP.NET debugging on the Start Options tab of the Property Pages for this example.
Figure 3: The Visual Studio 2005 Properties Start Options Page
If you edited the Logon.htm file with ISVUser1 and Pass.Word1, you see the following:
26 Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment
Figure 4: The Sample Logon Page
Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment 27
The next figure shows the WebControls example with four users enabled for Office Communications Server 2007 and each user logged on to Communicator Web Access with a different status. Figure 5: SDK Sample Web Control
Running the CwaApiViewer Sample The CwaApiViewer SDK sample is a Win32® API sample, and is not Web-based, though it does access the Communicator Web Access Web site. In the LoginForm.cs file, modify the this.Account, this.Uri, this.Server, this.Domain, and this.Password variables for your deployment. Build the project, save it, and then run the program. Figure 6 shows the CwaApiViewer SDK sample in the Microsoft Visual Studio® 2005 integrated development environment. Figure 7 shows the CwaApiViewer SDK sample connected to Communicator Web Access (2007 release) using domain credentials for isvuser1, who has been granted access to Office Communications Server 2007 and Communicator Web Access.
28 Microsoft Office Communicator Web Access (2007 release) Guide to Lab Deployment
Figure 6: The CwaApiViewer SDK Sample in Visual Studio 2005
Figure 7 shows the running CwaApiViewer SDK sample. Figure 7: The CwaApiViewer
Related Documents
Cwa Isvquickstart
October 2019 14
Cwa Alg
October 2019 18
Cwa-854
August 2019 12
Teaching Cwa
June 2020 6
Cwa Plandeploy
October 2019 15