Today, the Microsoft Lync Server 2010 documentation team released an update to the technical library, which includes updates to existing topics in the following areas: Clients & Devices, Planning, Deployment, Topology Builder, Migration, and Supportability.
Author: Chloe Brussard
Publication date: March 15, 2012
Product version: Lync Server 2010
The following updates were made to the documentation.
In multiple topics, we removed the following text about providing the fully qualified domain name (FQDN) value:
The name you specify must be identical to the computer name configured on the server. By default the computer name of a computer that is not joined to a domain is a short name, not an FQDN. Topology Builder uses FQDNs, not short names. So, you must configure a DNS suffix on the name of the computer to be deployed as an Edge Server that is not joined to a domain.
This does not apply to a computer pool, where the name specified will be the pool name, not an individual computer. This is, however, important for a single Edge Server deployment and for defining individual computers in a pool.
In multiple topics, we added information to clarify the use of routable public addresses and non-routable private addresses, and the scenarios in which NAT is used. The five scenarios in which NAT can be used include the following:
- Scaled Edge Server deployment with hardware load balancer.
- Scaled Edge Server deployment with private IP using NAT Domain Name System (DNS) load balancer.
- Scaled Edge Server deployment with public IP DNS load balancer.
- Single Consolidated Edge Server deployment with private IP addresses using NAT.
- Single Consolidated Edge Server deployment with public IP.
Client & Device Updates
In the following topics, we included a requirement that Windows Media Player 11 must be installed for recording features in the client to work properly:
In the topic Configuring Client Bootstrapping Policies for Lync 2010, we added a link to the communicator.adm file, which is not included in the Lync installer.
In the topic, Technical Considerations for Mobile Clients, we removed the information that a user can create an email addressed to the support team and attach the log files. The log files are not accessible on Nokia devices.
In the following topics, we removed the statement indicating support for the Lync Attendant Console on Microsoft Lync 2010 Phone Edition:
In the Troubleshooting Devices topic, Unable to get voice mails and calendar information, we updated the information about authentication and Exchange Web Service certificates.
In the topic, Client Software Support, we added a new section “Using Mandatory Profiles,” which states the following:
“If users are planning to use Lync 2010 conferencing features, they should not use Windows Active Directory Domain Services mandatory profiles to sign into the Lync 2010 client. Because mandatory profiles are read-only user profiles, the Public Key Infrastructure (PKI) keys that are required for Lync 2010 conferencing cannot be saved to the profile. For more information, see Lync 2010 conferencing feature fails when the user is signed in using a mandatory user profile.”
Topology Builder Help
In the topic, Edit Federation Route Settings, we added information about editing federation routes from a local server or pool to a local Edge Server so that local federation routes take precedence over global federation routes.
In the topic, Edit Properties for A/V Conferencing Pool, we removed the following text that indicated a DNS host (A) record is required:
“You must have a DNS host (A) record that corresponds with the A/V Conferencing Server pool name.”
In the topic, Encryption for Lync Server 2010, we added information about how media encryption works for secure real-time transport protocol (SRTP).
In the topic, Create a Kerberos Authentication Account, we added information about manually creating a Kerberos account for administrators who cannot run the New-CsKerberosAccount cmdlet.
In the topic, User and Client Authentication for Lync Server 2010, we removed the reference to smart-card authentication because this is not supported.
In the topic, Specifying Antivirus Scanning Exclusions, we added a note about the default file and folder locations for RtcReplicaRoot. We also added the following note about SQL Server statements:
“Note: Folder and file locations listed below are the defaults for Lync Server 2010. For any locations for which you did not use the default, exclude the locations you specified for your organization instead of the default locations specified in this topic.”
In the topic, Scenario-Based Capacity Planning, we changed the value used in the formula to calculate network bandwidth requirements for IM and presence from 6.37e-8 to 0.0000000637.
In the topic, External Communications Capabilities, we added information to clarify that instant messaging (IM) and presence is always available, and that you can optionally add conferencing, which enables both web and A/V conferencing.
In the topic, Overview of External User Access, we clarified the description of remote users.
In the following topics, we updated the number of client connections supported on the Access Edge service to 15,000:
In the topic, Database Software and Clustering Support, we added information to clarify clustering node failover and update support for Microsoft SQL Server 2008 SP1, including support for Standard Edition server.
In the topic, Using DHCPUtil, we included additional information about how to enable Lync Server 2010 DHCP server.
In the topic, Configure the Edge Server for Integration with Hosted Exchange UM, in the section “To create a hosting provider on the Edge Server,” we added the VerficationLevel parameter to the cmdlet example. This parameter is required for verification of messages sent from the specified hosting provider.
In the following topics, we updated information about DHCP option 43 for Lync Phone Edition:
Add the topic, Create a DNS SRV Record for Integration with Hosted Exchange UM, to describe how to create the DNS SRV record that is required for a Lync Server 2010 Edge Server to route to a hosted Exchange service such as Microsoft Exchange Online.
In the topic, Changes Made by Forest Preparation, we corrected the groups that are created during Active Directory forest preparation.
In the topic, Installing the Mobility and Autodiscover Services, we updated the order in which the steps should be performed when using IIS 7.0.
We added the following topics to the Active Directory Domain Services Reference section of the documentation to explain the permission changes made by the cmdlets:
In the topic, Technical Requirements for Mobility, we added information about the DNS records required for the Mobility Service and the Autodiscover Service.
In the topic, Setting Up SQL Server Accounts, Rights, and Permissions, we added information about the requirement that the account used must have serveradmin permissions.
In the following topics, we replaced the “Traffic flow during migration coexistence phase” image to clarify flow through a SIP/PSTN gateway:
In the topic, Configure Certificates on the Server Running Microsoft Exchange Server Unified Messaging, we added information to clarify certificates and trust with certificate authorities (CA).
In the topic, Call Admission Control Deployment Checklist, we added a note to clarify that an Edge Server is not required for call admission control (CAC).
In the following topics, we added information to clarify database collocations support for Group Chat:
In the topic, Supported Lync Server 2010 Topologies, we added a requirement that the external Edge and internal Edge must use the same type of load balancing.
In the topic, File Storage Support, we added text to include support for the latest service pack for SQL Server.
In the topic, Domain Name System (DNS) Infrastructure Support, we updated the information about mobility support.
Microsoft Lync Server 2010 Documentation Help File
This download contains a compiled help file (chm) of all available Lync Server 2010 IT professional documentation in the TechNet Library. Click Lync_ITPro.exe to download the Lync Server 2010 chm.
Lync Server Resources
We Want to Hear from You