Microsoft Lync Server 2010 (RTM) Release Notes

Welcome to the Microsoft Lync Server 2010 (RTM) Release Notes. Refer to this file for information regarding known issues about Setup, management, Lync Server 2010 (RTM) server roles, and unified communications applications.

About This Document

Setup

Migration

Management

Lync Web App

Localization

Enterprise Voice

Deployment

Configuration

Conferencing

Collaboration

Call Admission Control

Copyright

© 2010 Microsoft Corporation. All rights reserved.

About this Document

This document contains important information that you should know before you deploy and use Microsoft Lync Server 2010 (RTM). For detailed information about Lync Server 2010 (RTM), refer to the documentation included with your installation media.

Back to Top

Setup

Setup Does Not Work When User Downloads and Installs Downloaded UCMASDKWebDownload.msi in a Path that Contains Double-Byte Characters

Issue:

When a user downloads and installs UCMASDKWebDownload.msi in a path that contains a double-byte character set (for example, %Systemdrive%\UCMASDK\) and then clicks SetupUCMASdk.exe from that path, no Install button appears in the setup wizard to install the SDK.

Resolution:

Use the default installation location or a location without double-byte characters to install the downloaded .msi file.

Monitoring-Archiving Server Installation MSI Fails While Creating MSMQ Queue File

Issue:

Although the Microsoft Message Queuing (MSMQ) and Active Directory Domain Services prerequisites are satisfied, installing the Monitoring-Archiving server fails with an error indicating that the MSI failed to create the .\lcsxxx queue file. The error appears in the MSI log file.

Resolution: To work around this issue, perform the following steps:

1.  Determine whether you installed MSMQ before you joined the server to the domain:

1. On the server where you are installing Monitoring-Archiving, click Start, then Administrative Tools, and then Server Manager.

2. Expand Features, right-click Message Queuing, click Properties, and then click the Security tab.

If you see the following error, MSMQ was not installed correctly:

"The security descriptor cannot be obtained. Error: This operation is not supported for Message Queuing installed in workgroup mode"

2.  Remove MSMQ by using Server Manager:

1.  In Server Manager, click Features.

2.      Click Remove Feature, and clear Message Queuing.

3.      Use the Remove Feature wizard to remove MSMQ.

3.      Restart the server, and reinstall MSMQ, including the Directory Service Integration component.

4.  Rerun Setup to install Monitoring-Archiving server.

Back to Top

Migration

Mediation Server Pools Have Interoperability Issue with Office Communications Server 2007 and Office Communications Server 2007 R2

Issue:

Due to an architectural change in Lync Server 2010, you can now deploy a Mediation Server pool with multiple computers. If you have a coexistence environment with Office Communications Server 2007 or Office Communications Server 2007 R2 and you use the down-level Phone Routing Configuration dialog box, you see the pool as well as the individual servers within the pool listed as individual entries. You cannot use the individual servers in the pool for route configuration. You can use only the pool fully qualified domain name (FQDN) for route configuration.

Resolution: If you require a phone route from a down-level pool, first determine the valid pool FQDN of the Lync Server 2010 Mediation Server pools, and then configure phone routes only to the pool FQDNs.

Back to Top

Management

Do Not Override Execution Time for Synthetic Transactions in System Center Operations Manager 2007 R2

Issue:

If you override the execution time (Interval) or sync time (SyncTime) parameters for any synthetic transaction by using Microsoft System Center Operations Manager 2007 R2, you will break the workflow "cook down" feature in System Center Operations Manager . Breaking this feature results in higher CPU and memory utilization on the synthetic transaction watcher node, because multiple workflows are now running for each pool.

This situation applies only to deployments that have deployed System Center Operations Manager pack monitoring and have deployed a Synthetic Transaction watcher node to automatically execute synthetic transactions periodically from System Center Operations Manager.

Resolution:

The possible workarounds are as follows:

Some Synthetic Transactions Ignore the -RegistrarPort Input Parameter

Issue:

Synthetic transactions that test web service (https) functionality do not use the RegistrarPort parameter that is passed using command line. Instead they use the default values specified in the topology document.

The following synthetic transaction cmdlets exhibit this behavior:

Test-CsAddressBookService

Test-CsAddressBookWebQuery

Test-CsGroupExpansion

Test-CsLIsCinfiguration

Test-CsClientAuth

Test-CsPhoneBootStrap

Resolution:

No workaround is available in this release.

Synthetic Transactions Do Not Work When Executed from a Workgroup or from Non-Domain Joined Computers

Issue:

Synthetic transactions need access to Active Directory Domain Services to execute successfully. Running a synthetic transaction from a workgroup or non-domain joined computer results in a failure.

Resolution:

No workaround available in this release.

Do Not Specify Invalid Override Values for Lync Server 2010 Script Parameters in System Center Operations Manager 2007 R2

Issue:

When you use Microsoft System Center Operations Manager 2007 R2 management pack to monitor Lync Server 2010, it does not provide parameter validation for script related rules and monitors.  Overriding script parameters with invalid values results in rule or monitor failure alerts.

This situation applies only to deployments that deployed System Center Operations Manager pack monitoring and deployed a Synthetic Transaction watcher node to automatically execute synthetic transactions periodically from System Center Operations Manager .

Resolution:

When overriding any script parameters in System Center Operations Manager 2007 R2, ensure that you use values that are acceptable for that parameter. For example, when overriding parameters such as Timeout or Interval, use integer values (in seconds) greater than zero.

Synthetic Transactions Do Not Work When TargetFqdn Parameter Is Not Specified

Issue:

Synthetic transactions do not work when executed without the optional TargetFqdn parameter.

This situation applies to deployments where the DNS SRV record for the SIP domain does not match the returned Host FQDN suffix. For example, DNS SRV lookup for SIP domain _sip_tls.contoso.com returns fqdn: pool01.abc.com.

Resolution:

Specify the TargetFqdn parameter explicitly in the command line. For example:

Test-CsRegistration -TargetFqdn pool01.abc.com -UserSipAddress user1@contoso.com

Alerts from Monitor "SIP Proxy: Sends Queued" May Be Inaccurate

Issue:

When Microsoft System Center Operations Manager 2007 R2 management pack is deployed to monitor Lync Server 2010, the alert "The average time (in seconds) the messages delayed in outgoing (send) queues" may be incorrect.  The underlying performance counter CS Registrar SIP -01 Peers -SIP  017 -Send Outstanding reports multi-instance values. The instances _Total and Clients are not filtered out, causing incorrect alerts.

This situation applies only to deployments that deployed System Center Operations Manager management pack to montior Lync Server 2010.

Resolution:

Disable this monitor in the System Center Operations Manager 2007 R2 Operations console, as follows: 

1. Navigate to the Alert details view.

2. Click Alert Monitor.

3. Click the Overrides tab, and then click Disable.

Lync Server Management Shell Caches Credentials Using CaAccount, CaPassword Parameters in the Request-CsCertificate Cmdlet

Issue: Lync Server Management Shell host caches credentials that are provided with the CaAccount and CaPassword  parameters in the Request-CsCertificate cmdlet. This enables the user to potentially request multiple certificates without providing a new account and password.

Resolution: Allow the credential cache to expire (after about two minutes), or close and reopen the Lync Server Management Shell host (cmdlet window) to force the deletion of the cached credentials.

Updating PSTN Gateway FQDN Is Not Correctly Reflected in Read-Only Property Page of PSTN Gateway

Issue:

When you modify a public switched telephone network (PSTN) gateway fully qualified domain name (FQDN) in the Edit Properties dialog box in Topology Builder, the updated FQDN is not correctly displayed in the Read-Only Property page. The page still shows the previous value.

Resolution:

The updated value is set correctly, so no further changes are required. To view the current value, reopen the Edit Properties page. To update the Read-Only Property page, you can save the topology to a file, close Topology Builder, and reload the topology document. Alternatively, publish the topology, and download it again.

IIS Logging for Lync Server Web Sites Is Enabled by Default

Issue:

IIS logging for Lync Server websites is enabled by default during Lync Server 2010 Front End Server installation. Based on user model performance runs, IIS logs grow at the rate of approximately 500 MB every day.

Resolution:

If you are concerned about running out of disk space due to growing IIS logs, disable IIS logging for Lync Server web sites by using IIS Manager.

You need to disable IIS logging during downtime because changing the IIS logging setting causes existing Lync Web App meetings to disconnect.

The Lync Server web site names are:

Lync Server Internal Web Site

Lync Server External Web Site

Using Non-ASCII Characters

Issue:

Setup will fail if the destination folder name includes non-ASCII characters (including UNICODE, double-byte character set (DBCS), UTF-8, and UTF-16). In addition, Setup may succeed but the server will not start if non-ASCII characters are contained in the following:

Resolution:

Use only ASCII characters in the destination folder name, computer name, domain name, user name, user SIP URI, and service account names.

Changing the FQDN of a Server or Pool

Issue:

Changing the FQDN of a server or pool that is part of a Lync Server 2010 Standard Edition or Enterprise Edition pool deployment is not supported. There are various dependencies in the deployment, including servers not functioning correctly and homed users not being able to connect.

Resolution:

Deactivate and uninstall the Lync Server 2010 servers, change the FQDN of these servers as desired, and then install and activate the Lync Servers with the new name.

Wildcard Not Supported for Internal SIP Domains in Microsoft Lync Server 2010

Issue:

In Office Communications Server 2007 R2, you could use a wildcard at the beginning of internal SIP domains in the Microsoft Management Console (for example: *.microsoft.com). The wildcard supported SIP domains such as finance.microsoft.com or exchange.microsoft.com. In Lync Server 2010, wildcards are not supported for internal SIP domains.

Resolution:

Manually enter every owned SIP domain in Topology Builder.

Lync Server Becomes Unresponsive when Running on Windows Server 2008 with SP2

Issue:

Lync Server services become non-responsive when running on Windows Server 2008 with SP2. The condition typically shows up under load.

Resolution:

Install the operating system update described in the Knowledge Base article KB968967 at http://go.microsoft.com/fwlink/?LinkId=187766. You should apply this update before you install Lync Server 2010 on Windows Server 2008 with SP2. The update is not needed if you install on Windows 2008 R2.

Default Security Settings on Windows Vista and XP Prevent Lync 2010 From Signing In Using NTLM When Minimum Session Security Requires 128-Bit Encryption on Lync Server

Issue:

Windows Server 2008 R2 has changed the default setting for NTLM minimum session security to require 128-bit encryption. By default, 128-bit encryption for NTLM authentication is disabled in Windows Vista and Windows XP SP3. As a result, unless this setting is harmonized between the client and Lync Server, NTLM authentication fails. This may result in users receiving the following error message: "Cannot Sign in to Lync : Lync was unable to sign in. Please verify your logon credentials and try again..." In this case, the client logs reveal only that the SIP registration request was rejected with a 401 response.

This is particularly important for external clients because Kerberos is not available externally.

Resolution:

It is currently recommended that for desktop clients, the settings be harmonized. For more information, see "Network security: Minimum session security for NTLM SSP based (including secure RPC) clients" at http://go.microsoft.com/fwlink/?LinkId=187784.

If this is not possible, 128-bit NTLM encryption must be disabled on the server.

Third-Party DLL Missing Version Information

Issue:

The third-party DLL (MS.errorreporting.dll ) that is used to create the DMP file that is uploaded to Watson when a crash occurs is missing version information. The file properties for this DLL are as follows:

Filename: MS.errorreporting.dll

Company: Microsoft Corporation, Copyright � 2007

Product Name: Microsoft Watson Error Reporting

Date: July 11, 2007

Resolution: There is no workaround.

Stopping RtcSrv for an Extended Time May Cause Web Authentication to Fail if the Local Database Becomes Stale

Issue:

Running Stop-CsWindowsService stops all Lync Server services, including RtcSrv, and provides a warning that IIS is not stopped. Because IIS is still running and RtcSrv is stopped, Web authentication may fail. This situation occurs because Web authentication accesses the local database, which might have stale data because RtcSrv is not running. This issue occurs only on servers running Lync Server 2010 Enterprise Edition.

Resolution: Manually stop Lync Server IIS Web sites.

Cmdlets that Use DCOM or Moving Users by Using Lync Server Control Panel Can Fail for Hardware Load Balanced Pools

Issue:

The Windows Server security feature called loopback check can cause cmdlets that use DCOM to fail for hardware load balanced pools with the following error:

Unable to connect to some of the servers in pool "<pool FQDN>" due to a Distributed Component Object Model (DCOM) error. Verify that Front End service is running on servers in this pool. If the pool is set up for load balancing, verify that load balancer is configured correctly.

The following cmdlets use DCOM:

Move-CsAnalogDevice

Move-CsApplicationEndpoint

Move-CsCommonAreaPhone

Move-CsConferenceDirectory

Move-CsExUmContact

Move-CsLegacyUser

Move-CsRgsConfiguration

Move-CsUser

Update-CsAddressBook

Update-CsUserDatabase

Moving users by using Lync Server Control Panel may fail with the same error.

These cmdlets use the IP address of the pool to connect to the DCOM interface for moving and updating data. When a DCOM call loops back to the same Front End Server, it fails authentication because the IP address for the pool is not in the list of allowed host names for loop-back check (that is, the IP address is not in BackConnectionHostNames).

Resolution:

Use one of the following workarounds:

1.    Locate the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0 registry key.

2.    In BackConnectionHostNames, add the IP address of the hardware load balancer for the pool.

3.    Rerun the cmdlet.

Do Not Use Short (Netbios) Name When Specifying a SQL Server Store (Specifically, Central Management Store)

Issue:

Performance issues and time-outs may occur if you do not specify the full fully qualified domain name (FQDN) for the SQL Server.

Resolution:

When setting up SQL stores, you must specify the full FQDN of the SQL Server. Do not use the short (NetBIOS) name.

This workaround applies to the following:

  • Setting up SQL stores by using Topology Builder.
  • The Install-CSdatabase cmdlet. Use the full FQDN:
    Install-CSDatabase -CentralMgmtStore -SqlServer sqlsrv.contoso.com -InstanceName rtcinst
  • The Set-CSConfigurationStoreLocation cmdlet. Use the full FQDN:
    Set-CSConfigurationStoreLocation -SqlServer sqlsrv.contoso.com -InstanceName rtcinst

For Beta and RC/RTM it will be validated that the full FQDN name is specified for the SQL Server.

Conferencing Attendant Application Does Not Work Correctly if Default SIP Domain Is Changed

Issue: If you change the default SIP domain after installing the Conferencing Attendant application, the Conferencing Attendant application does not work correctly.

Resolution:

If you need to change the default SIP domain, perform the following steps:

Autoupdate Has Been Removed; Lync Automatic Updates Now Use Windows Server Update Services or Microsoft Update (Beta Refresh)

Issue:

You can no longer automatically update Lync 2010 by creating a Client Version rule and specifying the location where you downloaded an update from Microsoft.

Resolution:

You can update Lync 2010 by checking Microsoft Update for a newer version. Alternatively, if your organization uses Windows Server Update Services (WSUS), you can use it to deploy updates to Lync endpoints.

To check for updates, create a Client Version rule and specify block and upgrade or allow and upgrade. When Lync 2010 receives this message from the server, it checks Microsoft Update (or WSUS, if you use WSUS) for an update. If an update is available, Lync 2010 downloads it.

Back to Top

Lync Web App

Firefox Users Cannot Join Meeting as Authenticated User Through Lync Web App from a Computer Running a Windows Operating Sysytem when Their Primary Registrar Is Down.

Issue:

A user can be assigned to primary and secondary registrar pools. When the primary registrar is down, users who use the Firefox browser on a computer running a Windows operating system cannot join a meeting as authenticated users by using Lync Web App.

Resolution:

Running Test-CsWebApp and Test-CsWebAppAnonymous Cmdlets Cause Lync Server Management Shell to Fail

Issue:

Test-CsWebApp and Test-CsWebAppAnonymous cmdlets are not supported in Lync Server 2010. Running these cmdlets causes Lync Server Management Shell to fail. 

Resolution: Test-CsWebApp and Test-CsWebAppAnonymous cmdlets are not supported in Lync Server 2010. If you ran one of these cmdlets and Lync Server Management Shell failed, close Lync Server Management Shell and restart it to run other cmdlets.

Back to Top

Localization

Content for Catalan Not Available

Issue: Due to technical limitations, localized content and Help files cannot be provided online for the Catalan release of Microsoft Lync 2010.

Resolution:

Users will be directed to Spanish product documentation and Help files at Office.com.

Note: The referenced user interface strings and screenshots in the Spanish content may differ from the Catala user interface.

Back to Top

Enterprise Voice

Installing Lync 2010 Cleans up Delegates/ Team-Call Group Members for Existing Users Because the Enterprise In-Band Policy for Delegates/ Team-Call Group False by Default

Issue:

By default, the Delegate/ Team-Call Group features are disabled across the enterprise. As a result, the Delegates/ Team-Call Group members are cleaned up for any existing users when Microsoft Lync 2010 is installed unless the appropriate voice policy for Delegates/ Team-Call Group is set.

Resolution:

The administrator can enable or disable the Delegate/ Team-Call Group features by setting the appropriate per-user voice policy on the server. The in-band policies to control these features are EnableDelegation and EnableTeamCall.

Incorrect Response Group Agent Console Web Page Is Shown When Logged in Lync 2010 User Differs From Logged in Computer User

Issue:

When users sign into Lync 2010 as a different user than they used to sign in to the desktop computer, they are unable to view the correct Response Group agent console Web page. 

Resolution:

This issue may occur because the credentials for the logged in computer user are used instead of the specified Lync credentials. Internet Explorer might be configured to operate this way by default.

To resolve this issue, perform the following steps in Internet Explorer:

1.    Click Tools, Internet Options, and then Security.

2.    Select the proper zone visibility for the Response Group agent console (for example, Local intranet or Trusted sites).

3.    Under the Scripting node, verify that Active scripting is set to Enable.

4.    Under the User Authentication node, verify that Logon is set to Prompt for user name and password.

This change requires users logged into Lync 2010 to re-enter their user credentials upon successful signin, but ensures that the correct Response Group agent console is displayed.

Cannot Add IM to an Anonymous Response Group Conversation to a Work Phone Number

Issue: A Lync Server 2010 Response Group agent making a call on behalf of a response group cannot add instant messaging (IM) to the anonymous conversation if the call has been started by calling a work phone number.

Resolution: To be able to add the IM modality to an anonymous call, a Lync Server 2010 Response Group agent needs to start the call on behalf of the response group by making a Lync call.

Calls Routed Through a Mediation Server Running Office Communications Server 2007 Cannot Be Parked

Issue: When an incoming public switched telephone network (PSTN) call routes through an Office Communications Server 2007 Mediation Server to reach a Lync user homed on Lync Server 2010, and the Lync user tries to park the PSTN call, the call will fail.

Resolution: Upgrade the topology to Lync Server 2010.

Moving the Audio of a Call to Another Device While Connected to Conferencing Attendant or Response Group Applications Does Not Work as Expected

Issue:

If you use Lync 2010 and you attempt to move the audio of a call that is connected to the Response Group application or Conferencing Attendant application, including moving the call to your mobile phone by using the endpoint transfer feature, the operation fails and the call remains connected to Lync 2010.

If you use Lync 2010 Phone Edition and you attempt to move the audio of a call that is connected to the Response Group application or Conferencing Attendant application, the operation fails and the call remains connected to Lync 2010 Phone Edition. An error message may not appear.

Resolution: There is no workaround for this release.

Call from Mediation Server Is Sent to Old Front End Pool if a 302 Is Received After Changing Mediation Server to a New Front End Pool

Issue:

If a stand-alone Mediation Server receives a call from a public switched telephone network (PSTN) gateway or SIP trunk, and Lync Server 2010 returns a 302 redirecting the call to a new target, and the next hop Front End was updated to a new pool, Mediation Server sends the redirected call to the old Front End pool.

Resolution:

Restart the Mediation Server service after publishing the new topology document with the new Front End pool as the Mediation Server next hop.

Mediation Server Cannot Process a REFER Message if Target Is a Server with Format sip:hostname:port and Associated Trunk Has EnableReferSupport Set to True

Issue:

When Mediation Server receives a request from Microsoft Lync 2010 or Microsoft Lync Server 2010 to transfer the call to a SIP server, if the new destination in the refer-to header has the format sip:hostname:port and the associated trunk has EnableReferSupport set to True in TrunkConfiguration, the transfer operation fails with a 400 Invalid Request error.

Resolution:

To transfer a call to a SIP server, use a Globally Routable UA URI (GRUU) format for the refer-to URI, or set EnableReferSupport to False.

KHI Alerts in System Center Operations Manager Do Not Contain the List of All Gateways Detected as Down by Mediation Server

Issue:

When Mediation Server detects that new gateways are down, the alert description contains only the original list of gateways, due to a limitation in Microsoft System Center Operations Manager when updating the description of alerts associated with a key health indicator (KHI).

Resolution:

To see the updated list of gateways that are detected as down, review the events associated with the alert and look for the most recent event raised by Mediation Server.

RTCPCallOnHold Setting in CSTrunkConfiguration Is Not Applied if Music On Hold Is Enabled in Lync 2010

Issue:

Lync 2010 and Mediation Server by default expect public switched telephone network (PSTN) gateways and trunks to send Real-Time Transport Control Protocol (RTCP) packets independently if Real-Time Transport Protocol (RTP) packets are being sent. If an associated trunk configuration has RTCPCallsOnHold set to False and RTCPActiveCalls set to True, calls put on hold may be terminated after 30 seconds if Music on Hold is enabled on Lync 2010 and the gateway or SIP trunk does not send RTCP packets to the Mediation Server.

Resolution:

To avoid calls being terminated when they are put on hold, set RTCPActiveCalls to False. When Music on Hold is enabled, music flows from Lync 2010 to the PSTN gateway or SIP trunk and the call is considered to be in active state.

Quality Of Service Reports Sent from Lync Server 2010 Mediation Server Are Rejected by Office Communications Server 2007 R2 Front End

Issue:

Calls that involve an Office Communications Server 2007 R2 endpoint and are routed to a Lync Server 2010 Mediation Server are missing the gateway side Quality of Service report. When Lync Server 2010 Mediation Server sends a Quality of Service report for the gateway link side of a call that is associated with an Office Communications Server 2007 R2 endpoint, the report is routed to a QoE Agent on the Office Communications Server 2007 R2 endpoint, which cannot route the report, and the report is rejected. This problem affects only the gateway side report. The Quality of Service report for the Lync Server side of the call is processed properly.

Resolution:

No workaround is available.

The Order of Secondary Languages for Dial-In Conferencing Access Numbers Is Random

Issue:

When creating secondary languages for a dial-in conferencing access number, the administrator cannot choose the order of the languages, and the caller hears the prompts for choosing the languages in a random order.

Resolution:

There is no workaround in this release.

Back to Top

Deployment

Single-Label Active Directory Domains Are Not Supported

Issue: Using Active Directory domains configured with single-label domains is not supported in Lync Server 2010. For example, using a domain of contoso is not supported, but using a domain name of contoso.com is supported. For more information, see http://go.microsoft.com/fwlink/?LinkId=143752.

Resolution: By design.

Windows Updates Needed for Lync Server 2010 Monitoring and Archiving Deployments

Issue:

If you plan to deploy Monitoring or Archiving, you should install the appropriate Windows Update on each Front End, Archiving, and Monitoring server. The update fixes issues with MSMQ.

Resolution:

For Windows Server 2008 R2, install the following update:

 http://go.microsoft.com/fwlink/?LinkId=202959

For Windows Server 2008, install the following update:

 http://go.microsoft.com/fwlink/?LinkId=202958

Limited Support of Standard Edition Server Collocation with Monitoring and Archiving Server

Issue:

You can collocate Standard Edition Server with Monitoring and Archiving Server in Topology Builder for evaluation or demonstration purposes. Collocating Standard Edition Server with Monitoring and Archiving Server is not supported in production deployments.

Resolution: There is no workaround.

Back to Top

Configuration

Non-Domain Joined Edge Computer Requires DNS Suffix to Be Set Manually

Issue:

By default, a computer that is running the Edge Server role and is not joined to a domain is configured only with a shortname. However, it is configured with its FQDN in the topology document.

You must configure each Edge server with its full FQDN in the topology, as well as ensure that this Edge server is configured with the correct DNS suffix.

Resolution:

Perform one of the following procedures to set up the DNS suffix on an Edge server that is not joined to the domain:

 

Using the user interface:

1.    Click Start, right-click Computer, and then click Properties.

2.    Under Computer name, domain and workgroup settings, click Change Settings.

3.    On the Computer Name tab, click Change.

4.    In the Computer Name/Domain Changes dialog box, click More.

5.    Under Primary DNS suffix of this computer, enter the domain suffix, for example, Contoso.com.

6.    Click OK to close the dialog boxes.

Using the command line:

1.    Open a cmd prompt as local administrator.

2.    Type netdom computername <hostname> /Add:<hostname>.<domain>.

3.    Type netdom computername <hostname> /MakePrimary:<hostname>.<domain>.

For example, if your short hostname is "edge1" (non-domain joined) and your desired domain is "contoso.com":

netdom computername edge1 /Add:edge1.contoso.com

netdom computername edge1 /MakePrimary:edge1.contoso.com

Back to Top

Conferencing

User May Get Disconnected from Audio/Video Conferences after Front End Server Restarts in an Enterprise Edition Topology or After a Survivable Branch Appliance Restarts

Issue:

Users who are part of an active audio/video conferences may get disconnected after Front End server restarts in an Enterprise Edition topology or after a Survivable Branch Appliance restarts. 

Resolution:

Users have to rejoin the conference.

Windows Server 2008 SP2 Update Required to Avoid Increasing Memory Usage on Web Conferencing Proxy Server

Issue:

Computers running Windows Server 2008 with Service Pack 2 (SP2) require an operating system update to avoid increasing memory usage on the Web Conferencing proxy server.

Resolution:

Install the operating system update described in the Knowledge Base article KB979231 at http://go.microsoft.com/fwlink/?LinkId=200747. After you apply this update, there should be no increased memory usage. 

.NET Framework Update Required to Avoid Increasing Memory Usage on Web Conferencing Server

Issue:

The following .NET Framework update is required to avoid increasing memory usage on Web Conferencing Server: http://go.microsoft.com/fwlink/?LinkId=202909

Resolution:

After you apply the update, memory usage should not increase.

Lync Server Web Conferencing Compatibility Does Not Support a Custom URL for In Meeting Help

Issue:

Lync Server Web Conferencing Compatibility does not support a custom URL for In Meeting Help. As a result, you cannot customize your help pages for Live Meeting Console meetings that you migrated from Office Communications Server 2007 R2 pools. Users will always be directed to the default help page on the Internet.

Resolution: There is no workaround for this release.

Some Office Communications Server 2007 Clients Cannot Join a Lync Server 2010 Meeting (Invitee Only or Locked) By Using the PSTN

Issue:

Users who try to join a Lync Server 2010 meeting (invitee only or locked) by using Office Communicator 2007 or Office Communicator 2007 Phone Edition when they are not invited cannot join the meeting by using the public switched telephone network (PSTN).

Resolution: There is no workaround in this release.

Internet Explorer 8 Users on Windows Server 2008 May Need to Click Through Four Pop-up Windows to Join a Meeting on Lync Server 2010

Issue:

When a user joins a meeting using Internet Explorer 8 on Windows Server 2008 and uses the default Internet Explorer 8 security settings, the user may have to click through as many as four pop-up windows to join the meeting. Specifically, the user may be prompted for the following:

Resolution:

Click OK on each pop-up window.

If a User Uses Lync Web App for Collaboration and Office Communicator 2007 R2 for Audio and Then Unmutes from Lync Web App, the User Cannot Hear the Audio

Issue: In a meeting, if a user is using Lync Web App for collaboration and joins audio by using Office Communicator 2007 R2 and then unmutes from Lync Web App, the user cannot hear the audio.

Resolution: The user needs to unmute from both Lync Web App and Office Communicator 2007 R2 to allow the call to be heard. Alternatively, when a user joins audio by using Office Communicator 2007 R2, both mute and unmute can be managed from the same client.

Moving a Lync Server 2010 User Back to Office Communications Server 2007 R2 or Office Communications Server 2007 Causes Conferences that Were Scheduled on Lync Server 2010 to Be Lost

Issue: If you use Move-CsUser to move a Lync Server 2010 user back to Office Communications Server 2007 R2 or Office Commmunications Server 2007, the conferences that the user scheduled while on Lync Server 2010 are lost.

Resolution: After users are moved back to Office Communications Server 2007 R2 or Office Communications Server 2007, they must reschedule all the conferences they scheduled when they were on Lync Server 2010.

Office Communications Server 2007 R2 Users Cannot Sign In to a Lync Server 2010 Dial-In Conferencing Settings Web Page

Issue:

Office Communications Server 2007 R2 users cannot sign in to the Lync Server 2010 Dial-in Conferencing Settings Web page.

Resolution:

Office Communications Server 2007 R2 users must use only the Office Communications Server 2007 R2 Dial-in Conferencing Settings Web page. Users can access this page from Office Communicator 2007 R2 or from the invitations created from the 2007 R2 version of Conferencing Add-in for Microsoft Office Outlook.

Microsoft Lync 2010 Attendee Is Not Available For Download from the Automated Redirection in Join Launcher

Issue:

Microsoft Lync 2010 Attendee is not available for download by using the automated redirection to the Lync 2010 Attendee download page listed in the web.config file of the Join Launcher Web component.

Resolution:

Administrators should install Lync 2010 Attendee by using the images provided on installation media. Details about this installation are provided in the Deployment Guide. Administrators should also remove the Lync 2010 Attendee URL from "aocPath" setting in the Join Launcher web.config file.

Meeting Join Fails for Deployments That Have FIPS Enabled

Issue:

When a Lync Server 2010 deployment is enabled for Federal Information Processing Standard (FIPS), the URL for joining a meeting fails to join the meeting.

Resolution: See the workaround described at http://go.microsoft.com/fwlink/?LinkId=196183.

Meeting Join Fails When ActiveX Controls Are Disabled on Internet Explorer 6 Running on Windows XP with Service Pack 3

Issue:

If a user runs Internet Explorer 6 on Windows XP with SP3 and has ActiveX controls disbled, the meeting join fails. The user sees a blank browser window after clicking the join link.

Resolution:

Enable ActiveX controls in Internet Explorer.

Lync Server 2010 Users Who Dial In to an Office Communications Server 2007 R2 Conference Do Not Appear in the Roster of Participants Who Are Already in the Conference

Issue:

Lync Server 2010 users who join an Office Communications Server 2007 R2 conference by dialing in do not appear in the roster of participants who are already in the conference. However, they do appear in the roster of participants that join the conference after them.

Resolution:

Users are encouraged to rely on social confirmation of new attendees joining a conference.

Dial-In Conferencing Does Not Work If the Domain of an Access Number Is Changed After It Is Created

Issue:

Lync Server 2010 Conferencing Attendant stops functioning and requires a restart if the SIP address of its private contact object no longer matches the default SIP domain of the deployment. This error can occur if the default SIP domain of the deployment is changed (for example, by using the New-CsSipDomain cmdlet or the Set-CsSipDomain cmdlet) or the SIP address of the Conferencing Attendant private contact object is changed.

Resolution:

If you need to change the default SIP domain of the Lync Server 2010 deployment after deploying Conferencing Attendant or the SIP domain of a private contact object for an instance of Conferencing Attendant, you must restart the Conferencing Attendant service after you make the change.

Office Communications Server 2007 R2 Dial-In Conferencing Access Numbers that are Represented in Lync Server Central Management Store Cannot Be Removed

Issue:

During migration, the Lync Server Management Shell cmdlet Import-CsLegacyConfiguration is run. This cmdlet creates representations of Office Communications Server 2007 R2 access numbers in Lync Server 2010 Central Management Store so that Lync Server 2010 users can see all access numbers. These Office Communications Server 2007 R2 access numbers cannot be removed from Central Management store.

Resolution:

You can modify the order in which dial-in access numbers are displayed in a meeting invitation by using the Set-CsDialInConferencingAccessNumber cmdlet, as follows:

Set-CsDialInConferencingAccessNumber <sip uri> -ReorderedRegion <region name> -Priority <new index>

If a User with an Office Communications Server 2007 Client Enters the Lobby When Calling Conferencing Attendant, the User Cannot Be Admitted to the Meeting

Issue:

If a meeting is scheduled by using the Online Meeting Add-in for Microsoft Lync 2010 and a user who is homed on Office Communications Server 2007 uses an Office Communications Server 2007 client to dial in to the meeting from inside the enterprise, the user will be unable to join the meeting if he enters the lobby while trying to join. Even if the leader attempts to admit the user, the user remains in the lobby and is unable to join the meeting.

A user could end up in the lobby, creating this situation, if the Lync Server 2010 meeting is locked or is a closed meeting, or if other meeting settings are configured in such a way as to cause a user to end up in the lobby.

This issue does not affect users who dial in to the meeting from outside the enterprise. This issue does not occur with Office Communications Server 2007 R2 users and clients.

Resolution:

Migrate users who are homed on an Office Communications Server 2007 pool and who use Office Communications Server 2007 clients to a Lync Server 2010 pool. Users can continue to use Communications Server 2007 clients with a Lync Server 2010 pool. This problem occurs only for Office Communications Server 2007 clients on an Office Communications Server 2007 pool.

If You Use Set-CsPinSendCAWelcomeMail to Send an Email that Contains Non-ASCII Characters, the Email Appears Garbled or Has Many '?'s

Issue: If you use Set-CsPinSendCAWelcomeMail to send an email that contains non-ASCII characters, the email appears garbled or has many questions marks ('?').

Resolution:

To include non-ASCII characters in the welcome email template, you need to modify the Set-CsPinSendCAWelcomeMail.ps1 script. The default location for the script, as well as the default template, is at C:\Program Files\Common Files\Microsoft Lync Server 2010\Modules\Lync.

To make your modifications take effect after you modify the file, close the open Lync Server Management Shell window and re-open it.

Modify the script as follows:

In line 48:

$MailBody = Get-Content $TemplatePath -Encoding ASCII -Delimiter "\b"

replace "ASCII" with another encoding. The recommended encoding is "UTF8", but you can also use "Unicode". (For an explanation of the recommendations, see below.)

For example:

$MailBody = Get-Content $TemplatePath -Encoding UTF8 -Delimiter "\b"

In lines 138 and 143:

Send-MailMessage [...]

You need to add an encoding parameter, using the same encoding choice that you used in line 48. In this cmdlet, you cannot fill the encoding parameter with a simple string as in line 48. Instead, you need to specify it as "System.Text.Encoding". Append the modification (using either "UTF8" or "Unicode") at the end of both lines:

-Encoding ([System.Text.Encoding]::UTF8)

For example:

Send-MailMessage -To $UserEmailAddress -From $From -Bcc $Bcc -Cc $Cc -Subject $Subject -Body "$MailBody" -BodyAsHtml:$BodyAsHtml -SmtpServ $SmtpServer -UseSsl:$UseSsl -Verbose:$Verbose -Encoding ([System.Text.Encoding]::UTF8)

Send-MailMessage -Credential $Local_Credential -To $UserEmailAddress -From $From -Bcc $Bcc -Cc $Cc -Subject $Subject -Body "$MailBody" -BodyAsHtml:$BodyAsHtml -SmtpServ $SmtpServer -UseSsl:$UseSsl -Verbose:$Verbose -Encoding ([System.Text.Encoding]::UTF8)

 

UTF8 is the recommended encoding choice over Unicode because when the script is modified to use UTF8 encoding in all three places, the script works well with any template:

- Encoded in UTF8 (with or without special characters)

- Encoded in Unicode (with or without special characters)

- Encoded in Unicode Big Endian (with or without special characters)

- Encoded in ANSI (without special characters, that format doesn't support non-ASCII characters)

When the script is modified to use Unicode encoding, the script works with any template encoded in UTF8, Unicode or Unicode Big Endian (with or without special characters), but it does not work with a template encoded in ANSI.

Desktop-Paired Lync 2010 Phone Edition Presenter Is Muted in a Conference That Is Under "Audience Mute" When the Video Modality Is Added

Issue:

When the video modality is added to a conference that is under Audience Mute, a desktop-paired Lync 2010 Phone Edition presenter is muted.

Resolution: Desktop-paired Lync 2010 Phone Edition presenters can umute themselves in the conference.

Conference Continues to Be Under "Audience Mute" Even After the Presenter Leaves the Conference

Issue: When a leader or presenter mutes the audience in a conference and then leaves, the conference continues to be under Audience Mute and attendees cannot unmute themselves.

Resolution: Another presenter can remove Audience Mute mode so that attendees in the conference can unmute themselves.

KHI Alerts in System Center Operations Manager Are Not Updated with the List of All the Redundant Trusted Services Marked as Down by Audio-Video Conferencing Server

Issue: When Lync Server 2010 Audio-Video Conferencing Server marks trusted services as down, Microsoft System Center Operations Manager has a limitation when updating the description with new redundant trusted services (such as Lync Server 2010 Audio-Video Edge Service, Lync Server 2010 Conferencing Announcement Service, etc.) in the associated key health indicator (KHI) Alert. The KHI Alert description contains only the original list of trusted services that went down, triggering this Alert.

Resolution: To see the updated list of redundant trusted services marked as down, review the other events associated with this alert in System Center Operations Manager and look for the most recent event raised by Audio-Video Conferencing Server.

Back to Top

Collaboration

IM Conferencing Does Not Work for Outside Branch Users Who Are Signed in Through Office Communications Server 2007 R2 Edge Server and Director

Issue: When a branch office user who is homed on a Survivable Branch Appliance or Survivable Branch Server is signed in through Office Communications Server 2007 R2 Edge Server and Director, some functionality in conferences, such as instant messaging (IM) and data sharing, may not work properly.

Resolution:

Use one of the following workarounds:

 

 

Back to Top

Call Admission Control

Call Admission Control : For Transition from Beta Refresh to RC the Front End Pool Needs to be Upgraded Before the A/V Edge Server

Issue:

Due to incompatibility in authentication protocol between the A/V Edge Server and the Bandwidth Policy Service, the Front End pool needs to be upgraded from Beta/Beta Refresh to RTM before the A/V Edge Server is upgraded from Beta/Beta Refresh.

Resolution: There is no workaround for this release.

Back to Top

Copyright

This document supports a preliminary release of a software product that may be changed substantially prior to final commercial release, and is the confidential and proprietary information of Microsoft Corporation. It is disclosed pursuant to a non-disclosure agreement between the recipient and Microsoft. This document is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in this document. Information in this document, including URL and other Internet Web site references, is subject to change without notice. The entire risk of the use or the results from the use of this document remains with the user. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 2010 Microsoft Corporation. All rights reserved.

Microsoft, Windows, Windows Live, Active Directory, Internet Explorer, MSN, Outlook, and SQL Server 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.

Back to Top