Вы находитесь на странице: 1из 45

®

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
2 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007
Deployment Guide

Infrastructure Requirements and


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

Office Communications Server Windows Service Dependencies


Service Name
(Event Log and Remote Procedure Call)
Office Communications Server HTTP SSL (HTTP, IIS Admin Service,
Telephony Conferencing Remote Procedure Call, Security
(RTCACPMCU) Accounts Manager)
Windows Management Instrumentation
(Event Log and Remote Procedure Call)
Office Communications Server Web HTTP SSL (HTTP, IIS Admin Service,
Conferencing (RTCDATAMCU) Remote Procedure Call, Security
Accounts Manager)
Windows Management Instrumentation
(Remote Procedure Call)
Office Communications Server Message Queuing (Message Queuing
Archiving and CDR (RTCLOG) access control, NT LM Security Support
Provider, Remote Procedure Call,
RMCAST (Pgm) Protocol Driver, TCP/IP
Protocol Driver, IPSEC Driver, Security
Accounts Manager)
Office Communications Server Windows Management Instrumentation
Audio/Video Authentication (Event Log and Remote Procedure Call)
(RTCMRAUTH)
Office Communications Server Office Communications Server
Audio/Video Edge Audio/Video Authentication
(RTCMEDIARELAY) Windows Management Instrumentation
(Event Log and Remote Procedure Call)
Office Communications Server Windows Management Instrumentation
Access Edge (RTCSRV) (Event Log and Remote Procedure Call)
Windows Management Instrumentation
Driver Extensions
Office Communications Server Web Windows Management Instrumentation
Conferencing Edge (Event Log and Remote Procedure Call)
(RTCDATAPROXY)
Office Communications Server Windows Management Instrumentation
Mediation (RTCMEDSRV) (Remote Procedure Call)

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, consider storage
needs for archiving files.
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, you will perform the
following major tasks:
1. Prepare Active Directory schema, forest, and domain
2. Configure DNS for your Standard Edition server
3. Deploy a Standard Edition server
4. Create and enable users.
5. Deploy the Office Communicator 2007 client.
6. Deploy the Microsoft Office Live Meeting 2007 client.
The following sections describe these steps in detail.

Step 1: Prepare Active Directory


Schema, Forest, and Domain
Before you deploy Office Communications Server, you must prepare the Active Directory®
Domain Services. Active Directory preparation includes schema preparation, forest preparation,
and domain preparation. You prepare Active Directory during the initial deployment, but you do
not have to repeat this step if you add servers or pools to the deployment. For detailed
instructions and information about Active Directory preparation, see the Microsoft Office
Communications Server 2007 Active Directory Guide.
For information about delegating Office Communications Server setup or administration, see the
Microsoft Office Communications Server 2007 Active Directory Guide.

Step 2: Configure DNS for Your


Standard Edition Server
When you deploy a Standard Edition Server, Setup creates Active Directory objects and settings
for the server, including the server FQDN. For clients to be able to connect to the server, this
server FQDN must be registered in the Domain Name Service (DNS).
In addition, for clients to automatically detect a pool or Standard Edition Server on which a user
is hosted, 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.
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.

Required DNS Records


At a minimum, 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.
• If you plan to support Web conferencing for external users, an external DNS A record
that resolves the external Web farm FQDN to the external IP address of the reverse
proxy. The client uses this record to connect to the reverse proxy. (as described in the
Microsoft Office Communications Server 2007 Edge Server Deployment Guide).

Required DNS Records for Automatic Client Sign-In


If you are enabling automatic sign-in for clients of Office Communications Server, you will need
to configure additional DNS records as explained in this section. If you will require your clients
to manually connect to Office Communications Server, you can skip this section.
To support automatic client sign-in, you must do the following:
• Designate a single server or pool to distribute and authenticate client sign-in requests.
This can be an existing server or pool that host users, or you can designate a
dedicated server or pool that hosts no users for this purpose. If you require high
availability, we recommend that you designate an Enterprise pool for this function.
• Create an internal DNS SRV record to support automatic client sign-in for this server
or pool.
To enable automatic sign-in for your clients, 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.<domain> - for internal TLS connections
• _sipinternal._tcp. <domain> - 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.

Important
Only a single pool or Standard Edition Server can be designated
to distribute sign-in requests. Create only one SRV record for
the designated server or pool. Do not create an SRV record for
additional internal servers or pools.

Table 2 shows some example records that are required for the fictitious company, Contoso, that
supports SIP domains of contoso.com and retail.contoso.com.

Note
The SIP domain refers to the host portion of the SIP URIs that
are assigned to users. For example, if SIP URIs are of the form
*@contoso.com, then contoso.com is the SIP domain. The name
of the SIP domain is often different from that of the internal
Active Directory domain. An organization may also support
multiple SIP domains For more information on configuring SIP
domains, see the Microsoft Office Communications Server 2007
Administration Guide.
6 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007
Deployment Guide
Table 2. Example DNS Records Required for Automatic Client Sign-In
with Multiple SIP Domains
FQDN of SIP Domain DNS SRV Record
Standard
Edition Server
used to
distribute sign-
in requests
server1.Contos Contoso.com An SRV record for _sipinternaltls._tcp.contoso.com
o.com domain over port 5061 that maps to
server1.Contoso.com

server1.Contos Retail.Contoso. An SRV record for


o.com com _sipinternaltls._tcp.retail.contoso.com domain over
port 5061 that maps to server1.Contoso.com

Note
By default, queries for DNS records adhere to strict domain
name matching between the domain in the user name and the
SRV record. If you prefer that client DNS queries use suffix
matching instead, you can configure the
DisableStrictDNSNaming group policy. For details, see the
Microsoft Office Communicator Deployment Guide.

Example of the Certificates and DNS Records Required for


Automatic Client Sign-in
Using the examples in the preceding table, the Contoso organization supports the SIP domains of
contoso.com and retail.contoso.com, and all its users have a SIP URI in one of the following
forms:
• <user>@retail.contoso.com
• <user>@contoso.com
If the administrator at Contoso configures pool1.contoso.com as the pool that will distribute its
sign-in requests, the following DNS records are required:
• SRV record for _sipinternaltls._tcp.contoso.com domain over port 5061 that maps to
server1.contoso.com
• SRV record for _sipinternaltls._tcp. retail.contoso.com domain over port 5061 that
maps to server1.contoso.com
In addition, the certificate that is assigned to the server, pool1.contoso.com must have the
following in their Subject Alternate Names:
• sip.contoso.com
• sip.retail.contoso.com
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. The following
procedure assumes that your internal DNS has zones for your SIP user domains.

To create a DNS SRV record


1. On the DNS server, click Start, click Control Panel, click Administrative Tools,
and then click DNS.
2. In the console tree for your SIP domain, expand Forward Lookup Zones, and then
right-click the SIP domain in which your Office Communications Server will be
installed.
3. Click Other New Records.
4. In Select a resource record type, click Service Location (SRV), and then click
Create Record.
5. Click Service, and then type _sipinternaltls.
6. Click Protocol, and then type _tcp.
7. Click Port Number, and then type 5061.
8. Click Host offering this service, and then type the FQDN of the Standard Edition
Server.
9. Click OK.
10. Click Done.
After you have created the DNS SRV record, create a DNS A for the Standard Edition Server.
To create a DNS A record
1. On the DNS server, click Start, click Control Panel, click Administrative Tools,
and then click DNS.
2. In the console tree for your domain, expand Forward Lookup Zones, and then right-
click the domain in which your Office Communications Server will be installed.
3. Click New Host (A).
4. Click Name (uses parent domain name if blank), and then type the name of the
pool.
5. Click IP Address, and then enter the IP address of the Standard Edition Server.
6. Click Add Host, and then click OK.
7. Click Done.
To verify that the required records have been created successfully, wait for DNS replication (if
you have just added the records), and then verify that the records were created as described in the
next procedure.

Notethe creation of a DNS SRV record


To verify
For illustrative purposes, the following procedure uses
example.com as the domain portion of the SIP URI namespace.
When executing these steps, use your actual SIP domain name
instead.
8 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007
Deployment Guide
1. Log on to a client computer in the domain with an account that is a member of the
Administrators group or has equivalent permissions.
2. Click Start, and then click Run. In the Open box, type cmd, and then click OK.
3. At the command prompt, type nslookup, and then press ENTER.
4. Type set type=srv, and then press ENTER.
5. Type _sipinternaltls._tcp.example.com, and then press ENTER. The output
displayed for the TLS record is as follows:
Server: <dns server>.corp.example.com
Address: <IP address of DNS server>
Non-authoritative answer:
_sipinternaltls._tcp.example.com SRV service location:
priority = 0
weight = 0
port = 5061
svr hostname = server1.example.com
server1.example.com internet address = <IP address of the Standard
Edition Server>

6. When you are finished, at the command prompt, type exit, and then press ENTER.
After you configure the DNS records, verify that the FQDN of the Standard Editon Server can be
resolved by DNS.
To verify that the FQDN of the Standard Edition Server can be
resolved
1. Log on to a client computer in the domain.
2. Click Start, and then click Run. In the Open box, type cmd, and then click OK.
3. At the command prompt, type ping <FQDN of the Standard Editon Server>, and then
press ENTER.
4. Verify that you receive a response similar to the following, where the IP address
returned is the IP address of the Standard Edition Server.
Reply from 172.27.176.117: bytes=32 time<1ms TTL=127
Reply from 172.27.176.117: bytes=32 time<1ms TTL=127
Reply from 172.27.176.117: bytes=32 time<1ms TTL=127
Reply from 172.27.176.117: bytes=32 time<1ms TTL=127

How Client DNS Queries Work


During DNS lookup, SRV records are queried in parallel and returned in the following order to
the client.
1. _sipinternaltls._tcp.<domain> - for internal TLS connections
2. _sipinternal._tcp. <domain> - for internal TCP connections (performed only if TCP
is allowed)
3. _sip._tls. <domain> - for external TLS connections
Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 9
4. _sip._tcp.<domain> - 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.
For more information on remote user access, see the Microsoft Office Communications
Server 2007 Edge Server Deployment Guide.
The client uses the SRV record that is returned successfully, and it does not try any other SRV
records.
After the SRV record is returned, a query is performed for the DNS A record for the host name
that is returned by the SRV record. If no records are found during the DNS SRV query, the client
performs an explicit lookup of sip.<domain>. If the explicit lookup does not produce results, the
client performs a lookup for sipinternal.<domain>. If the client does not find
sipinternal.<domain>, it performs a lookup for sipexternal.<domain>.
If your DNS infrastructure prohibits configuration of these DNS records, you can manually edit
the client registry to point to the appropriate home server. For more information about editing the
client registry and configuring policy settings for the client, see the Microsoft Office
Communicator 2007 Deployment Guide.

Step 3: Deploy a Standard Edition


Server
When you deploy a Standard Edition server, you install all the server components on one
physical computer. The steps are as follows:
1. Install Office Communications Server Standard Edition.
2. Configure Standard Edition server.
3. Configure certificates.
4. Start the services.
5. Validate your server configuration.
6. Enable Audio/Video conferencing and Web conferencing.
These steps are explained in detail in the following sections.

3.1 Install Office Communications Server Standard


Edition
Use the following procedure to deploy Office Communications Server Standard Edition.

Note Office Communications Server Standard Edition


To deploy
Before you install the server, ensure that IIS is installed. When
you run the Deployment Tool, Setup automatically installs
Microsoft SQL Server™ 2005 Express Edition with SP2, MSXML
6.0 SP1 Parser, the Microsoft Visual C++® 8.0 SP1
development system, Microsoft Visual J#® development tool,
and the Microsoft .NET Framework 2.0. You do not need to
install them separately.
10 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007
Deployment Guide
1. 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.
2. Insert the Microsoft Office Communications Server 2007 CD. The Deployment Tool
will start automatically. If you are installing from a network share, go to the
\Setup\I386 folder, and then double-click Setup.exe.
3. Click Deploy Standard Edition Server.
4. At Deploy Server, click Run.
5. On the Welcome to the Deploy Server Wizard page, click Next.
6. Review the license agreement, and then click I accept the terms in the license
agreement if you agree to the terms of installation. (Required to continue
installation) To continue, click Next.
7. On the Location for Server Files page, do one of the following:
• To accept the default location where the files will be installed, click Next.
• To install the files at another location, click Browse. Browse to the location
where you want the files to be installed, and then click Next.
8. On the Main Service Account for Standard Edition Server page, enter the name of
a new or existing service account that will run the core Office Communications
Server service on this computer, and then enter the password for the account. The
default account is RTCService. For a new account, ensure that you use a strong
password that meets your organization’s Active Directory password requirements.
When you are finished, click Next to continue.

Note
When you create a new account, activation may fail until the
account has been replicated in Active Directory. If this happens,
wait until the account has been replicated, and then try again.

9. On the Component Service Account for this Standard Edition Server page, 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,
and then enter the password for the account. The default account is
RTCComponentService. For a new account, ensure that you use a strong password
that meets your organization’s Active Directory password requirements. When you
are finished, click Next to continue.
10. On the Web Farm FQDNs page, do one or more of the following:

• Verify that Internal web farm FQDN displays your server FQDN. This FQDN
is used by internal users for client download of Web conferencing content,
distribution group expansion, and Address Book files.
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, under External Web farm FQDN (optional), type the FQDN that
resolves to the external IP address of your reverse proxy. This FQDN is used by
external users for client download of Web conferencing content, distribution
group expansion, and Address Book files. It is also used by anonymous and
federated users to download Web conference content. For details about external
user access, see the Microsoft Office Communications Server 2007 Edge Server
Deployment Guide.

Important
If you plan to deploy edge servers for external user access, we
recommend that you configure the external URL during your
Standard Edition deployment. If you create this URL later, you
will need to use the LcsCdm.exe command-line tool, as
documented in the Microsoft Office Communications Server
2007 Edge Server Deployment Guide.

11. When you are finished, click Next.


12. On the Location for Database Files page, to accept the default directories for user
database and transaction log files, click Next.

Note
Setup automatically detects the best location for the files. If
possible, place each database and transaction log file on a
separate physical disk to improve performance. Do not place
these files on the system disk or page file disk.

13. When you are finished, click Next.


14. On the Ready to Deploy Server page, review the settings that you specified. If you
are satisfied with them, click Next to install, the Standard Edition server.
15. When the files have been installed and the wizard has completed, select the View the
log when you click Finish check box, and then click Finish.
16. In the log file, verify that <Success> appears under the Execution Result column.
Look for <Success> Execution Result at the end of each task. Close the log window
when you finish.

3.2 Configure Standard Edition Server


After you have deployed your Standard Edition server, use the Configure Server Wizard to
configure it.

Note
To configure Office Communications Server Standard Edition
In Office Communications Server 2007, the Address Book Server
is configured automatically. For information about changing
Address Book Server settings, see the Microsoft Office
Communications Server 2007 Administration Guide
12 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007
Deployment Guide
1. Log on to your Standard Edition Server as a member of the
RTCUniversalServerAdmins group or with equivalent user rights.
2. Insert the Microsoft Office Communications Server CD. If you are installing from a
network share, go to the \Setup\I386 folder, and then double-click setup.exe. The
Deployment Tool will start automatically.
3. In the Deployment Tool, click Deploy Standard Edition Server.
4. At Configure Server, click Run.
5. On the Welcome to the Configure Pool/Server Wizard page, click Next.
6. On the Server or Pool to Configure page, select the server from the list, and then
click Next.
7. On the SIP domains page, verify that your SIP domain appears in the list. If it does
not, click the SIP domains in your environment box, type your SIP domain, and
then click Add. Repeat these steps for all other SIP domains that the Standard Edition
server will support. When you are finished, click Next.
8. On the Client Logon Settings page, 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,
click Some or all clients will use DNS SRV records for automatic logon.
If this server or pool will also be used as a authenticate and redirect requests for
automatic sign-in, then select the Use this server or pool to authenticate and redirect
automatic client logon requests check box.

Note When you configure automatic client sign-in, you must


designate one (and only one) Enterprise pool or Standard
Edition Server to authenticate and redirect client sign-in
requests.

• If the Office Communicator clients and Live Meeting 2007 clients in your
organization will not be configured to use automatic sign-in, click Clients will
be manually configured for logon.
9. Click Next.
10. If in the previous step, you selected Some or all clients will use DNS SRV records
for automatic logon, on the SIP Domains for Automatic Logon page, select the
check box for the domains that will be supported by the server for automatic sign-in,
and then click Next. Otherwise, skip to the next step.
11. On the External User Access Configuration page, do one of the following:
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, click Configure for external user access now. For
details about completing this portion of the wizard, refer to the edge server
document.
• If you have not deployed any edge servers, click Do not configure for external
user access now.
12. When you are finished, click Next.
13. On the Ready to Configure Server or Pool page, review the settings that you
specified, and then click Next to configure the Standard Edition server.
14. When the files have been installed and the wizard has completed, select the View the
log when you click Finish check box, and then click Finish.
15. In the log file, verify that <Success> appears under the Execution Result column.
Look for <Success> Execution Result at the end of each task to verify Standard
Edition server configuration completed successfully. Close the log window when you
finish.
You can configure additional SIP server, domain, and forest settings as described in the
Microsoft Office Communications Server 2007 Administration Guide, Microsoft Office
Communications Server 2007 Archiving and CDR Server Deployment Guide, or the Microsoft
Office Communications Server 2007 Edge Server Deployment Guide. For details about
configuring SIP user settings, see 4.3 Configure Users in this document.

3.3 Configure Certificates


Office Communications Server requires certificates on each Standard Edition server in order to
use MTLS (TLS with mutual authentication). All Office Communications Servers use MTLS to
communicate with one another. If you do not configure MTLS on each server, users may be able
to sign in to Office Communications Server, but presence and IM communications may not work
properly.
Each client will also need to trust the certificate that the server is using in order to connect to the
server by using TLS. You can use the Certificates Wizard on a Standard Edition server to do the
following:
• Request, create, and assign a new Web certificate with enhanced key usage for server
authentication.
• Assign an existing certificate.
You can use the same certificate for the Web Components Server, but the certificate for the Web
Components Server must be assigned separately in IIS. You cannot use the Certificates Wizard
to the assign the certificate to the Web Components Server; instead, the certificate must be
assigned by using Internet Information Services (IIS) Manager.
To configure a new certificate
14 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007
Deployment Guide
1. Log on to your Standard Edition server as a member of the Administrators group
and the RTCUniversalServerAdmins group. You must also have permission from
your certificate authority to request a certificate.
2. Insert the Microsoft Office Communications Server 2007 CD. If you are installing
from a network share, go to the \Setup\I386 folder, and then double-click setup.exe.
The Deployment Tool will start automatically.
3. Click Deploy Standard Edition Server.
4. At Configure Certificate, click Run.
5. On the Welcome to the Certificate Wizard page, click Next.
6. On the Available Certificate Tasks page, click Create a new certificate, and then
click Next.
7. On the Delayed or Immediate Request page, click Send the request immediately
to an online certification authority, and then click Next.
8. On the Name and Security Settings page, do the following:
• Under Name, enter a meaningful name for the certificate that this server will use
for Office Communications Server communications.
• Under Bit length, select the bit length that you want to use for encryption. A
higher bit length is more secure, but it can degrade performance.
• Clear the Mark cert as exportable check box.
9. When you are finished, click Next.
10. On the Organization Information page, type or select the name of your organization
and organizational unit, and then click Next.
11. On the Your Server’s Subject Name page, do the following:
• In Subject Name, verify that the server FQDN is displayed.
• In Subject Alternate Name, verify that the required entries exist.

Note
SANs are required on your server for each supported SIP
domain in the format sip.<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, the Certificate
Wizard automatically added these SIP domains to the certificate
request.
Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 15
12. When you are finished, click Next.
13. On the Geographical Information page, enter the Country/Region, State/Province,
and City/Locality. Do not use abbreviations. When you are finished, click Next.
14. On the Choose a Certification Authority page, the wizard attempts to automatically
detect any CAs that are published in Active Directory. Do one of the following:
 Click Select a certificate authority from the list detected in your
environment, and then click your certification authority (CA).
 Click Specify the certificate authority that will be used to request this
certificate, and then type the name of your CA in the box in the format
<CA_FQDN>\CA_instance> For example, CA.contoso.com\CAserver1. If you
type the name of an external CA, a dialog box appears. Type the user name and
password that you use for the external CA, and then click OK.
15. When you are finished, click Next.
16. On the Request Summary page, review the settings that you specified, and then
click Next.
17. On the Certificates Wizard completed successfully page, click Assign.
18. A dialog box appears and informs you that the settings were applied successfully.
Click OK.
19. Click Finish.
20. Submit this file to your CA (by e-mail or other method supported by your
organization for your Enterprise CA). If your CA is configured for automatic
approval, proceed to the next procedure. If your CA requires CA administrator
approval to issue a certificate, the administrator must manually approve or deny the
certificate issuance request on the issuing CA before you can assign it.
To configure an existing certificate
1. 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.
2. Insert the Microsoft Office Communications Server 2007 CD. If you are installing
from a network share, go to the \Setup\I386 folder, and then double-click Setup.exe.
The Deployment Tool will start automatically.
3. Click Deploy Standard Edition Server.
4. At Configure Certificate, click Run.
5. On the Welcome to the Certificate Wizard page, click Next.
6. On the Available Certificate Tasks page, click Assign an existing certificate, and
then click Next.
7. On the Available Certificates page, click the certificate that you want to assign to
the server, and then click Next.
16 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007
Deployment Guide
8. On the Configure the Certificate(s) of your Server page, review the certificate
assignments, and then click Next to assign the certificate.
9. Click Finish.
Assign the Web Components Server (IIS) Certificate
Assign the certificate to the Web Components Server by using the Internet Information Services
(IIS) Manager.
To assign the certificate to the Web Components Server (IIS)
1. Log on to the server as a member of the Administrators group.
2. Click Start, click Control Panel, click Administrative Tools, and then click
Computer Management.
3. Expand the Services and Applications node, and then expand the Internet
Information Services (IIS) Manager node.
4. Expand the Web Sites node, right-click Default Web Site, and then click
Properties.
5. Click the Directory Security tab.
6. Under Secure communications, click Server Certificate.
7. On the Welcome to the Web Server Certificate Wizard page, click Next.
8. Click Assign an existing certificate, and then click Next.
9. Select the certificate that you requested by using the Certificates Wizard, and then
click Next.
10. On the SSL Port page, verify that port 443 will be used for SSL, and then click Next.
11. Review the certificate details, and then click Next to assign the certificate.
12. Click Finish to exit.
13. Click OK to close the Default Web Site Properties page.

3.4 Start the Services


Confirm that the Active Directory changes have replicated before you start the services. For more
information about the Active Directory changes that occur when you deploy Office
Communications Server, see the Microsoft Office Communications Server 2007 Active Directory
Guide.
To start the services
1. Log on to your Standard Edition Server with an account that is a member of the
RTCUniversalServerAdmins group or has equivalent user rights.
2. Insert the Microsoft Office Communications Server 2007 CD. If you are installing
from a network share, go to the \Setup\I386 folder, and then double-click setup.exe.
The Deployment Tool will start automatically.
3. In the deployment tool, click Deploy Standard Edition Server.
Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 17
4. At Start Services, click Run.
5. On the Welcome to the Start Services Wizard page, click Next.
6. Click Next again to start the services.
7. When the wizard has completed, select the View the log when you click ‘Finish’
check box, and then click Finish.
8. In the log file, verify that <Success> appears under the Execution Result column.
Look for <Success> Execution Result at the end of each task to verify each service on
the Standard Edition server started successfully. Close the log window when you
finish.

Note
If a service does not respond to the wizard in a timely fashion,
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,
check the Office Communications Server 2007 event log for
errors or warnings.

3.5 Validate Your Server Configuration


After you deploy the server and configure the certificates, verify that the server is correctly
configured. 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.

Note
If you have not configured Enterprise Voice or deployed edge
servers, you will get the following warning messages:
• “One or more phone usages are not assigned
to any route or VOIP policy. Warning [0x43FC200C]
Not all checks were successful.”
• “Federation: Disabled. Warning [Ox43FC200C]
Not all checks were successful.”
You can safely ignore these warnings.

3.5.1 Validate Your Front End Server Configuration


Use the following procedure to validate Front End Server configuration.
To validate your Front End Server configuration
18 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007
Deployment Guide
1. Log on to a server in your domain as a member of the RTCUniversalServerAdmins
group.
2. Insert the Microsoft Office Communications Server CD. If you are installing from a
network share, go to the \Setup\I386 folder, and then double-click Setup.exe. The
deployment tool will start automatically.
3. In the deployment tool, click Deploy Standard Edition Server.
4. Click Validate Server Functionality.
5. At Step 1 Validate Front End Server Functionality, click Run.
6. On the Welcome to the Office Communications Server 2007 Validation wizard
page, click Next.
7. On the Validation steps page, do any or all of the following:
• To validate that the Office Communications Server is configured correctly, select
the Validate Local Server Configuration check box.
• To verify that the Office Communications Server has connectivity to the Back-
End Database, the Web Conferencing Server, and the Audio/Video Conferencing
Server, select the Validate Connectivity check box.
• Clear the Validate SIP Logon (1-Party) and IM (2-Party) and Validate IM
Conference (2-Party) check boxes.

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. You can rerun the Validation Wizard and select these
tasks after you have created and enabled users for Office
Communications Server.

8. When you are finished, click Next.


9. When the wizard is complete, select the View the log when you click Finish check
box, and then click Finish.
10. In the log file, verify that <Success> appears under the Execution Result column.
Look for <Success> Execution Result at the end of each task. Close the log window
when you finish.
You can perform additional validation of server functionality by using the steps described in
Validation and Troubleshooting Hints in this document.

3.5.2 Validate Your Web Components Server Configuration


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

3.5.3 Validate Your Web Conferencing Server Configuration


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

3.5.4 Validate Your A/V Conferencing Server Configuration


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

3.6 Enable Audio/Video Conferencing and Web


Conferencing
Note
Instant messaging and presence are enabled by default when
you deploy Office Communications Server. If your organization
plans to support only instant messaging and presence features,
you can skip to the next deployment task.

In Office Communications Server, conferencing enables Office Communications Server users to


organize and invite other users to Web conferences that are hosted on your own on-premise
servers. The default meeting policy, which all users are initially configured to use , prevents users
from organizing conferences that use the Web conferencing or audio/video (A/V) conferencing
features. To allow access to these features, you must configure a policy that enables Web
conferencing and A/V conferencing and then assign this policy to your users. You can define the
policy to as a global policy so that it applies to all users, or you can apply the policy on a per-user
basis.
The meeting policy that applies to a meeting organizer also applies to all attendees of the
meeting. For example, if Bob organizes a meeting with IP audio enabled and the meeting policy
for Sue does not allow her to use IP audio, as an attendee of Bob’s meeting Sue will be able to
use IP audio. If, however, Sue organizes a meeting, all attendees of this meeting will use her
meeting policy and so no IP audio will be available.

To configure Audio/Video and Web conferencing


1. 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.
2. Click Start, click Control Panel, click Administrative Tools, and then click Office
Communications Server 2007.
3. Right-click the Forest node, click Properties, and then click Global Properties.
4. Click Meetings, and then do one of the following:
• To allow all users to organize Web conferences that include anonymous
participants, click Anonymous participants, and then click Allow users to
invite anonymous participants.
• To prevent all users from organizing Web conferences that include anonymous
participants, click Anonymous participants, and then click Disallow users
from inviting anonymous participants. This is the default setting.
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, click Anonymous participants, and then click Enforce per user.
Only users that you enable individually, as described in 4.3 Configure Users in
this document, are allowed to invite anonymous participants.
5. In the Policy Definition list, click the name of a policy, and then click Edit.
6. In the Edit Policy dialog box, select the Enable Web conferencing check box.
7. To enable audio, select the Enable IP audio.
8. To enable video, select Enable IP video.
9. Click OK.
10. Click Apply.
11. After you finish editing the features that are enabled by each policy, decide which
policy to apply to Web conferences organized by users. Do one of the following:
• To apply the same policy to all users, click Global policy, and then click the
name of the policy that defines the features that you want to enable for all users.
• To apply different policies to different users, click Global policy, and then click
Use per user policy. Ensure that you follow the procedures in 4.3 Configure
Users in this document to configure the Web conferencing policy for individual
users.
12. When you are finished, click OK.
For more information about administering Web and A/V conferencing features, refer to the
Microsoft Office Communications Server 2007 Administration Guide.
If you expect heavy audio/video traffic in your environment, you can optimize your network
adapter settings to accommodate this volume. See Appendix B: Optimizing Your Network
Adapter for High Audio/Video Traffic in this document for more information.

Step 4: Create and Enable Users


After you have deployed and configured your Standard Edition server, you must create users and
then enable them for the Office Communications Server features that you want them to use. If
you are deploying Office Communications Server 2007 in a new environment without existing
Live Communications Servers, create and enable users as described below.

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, use the
Migrating to Microsoft Office Communications Server 2007
guide.
Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 23

4.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, you must create user accounts and then configure the accounts for
Office Communications Server. The following sections explain these steps in detail.

Create User Accounts


You create user accounts in Active Directory.
To create user accounts
1. 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.
2. Click Start, and then click Run. In the Open box, type dsa.msc, and then click OK.
3. Right-click the Users container or another container where you want to create your
users, click New, and then click User.
4. Complete the New Object - User wizard.

Enable Users for Office Communications Server 2007


After you create users in Active Directory, enable the users so that they can connect to Office
Communications Server. Office Communications Server provides the infrastructure to enable
client applications to publish and subscribe to extended, or enhanced, presence information. The
enhanced presence infrastructure includes categories and containers. Categories are collections of
presence information, such as status, location, or calendar state. Containers are logical buckets
into which clients group instances of various categories of presence information for publication
to other users, depending on what a user wants the others to be able to see. When you enable
users for Office Communications Server 2007, they are automatically enabled for enhanced
presence. You cannot undo this setting.

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, the user account is converted to use
enhanced presence. 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, including
Communicator Web Access (2005 release) or Communicator
Mobile (2005 release), to sign in.
If you are deploying Office Communications Server 2007 in an
environment with Live Communications Server 2005 with SP1
servers or Communicator 2005 users, see the Migrating to
Microsoft Office Communications Server 2007 guide for more
information.
24 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007
Deployment Guide
To enable users for Office Communications Server
1. 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.
2. Click Start, and the click Run. In the Open box, type dsa.msc, and then click OK.
3. In the console pane, expand the Users folder or other organization unit where your
user accounts reside.
4. For each user whom you want to enable for Office Communications Server, right-
click the user name, and then click Enable users for Communications Server.
5. On the Welcome to the Enable Office Communications Server Users Wizard
page, click Next.
6. On the Select Server or Pool page, select the Standard Edition server from the list,
and then click Next.
7. On the Specify Sign-in Name page, 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 user’s e-
mail address. Select this option only if you have configured an e-mail address
for your users.
• To generate the SIP address from the user’s principal name, click Use
userPrincipalName.
• To generate the SIP address using the user’s full name, click Use the format:
<first name>.<lastname>@, and then select the Office Communications Server
domain.
• To generate the SIP address using the user’s SAM account, click Use the
format: <SAMAccountName>@, and then select the Office Communications
Server domain.

Note
If you need to configure SIP addresses using a different format
from the options presented, you can enable users individually or
use the Office Communications Server 2007 Software
Development Kit to enable a group of users. .

8. When you are finished, click Next.


9. Verify that the user or users were enabled successfully, and then click Finish.
To create a mailbox for the users to receive Web conference invitations, see the Microsoft
Exchange Server documentation.
Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 25

4.2 Wait for User Replication to Complete


Before you try to test or verify any end user functionality, verify that the changes you made to
enable users have been replicated by the Office Communications Server User Replicator. The
User Replicator logs an event with ID 30024when replication completes successfully.
To verify that users were enabled
1. 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.
2. Click Start, click Control Panel, click Administrative Tools, and then click Office
Communications Server 2007.
3. Expand the forest node and the pool node, and then click Users.
4. Confirm that the users you successfully enabled for Office Communications Server
are listed.

4.3 Configure Users


Procedures to configure global meeting settings are included in 3.6 Enable Audio/Video
Conferencing and Web Conferencing in this document. All other user configuration settings are
described in this section. Ensure that the global settings for desired features are such that they can
be configured for individual users.
To configure users for Office Communications Server
1. 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.
2. Click Start, click Control Panel, click Administrative Tools, and then click Office
Communications Server 2007.
3. Expand the Forest node, expand Standard Edition Servers, and then expand your
Standard Edition Server.
4. Select one of the following:
• To configure all users the Standard Edition Server, right-click Users, and then
click Configure users.
• To configure an individual user, in the console pane, expand Users. In the details
pane, right-click the user account that you want to configure.
5. On the Welcome to the Configure Users Wizard page, click Next.
6. Select the check boxes for the features that you want to configure for the selected
user or users: Federation, Remote user access, Public IM connectivity, Enhanced
Presence, Archive internal messages, and Archive federated messages. For each
feature, click Enable or Disable, as appropriate. When you are finished, click Next.

Note
If you did not configure your global properties on the Meetings
tab to enforce policies per user, some of options in the following
steps will be unavailable.
26 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007
Deployment Guide
7. Select the Organize meetings with anonymous participants check box, and then
click Allow or Disallow. Click Next.
8. Select the Change meeting policy check box. In the Select a meeting policy for the
users list, click the name of the policy that you want to apply to the selected users.
When you are finished, click Next:
9. To enable Enterprise Voice and configure the Enterprise Voice policy that will be
applied to the selected users, select the Change Enterprise Voice Settings check
box, and then select the Enable Voice check box. In the Select a Voice policy for
the users list, click the name of the policy that you want to apply to the selected user
or users, and then click Next.

Note
In order to configure a particular Enterprise Voice setting for a
specific user, the corresponding setting under Voice Properties
must be configured to allow enforcement on a per user basis.
For more information about Enterprise Voice, see the e
Microsoft Office Communications Server 2007 Enterprise Voice
Planning and Deployment Guide.

10. Verify the status of each user configuration operation, and then click Finish to close.

Step 5: Deploy the Office


Communicator 2007 Client
Install and configure Microsoft Office Communicator 2007 on each client in your organization.
This section provides high-level guidance on how to deploy Office Communicator 2007. For in-
depth information, see the Microsoft Office Communicator 2007 Deployment Guide.
Users of Communicator 2005 can still sign in to Office Communications Server if their account
has been moved to an Office Communications Server, but there are important considerations if
you choose to have users running both Communicator 2005 and 2007 in your environment. For
details, see the Migrating to Microsoft Office Communications Server 2007 guide.

5.1 Deploy Office Communicator


Deploy Office Communicator 2007 by using a Windows Installer package (.msi file). To deploy
Office Communicator, run the package by using your organization’s preferred deployment
method; for example, Systems Management Server (SMS), an Active Directory Domain Services
Group Policy, a scripted deployment, or any other third-party software that supports .msi-based
deployment. The following procedure shows how to run the MSI to install Communicator.
To install Communicator
1. Download Communicator.msi, and then double-click it.
2. On the Welcome to Microsoft Office Communicator 2007 Setup page, click Next.
Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 27
3. Review the license agreement, and then click I accept the terms in the License
Agreement if you agree to the terms of installation (required to continue installation).
Click Next to continue.
4. On the Configure Microsoft Office Communicator 2007 page, accept the default
folder or click Browse and browse to another folder. When you are finished, click
Next.
5. When the wizard has completed, click Finish.
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, as follows:
msiexec /qn /i Communicator.msi

5.2 Configure Client Sign-In


After the DNS records have been configured, by default Communicator is configured for
automatic connectivity. If you need to, you can modify this setting. Use the following procedure
on each client to enable your users to connect to Office Communications Server.
To configure automatic connectivity for Office Communicator clients
1. On the client computer, start Microsoft Office Communicator 2007.
2. Click the down arrow in the Office Communicator title bar, click Tools, and then
click Options.
3. On the Personal tab, click Advanced, and then click Automatic Configuration.
4. Click OK, and then click OK again.
To configure Office Communicator clients manually
1. Open Microsoft Office Communicator 2007.
2. Click the down arrow in the Office Communicator title bar, click Tools, and then
click Options.
3. On the Personal tab, click Advanced, and then click Manual Configuration.
4. To test access to the server from inside your organization, click Internal server
name or IP address, and then type the internal Standard Edition server FQDN or IP
address. 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.
5. When you are finished, click OK, and then click OK again.
28 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007
Deployment Guide

5.3 Test Office Communications Server


Configuration for Office Communicator
To test the Office Communications Server configuration for Office Communicator, you can use
the Validation Wizard. 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.
To test Office Communications Server configuration for Office
Communicator clients using the Validation Wizard
1. Log on to a server in your domain as a member of the RTCUniversalServerAdmins
group.
2. Insert the Microsoft Office Communications Server 2007 CD. The Deployment Tool
will start automatically. If you are installing from a network share, go to the
\Setup\I386 folder, and then double-click Setup.exe.
3. In the deployment tool, click Deploy Standard Edition Server.
4. At Validate Server Functionality, click Run.
5. On the Welcome to the Office Communications Server 2007 Validation wizard
page, click Next.
6. To verify that enabled users can sign in, select the Validate SIP Logon (1-Party)
and IM (2-Party) check box.
7. If you configured your Office Communicator clients for automatic sign-in and have
configured the required DNS records, select the Check this box to use client auto-
logon for validation check box to verify that automatic client sign-in works.
8. On the User Account page, enter a user name, sign-in name, and password of a test
user or another user enabled for SIP.
9. In Server or Pool, select the server where the user is hosted. When you are finished,
click Next.
10. On the Second user account (required) page, enter a user name, sign-in name, and
password of another test user (another user enabled for SIP). This account will be
used with the first account you specified to test IM functionality between two users.
11. In Server or Pool, select the server where the user is hosted. When you are finished,
click Next.
12. If you have configured federation or public IM connectivity, on the Federation and
Public IM Connectivity page, click Test connectivity of internal and federated
users, and then type the SIP URI of a federated user account with which you want to
test this functionality. Otherwise, clear the check box.
13. Click Next.
Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 29
14. When the wizard is finished, select the View the log file when you click Finish
check box, and then click Finish.
15. In the log file, verify that <Success> appears under the Execution Result column.
Look for <Success> Execution Result at the end of each task to verify that the server
was added successfully to the Standard Edition server. Close the log window when
you finish.
To sign in and test Communicator
1. Log on to a client computer with a user account that is enabled for Office
Communications Server.
2. Click Start, click Programs, and then click Microsoft Office Communicator 2007.
3. In the Sign-in address, enter your SIP account.
4. Click Sign In.
5. If you are prompted for credentials, in User name, type the SIP username in one of
the suggested formats. In Password, type the user account password, and then click
Sign In.
6. Repeat steps 1 through 7 on a second client computer using a second user account
enabled for Office Communications Server.
7. On the first computer, open Communicator and then type the full SIP URI of the
account that is logged in on the second computer.
8. In the results list, double-click the name of the user logged in on the second
computer.
9. Type a message, and then press ENTER.
10. On the second computer, verify that the message was received, and then type a
message and press ENTER.
11. On the first computer, verify that the message was received.
For a complete list of Communicator features to test, along with detailed step-by-step
instructions, see the Microsoft Office Communicator 2007 Testing and Troubleshooting Guide.

Step 6: Deploy the Live Meeting


2007 Client
Web conferences require the Microsoft Office Live Meeting 2007 client. For detailed information
regarding Live Meeting 2007 client deployment, see Deploying the Microsoft Office Live
Meeting 2007 Client with Office Communications Server 2007.

6.1 Deploy the Live Meeting Client


You deploy the Microsoft Office Live Meeting client by using a Windows Installer package (.msi
file). To deploy the meeting client, run the package by using your organization’s preferred
30 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007
Deployment Guide
deployment method; for example, Systems Management Server (SMS), an Active Directory
Domain Services Group Policy, a scripted deployment, or any other third-party software that
supports .msi-based deployment.

Note
End users who are installing the Live Meeting client manually
should use LMSetup.exe instead of the Windows Installer
package. On Windows Vista™, the .Installer package will not
work correctly unless the user runs Windows Installer as a
member of the Administrators group, for example, from an
administrative command line prompt.

Extracting the installer package


You can extract the installer package (.msi) from the LMSetup.exe application.

To extract the installer package (.msi)


1. Copy the file LMSetup.exe to a folder on your local hard disk. You can download the Live
Meeting 2007 client from the Microsoft Web site at: http://r.office.microsoft.com/r/rlidOCS?
clid=1033&p1=LiveMeeting
2. Open a command prompt window: Click Start, and then click Run. In the Open box, type
cmd, and then click OK.
3. Change the directory to the folder to which you copied the .exe.
4. To extract the LMConsole.msi file, at the command prompt, type the following command:
LMSetup.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, you can use
the “silent installation” option, so that the users do not see it or interact with the installation. To
install the meeting client silently, use the /qn switch.
To install the Live Meeting client
• At the command prompt, type the following command:
msiexec /qn /I LMConsole.msi

To verify installation of the client


1. Click Start, and then click All Programs. Point to Microsoft Office Live Meeting 2007,
and then click Microsoft Office Live Meeting 2007.
2. Click the title bar down arrow, and then click Open User Accounts.
3. Under Server, type a sign-in name or verify that the sign-in name that appears in the Sign-in
name box is valid.
Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 31
4. Click Test Connection and verify that your Live Meeting sign-in information is successfully
verified. If you are using an account that is authorized to organize meetings, the Welcome to
Microsoft Office Live Meeting page contains a Meet Now button. Click Meet Now, and
then click Continue.
5. In the Live Meeting client, click Meeting, and then verify that the status is Connected.
6. In the Voice & Video pane, click the More button (>>), click Options, and then click Set Up
Audio and Video. Use the wizard to select audio and video settings. Verify that you can use
audio and video.
7. Click Content, click Share, and then click Upload File (View Only). Select a document, and
then click Open. Verify that the file is added to the Live Meeting.

6.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. After you deploy the Live Meeting client,
deploy the Outlook add-in from the Outlook add-in Windows Installer file (.msi), and then
distribute the add-in as you would from any other .msi file.

Note
Microsoft Office Outlook must already be installed on the
computer where you install the Outlook add-in.

To deploy the Live Meeting 2007 Outlook add-in


1. Download LMAddinPack.msi, and then double-click it. You can download the add-
in from the Microsoft Web site at http://r.office.microsoft.com/r/rlidOCS?
clid=1033&p1=confadd.
2. Click Run.
3. On the Microsoft Office Live Meeting Add-in Pack page, click Next to begin
installation.
4. When the wizard has completed, click Finish.
You must restart Outlook to use the add-in.

6.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, the user receives a meeting invitation through the Microsoft
Office Outlook® messaging and collaboration client. The meeting invitation contains a URL to
join the meeting. Additionally, if you have configured Office Communications Server 2007 to
32 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007
Deployment Guide
support meetings for both internal and external users, the following URLs are available to
meeting attendees:
• Support page URLs. By default, both the internal and external URLs link to a
Microsoft support page (http://r.office.microsoft.com/r/rlidLiveMeeting?
p1=12&p2=en_us&p3=LMInfo&p4=supportserver), but you can host your own
support page on your own Web server.
• Meeting client download URL. Users can click this link to download and install the
Live Meeting 2007 client. You can only change the internal meeting client download
URL, not the external client download URL.
Use the procedures in this section to do the following:
• Specify a URL for downloading the Live Meeting 2007 Client
• Host the support page on a Web server and specify the support URL
To specify a URL for downloading the Live Meeting 2007 Client
1. On the Office Communications Server 2007 server configured as the Web
Components Server, open Office Communications Server 2007.
2. In the console tree, expand the forest node, and then do one of the following:
• For an Enterprise pool, expand Enterprise pools, expand the pool, right-click
Web Components, and then click Properties.
• For a Standard Edition Server, expand Standard Edition servers, right-click the
pool, click Properties, and then click Web Component Properties.
3. Click the Meeting Invitations tab.
Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 33

4. Under Live Meeting 2007 Client URL, in the Internal box, type the URL that
internal users will use to download the Live Meeting 2007 client. For example,
http://eepool1.contoso.com/meetings/int/clientdownload.html or
http://OCSServer1.contoso.com/meetings/int/clientdownload.html.
To host the support page on a Web server and specify the support
URL
1. 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.
2. Host the internal page on your internal Web server and the external Web page on
your external Web server.

Note
After you copy the support page to the appropriate locations,
verify the following:
• The URL that internal users will use to
download the page works inside the corporate
network only.
• The URL that external users will use to
download the page works from outside the corporate
network.
34 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007
Deployment Guide
3. 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.
4. Open Office Communications Server 2007 administrative snap-in: Click Start,
point to All Programs, and then click Office Communications Server 2007.
5. In the console tree, expand the forest node, and then do one of the following:
• For an Enterprise pool, expand Enterprise pools, expand the pool, right-click
Web Components, and then click Properties.
• For a Standard Edition Server, expand Standard Edition servers, right-click the
pool, click Properties, and then click Web Component Properties.
6. Click the Meeting Invitations tab.
7. Under Technical Support URL, do the following:
• In the Internal box, type the URL that internal users will use to view the support
page. For example, http://eepool.contoso.com/meeting/int/Tshoot.html or
http://OCSServer1.contoso.com/meeting/int/Tshoot.html.
• In the External box, type the URL that external users will use to view the
support page. For example, http://eepool.contoso.com/meeting/ext/Tshoot.html
or http://OCSServer1.contoso.com/meeting/ext/Tshoot.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.
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.
To change the organization name for meeting invitations
Open Office Communications Server 2007.
1. In the console tree, expand the forest node, and then do one of the following:
• For an Enterprise pool, expand Enterprise pools, expand the pool, right-click
Web Components, and then click Properties.
• For a Standard Edition server, expand Standard Edition servers, right-click the
pool, click Properties, and then click Web Component Properties.
Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 35

2. On the General tab, in the Organization type the name of your organization.

6.4 Set Up a Test Web Conference


After you install the Live Meeting client and the add-in, you can test the Office Communications
Server configuration for Web conferencing by setting up a test conference. To perform this test,
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. See 3.6 Enable Audio/Video Conferencing and
Web Conferencing and 4.3 Configure Users in this document for details.
To set up a test conference
1. Open Microsoft Office Outlook.
2. In the Microsoft Office Live Meeting dialog box that indicates the add-in was
successfully installed, click OK.
3. Close Outlook, and then restart it to initialize the add-in.
4. On the Conferencing menu, click User Account.
36 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007
Deployment Guide
5. In the User Accounts dialog box, click Sign-in name, and then type the name of
your SIP account.
6. Click Test Connection.
7. 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, and then skip
to step 12 to continue.
• If the Error - Microsoft Office Live Meeting dialog box appears because the
client is unable to establish a connection to the server, click OK, and then click
Advanced.
8. Select the Use these servers check box, and then do one of the following:
• To test access to the server from inside your organization, click Internal Server
name or IP address, and then type either the FQDN or the IP address of the
internal Standard Edition server.If you configured the server so that clients can
connect by using TCP, click TCP. If you configured the server so that clients can
connect only by using TLS, click TLS.
• To test access to the server from outside your organization, click External
Server name or IP address, and then type either the FQDN or the IP address of
the external Standard Edition server. If you configured the server so that clients
can connect by using TCP, click TCP. If you configured the server so that clients
can connect only by using TLS, click TLS.
9. Select the Use the following user name and password check box. Click User name
and type your domain and user name in the following format: domain\username.
Click Password, and then type your domain password. When you are finished, click
OK.
10. Click Test Connection and ensure that Microsoft Office Live Meeting dialog box
appears, which indicates that the client can establish a connection to the server.
11. Click OK to close the User Accounts dialog box.
12. In Outlook, in the toolbar, click Schedule a Live Meeting.
13. In the e-mail template, click To, 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 Subject, type a name for the conference, and then click
Send.
14. When the second client receives the e-mail invitation for the scheduled Web
conference, open the invitation on both clients, and then click the Join the meeting
link in each invitation. The Live Meeting client appears.
15. If the meeting link does not work, follow the instructions in the Troubleshooting
section of the meeting invitation e-mail.
16. After you have joined the Web conference from both computers, click the Attendees
list and verify that both users are listed.
Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 37
17. Test other Web conferencing features by using the instructions in the Microsoft
Office Live Meeting 2007 Getting Started Guide.

Validation and Troubleshooting Hints


ISSUE: Problems signing in with the client
RESOLUTION: In order to troubleshoot user sign-in issues, use the Validation Wizard option to
test SIP sign-in, and check the Office Communications Server 2007 event log for error or
warnings. You can also verify the following:
• The user is enabled and configured properly in Active Directory.
• Office Communications Server User Replicator has finished synchronizing the user’s
information from Active Directory. Check for event codes by the OCS User
Replicator in the Windows event log.
• All users’ SIP domains (at least the suffix) are reflected in the SIP Domain list in the
global settings.
• The client computer trusts the Certificate Authority.
• The server certificate is configured and, if you are not using manual sign-in, is valid
for client automatic sign-in. The certificate must match the domain suffix of the end-
user’s SIP URI.
• The Office Communications Server Standard Edition service (RTCSrv) is running.
• The server has permissions on the database. 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.
ISSUE: Problems starting the services
RESOLUTION: At times, 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. This can happen
even when all services have started successfully. You can check the Office Communications
Server event log in the Windows event viewer to verify the services that have been started. You
can also rerun the Start Services Wizard to verify the results.
ISSUE: Problems using the Web Components Server
RESOLUTION:
• Check the event log for error or warnings.
• If the user receives an “unauthorized 401” error message, verify that the user is
enabled for Web conferencing by checking the user properties. See 3.6 Enable
Audio/Video Conferencing and Web Conferencing and 4.3 Configure Users in this
document for details on configuring these settings.
• 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.
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, verify that the IIS
server is running. 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.
ISSUE: Problems with archiving or CDR
RESOLUTION: The certificate on the server may not be configured correctly. Check the Office
Communications Server 2007 event logs on the client and the server for events that mention
certificate-related issues.
• Stop and restart Office Communications Server. Sign out and then sign in again
from Office Communicator, and then try to send an instant message. Check the
Archiving and CDR Server again to see if it is archiving messages.
• 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.
• Check event logs for warnings or errors.
• If Archiving or CDR was enabled after the Front End Server started, restart the
Front End Server services (RTCSrv) to apply these changes.
• 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, see the
certificate instructions in the Microsoft Office Communications
Server 2007 Edge Server Deployment Guide.

This section contains examples of various server FQDN and Web conferencing URL scenarios.
These examples can help you to determine the certificates that you need to request from your
certification authority (CA).
This section describes the procedures for requesting a certificate from a public CA. If you need to
generate an offline request or you are using a public CA, use the following procedures to request
and process the certificate.
To request the certificate
18. On the server on which you have installed Office Communications Server, click
Start, click Programs, click Administrative Tools, and then click Office
Communications Server 2007.
19. In the console pane of the snap-in, expand the nodes until you reach the Standard
Edition server that you installed.
Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 39
20. Right-click the server name, and then click Certificates.
21. On the Welcome to the Certificate Wizard page, click Next.
22. On the Available Certificate Tasks page, click Create a new certificate, and then
click Next.
23. Select Prepare the request now, but send it later, and then click Next.
24. Click Name, and then type the name for the new certificate. For example, you can
use the server name as the certificate name.
25. Clear the Mark cert as exportable check box, and then click Next.
26. Click Organization, and then type your organization name.
27. Click Organizational unit, type the name of your department, and then click Next.
28. Click Subject name, type the FQDN of the server, and then click Next.
29. Select your Country/Region, State/Province, and City/Locality, and then click
Next.
30. Click Browse, choose a location, enter a File name (with a .txt extension) for the
certificate request, and then click Save.
31. Verify the path and file name of the certificate request file in the File name box, and
then click Next.
32. Review the request information, and then click Next.
33. Click Finish.
Repeat these steps on the other Front End Servers.
Issuing the Certificate Request
If you are an administrator on the certificate authority, follow these steps to issue the certificate
after you have generated the request. If you are not an administrator for the certification
authority, follow the instructions in the following section, Submitting an Offline Request to a
Public CA, instead.

To issue a certificate
1. Click Start, and then click Run. In the Open box, type mmc, and then click OK.
2. In the File menu, click Add/Remove Snap-in.
3. Click Add, click Certification Authority, and then click Add.
4. Click Another computer, and then click Browse.
5. Choose your CA, and then click OK.
6. Click Finish.
7. Click Close.
8. Click OK.
9. In the snap-in, expand the Certification Authority node.
40 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007
Deployment Guide
10. Right-click your CA, click All Tasks, and then click Submit new request.
11. In the Open Request File dialog box, navigate to and click the certificate request
(.txt) file that you created by using the wizard, and then click Open.
12. In the Save Certificate dialog box, enter a File name (with an X.509 extension,
.cer, .crt, or .der) for the certificate, and then click Save.
13. Close the CA snap-in.
Repeat these steps on the servers in the pool for which you generated an offline certificate
request.
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, after you
have generated the certificate request, access the public CA site to submit the request. Depending
on the CA, the process will vary, but you generally need to supply your organizational and
contact information.
If you are prompted, 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, you will receive an e-mail message that
contains the text that is required for the certificate.
Process the Pending Certificate Request
After you submit the certificate request, verify that the certificate was downloaded correctly and
that it has been bound to the local computer store.
To process the certificate from the Public CA
1. On the server on which you have installed Office Communications Server, click
Start, click Programs, click Administrative Tools, and then click Office
Communications Server 2007.
2. In the console pane of the snap-in, expand the nodes until you reach the Standard
Edition server that you installed.
3. Right-click the Office Communications Server, and then click Certificates.
4. On the Welcome to the Certificate Wizard page, click Next.
5. Click Process the pending request and install the certificate, and then click Next.
6. In Path and file name, do one of the following:
• Enter the location and file name of the .cer file issued to you by the CA, and then
click Next.
• Click Browse. Locate the certificate issued to you by the CA, and then click
Open.
Appendix B: Optimizing Your Network Adapter for High Audio/Video Traffic 41
7. Verify the certificate location and file name in the Path and file name box, and then
click Next. The certificate is installed to the local computer store.
8. Click View Certificate to view the details of the certificate, and then close the
certificate.
9. Click Finish.

Appendix B: Optimizing Your


Network Adapter for High
Audio/Video Traffic
For many deployments, you can use the default settings on your network adapter; however, in the
following situations, 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. The procedure will vary
depending on your manufacturer.

To change your network adapter settings


1. Log on as a member of the Administrators group to the computer that is running
Audio/Video Conferencing Server or Audio/Video Edge Server.
2. Right-click Computer Manager, and then click Manage.
3. In the console pane, click Device Manager.
4. In the details pane, expand Network adaptors
5. Right-click your network adapter, and then click Properties.
6. Click the Advanced tab.
7. Under Settings, click Performance Options.
8. Under Settings, click Receive Descriptors.
42 Microsoft Office Communications Server 2007 Standard Edition and Communicator 2007
Deployment Guide

9. In the Value box, change the value to three times the default value, and then click
OK
10. In the Settings box, click Transmit Descriptors.
11. In the Value box, change the value to three times the default value, and then click
OK.

Вам также может понравиться