Microsoft Office Communications Server 2007 Standard Edition Deployment Guide

Published: July 2007 Updated: October 2007

®

Information in this document, including URL and other Internet Web site references, is subject to change without notice. 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, Windows Vista, Active Directory, Outlook, PowerPoint, SQL Server, Visual C++, and Visual J# 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
Introduction......................................................................................1 Overview of Office Communications Server 2007 Standard Edition. .1 Infrastructure Requirements and Prerequisites.................................2 Overview of Standard Edition Deployment........................................4 Step 1: Prepare Active Directory Schema, Forest, and Domain.........4 Step 2: Configure DNS for Your Standard Edition Server...................4 Required DNS Records for Automatic Client Sign-In.....................5 Step 3: Deploy a Standard Edition Server.........................................9 3.1 Install Office Communications Server Standard Edition..........9 3.2 Configure Standard Edition Server.......................................11 3.3 Configure Certificates...........................................................13 3.4 Start the Services.................................................................16 3.5 Validate Your Server Configuration......................................17 3.6 Enable Audio/Video Conferencing and Web Conferencing....21 Step 4: Create and Enable Users.....................................................22 4.1 Create and Enable Users for Office Communications Server 23 4.2 Wait for User Replication to Complete..................................25 4.3 Configure Users....................................................................25 Step 5: Deploy the Office Communicator 2007 Client.....................26 5.1 Deploy Office Communicator................................................26 5.2 Configure Client Sign-In........................................................27 5.3 Test Office Communications Server Configuration for Office Communicator............................................................................28 Step 6: Deploy the Live Meeting 2007 Client..................................29 6.1 Deploy the Live Meeting Client.............................................29 6.2 Deploy the Outlook Add-in...................................................31 6.3 Customize Meeting Invitations.............................................31 6.4 Set Up a Test Web Conference.............................................35 Validation and Troubleshooting Hints..............................................37 Appendix A: Certificate Request Scenarios.....................................38 Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic ........................................................................................................41

Introduction
This document describes the high-level steps that are necessary to deploy Microsoft® Office Communications Server 2007 Standard Edition.

Important
If you are updating your system from Live Communications Server 2005 with Service Pack 1, see Migrating to Microsoft Office Communications Server 2007.

Overview of Office Communications Server 2007 Standard Edition
Office Communications Server offers a Standard Edition and an Enterprise Edition: • Standard Edition is designed for use in small or medium-sized organizations. Standard Edition is also recommended for organizations that do not require the performance, scalability, and high availability that Enterprise Edition provides. Enterprise Edition is designed for large-scale deployments that are typical of large organizations. In an Enterprise Edition deployment, multiple Office Communications Server Enterprise Edition servers are deployed as a pool behind a load balancer. Servers in the pool share a central Microsoft SQL Server™ database that stores user data.

Office Communications Server Standard Edition Server Roles
In Office Communications Server Standard Edition, the following components run on a single physical computer: • • • • • Microsoft SQL Server™ 2005 Express Edition with Service Pack 2 (SP2) Front End Server, which houses instant messaging, presence, telephony conferencing servers, and all essential user services. Web Conferencing Server, which enables on-premise conferencing. A/V (Audio/Video) Conferencing Server, which enables users to share audio and video streams. Web Components Server, which enables users to do the following: • • • Access meeting presentations and other content from Web conferences Download Address Book Server files, which provide the Microsoft Office Communicator client with global address list information Expand distribution groups in order to communicate with individual members

Windows Service Dependencies We recommend that you disable the Windows services that are not required on the computers where you install Office Communications Server. For details. and Audio/Video Infrastructure Requirements Before you deploy Office Communications Server Standard Edition. ensure that your environment meets the software. IIS Admin Service. Remote Procedure Call. TCP/IP Protocol Driver. You can safely disable all other services. Table 1. Message Queuing (Message Queuing access control. Security Accounts Manager) Windows Management Instrumentation (Event Log and Remote Procedure Call) HTTP SSL (HTTP.2 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007 Deployment Guide Infrastructure Requirements and Prerequisites Software. Security Accounts Manager) Windows Management Instrumentation (Event Log and Remote Procedure Call) Windows Management Instrumentation Driver Extensions If archiving is enabled. see the Microsoft Office Communications Server 2007 Planning Guide. hardware. Table 1 describes the Windows services that Office Communications Server requires. NTLM Security Support Provider. IPSEC Driver. Planning Requirements Before you begin deployment. Hardware. Office Communications Server Service Dependencies Office Communications Server Service Name Office Communications Server Front-End (RTCSRV) Windows Service Dependencies HTTP SSL (HTTP. Security Accounts Manager) Windows Management Instrumentation Office Communications Server Audio/Video Conferencing (RTCAVMCU) Office Communications Server IM Conferencing (RTCIMMCU) . RMCAST (Pgm) Protocol Driver. Security Accounts Manager) HTTP SSL (HTTP. and audio/video infrastructure requirements as described in the Microsoft Office Communications Server 2007 Planning Guide. IIS Admin Service. IIS Admin Service. Remote Procedure Call. Remote Procedure Call. Remote Procedure Call. you need to determine the best deployment path for your organization.

IIS Admin Service. Security Accounts Manager) Windows Management Instrumentation (Event Log and Remote Procedure Call) HTTP SSL (HTTP. RMCAST (Pgm) Protocol Driver. Security Accounts Manager) Windows Management Instrumentation (Event Log and Remote Procedure Call) Office Communications Server Audio/Video Authentication Windows Management Instrumentation (Event Log and Remote Procedure Call) Windows Management Instrumentation (Event Log and Remote Procedure Call) Windows Management Instrumentation Driver Extensions Windows Management Instrumentation (Event Log and Remote Procedure Call) Windows Management Instrumentation (Remote Procedure Call) Office Communications Server Web Conferencing (RTCDATAMCU) Office Communications Server Archiving and CDR (RTCLOG) Office Communications Server Audio/Video Authentication (RTCMRAUTH) Office Communications Server Audio/Video Edge (RTCMEDIARELAY) Office Communications Server Access Edge (RTCSRV) Office Communications Server Web Conferencing Edge (RTCDATAPROXY) Office Communications Server Mediation (RTCMEDSRV) Storage Requirements If you plan to install the Archiving and CDR Server as described in the Microsoft Office Communications Server 2007 Archiving and CDR Server Deployment Guide. IIS Admin Service. Remote Procedure Call. . TCP/IP Protocol Driver. IPSEC Driver. Remote Procedure Call. Remote Procedure Call. NT LM Security Support Provider.Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 3 Office Communications Server Service Name Windows Service Dependencies (Event Log and Remote Procedure Call) Office Communications Server Telephony Conferencing (RTCACPMCU) HTTP SSL (HTTP. Security Accounts Manager) Windows Management Instrumentation (Remote Procedure Call) Message Queuing (Message Queuing access control. consider storage needs for archiving files.

2. Active Directory preparation includes schema preparation. you must designate a Standard Edition Server or a pool in your internal Office Communications Server infrastructure to authenticate and distribute incoming client sign-in requests. For information about delegating Office Communications Server setup or administration. For detailed instructions and information about Active Directory preparation. but you do not have to repeat this step if you add servers or pools to the deployment. 6. . 5. The following sections describe these steps in detail. 4. forest preparation. this server FQDN must be registered in the Domain Name Service (DNS). and Domain Before you deploy Office Communications Server. see the Microsoft Office Communications Server 2007 Active Directory Guide. for clients to automatically detect a pool or Standard Edition Server on which a user is hosted. Deploy the Microsoft Office Live Meeting 2007 client. In addition. Deploy the Office Communicator 2007 client. you must prepare the Active Directory® Domain Services. including the server FQDN.4 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007 Deployment Guide Overview of Standard Edition Deployment When you deploy Office Communications Server Standard Edition. Step 1: Prepare Active Directory Schema. Step 2: Configure DNS for Your Standard Edition Server When you deploy a Standard Edition Server. and domain Configure DNS for your Standard Edition server Deploy a Standard Edition server Create and enable users. you will perform the following major tasks: 1. Forest. Prepare Active Directory schema. forest. and domain preparation. 3. see the Microsoft Office Communications Server 2007 Active Directory Guide. For clients to be able to connect to the server. You prepare Active Directory during the initial deployment. Setup creates Active Directory objects and settings for the server.

To support automatic client sign-in. If you plan to support Web conferencing for external users. you will need to configure additional DNS records as explained in this section. Required DNS Records At a minimum.com. you are required to configure the following DNS record for all Standard Edition Server deployments: • • An internal DNS A record that resolves the FQDN of your Standard Edition Server. Do not create an SRV record for additional internal servers or pools. Important Only a single pool or Standard Edition Server can be designated to distribute sign-in requests. This can be an existing server or pool that host users. For example. Table 2 shows some example records that are required for the fictitious company.contoso.com. if SIP URIs are of the form *@contoso. Contoso. Required DNS Records for Automatic Client Sign-In If you are enabling automatic sign-in for clients of Office Communications Server. The name of the SIP domain is often different from that of the internal Active Directory domain.for internal TLS connections _sipinternal.Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 5 This section describes the DNS records that you are required to configure in all Office Communications Server deployments and those required for automatic client sign-in.for internal TCP connections (performed only if TCP is allowed) You need to create only a single SRV record for the Standard Edition Server or Enterprise pool that will distribute sign-in requests. (as described in the Microsoft Office Communications Server 2007 Edge Server Deployment Guide). <domain> . see the Microsoft Office Communications Server 2007 Administration Guide. The client uses this record to connect to the reverse proxy. Create an internal DNS SRV record to support automatic client sign-in for this server or pool. Create only one SRV record for the designated server or pool.com and retail. that supports SIP domains of contoso.com is the SIP domain._tcp._tcp. • To enable automatic sign-in for your clients.<domain> . If you require high availability. Note The SIP domain refers to the host portion of the SIP URIs that are assigned to users. you must do the following: • Designate a single server or pool to distribute and authenticate client sign-in requests. then contoso. An organization may also support multiple SIP domains For more information on configuring SIP domains. we recommend that you designate an Enterprise pool for this function. an external DNS A record that resolves the external Web farm FQDN to the external IP address of the reverse proxy. If you will require your clients to manually connect to Office Communications Server. or you can designate a dedicated server or pool that hosts no users for this purpose. . you can skip this section. you must create an internal DNS SRV record that maps one of the following records to the FQDN of the server or pool that distributes sign-in requests from Office Communicator: • • _sipinternaltls.

_tcp. retail._tcp.Contos o.com SIP Domain DNS SRV Record Contoso.Contoso.com must have the following in their Subject Alternate Names: • • sip.contoso._tcp.Contoso.contoso.com sip.com as the pool that will distribute its sign-in requests. Example of the Certificates and DNS Records Required for Automatic Client Sign-in Using the examples in the preceding table.retail. and all its users have a SIP URI in one of the following forms: • • <user>@retail.com Retail.com domain over port 5061 that maps to server1. com Note By default. pool1.contoso.contoso.com If the administrator at Contoso configures pool1.contoso. the certificate that is assigned to the server.com In addition.com and retail. Example DNS Records Required for Automatic Client Sign-In with Multiple SIP Domains FQDN of Standard Edition Server used to distribute signin requests server1. you can configure the DisableStrictDNSNaming group policy.com <user>@contoso.contoso.contoso.com domain over port 5061 that maps to server1.com server1.com.retail._tcp. queries for DNS records adhere to strict domain name matching between the domain in the user name and the SRV record.Contos o.Contoso.com An SRV record for _sipinternaltls. If you prefer that client DNS queries use suffix matching instead.com domain over port 5061 that maps to server1.contoso. the following DNS records are required: • • SRV record for _sipinternaltls.com domain over port 5061 that maps to server1.contoso.contoso.com An SRV record for _sipinternaltls.com SRV record for _sipinternaltls. the Contoso organization supports the SIP domains of contoso.contoso.com . For details.6 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007 Deployment Guide Table 2. see the Microsoft Office Communicator Deployment Guide.contoso.

6. Click Host offering this service. and then right-click the SIP domain in which your Office Communications Server will be installed. In Select a resource record type. To verify that the required records have been created successfully. The following procedure assumes that your internal DNS has zones for your SIP user domains. 5. 6. 8. Click IP Address. 7. and then type the name of the pool. click Control Panel. 3. In the console tree for your SIP domain. click Control Panel. and then click Create Record. On the DNS server.Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 7 Create and Verify DNS SRV and A Records for Client Automatic Client Sign-in You must create DNS SRV records in your internal DNS for every SIP domain. expand Forward Lookup Zones. create a DNS A for the Standard Edition Server. When executing these steps. expand Forward Lookup Zones. 9. Click Add Host. Click Done. wait for DNS replication (if you have just added the records). 4. Click New Host (A). click Service Location (SRV). Click OK. Click Port Number. and then click DNS. 3. Click Other New Records. 2. click Start. and then type the FQDN of the Standard Edition Server. click Start. use your actual SIP domain name instead. Click Protocol. and then type _sipinternaltls. and then type _tcp. and then enter the IP address of the Standard Edition Server. and then type 5061. and then click DNS. 5.com as the domain portion of the SIP URI namespace. and then verify that the records were created as described in the next procedure. the following procedure uses example. . On the DNS server. Click Done. Note To verify the creation of a DNS SRV record For illustrative purposes. 7. To create a DNS A record 1. Click Name (uses parent domain name if blank). 10. 4. click Administrative Tools. Click Service. In the console tree for your domain. click Administrative Tools. and then rightclick the domain in which your Office Communications Server will be installed. and then click OK. 2. After you have created the DNS SRV record. To create a DNS SRV record 1.

8 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007 Deployment Guide 1.27. Click Start.<domain> .117: bytes=32 bytes=32 bytes=32 bytes=32 time<1ms time<1ms time<1ms time<1ms TTL=127 TTL=127 TTL=127 TTL=127 How Client DNS Queries Work During DNS lookup._tcp. and then press ENTER. and then click OK. Click Start. and then press ENTER.corp. type exit. <domain> . 2. Type set type=srv. Type _sipinternaltls. _sipinternaltls.117: 172. <domain> . type ping <FQDN of the Standard Editon Server>.for internal TCP connections (performed only if TCP is allowed) 3.27.com internet address = <IP address of the Standard Edition Server> 6.117: 172.for internal TLS connections 2. at the command prompt. and then click OK.example. 3. type nslookup.for external TLS connections . and then click Run. 4. type cmd. Verify that you receive a response similar to the following.176. type cmd._tls.27.example. SRV records are queried in parallel and returned in the following order to the client.com Address: <IP address of DNS server> Non-authoritative answer: _sipinternaltls._tcp. and then click Run.com. At the command prompt.example.27.example. To verify that the FQDN of the Standard Edition Server can be resolved 1. When you are finished. where the IP address returned is the IP address of the Standard Edition Server.176. and then press ENTER. _sip._tcp.example. verify that the FQDN of the Standard Editon Server can be resolved by DNS. The output displayed for the TLS record is as follows: Server: <dns server>. 5. After you configure the DNS records.117: 172.com server1. Log on to a client computer in the domain. In the Open box. At the command prompt. 1.com SRV service location: priority = 0 weight = 0 port = 5061 svr hostname = server1. and then press ENTER. 4. In the Open box. _sipinternal. Log on to a client computer in the domain with an account that is a member of the Administrators group or has equivalent permissions. Reply Reply Reply Reply from from from from 172.176. 2._tcp.176. 3. and then press ENTER.

. The client uses the SRV record that is returned successfully. For more information on remote user access.0. For more information about editing the client registry and configuring policy settings for the client. ensure that IIS is installed. _sip. you install all the server components on one physical computer. see the Microsoft Office Communicator 2007 Deployment Guide. The steps are as follows: 1. If your DNS infrastructure prohibits configuration of these DNS records.Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 9 4.for external TCP connections where <domain> is the SIP domain used by your internal clients The last two queries are useful when clients are connecting from outside your network.<domain>. Step 3: Deploy a Standard Edition Server When you deploy a Standard Edition server. 6. 2. the client performs a lookup for sipinternal. 4. MSXML 6._tcp. Microsoft Visual J#® development tool. If the client does not find sipinternal. Enable Audio/Video conferencing and Web conferencing. 3. You do not need to install them separately. After the SRV record is returned.<domain> . see the Microsoft Office Communications Server 2007 Edge Server Deployment Guide. and it does not try any other SRV records. Configure certificates. These steps are explained in detail in the following sections. Note To deploy Office Communications Server Standard Edition Before you install the server. Start the services. Install Office Communications Server Standard Edition.0 SP1 development system. If the explicit lookup does not produce results. the client performs an explicit lookup of sip. Configure Standard Edition server. and the Microsoft .NET Framework 2. If no records are found during the DNS SRV query.0 SP1 Parser. Validate your server configuration. 3. Setup automatically installs Microsoft SQL Server™ 2005 Express Edition with SP2. 5. a query is performed for the DNS A record for the host name that is returned by the SRV record. When you run the Deployment Tool.<domain>.<domain>.<domain>. you can manually edit the client registry to point to the appropriate home server. the Microsoft Visual C++® 8. it performs a lookup for sipexternal.1 Install Office Communications Server Standard Edition Use the following procedure to deploy Office Communications Server Standard Edition.

Browse to the location where you want the files to be installed. If this happens. and then enter the password for the account. The default account is RTCComponentService. If you are installing from a network share. On the Welcome to the Deploy Server Wizard page. ensure that you use a strong password that meets your organization’s Active Directory password requirements. 8. 10. On the Location for Server Files page. ensure that you use a strong password that meets your organization’s Active Directory password requirements. do one or more of the following: • Verify that Internal web farm FQDN displays your server FQDN. Log on the server where you want to install Standard Edition server as a member of the DomainAdmins and the RTCUniversalServerAdmins groups or equivalent permissions. and then click Next. Review the license agreement. click Next. Note When you create a new account. and Address Book files. do one of the following: • • To accept the default location where the files will be installed. When you are finished. click Next. 6. enter the name of a new or existing service account that will run the Audio/Video Conferencing Server and Web Conferencing Server components on this computer.10 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007 Deployment Guide 1. On the Main Service Account for Standard Edition Server page. For a new account. and then click I accept the terms in the license agreement if you agree to the terms of installation. The default account is RTCService. When you are finished. To install the files at another location. and then try again. 3. This FQDN is used by internal users for client download of Web conferencing content. activation may fail until the account has been replicated in Active Directory. On the Component Service Account for this Standard Edition Server page. distribution group expansion. Click Deploy Standard Edition Server. enter the name of a new or existing service account that will run the core Office Communications Server service on this computer. On the Web Farm FQDNs page. The Deployment Tool will start automatically. At Deploy Server. 4. 5. and then enter the password for the account. wait until the account has been replicated. 7. 9. Insert the Microsoft Office Communications Server 2007 CD. go to the \Setup\I386 folder. click Browse. click Next. and then double-click Setup. . For a new account. click Run. (Required to continue installation) To continue.exe. click Next to continue. click Next to continue. 2.

verify that <Success> appears under the Execution Result column. as documented in the Microsoft Office Communications Server 2007 Edge Server Deployment Guide. 3. When you are finished. It is also used by anonymous and federated users to download Web conference content. Close the log window when you finish. Note Setup automatically detects the best location for the files. distribution group expansion. review the settings that you specified. In the log file. the Standard Edition server. the Address Book Server is configured automatically. see the Microsoft Office Communications Server 2007 Administration Guide . On the Ready to Deploy Server page. For information about changing Address Book Server settings. If you are satisfied with them. Do not place these files on the system disk or page file disk. 14. Important If you plan to deploy edge servers for external user access. On the Location for Database Files page. click Next to install. 15. When you are finished. When the files have been installed and the wizard has completed. 12. 16. 11. we recommend that you configure the external URL during your Standard Edition deployment. you will need to use the LcsCdm. click Next. place each database and transaction log file on a separate physical disk to improve performance. select the View the log when you click Finish check box. use the Configure Server Wizard to configure it. Note To configure Office Communications Server Standard Edition In Office Communications Server 2007. For details about external user access.exe command-line tool. Look for <Success> Execution Result at the end of each task.2 Configure Standard Edition Server After you have deployed your Standard Edition server. click Next.Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 11 • If you will enable external user access or federated user access to Web conferences. and then click Finish. click Next. This FQDN is used by external users for client download of Web conferencing content. If possible. under External Web farm FQDN (optional). to accept the default directories for user database and transaction log files. type the FQDN that resolves to the external IP address of your reverse proxy. If you create this URL later. see the Microsoft Office Communications Server 2007 Edge Server Deployment Guide. and Address Book files. 13.

click Run. then select the Use this server or pool to authenticate and redirect automatic client logon requests check box. click Next. At Configure Server. On the Client Logon Settings page. If this server or pool will also be used as a authenticate and redirect requests for automatic sign-in. Log on to your Standard Edition Server as a member of the RTCUniversalServerAdmins group or with equivalent user rights. and then click Next. you must designate one (and only one) Enterprise pool or Standard Edition Server to authenticate and redirect client sign-in requests. do one of the following: • If the Office Communicator clients and Microsoft Office Live Meeting 2007 clients in your organization will use DNS SRV records for automatic sign-in. The Deployment Tool will start automatically. 6. On the External User Access Configuration page. click Some or all clients will use DNS SRV records for automatic logon. 5. • If the Office Communicator clients and Live Meeting 2007 clients in your organization will not be configured to use automatic sign-in. On the SIP domains page. Click Next. and then click Next. select the server from the list. select the check box for the domains that will be supported by the server for automatic sign-in. verify that your SIP domain appears in the list. If it does not. click Clients will be manually configured for logon. 11. do one of the following: . type your SIP domain. 9. 7. you selected Some or all clients will use DNS SRV records for automatic logon. and then click Add. click Deploy Standard Edition Server. skip to the next step. Insert the Microsoft Office Communications Server CD. and then double-click setup. On the Welcome to the Configure Pool/Server Wizard page. on the SIP Domains for Automatic Logon page.12 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007 Deployment Guide 1. 4. When you are finished. Repeat these steps for all other SIP domains that the Standard Edition server will support. If in the previous step. Otherwise. If you are installing from a network share. On the Server or Pool to Configure page. 3. 2. click the SIP domains in your environment box.exe. click Next. go to the \Setup\I386 folder. Note When you configure automatic client sign-in. 10. 8. In the Deployment Tool.

select the View the log when you click Finish check box. On the Ready to Configure Server or Pool page. Assign an existing certificate.3 Configure Users in this document. click Next. 3. To configure a new certificate . All Office Communications Servers use MTLS to communicate with one another. instead. and then click Finish. 14. 13. You can configure additional SIP server. Each client will also need to trust the certificate that the server is using in order to connect to the server by using TLS. and assign a new Web certificate with enhanced key usage for server authentication. domain. Close the log window when you finish. or the Microsoft Office Communications Server 2007 Edge Server Deployment Guide. 15. create. the certificate must be assigned by using Internet Information Services (IIS) Manager. and then click Next to configure the Standard Edition server. You can use the same certificate for the Web Components Server. Microsoft Office Communications Server 2007 Archiving and CDR Server Deployment Guide. review the settings that you specified. but presence and IM communications may not work properly. • 12. You can use the Certificates Wizard on a Standard Edition server to do the following: • • Request. In the log file. If you have not deployed any edge servers. When you are finished. click Configure for external user access now. but the certificate for the Web Components Server must be assigned separately in IIS.Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 13 • If you have deployed your edge servers and have configured all necessary settings as described in the Microsoft Office Communications Server 2007 Edge Server Deployment Guide. For details about configuring SIP user settings. verify that <Success> appears under the Execution Result column. users may be able to sign in to Office Communications Server. For details about completing this portion of the wizard. click Do not configure for external user access now. and forest settings as described in the Microsoft Office Communications Server 2007 Administration Guide. Look for <Success> Execution Result at the end of each task to verify Standard Edition server configuration completed successfully. You cannot use the Certificates Wizard to the assign the certificate to the Web Components Server. refer to the edge server document.3 Configure Certificates Office Communications Server requires certificates on each Standard Edition server in order to use MTLS (TLS with mutual authentication). When the files have been installed and the wizard has completed. see 4. If you do not configure MTLS on each server.

6. 8. do the following: • • • Under Name. In Subject Alternate Name. You must also have permission from your certificate authority to request a certificate. 2. 4. and then click Next. If you are installing from a network share. go to the \Setup\I386 folder.<domain> if all of the following are true: • Your organization supports multiple SIP domains • Clients are using automatic configuration • This server is the first server that clients connect to If you configured clients for automatic sign-in. enter a meaningful name for the certificate that this server will use for Office Communications Server communications. the Certificate Wizard automatically added these SIP domains to the certificate request. and then double-click setup. click Next. . Note SANs are required on your server for each supported SIP domain in the format sip. On the Delayed or Immediate Request page. 10.14 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007 Deployment Guide 1. click Send the request immediately to an online certification authority. On the Organization Information page. When you are finished. 11. At Configure Certificate. Under Bit length. On the Welcome to the Certificate Wizard page. click Run. click Create a new certificate. A higher bit length is more secure. On the Your Server’s Subject Name page. but it can degrade performance. click Next. 9. do the following: • • In Subject Name. 5. verify that the server FQDN is displayed. type or select the name of your organization and organizational unit. and then click Next. verify that the required entries exist. Log on to your Standard Edition server as a member of the Administrators group and the RTCUniversalServerAdmins group. Clear the Mark cert as exportable check box.exe. 7. The Deployment Tool will start automatically. On the Name and Security Settings page. Click Deploy Standard Edition Server. and then click Next. Insert the Microsoft Office Communications Server 2007 CD. On the Available Certificate Tasks page. select the bit length that you want to use for encryption. 3.

and then click Next. the administrator must manually approve or deny the certificate issuance request on the issuing CA before you can assign it. 20. 18. Log on to your Standard Edition server with an account that is a member of the Administrators group and the RTCUniversalServerAdmins group and has permissions to request and assign a certificate from your certificate authority. If your CA is configured for automatic approval. enter the Country/Region. 2. On the Available Certificates page. 7.contoso. Do not use abbreviations. Type the user name and password that you use for the external CA. Submit this file to your CA (by e-mail or other method supported by your organization for your Enterprise CA). A dialog box appears and informs you that the settings were applied successfully. Click Specify the certificate authority that will be used to request this certificate. On the Certificates Wizard completed successfully page. 15.Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 15 12. On the Geographical Information page. On the Request Summary page. 17. On the Welcome to the Certificate Wizard page. click Run. go to the \Setup\I386 folder. click Next. 5. At Configure Certificate. The Deployment Tool will start automatically. Click Finish. and then double-click Setup. 13. State/Province. click Next. 3. If your CA requires CA administrator approval to issue a certificate. Click OK. and then click your certification authority (CA). If you are installing from a network share. 19.com\CAserver1. click Next. If you type the name of an external CA. click the certificate that you want to assign to the server. Click Deploy Standard Edition Server. CA. When you are finished. and then type the name of your CA in the box in the format <CA_FQDN>\CA_instance> For example.exe. When you are finished. Insert the Microsoft Office Communications Server 2007 CD. Do one of the following:   Click Select a certificate authority from the list detected in your environment. 4. On the Available Certificate Tasks page. and then click Next. click Next. and then click OK. 14. a dialog box appears. and City/Locality. To configure an existing certificate 1. and then click Next. review the settings that you specified. When you are finished. 6. proceed to the next procedure. . 16. On the Choose a Certification Authority page. click Assign. click Assign an existing certificate. the wizard attempts to automatically detect any CAs that are published in Active Directory.

5. and then double-click setup. 13.exe. see the Microsoft Office Communications Server 2007 Active Directory Guide. 2. Expand the Web Sites node. Click the Directory Security tab. 8. 11. 12. Assign the Web Components Server (IIS) Certificate Assign the certificate to the Web Components Server by using the Internet Information Services (IIS) Manager. and then click Properties. review the certificate assignments. and then click Next. Under Secure communications. Click Assign an existing certificate. Click Start. click Deploy Standard Edition Server. go to the \Setup\I386 folder. and then expand the Internet Information Services (IIS) Manager node. and then click Next to assign the certificate. 10. 3. 2. 9. Expand the Services and Applications node. and then click Next. 3.4 Start the Services Confirm that the Active Directory changes have replicated before you start the services. and then click Computer Management. In the deployment tool. click Administrative Tools. To start the services 1. . click Next. 7. Review the certificate details. Click OK to close the Default Web Site Properties page. 3. Click Finish to exit. Insert the Microsoft Office Communications Server 2007 CD. On the SSL Port page. If you are installing from a network share. The Deployment Tool will start automatically. Select the certificate that you requested by using the Certificates Wizard. click Server Certificate.16 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007 Deployment Guide 8. right-click Default Web Site. For more information about the Active Directory changes that occur when you deploy Office Communications Server. and then click Next to assign the certificate. To assign the certificate to the Web Components Server (IIS) 1. 6. click Control Panel. Click Finish. On the Configure the Certificate(s) of your Server page. On the Welcome to the Web Server Certificate Wizard page. verify that port 443 will be used for SSL. Log on to the server as a member of the Administrators group. 9. 4. and then click Next. Log on to your Standard Edition Server with an account that is a member of the RTCUniversalServerAdmins group or has equivalent user rights.

Note If a service does not respond to the wizard in a timely fashion. and then click Finish. In the log file.” • “Federation: Disabled.5. click Run. Note If you have not configured Enterprise Voice or deployed edge servers.1 Validate Your Front End Server Configuration Use the following procedure to validate Front End Server configuration. select the View the log when you click ‘Finish’ check box. When the wizard has completed. Validating server functionality included four tasks: • • • • Validate Front End Server functionality Validate Web Components Server functionality Validate Web Conferencing Server functionality Validate A/V Conferencing Server functionality These tasks are explained in detail in the following sections.” You can safely ignore these warnings. the log file will show that a service did not start successfully. If the log file shows that one or more services failed to start. 7. verify that <Success> appears under the Execution Result column. 3. Look for <Success> Execution Result at the end of each task to verify each service on the Standard Edition server started successfully. check the Office Communications Server 2007 event log for errors or warnings. 3. you will get the following warning messages: • “One or more phone usages are not assigned to any route or VOIP policy. 5. Warning [0x43FC200C] Not all checks were successful. At Start Services. Close the log window when you finish. 8.Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 17 4.5 Validate Your Server Configuration After you deploy the server and configure the certificates. On the Welcome to the Start Services Wizard page. Warning [Ox43FC200C] Not all checks were successful. To validate your Front End Server configuration . verify that the server is correctly configured. click Next. Click Next again to start the services. 6.

6. click Next. 7. When you are finished. When the wizard is complete. To validate your Web Components Server configuration 1. In the deployment tool. Close the log window when you finish. In the log file. You can perform additional validation of server functionality by using the steps described in Validation and Troubleshooting Hints in this document. On the Welcome to the Office Communications Server 2007 Validation wizard page. and then click Finish. Log on to a server in your domain as a member of the RTCUniversalServerAdmins group. 5. 10. On the Validation steps page. go to the \Setup\I386 folder. Clear the Validate SIP Logon (1-Party) and IM (2-Party) and Validate IM Conference (2-Party) check boxes. You can rerun the Validation Wizard and select these tasks after you have created and enabled users for Office Communications Server. . select the Validate Local Server Configuration check box. 4. do any or all of the following: • • To validate that the Office Communications Server is configured correctly. select the Validate Connectivity check box. click Deploy Standard Edition Server. 8. click Next. 3. Log on to a server in your domain as a member of the RTCUniversalServerAdmins group. verify that <Success> appears under the Execution Result column. select the View the log when you click Finish check box.5. Look for <Success> Execution Result at the end of each task. Insert the Microsoft Office Communications Server CD. the Web Conferencing Server. 9. 3. and then double-click Setup.18 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007 Deployment Guide 1. At Step 1 Validate Front End Server Functionality. To verify that the Office Communications Server has connectivity to the BackEnd Database. If you are installing from a network share. 2.2 Validate Your Web Components Server Configuration Use the following procedure to validate your Web Components Server configuration. and the Audio/Video Conferencing Server. The deployment tool will start automatically. • Note The Validate SIP Logon (1-Party) and IM (2-Party) and Validate IM Conference (2-Party) options determine whether your enabled users can log on and send instant messages to one another. click Run. Click Validate Server Functionality.exe.

exe. and then double-click Setup. On the Welcome to the Office Communications Server 2007 Validation wizard page. go to the \Setup\I386 folder. The deployment tool will start automatically. In the deployment tool. 10. Log on to your Standard Edition server as a member of the RTCUniversalServerAdmins group. If you are installing from a network share. The deployment tool will start automatically. Close the log window when you finish. To verify that clients have connectivity to the IIS directories where the Address Book files. 9. At Step 2. Click Next. On the Validation steps page. click Run. At Step 3. verify that <Success> appears under the Execution Result column. 4. 5.5. Insert the Microsoft Office Communications Server CD. click Next. 5. go to the \Setup\I386 folder.3 Validate Your Web Conferencing Server Configuration Use the following procedure to validate your Web Conferencing Server configuration. In the log file. click Run. do any or all of the following: • • To validate that the Office Communications Server is configured correctly. In the deployment tool. Click Validate Server Functionality. 6. To validate your Web Conferencing Server configuration 1. Validate Web Conferencing Server Functionality. Look for <Success> Execution Result at the end of each task. Click Validate Server Functionality. 6. select the Validate Local Server Configuration check box. Insert the Microsoft Office Communications Server CD.exe. Validate Web Components Server Functionality. click Deploy Standard Edition Server 4. On the Welcome to the Office Communications Server 2007 Validation wizard page. do any or all of the following: . 3. click Next. select the View the log when you click Finish check box. 7. 3. On the Validation steps page. 2. When the wizard is complete. 3.Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 19 2. 8. and compliance data are stored. If you are installing from a network share. group expansion and meeting content. click Deploy Standard Edition Server. and then click Finish. select the Validate Connectivity check box. You can perform additional validation of server functionality by using the steps described in Validation and Troubleshooting Hints in this document. and then double-click Setup. 7.

Log on to a server in your domain as a member of the RTCUniversalServerAdmins group. To verify that the A/V Conferencing Server has connectivity to Front End Servers and A/V Edge Servers. 9. 7. and then click Finish. select the View the log when you click Finish check box. click Deploy Standard Edition Server 4. 3. 6. • • To validate that the Office Communications Server is configured correctly. Look for <Success> Execution Result at the end of each task. 5. and then click Finish. At Step 4. If you are installing from a network share. select the View the log when you click Finish check box. In the log file. In the log file.exe. Click Next. click Run. When the wizard is complete. 10. On the Validation steps page. When the wizard is complete. Insert the Microsoft Office Communications Server CD. The deployment tool will start automatically. 2. verify that <Success> appears under the Execution Result column. verify that <Success> appears under the Execution Result column. click Next.20 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007 Deployment Guide • • To validate that the Office Communications Server is configured correctly. 10. 9. select the Validate Connectivity check box. In the deployment tool.5.4 Validate Your A/V Conferencing Server Configuration Use the following procedure to validate A/V Conferencing Server configuration. and then double-click Setup. You can perform additional validation of server functionality by using the steps described in Validation and Troubleshooting Hints in this document. Click Validate Server Functionality. Close the log window when you finish. select the Validate Local Server Configuration check box. On the Welcome to the Office Communications Server 2007 Validation wizard page. select the Validate Connectivity check box. do any or all of the following: 8. go to the \Setup\I386 folder. select the Validate Local Server Configuration check box. Close the log window when you finish. Validate Audio/Video Conferencing Server Functionality. if deployed. Look for <Success> Execution Result at the end of each task. Click Next. To verify that the Web Conferencing Server has connectivity to the Front End Server and to any Web Conferencing Edge Servers (if configured). . 3. 8. To validate your A/V Conferencing Server configuration 1.

click Anonymous participants. prevents users from organizing conferences that use the Web conferencing or audio/video (A/V) conferencing features. and then click Allow users to invite anonymous participants. Right-click the Forest node. 3. and then click Disallow users from inviting anonymous participants. which all users are initially configured to use . To allow access to these features. click Anonymous participants. and then click Global Properties. and then click Office Communications Server 2007.Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 21 You can perform additional validation of server functionality by using the steps described in Validation and Troubleshooting Hints in this document. all attendees of this meeting will use her meeting policy and so no IP audio will be available. as an attendee of Bob’s meeting Sue will be able to use IP audio. 4. 2. The meeting policy that applies to a meeting organizer also applies to all attendees of the meeting. Sue organizes a meeting. however. and then do one of the following: • To allow all users to organize Web conferences that include anonymous participants. Click Start. To configure Audio/Video and Web conferencing 1. you must configure a policy that enables Web conferencing and A/V conferencing and then assign this policy to your users. • . if Bob organizes a meeting with IP audio enabled and the meeting policy for Sue does not allow her to use IP audio. or you can apply the policy on a per-user basis. To prevent all users from organizing Web conferences that include anonymous participants. If your organization plans to support only instant messaging and presence features. you can skip to the next deployment task. This is the default setting. click Administrative Tools. 3. The default meeting policy. If. conferencing enables Office Communications Server users to organize and invite other users to Web conferences that are hosted on your own on-premise servers. click Control Panel. Log on as a member of the RTCUniversalServerAdmins group to an Office Communications Server or to any computer that is joined to an internal domain and that has the Office Communications Server administrative tools installed. For example.6 Enable Audio/Video Conferencing and Web Conferencing Note Instant messaging and presence are enabled by default when you deploy Office Communications Server. You can define the policy to as a global policy so that it applies to all users. click Properties. In Office Communications Server. Click Meetings.

5.22 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007 Deployment Guide • To allow only some users to organize Web conferences that include anonymous participants. and then click the name of the policy that defines the features that you want to enable for all users. 7. 12. 10. After you finish editing the features that are enabled by each policy. Click Apply.3 Configure Users in this document. 9. click OK. as described in 4. If you expect heavy audio/video traffic in your environment. If you are deploying Office Communications Server 2007 in a new environment without existing Live Communications Servers. To enable video. See Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic in this document for more information. In the Policy Definition list. 11. are allowed to invite anonymous participants. To enable audio. use the Migrating to Microsoft Office Communications Server 2007 guide. and then click Use per user policy. decide which policy to apply to Web conferences organized by users. you can optimize your network adapter settings to accommodate this volume. create and enable users as described below. click the name of a policy. Ensure that you follow the procedures in 4. and then click Edit. Click OK. select the Enable IP audio. To apply different policies to different users. click Anonymous participants.3 Configure Users in this document to configure the Web conferencing policy for individual users. and then click Enforce per user. . select Enable IP video. 6. For more information about administering Web and A/V conferencing features. When you are finished. click Global policy. refer to the Microsoft Office Communications Server 2007 Administration Guide. Important If you are deploying Office Communications Server 2007 in an environment with existing Live Communications Server 2005 with SP1 servers and Communicator 2005 users. click Global policy. In the Edit Policy dialog box. Only users that you enable individually. 8. Step 4: Create and Enable Users After you have deployed and configured your Standard Edition server. Do one of the following: • • To apply the same policy to all users. you must create users and then enable them for the Office Communications Server features that you want them to use. select the Enable Web conferencing check box.

enable the users so that they can connect to Office Communications Server. and then click OK. Click Start. In the Open box.1 Create and Enable Users for Office Communications Server In order for users to access the features and functions that are provided by Office Communications Server. or enhanced. to sign in. Right-click the Users container or another container where you want to create your users.msc. and then click Run. The following sections explain these steps in detail. or calendar state. you must create user accounts and then configure the accounts for Office Communications Server.Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 23 4. 2. and then click User. type dsa. see the Migrating to Microsoft Office Communications Server 2007 guide for more information. 3. . location. When you enable users for Office Communications Server 2007. Log on as a member of the DomainAdmins group to your Standard Edition server or to another server in the same Active Directory domain that has the Office Communications Server administration tools installed. including Communicator Web Access (2005 release) or Communicator Mobile (2005 release). Enable Users for Office Communications Server 2007 After you create users in Active Directory. The user will then no longer be able to sign in to Live Communications Server 2005 with SP1 and cannot use any previous version of Communicator. Complete the New Object . Categories are collections of presence information. 4. Important If you enable enhanced presence for a user and the user signs in to Office Communications Server by using the Office Communicator 2007 client. Create User Accounts You create user accounts in Active Directory. click New.User wizard. Office Communications Server provides the infrastructure to enable client applications to publish and subscribe to extended. If you are deploying Office Communications Server 2007 in an environment with Live Communications Server 2005 with SP1 servers or Communicator 2005 users. The enhanced presence infrastructure includes categories and containers. depending on what a user wants the others to be able to see. such as status. they are automatically enabled for enhanced presence. You cannot undo this setting. the user account is converted to use enhanced presence. Containers are logical buckets into which clients group instances of various categories of presence information for publication to other users. presence information. To create user accounts 1.

<lastname>@. Verify that the user or users were enabled successfully. To generate the SIP address using the user’s full name. type dsa. rightclick the user name. and then select the Office Communications Server domain. 9. and then select the Office Communications Server domain. 5.24 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007 Deployment Guide To enable users for Office Communications Server 1. expand the Users folder or other organization unit where your user accounts reside. On the Welcome to the Enable Office Communications Server Users Wizard page. see the Microsoft Exchange Server documentation. • • • Note If you need to configure SIP addresses using a different format from the options presented. In the Open box. On the Select Server or Pool page. 6. When you are finished. and the click Run. Click Start. 7. Log on as a member of the RTCUniversalUserAdmins group to an Office Communications Server or another server that is joined to an Active Directory domain with the Office Communications Server 2007 administration tools installed. 4. To generate the SIP address from the user’s principal name.msc. 2. click Use userPrincipalName. click Next. For each user whom you want to enable for Office Communications Server. 8. Select this option only if you have configured an e-mail address for your users. select the Standard Edition server from the list. . click Next. and then click Next. you can enable users individually or use the Office Communications Server 2007 Software Development Kit to enable a group of users. . and then click OK. specify how to generate the SIP address by doing one of the following: • To generate the SIP address from the user’s e-mail address. click Use the format: <first name>. click Use user’s email address. To generate the SIP address using the user’s SAM account. 3. and then click Enable users for Communications Server. click Use the format: <SAMAccountName>@. On the Specify Sign-in Name page. and then click Finish. To create a mailbox for the users to receive Web conference invitations. In the console pane.

3. 4. Public IM connectivity. and then click Office Communications Server 2007. Log on to a server with the Office Communications Server 2007 administration tools as a member of the RTCUniversalUserAdmins group or with equivalent user rights. 4. Select the check boxes for the features that you want to configure for the selected user or users: Federation. Select one of the following: • • To configure all users the Standard Edition Server. Ensure that the global settings for desired features are such that they can be configured for individual users. When you are finished.Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 25 4. as appropriate. expand Users. 4. click Next. Confirm that the users you successfully enabled for Office Communications Server are listed. .2 Wait for User Replication to Complete Before you try to test or verify any end user functionality. and then click Users. Expand the forest node and the pool node. right-click the user account that you want to configure.6 Enable Audio/Video Conferencing and Web Conferencing in this document. Log on to a server with the Office Communications Server 2007 administration tools as a member of the RTCUniversalUserAdmins group or with equivalent user rights. and then click Office Communications Server 2007. On the Welcome to the Configure Users Wizard page. Click Start. some of options in the following steps will be unavailable. Click Start. 2. and then expand your Standard Edition Server. For each feature. To configure an individual user. The User Replicator logs an event with ID 30024when replication completes successfully. 2. Archive internal messages. Expand the Forest node. To verify that users were enabled 1.3 Configure Users Procedures to configure global meeting settings are included in 3. 3. To configure users for Office Communications Server 1. right-click Users. expand Standard Edition Servers. click Control Panel. click Next. Enhanced Presence. click Control Panel. click Enable or Disable. and then click Configure users. verify that the changes you made to enable users have been replicated by the Office Communications Server User Replicator. in the console pane. 6. All other user configuration settings are described in this section. click Administrative Tools. Note If you did not configure your global properties on the Meetings tab to enforce policies per user. click Administrative Tools. 5. and Archive federated messages. In the details pane. Remote user access.

Users of Communicator 2005 can still sign in to Office Communications Server if their account has been moved to an Office Communications Server. For details.msi file). see the e Microsoft Office Communications Server 2007 Enterprise Voice Planning and Deployment Guide. for example. Select the Organize meetings with anonymous participants check box. and then click Finish to close. and then click Next. To enable Enterprise Voice and configure the Enterprise Voice policy that will be applied to the selected users. To install Communicator 1. an Active Directory Domain Services Group Policy. The following procedure shows how to run the MSI to install Communicator. 5. and then double-click it. see the Migrating to Microsoft Office Communications Server 2007 guide. but there are important considerations if you choose to have users running both Communicator 2005 and 2007 in your environment. Step 5: Deploy the Office Communicator 2007 Client Install and configure Microsoft Office Communicator 2007 on each client in your organization. a scripted deployment. click the name of the policy that you want to apply to the selected user or users. click Next: 9. click Next. see the Microsoft Office Communicator 2007 Deployment Guide. and then select the Enable Voice check box. Download Communicator.1 Deploy Office Communicator Deploy Office Communicator 2007 by using a Windows Installer package (. select the Change Enterprise Voice Settings check box. Note In order to configure a particular Enterprise Voice setting for a specific user. On the Welcome to Microsoft Office Communicator 2007 Setup page. Systems Management Server (SMS). or any other third-party software that supports . Click Next. For more information about Enterprise Voice. In the Select a Voice policy for the users list. Verify the status of each user configuration operation. In the Select a meeting policy for the users list.msi.msi-based deployment. Select the Change meeting policy check box. run the package by using your organization’s preferred deployment method. 2. 8. and then click Allow or Disallow. 10. This section provides high-level guidance on how to deploy Office Communicator 2007. the corresponding setting under Voice Properties must be configured to allow enforcement on a per user basis. .26 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007 Deployment Guide 7. To deploy Office Communicator. When you are finished. click the name of the policy that you want to apply to the selected users. For indepth information.

as follows: msiexec /qn /i Communicator. click OK. 4. 3.Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 27 3. and then click Options. click Finish. accept the default folder or click Browse and browse to another folder. Click OK. 4. 5. and then click Options. To test access to the server from inside your organization. and then click OK again. and then click Automatic Configuration. . On the Personal tab. Review the license agreement. Open Microsoft Office Communicator 2007. click Tools. 3. 4. Use the following procedure on each client to enable your users to connect to Office Communications Server. Click TCP if you configured the server so that clients can connect by using TCP. or click TLS if you configured the server so that clients can connect only by using TLS. by default Communicator is configured for automatic connectivity. click Advanced. Click the down arrow in the Office Communicator title bar. 2. When you are finished. To configure automatic connectivity for Office Communicator clients 1. On the Configure Microsoft Office Communicator 2007 page.msi 5. click Advanced. Click the down arrow in the Office Communicator title bar. Quiet-Mode Installation You can suppress the installation user interface completely when deploying Communicator 2007 by using the Windows Installer command-line option /qn in your script. click Next. On the client computer. To configure Office Communicator clients manually 1. If you need to. 2. and then click OK again. you can modify this setting. click Tools. On the Personal tab. When you are finished. and then click Manual Configuration. and then click I accept the terms in the License Agreement if you agree to the terms of installation (required to continue installation).2 Configure Client Sign-In After the DNS records have been configured. start Microsoft Office Communicator 2007. click Internal server name or IP address. 5. Click Next to continue. When the wizard has completed. and then type the internal Standard Edition server FQDN or IP address.

In Server or Pool. 4. you can use the Validation Wizard. 6. Insert the Microsoft Office Communications Server 2007 CD. on the Federation and Public IM Connectivity page. In Server or Pool. You can also test the Office Communications Server configuration for Office Communicator by signing in to Office Communicator on two computers from two different accounts that you have created on the server and then conducting an IM conversation between the two clients. 9. and then double-click Setup. 8. On the Welcome to the Office Communications Server 2007 Validation wizard page. To test Office Communications Server configuration for Office Communicator clients using the Validation Wizard 1. To verify that enabled users can sign in. This account will be used with the first account you specified to test IM functionality between two users. On the Second user account (required) page. When you are finished. 3. select the Validate SIP Logon (1-Party) and IM (2-Party) check box. click Test connectivity of internal and federated users. When you are finished. Otherwise. select the server where the user is hosted. If you are installing from a network share. 2. . click Next. enter a user name.3 Test Office Communications Server Configuration for Office Communicator To test the Office Communications Server configuration for Office Communicator. click Deploy Standard Edition Server. If you have configured federation or public IM connectivity. 5. clear the check box. click Next.exe. In the deployment tool. At Validate Server Functionality. 13. select the Check this box to use client autologon for validation check box to verify that automatic client sign-in works. and password of a test user or another user enabled for SIP.28 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007 Deployment Guide 5. and then type the SIP URI of a federated user account with which you want to test this functionality. 10. go to the \Setup\I386 folder. sign-in name. and password of another test user (another user enabled for SIP). 7. click Run. Log on to a server in your domain as a member of the RTCUniversalServerAdmins group. 11. If you configured your Office Communicator clients for automatic sign-in and have configured the required DNS records. select the server where the user is hosted. On the User Account page. Click Next. click Next. enter a user name. The Deployment Tool will start automatically. 12. sign-in name.

6. On the second computer. open Communicator and then type the full SIP URI of the account that is logged in on the second computer. in User name. Step 6: Deploy the Live Meeting 2007 Client Web conferences require the Microsoft Office Live Meeting 2007 client. To deploy the meeting client. 7. 4. On the first computer. and then type a message and press ENTER. along with detailed step-by-step instructions.1 Deploy the Live Meeting Client You deploy the Microsoft Office Live Meeting client by using a Windows Installer package (. and then press ENTER. Log on to a client computer with a user account that is enabled for Office Communications Server. On the first computer. see the Microsoft Office Communicator 2007 Testing and Troubleshooting Guide. Look for <Success> Execution Result at the end of each task to verify that the server was added successfully to the Standard Edition server. see Deploying the Microsoft Office Live Meeting 2007 Client with Office Communications Server 2007. In Password. In the results list. 8.msi file). enter your SIP account. When the wizard is finished. 2. If you are prompted for credentials. 5. run the package by using your organization’s preferred . 10. Click Sign In. verify that <Success> appears under the Execution Result column. Type a message. Click Start. Repeat steps 1 through 7 on a second client computer using a second user account enabled for Office Communications Server. select the View the log file when you click Finish check box. 9.Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 29 14. and then click Microsoft Office Communicator 2007. 6. and then click Finish. For detailed information regarding Live Meeting 2007 client deployment. For a complete list of Communicator features to test. verify that the message was received. To sign in and test Communicator 1. 3. verify that the message was received. 11. Close the log window when you finish. In the Sign-in address. click Programs. In the log file. 15. double-click the name of the user logged in on the second computer. type the SIP username in one of the suggested formats. and then click Sign In. type the user account password.

com/r/rlidOCS? clid=1033&p1=LiveMeeting 2.exe application. and then click Open User Accounts. . the . 2.microsoft. To install the meeting client silently. at the command prompt.msi) from the LMSetup. To extract the LMConsole. On Windows Vista™.msi To verify installation of the client 1. type a sign-in name or verify that the sign-in name that appears in the Sign-in name box is valid. for example. so that the users do not see it or interact with the installation. Extracting the installer package You can extract the installer package (. Change the directory to the folder to which you copied the . and then click Microsoft Office Live Meeting 2007. Open a command prompt window: Click Start. type the following command: LMSetup. To install the Live Meeting client • At the command prompt. type the following command: msiexec /qn /I LMConsole. type cmd. In the Open box. 4. for example.msi) 1.exe instead of the Windows Installer package.msi-based deployment. Click the title bar down arrow. an Active Directory Domain Services Group Policy. you can use the “silent installation” option. 3. and then click OK.exe. You can download the Live Meeting 2007 client from the Microsoft Web site at: http://r. and then click Run. Copy the file LMSetup. or any other third-party software that supports .30 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007 Deployment Guide deployment method. use the /qn switch.Installer package will not work correctly unless the user runs Windows Installer as a member of the Administrators group. and then click All Programs. 3. Under Server. a scripted deployment.exe to a folder on your local hard disk. Point to Microsoft Office Live Meeting 2007. To extract the installer package (. from an administrative command line prompt.exe -out <drive>:\<folder path> Installing the Microsoft Office Live Meeting 2007 Client When you use Windows Installer to install the meeting client on users’ computers. Note End users who are installing the Live Meeting client manually should use LMSetup. Click Start.office.msi file. Systems Management Server (SMS).

and then distribute the add-in as you would from any other . the Welcome to Microsoft Office Live Meeting page contains a Meet Now button. You can download the addin from the Microsoft Web site at http://r. Select a document.msi. the user receives a meeting invitation through the Microsoft Office Outlook® messaging and collaboration client.2 Deploy the Outlook Add-in The Outlook Add-in is required for users to schedule Web conferences by using the Microsoft Office Outlook® messaging and collaboration client. 7. Verify that the file is added to the Live Meeting. 6. click Share. 6. Additionally. click Options. 2. In the Voice & Video pane. and then click Set Up Audio and Video.microsoft. if you have configured Office Communications Server 2007 to . The meeting invitation contains a URL to join the meeting. click Meeting. On the Microsoft Office Live Meeting Add-in Pack page. Use the wizard to select audio and video settings. 6. click Next to begin installation. Verify that you can use audio and video. Note Microsoft Office Outlook must already be installed on the computer where you install the Outlook add-in. If you are using an account that is authorized to organize meetings. and then double-click it. and then click Continue. After you deploy the Live Meeting client.Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 31 4. Download LMAddinPack. and then click Upload File (View Only). To deploy the Live Meeting 2007 Outlook add-in 1. 4. In the Live Meeting client.3 Customize Meeting Invitations You can customize meeting invitations by doing the following: • • Configuring meeting invitation URLs Configuring the organization name for meeting invitations Configuring Meeting Invitation URLs When a user is invited to a meeting.msi file.office. and then verify that the status is Connected. 5. click the More button (>>). Click Run. 3. Click Test Connection and verify that your Live Meeting sign-in information is successfully verified. Click Meet Now. When the wizard has completed.com/r/rlidOCS? clid=1033&p1=confadd. click Finish.msi). Click Content. and then click Open. deploy the Outlook add-in from the Outlook add-in Windows Installer file (. You must restart Outlook to use the add-in.

Users can click this link to download and install the Live Meeting 2007 client. but you can host your own support page on your own Web server. expand the pool. • • 3. Meeting client download URL. On the Office Communications Server 2007 server configured as the Web Components Server.office.microsoft. 2. You can only change the internal meeting client download URL. right-click the pool.com/r/rlidLiveMeeting? p1=12&p2=en_us&p3=LMInfo&p4=supportserver). both the internal and external URLs link to a Microsoft support page (http://r. For a Standard Edition Server. and then click Properties. not the external client download URL. click Properties. expand the forest node. Specify a URL for downloading the Live Meeting 2007 Client Host the support page on a Web server and specify the support URL 1. and then click Web Component Properties. the following URLs are available to meeting attendees: • Support page URLs. Click the Meeting Invitations tab.32 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007 Deployment Guide support meetings for both internal and external users. By default. right-click Web Components. expand Enterprise pools. open Office Communications Server 2007. In the console tree. and then do one of the following: For an Enterprise pool. • Use the procedures in this section to do the following: • • To specify a URL for downloading the Live Meeting 2007 Client . expand Standard Edition servers.

in the Internal box. Create a Web page (in any format) that provides support information for Office Communications Server Web conferencing users for internal use and an additional Web page for providing support information for external use. For example.Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 33 4.html or http://OCSServer1.com/meetings/int/clientdownload.html. To host the support page on a Web server and specify the support URL 1. 2.contoso. . Note After you copy the support page to the appropriate locations. http://eepool1. verify the following: • The URL that internal users will use to download the page works inside the corporate network only.com/meetings/int/clientdownload. • The URL that external users will use to download the page works from outside the corporate network.contoso. Under Live Meeting 2007 Client URL. Host the internal page on your internal Web server and the external Web page on your external Web server. type the URL that internal users will use to download the Live Meeting 2007 client.

• In the console tree. Under Technical Support URL. expand Enterprise pools.contoso. Log on as a member of the RTCUniversalServerAdmins group to an Office Communications Server or another server that is joined to an Active Directory domain with the Office Communications Server 2007 administration tools installed. http://eepool. point to All Programs. http://eepool.com/meeting/int/Tshoot. 1. right-click the pool. For example. click Properties. For example. expand the forest node. expand Standard Edition servers. expand Enterprise pools. and then click Web Component Properties. and then click Properties.html or http://OCSServer1. click Properties. • • In the console tree.contoso. and then click Web Component Properties.com/meeting/int/Tshoot. In the External box. and then click Office Communications Server 2007. 7.34 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007 Deployment Guide 3. 4. type the URL that external users will use to view the support page. right-click Web Components. For a Standard Edition Server. This name is sent to the Microsoft Office Live Meeting add-in for Microsoft Office Outlook for use in meeting invitations sent by users in this pool.contoso. 5. expand the pool. and then do one of the following: For an Enterprise pool. right-click Web Components.com/meeting/ext/Tshoot.html. • • 6. expand the forest node.html. • Specifying the Organization Name for Meeting Invitations You can also change the name of the organization that appears in the meeting e-mail invitation. expand Standard Edition servers. To change the organization name for meeting invitations Open Office Communications Server 2007.contoso. and then click Properties. right-click the pool.com/meeting/ext/Tshoot. and then do one of the following: For an Enterprise pool. . Click the Meeting Invitations tab. For a Standard Edition server. expand the pool.html or http://OCSServer1. do the following: In the Internal box. type the URL that internal users will use to view the support page. Open Office Communications Server 2007 administrative snap-in: Click Start.

Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 35 2. In the Microsoft Office Live Meeting dialog box that indicates the add-in was successfully installed. you can test the Office Communications Server configuration for Web conferencing by setting up a test conference. . On the Conferencing menu. click User Account. To set up a test conference 1.3 Configure Users in this document for details. On the General tab. See 3. 3. in the Organization type the name of your organization. Close Outlook. Open Microsoft Office Outlook. To perform this test. click OK.4 Set Up a Test Web Conference After you install the Live Meeting client and the add-in.6 Enable Audio/Video Conferencing and Web Conferencing and 4. and then restart it to initialize the add-in. 6. 2. 4. use two client computers that have both the Live Meeting client and the Outlook add-in installed and two user accounts that are enabled for Office Communications Server and that have a meeting policy that allows Web conferencing.

Microsoft Office Live Meeting dialog box appears because the client is unable to establish a connection to the server. and then type either the FQDN or the IP address of the external Standard Edition server. which indicates that the client can establish a connection to the server. and then type your domain password. 6. Do one of the following: • If the Microsoft Office Live Meeting dialog box appears because the client is able to successfully establish a connection to the server. Click OK to close the User Accounts dialog box. click Internal Server name or IP address. click OK. In the User Accounts dialog box. and then type the e-mail address of another user that is enabled for Office Communications Server and has a meeting policy that allows Web conferencing. Click User name and type your domain and user name in the following format: domain\username. click Schedule a Live Meeting. Click Password. In the e-mail template. • 8. open the invitation on both clients. If the Error . in the toolbar. 13. 12. If you configured the server so that clients can connect only by using TLS. 15. click TLS. When the second client receives the e-mail invitation for the scheduled Web conference. type a name for the conference. click OK. If the meeting link does not work. Select the Use the following user name and password check box.36 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007 Deployment Guide 5. 11. Click Test Connection. Select the Use these servers check box. 16. 14. and then click the Join the meeting link in each invitation. click TCP. click TLS. When you are finished. If you configured the server so that clients can connect by using TCP. Click Subject. To test access to the server from inside your organization. and then click Send. and then skip to step 12 to continue. and then click Advanced.If you configured the server so that clients can connect by using TCP. follow the instructions in the Troubleshooting section of the meeting invitation e-mail. click the Attendees list and verify that both users are listed. click External Server name or IP address. If you configured the server so that clients can connect only by using TLS. 10. and then type the name of your SIP account. click Sign-in name. . 7. click TCP. To test access to the server from outside your organization. After you have joined the Web conference from both computers. Click Test Connection and ensure that Microsoft Office Live Meeting dialog box appears. The Live Meeting client appears. click To. click OK. and then do one of the following: • • 9. and then type either the FQDN or the IP address of the internal Standard Edition server. In Outlook.

The client computer trusts the Certificate Authority. • . Test other Web conferencing features by using the instructions in the Microsoft Office Live Meeting 2007 Getting Started Guide. The server certificate is configured and. Check the SQL database by using SQL Query Analyzer to ensure that the RTC Server Local Group is a member of the “Server Role” on the RTC database. and check the Office Communications Server 2007 event log for error or warnings. See 3. use the Validation Wizard option to test SIP sign-in. ISSUE: Problems using the Web Components Server RESOLUTION: • Check the event log for error or warnings. Validation and Troubleshooting Hints ISSUE: Problems signing in with the client RESOLUTION: In order to troubleshoot user sign-in issues. Office Communications Server User Replicator has finished synchronizing the user’s information from Active Directory. Verify that the certificate for the Web Components Server has been correctly configured as described in Assign the Web Components Server (IIS) Certificate in this document. This can happen even when all services have started successfully. The Office Communications Server Standard Edition service (RTCSrv) is running. • • • • • ISSUE: Problems starting the services RESOLUTION: At times. All users’ SIP domains (at least the suffix) are reflected in the SIP Domain list in the global settings. verify that the user is enabled for Web conferencing by checking the user properties.6 Enable Audio/Video Conferencing and Web Conferencing and 4. The server has permissions on the database. the Start Services Wizard reports that there are failures when the services are started if one or more services do not respond in a timely fashion.3 Configure Users in this document for details on configuring these settings. You can also verify the following: • • The user is enabled and configured properly in Active Directory. is valid for client automatic sign-in. The certificate must match the domain suffix of the enduser’s SIP URI. Check for event codes by the OCS User Replicator in the Windows event log. You can also rerun the Start Services Wizard to verify the results. • If the user receives an “unauthorized 401” error message. if you are not using manual sign-in. You can check the Office Communications Server event log in the Windows event viewer to verify the services that have been started.Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 37 17.

If you need to generate an offline request or you are using a public CA. Check the Office Communications Server 2007 event logs on the client and the server for events that mention certificate-related issues. If Archiving or CDR was enabled after the Front End Server started. • Stop and restart Office Communications Server. Check the Archiving and CDR Server again to see if it is archiving messages. To request the certificate 18. ISSUE: Problems with archiving or CDR RESOLUTION: The certificate on the server may not be configured correctly.38 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007 Deployment Guide • If the user receives an error message that the server is unreachable. This section describes the procedures for requesting a certificate from a public CA. Verify that users are enabled for archiving and that archiving and CDR are configured on the Standard Edition Server • • • • Appendix A: Certificate Request Scenarios Note In order to configure certificates on the Edge Server. These examples can help you to determine the certificates that you need to request from your certification authority (CA). This section contains examples of various server FQDN and Web conferencing URL scenarios. 19. restart the Front End Server services (RTCSrv) to apply these changes. In the console pane of the snap-in. On the server on which you have installed Office Communications Server. click Administrative Tools. Sign out and then sign in again from Office Communicator. click Start. Check event logs for warnings or errors. expand the nodes until you reach the Standard Edition server that you installed. see the certificate instructions in the Microsoft Office Communications Server 2007 Edge Server Deployment Guide. Check that the queue name on the Archiving tab of the Standard Edition Server Properties dialog box points to a valid queue on the Archiving and CDR Server. verify that the IIS server is running. click Programs. and then click Office Communications Server 2007. Also verify that the Front End Server on which the Web Components Server is running has a valid service account and that the Front End Server service is enabled and is running by using the Service Control Manager. . and then try to send an instant message. use the following procedures to request and process the certificate.

Select Prepare the request now. Repeat these steps on the other Front End Servers. 32. If you are not an administrator for the certification authority. Select your Country/Region. . 31. Choose your CA. follow these steps to issue the certificate after you have generated the request. 9. 33. and then click Next.txt extension) for the certificate request. Click Subject name. 21. and then click Browse. follow the instructions in the following section. 3. 5. Click Finish. click Add/Remove Snap-in. Verify the path and file name of the certificate request file in the File name box. and then click Next. click Create a new certificate. and then click Save. 4. 26. 27. and then click Next. and then click OK. In the Open box. and then click Run. In the File menu. Clear the Mark cert as exportable check box. type the FQDN of the server. 25. and then click Next. Right-click the server name. 29. On the Available Certificate Tasks page. 30. 22. State/Province. 6. and then type the name for the new certificate. Click Another computer. and then click Next. Click Name. Click Browse. and then click Next. Click Organizational unit. Review the request information. Click Close. Click Add. type the name of your department. Click Organization. and then click Add. instead. 24. and City/Locality. To issue a certificate 1. enter a File name (with a . click Certification Authority. 8. On the Welcome to the Certificate Wizard page. and then click Certificates. Click Finish. Issuing the Certificate Request If you are an administrator on the certificate authority. and then click Next. and then click OK. click Next. 7. and then type your organization name. Submitting an Offline Request to a Public CA. Click Start. expand the Certification Authority node. 28. you can use the server name as the certificate name. 23. type mmc. 2. choose a location. In the snap-in. Click OK. and then click Next.Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 39 20. For example. but send it later.

Click Browse. Close the CA snap-in. 12. and then click Save. expand the nodes until you reach the Standard Edition server that you installed. . enter a File name (with an X. Repeat these steps on the servers in the pool for which you generated an offline certificate request.509 extension. click Next. click Programs. 6. choose the following options: • • • • Microsoft as the server platform IIS as the Version Web Server as the certificate usage type PKCS7 as the response format When the public CA has verified your information. click Start. the process will vary. 11. and then click Next. In the console pane of the snap-in. On the Welcome to the Certificate Wizard page. you will receive an e-mail message that contains the text that is required for the certificate. and then click Certificates. 4. or .cer.40 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007 Deployment Guide 10. On the server on which you have installed Office Communications Server. . verify that the certificate was downloaded correctly and that it has been bound to the local computer store. Click Process the pending request and install the certificate. and then click Next. 2. Right-click the Office Communications Server. If you are prompted. Locate the certificate issued to you by the CA.crt. In the Open Request File dialog box. do one of the following: • • Enter the location and file name of the . click Administrative Tools. 5. and then click Office Communications Server 2007. and then click Open. To process the certificate from the Public CA 1. In Path and file name. Process the Pending Certificate Request After you submit the certificate request. access the public CA site to submit the request. and then click Submit new request.txt) file that you created by using the wizard. but you generally need to supply your organizational and contact information. Right-click your CA. navigate to and click the certificate request (. 3. click All Tasks. after you have generated the certificate request. Depending on the CA.cer file issued to you by the CA. In the Save Certificate dialog box. Submitting an Offline Request to a Public CA If you are not an administrator on the Certification Authority or if you use a public CA. and then click Open.der) for the certificate. 13. .

8. click Performance Options. 2. Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic For many deployments. you should optimize for audio/video traffic flow by increasing receive and transmit buffers settings to three times their default value on your network adapters: • • If you anticipate audio and video traffic on any particular A/V Conferencing Server or A/V Edge Server to exceed 200 to 250 Mbps If your servers experience packet loss on the network Note The following procedure provides steps to change these settings on a typical network adapter. Under Settings. Right-click Computer Manager.Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 41 7. expand Network adaptors 5. in the following situations. In the console pane. and then close the certificate. 7. Right-click your network adapter. . Log on as a member of the Administrators group to the computer that is running Audio/Video Conferencing Server or Audio/Video Edge Server. The procedure will vary depending on your manufacturer. and then click Properties. click Receive Descriptors. Click View Certificate to view the details of the certificate. To change your network adapter settings 1. 6. Verify the certificate location and file name in the Path and file name box. The certificate is installed to the local computer store. 4. Click Finish. 8. you can use the default settings on your network adapter. 9. In the details pane. Under Settings. however. and then click Next. Click the Advanced tab. click Device Manager. and then click Manage. 3.

In the Value box. and then click OK. . click Transmit Descriptors. In the Value box. change the value to three times the default value. and then click OK 10. 11.42 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007 Deployment Guide 9. change the value to three times the default value. In the Settings box.

Sign up to vote on this title
UsefulNot useful