© 2010 Microsoft Corporation. All rights reserved.
Issue:
Two new top-level Lync 2010 environments, the Conversation Environment and the Phone Environment, work correctly only if Exchange Web Services (EWS) is enabled on the Exchange Server.
If EWS is not available, the following occurs:
Resolution: There currently is no workaround for this issue.
Issue: If a user selects a device as the preferred audio or video device for conversations using Lync 2010, and then detaches the device and plugs it into a different USB port, Lync 2010 may not recognize it because Windows gives it a different name. This issue is limited to Windows Vista.
Resolution: The user can reattach the device to the port to which it was originally attached.
Issue: The display name that appears for an incoming call in the pop-up alert or conversation window may be incorrect when there are multiple Global Address Library (GAL) and/or Outlook contacts that have the same phone number.
Resolution:
There currently is no workaround for this issue.
Issue:
For this release, phone number detection on Internet Explorer Web pages is not enabled in the following cases:
Resolution:
There currently is no workaround for this issue.
Issue:
For users who are using Remote Call Control (RCC), Lync 2010 will not support the following features:
Resolution:
There currently is no workaround for this issue.
Issue:
A user cannot open a voice mail in message in virtualized Outlook 2010 using Lync.
Resolution:
Open the message directly in Outlook.
Issue: Remote Call Control users will not support Web Search.
Resolution: Remote Call Control users should be provisioned with GAL download, and not Web Search.
Issue:
After you upgrade to any Lync 2010 client or device, you cannot update your call forwarding rules from your other clients and devices. This issue will not occur if you've only upgraded to Lync Server 2010 on the back end, and none of the user's clients or devices are upgraded to Lync 2010.
Resolution:
Upgrade all your Lync client or device endpoints at the same time. If that is not possible, you can change your call forwarding rules in your upgraded Lync 2010 client or device.
Issue:
If you place a call using your audio device while running Lync 2010 using two different accounts (on the same computer), the call recipient receives call alerts from both accounts.
If you answer a call on your audio device while running Lync using two different accounts (on the same computer), you may hear a continuous dial tone (which will subside in a few seconds) after the call is answered.
Resolution:
Exit the instance of Lync running the inactive account.
Issue: You are running Windows 7 or Windows Vista, and Lync stops responding when playing sounds.
Resolution:
This results from a Windows issue. Please install the following hotfix: http://support.microsoft.com/kb/981679
Issue:
You may see black squares or other display problems when viewing a shared application.
Resolution:
You can mitigate this by switching to a scaled view if you are viewing the application at a 1-to-1 ratio, or switching to the 1-to-1 view if you are in a scaled view.
Issue:
In a Lync meeting, if a participant is sharing an application or window that cannot be set to layered, for example a Command Prompt window or some versions of Windows Media Player, and another non-shared window completely covers the shared window, the other participants will see a black window. Even partial overlap will cause users to see a black window (in addition to the originally shared window).
Resolution: The participant who is sharing should bring the shared application window to the top, and make sure that none of it is being covered by another window.
Issue:
If Presenter A begins sharing a PowerPoint presentation or whiteboard and then leaves the meeting without clicking Stop Presenting, and then Presenter B begins sharing an application, two issues can occur:
Resolution:
Presenter A should click Stop Presenting before leaving a meeting. (This would prevent the problem from occurring.)
Presenter B should restart his or her sharing session (if it stops due to Presenter C joining the meeting).
Optionally, Presenter B could share the PowerPoint presentation or whiteboard again, and then click Stop Presenting.
Issue: When sharing Microsoft Word during a Lync 2010 meeting, some drop-down menus, tooltips, and combo boxes may not be visible to the viewers.
Resolution: Switch from program sharing to desktop sharing.
Issue:
In addition, the sharing of Windows Media Player in skin modes is not recommended because it results in a less than optimal user experience.
- Windows Server 2008 (earlier than version R2)
- Windows Vista
- Windows Explorer
- Lync (this includes the recording publishing manager and Lync Attendee)
- Sticky Notes
- Windows Sidebar
Resolution:
The user should share their desktop.
Note: A remote desktop session can be shared as an application from the local computer.
Issue:
If the presenter's computer is running outdated graphics drivers, the shared content may appear monochrome to the viewers.
Resolution: The presenter should update their graphics drivers.
Issue:
When the presenter is running Lync 2010, meeting participants who have not upgraded their client can still see the shared programs or desktop. However, if the shared material is much smaller than the screen of the presenter (for example, if the presenter has multiple monitors), the viewer will see a large black space representing the unshared area.
Resolution:
The viewer can upgrade to Lync 2010.
Alternatively, the presenter can share a monitor or desktop, or maximize the shared window so that the non-shared area is minimized.
Issue:
Windows prompts you to switch to basic color when you share your desktop. This may happen if your computer is low on memory, or if the video drivers are outdated.
Resolution:
Try closing other processes that may be consuming memory, and update the video drivers.
If the issue persists, consider switching to basic color when sharing your desktop.
Issue:
When you try to select the Save As or Save with Annotations option in the Attachments dialog box by pressing the Enter key, the content is not saved. This is true for content items that are available in the content bin as well as attachments.
Resolution:
Use your mouse to select the appropriate menu option.
Issue:
Audio and video files that are embedded in a Microsoft Office PowerPoint presentation cannot be played when you share the presentation in a Lync meeting.
Resolution:
There currently is no workaround for this issue.
Issue:
When a person using Lync 2010 joins a meeting that is hosted by a non-federated server, the person is listed as "Guest" in the meeting roster.
Resolution:
There currently is no workaround for this issue.
Issue:
If you are working on a remote computer and initiate a Lync 2010 meeting, you cannot share Microsoft Office Excel with meeting attendees.
Resolution:
To work around this issue, share your desktop instead of the application.
Issue: When you initiate an application sharing session in Lync, the screen flickers, Windows Aero is turned off, and you receive the following message: "The color scheme has been changed to Windows 7 Basic." This does not occur when you share your desktop rather than an application.
Resolution:
Aero is restored to its original state when sharing stops.
Issue:
When you export a meeting recording to a SharePoint site and play it from Windows 7 by using Internet Explorer 8, the browser cannot start the media player. Users are not able to play the WMV recording.
Resolution:
Update Windows manually by using the following steps, or see http://go.microsoft.com/fwlink/?LinkId=185215 for Knowledge Base article KB974431. 1. Close all instances of Internet Explorer. 2. Click Start and then click Default Programs. 3. Click Set program access and computer defaults. 4. Select Custom and then click the double down arrow to display the configuration options. 5. Under Choose a default media player, select Windows Media Player. 6. Click OK. 7. Restart Internet Explorer and try the links again. Internet Explorer should open the file in Windows Media Player.
Issue:
In a Lync meeting, you cannot give control of an application to another presenter if the following are true:
Resolution:
Run Lync with administrator privileges.
Alternatively, you can grant control of your desktop to the other presenter.
Issue:
When you run Lync on Citrix Xenappserver and try to use desktop sharing, Lync stops responding.
Resolution:
There currently is no workaround for this issue.
Issue:
When a meeting organizer schedules back-to-back online meetings using the default meeting options, participants in the second meeting may have access to content (PowerPoint files, whiteboards, polls) that were shared during the meeting organizer's previous meeting.
Lync 2010 makes all content "organizer only" when the last presenter leaves a meeting that is scheduled with default meeting options. However, if participants join the second meeting before all presenters have left the first meeting, these new participants will have access to content from the previous meeting.
Resolution:
The organizer or any presenter can select End and Exit Meeting when the first meeting ends. This ends the meeting for all participants, so Lync 2010 makes all content "organizer only" and therefore unavailable to participants of the second meeting.
Alternatively, the organizer can manually hide all content from meeting participants by choosing Make Available To - Organizer for each item in the meeting Content List.Issue:
If the following steps are performed, issues occur with Outlook integration because the ucmapi component is uninstalled in step 3:
1. Install Microsoft Lync 2010.
2. Later Install Microsoft Lync 2010 Attendant.
3. Uninstall Lync 2010 Attendant.
Resolution:
Reinstalling Lync 2010 addresses the issue by ensuring that the ucmapi component is available and in a suitable state to perform Outlook integration.
Issue:
If the following steps are performed, issues occur with Outlook integration because the ucmapi component is uninstalled in step 3:
1. Install Microsoft Lync 2010 Attendant.
2. Later Install Microsoft Lync 2010.
3. Uninstall Lync 2010.
Resolution:
Reinstalling Lync 2010 Attendant addresses the issue by ensuring that the ucmapi component is available and in a suitable state to perform Outlook integration.
Issue:
The Lync 2010 client installer creates a firewall exception rule for the client. Administrators who distribute the client should be aware of this system-level change.
Resolution: There is no workaround for this issue.
Issue:
The following are error messages related to account configuration issues in Microsoft Exchange or Microsoft Lync 2010 that a user may receive when scheduling an online meeting using the Online Meeting Add-in for Microsoft Lync 2010, followed by their cause and a suggested response:
Message: Unable to identify the calendar owner. Please contact your support team.
Cause: The Online Meeting Add-in for Lync 2010 cannot determine the SMTP or SIP address of the Outlook account.
Response: Contact your Exchange administrator.
Message: Microsoft Exchange is unable to identify you. Please contact your support team.
Cause: The Online Meeting Add-in for Lync 2010 cannot determine the X500 address of the Outlook account.
Response: Contact your Exchange administrator.
Message: You cannot schedule the online meeting because you are not UC enabled or there may be issues with your Lync Server account. Make sure you are signed in to the same account you use for Microsoft Outlook. If the problem continues, please contact your support team.
Cause: The Online Meeting Add-in for Lync 2010 located the account owner's SMTP from Exchange but could not locate the SIP address, either from Exchange or from Lync 2010. You may have signed in to Lync 2010 and Outlook using different accounts.
Response: Contact your Lync administrator.
Message: The person you are acting scheduling on behalf of is not UC enabled or there may be issues with this person's Lync Server account. Make sure you are signed in to the same account you use for Microsoft Outlook. If the problem continues, please contact your support team.
Cause: The Online Meeting Add-in for Lync 2010 located from Exchange the SMTP of the person for whom you are scheduling but could not locate the SIP address, either from Exchange or from Lync 2010. You may have signed in to Lync 2010 and Outlook using different accounts.
Response: Contact your Lync administrator.
Message: Microsoft Exchange is unable to find the email of the person you are acting on behalf of. Please contact your support team.
Cause: The Online Meeting Add-in for Lync 2010 cannot determine the SMTP or SIP address of the person for whom you are scheduling.
Response: Contact your Lync administrator.
Resolution:
Not applicable.
Issue: Scheduling online meeting in Microsoft Outlook 2003 causes Outlook to stop responding.
Resolution:
The fix for this issue will not be available through Windows Update. It will be released with the Office 2003 Cumulative Update around December 15, 2010, which is the regular bi-monthly Office update release. In the meantime, the fix is final and posted internally at http://hotfix. External customers can contact Microsoft Product Support, mention KB 2445403, and request the fix.
Issue:
Lync users may occasionally see "Presence Unknown" for themselves or other people. This is more likely to occur when a user first signs in to a Lync deployment.
Resolution: Sign out of Lync and then sign back in.
Issue:
Certain buttons on the contact card that appears when you point to a person's picture in Lync, as well as the display-related buttons above your contact list, may appear to be unavailable although they are actually available. This is because the buttons are set to a partially opaque state. The following buttons exhibit this behavior:
Resolution:
There currently is no workaround for this issue.
Issue: If Lync is running under a higher privilege than Outlook, Outlook integration features such as presence and conference scheduling may not work. This is because the lower privilege under which Outlook is running will not be able to create a proxy for the out-of-process Lync COM server running under a higher privilege.
Resolution: Check the User Account Control settings, lower the privilege under which Lync is running, and then restart Lync.
Issue:
Some of the existing features in Communicator Mobile 2007 R2 will not work with the upgrade to Microsoft Lync Server 2010. Instant messaging, contacts and presence, and enterprise search using the Communicator Mobile 2007 R2 client will continue to work. The following features will be unavailable until a new mobile client is released:
Resolution:
No workaround exists for the Communicator Mobile 2007 R2 client. A new COMO client is targeted for release with a future Service Pack version of Lync Server.
Issue:
The Attendee process starts automatically when Internet Explorer starts, and it causes Internet Explorer to slow down.
Resolution:
Follow these steps to work around this issue:
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 will fail. 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 as 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.
Issue:
If Lync 2010 is installed on your computer and you have an unsaved PowerPoint presentation, and then you put your computer into sleep mode, PowerPoint will close and your presentation will be lost when you wake your computer.
Resolution:
To avoid losing your presentation, save it before putting your computer to sleep.
Another option is to disable the Lync add-in in PowerPoint:
1. On the File tab in PowerPoint, click Options, and then click Add-Ins.
2. At the bottom of the Add-ins dialog box, in the Manage box, make sure that COM Add-ins is selected, and then click Go.
3. In the COM Add-ins dialog box, clear the Lync Collaboration Add-in check box and then click OK.
The Collaboration tab in PowerPoint will be disabled, but no other PowerPoint functionality will be affected.
Issue: After a user selects a custom sound to be played by Lync 2010, Lync does not play the sound. The most common .wav files have a WAVEFORMTEX format. However, there is a WAVEFORMATEXTENSIBLE format that supports higher quality sound and more channels. Lync 2010 does not support the WAVEFORMATEXTENSIBLE format. Files with the WAVEFORMTEX and WAVEFORMATEXTENSIBLE format have the same extension (.wav), so the user cannot distinguish them by looking at the filename.
Resolution: There is currently no resolution. Users must select .wav files that do not use the WAVFORMATEXTENSIBLE format.
Issue: Lync 2010 users who are logged on to an Office Communications Server 2007 R2 computer or Office Communications Server 2007 computer may see incorrect behavior.
Resolution: Do not use Lync 2010 with previous versions of Office Communications Server. Use Lync 2010 only to sign in to Lync Server 2010.
Issue:
If the system administrator enables Software Quality Metrics (SQM) by using in-band setting "EnableSQMData", end users cannot opt out of the program, and the user interface is misleading.
When a user tries to opt out of the Customer Experience Improvement Program (as SQM is called), the user has the option to click OK. However, when the user returns to the Options dialog, the user interface indicates that the user is participating in the program.
Resolution:
The administrator should disable SQM if end users do not want to send information to Microsoft.
Note: SQM is disabled by default.
Issue:
When you are running Lync 2010 or Lync Server 2010 Attendant, you cannot use the keyboard shortcut Alt+Ctrl+M for any other program. This is because the keyboard shortcut brings up the Lync "debugUI" interface.
When you are not running Lync or Attendant, you can use Alt+Ctrl+M in other programs such as OneNote, Word, or Outlook.
Resolution:
There currently is no workaround for this issue. It will be fixed for the final release candidate. Please use a different procedure to accomplish the task, or temporarily exit Lync.
Notes:
In Word , Alt+Ctrl+M is used to add comments to a document. With Lync running, you can click the Review tab and then click New Comment.
In OneNote, Alt+Ctrl+M is used to move or copy pages. With Lync running, you can right-click the page tab and then click Move or Copy.
Issue:
When using JAWS screen reading software, if you scroll down or up, some of the items in the list are skipped because the control jumps multiple items.
Resolution: This is a known limitation in JAWS. Disable the Access key in JAWS to resolve this issue
Issue: When the browser zoom setting is increased or decreased, Lync Web App does not respond.
Resolution:
Due to Silverlight limitations, the current release does not support browser zoom settings.
Issue:
On Windows Server 2008 R2, Windows Server 2008, and Windows Server 2003, you can't install the Lync Web App plug-in.
Resolution:
Try disabling the Do not save encrypted pages to disk option:
If this does not work, you may also need to change the default security settings. Please see the following article for instructions on how to change these settings:
http://msdn.microsoft.com/en-us/library/aa368304(VS.85).aspx
Issue:
In Windows Server 2008 and Windows Vista with SP2 or earlier, when you try to install the Lync Web App plug-in the process fails and you receive a "UAC" error.
Resolution:
Make sure that UAC is turned on, and then try installing the plug-in again.
Issue:
When you use MS Pinyin (SimpleFast style) to input Chinese characters in Lync Web App, the program stops responding.
Resolution:
This is a Silverlight issue that has been fixed. Please upgrade to Silverlight version 4.0.50723.0 or a later version.
Issue:
In the following situation, Lync Web App is no longer visible:
Resolution: Lync Web App remains invisible until content is presented on the stage, or the meeting ends.
Issue:
The UC Silverlight Application project template does not appear in the Silverlight category in Visual Studio when .NET Framework 3.5 is selected in the Framework Version box of the New Project dialog box.
Resolution:
In the Framework Version box, select .NET Framework 4.0.
Issue:
Lync controls do not appear in the Visual Studio integrated development environment (IDE) toolbox. This may occur in the following situation:
Resolution:
Browse to the SDK control assembly (Microsoft.Rtc.Controls.dll) and then manually add the Lync controls to the toolbox.
Issue:
In projects created using the UC WPF Application template, Microsoft.Office.Uc.dll is not copied to the debug output directory. As a result, no Lync 2010 controls are correctly initialized. Also, the control's UcConnectInitializationError property contains an exception object with the following inner exception message:
"Could not load file or assembly 'Microsoft.Office.Uc, Version=4.0.7246.504, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified."
Resolution:
To work around this issue, follow these steps:
Issue:
To author a Silverlight application that is compatible with Lync Server 2010, you must install the Silverlight 4.0 Public Beta release.
Resolution:
To author a WPF application compatible with Lync Server 2010, you can use Visual Studio 2008 SP1 or Visual Studio 2010 Beta Release.
To download Visual Studio 2010 and Microsoft .NET Framework Beta 2, visit http://msdn.microsoft.com/en-us/vstudio/dd582936.aspx.
To download the Silverlight 4.0 Public Beta release, visit http://silverlight.net/getstarted/silverlight-4-beta.
Issue:
You cannot debug Silverlight applications, and you are running Microsoft Visual Studio 2010 Beta 2 without the Silverlight developer runtime.
Resolution:
Uninstall the Silverlight runtime and then install the Silverlight 4.0 developer runtime.
Silverlight 4 (Release Candidate) tools can be downloaded from the following Web site:
http://msdn.microsoft.com/en-us/library/cc838244(VS.96).aspx
Issue:
When a developer creates a Silverlight project without using the Unified Communications SL template and then attempts to drag a control from the Visual Studio Toolbox, a "Value cannot be null" error message may appear.
Resolution:
Explicitly add a reference to the Silverlight Controls DLL by following these steps:
Issue:
The Silverlight controls in the Lync SDK cannot establish the required connection to Lync when Internet Explorer Protected Mode is enabled.
Resolution:
Clear the Enable Protected Mode check box in the security zone that hosts the Web page on which the Lync Controls appear. Changes to protected mode security settings require a restart of Internet Explorer to take effect.
Issue:
During installation, some of the links provided for required and recommended tools do not point to the correct location or fully identify the specific version of tools which should be used.
Resolution:
The correct set of prerequisites is:
The Express edition of Visual Studio 2008 SP1 can be downloaded from:
http://www.microsoft.com/express/Web/
The .NET Framework 3.5 SP1 can be downloaded from:
http://msdn.microsoft.com/en-us/netframework/aa569263.aspx
Support for developing applications with Silverlight is not a prerequisite for installing the Lync Controls SDK. However, the following additional tools are required to develop applications for Silverlight:
Silverlight 4 (Release Candidate) Tools can be downloaded from:
http://msdn.microsoft.com/en-us/library/cc838244(VS.96).aspx
The SDK does not support development of applications using Lync Controls with Silverlight 3 or Visual Studio 2008.
Issue:
The Lync SDK documentation found in LyncClientSDK.CHM contains class library reference documentation for the Lync Controls that documents namespaces and classes that are not intended for use by developers.
Resolution:
Documentation found in the section labeled "Lync Controls Class Library" should be disregarded with the exception of the specific set of classes identified in this release note. For this release, these are the only classes that should be used by developers: For this release, the supported set of controls is limited to the following:
Issue:
A WPF project created without using the Unified Communications WPF Application template may experience a TypeInitializationException error. This error may occur when the Embed Interop Types property for a referenced assembly is set to True, or when the /l switch is used at a command prompt.
Resolution:
To work around this issue, follow these steps: 1. In the project reference, select Microsoft.Office.Uc.dll. 2. In the properties window, change the Embed Interop Type value to False. 3. Make sure the Copy Local property value is True.
http://msdn.microsoft.com/en-us/library/dd264728(VS.100).aspx
Issue:
The Lync 2010 Attendee client installer creates a firewall exception rule for the client. Administrators who distribute the client should be aware of this system-level change.
Resolution: There is no workaround for this issue.
Issue:
Uninstalling the Multilingual User Interface (MUI) package deletes some Microsoft Lync 2010 resource .dll files. Deleted resource files affect the Online Meeting Add-in for Lync 2010 and Recording features after the MUI package is uninstalled.
Resolution: After uninstalling the MUI package, run auto-repair to repair the affected features.
Issue: When you install Microsoft Lync 2010 with a different language after you uninstall a localized language of Lync, you see content in the previous language in Microsoft Lync 2010 Recording Player instead of the language you just installed.
Resolution: Manually remove the file %AppData%\Microsoft\Communicator\Recording Player\playback.xap, and then restart Microsoft Lync 2010 Recording Player.
Issue:
The languages available for Lync Web App are not installed during Lync Server 2010 setup.
Resolution:
To add additional supported languages for Lync Web App, you need to install webcomponents.msp.
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.
Issue:
When administrators set TTY mode in conference phones, calls have echoes because TTY mode disables the acoustic echo cancelling (AEC) in the device. Setting this mode may also cause other audio issues.
Resolution:
Administrators should not set TTY mode in conference phones.
Issue: When a Lync user tries to place a call to another Lync user through an Exchange auto attendant, the call fails unless Microsoft Exchange Server 2010 SP1 is the server for the Exchange auto attendant.
Resolution:
Administrators should upgrade to Exchange Server 2010 SP1 if they wish to enable this scenario.
Issue: A Lync Server 2010 Response Group agent making a call on behalf of a response group cannot add instant messaging to an anonymous conversation if the call was placed to a published Work phone number. The Work phone number is used by default when you double-click a contact to make a call using Lync 2010 Attendant.
Resolution: To be able to add the IM modality to an anonymous call, a Lync Server 2010 Response Group agent must start the call on behalf of the response group by making a Lync call.
Issue: Although the Text Telephone (TTY) mode setting is available on the Polycom CX3000 phone, enabling this mode causes echoes during calls. This is because the Acoustic Echo Cancellation (AEC) is disabled when TTY is used.
Resolution: The only workaround is to not use the TTY mode.
Issue: Presence status appears for Common Area Phone accounts. This could lead to confusion for remote parties.
Resolution: The presence status should be ignored. Viewing presence for Common Area Phone accounts cannot be disabled.
Issue: Headsets are not supported on Polycom CX500 and Aastra 6721i phones. Although the Lync Settings screen displays a headset volume control for these devices, changes made to this control have no effect.
Resolution:
There is no workaround for this issue.
Issue: For Polycom CX500 and Aastra 6721i phones, if the user selects the speaker as the active audio device, the user can only listen to remote-party audio. Audio generated by the local user will not be transmitted to the other parties in the conversation. No indication is provided to the user that only one-way audio is available.
Resolution: There currently is no workaround for this issue. On these phones, users can select the speaker phone option to listen to calls, but not to engage in conversations.
Issue: For Common Area Phone accounts, the call forwarding interface is not displayed even if AllowCallForwarding is set to true in the voice policy.
Resolution: There is no workaround for this issue. The call forwarding enabling and disabling interface will not be made available for Common Area Phone accounts, so the AllowCallForwarding policy setting will not have any effect.
Issue: The on-phone Help content is for Information Worker accounts. Common Area Phone accounts have limited functionality. As a result, much of the on-phone Help content is not applicable to Common Area Phone accounts.
Resolution: There is no workaround. The content will always be displayed. Users should only consult the Help content for features they see available on the phone.
Issue:
In Microsoft Lync 2010 Phone Edition, if the phone is ringing with an incoming call and another call is made or accepted, audio from only one party may be heard in the second call.
Resolution:
There is no current workaround for this issue. The user must terminate the call and then re-establish it.
Issue:
It is possible to select headset mode on a Lync 2010 Phone Edition device even if there is no headset connected to the phone. In this case, if a call comes in and the user answers it using the Answer soft key on the phone user interface, the call is answered and audio is routed to the headset port. However, since there is no headset attached, there is no audio.
Resolution:
After the call has been answered, switch the audio mode by pressing the hands-free hard key or picking up the handset. This routes the audio to the newly selected mode, and the user will be able to send and receive audio.
Issue:
There are two types of NAND memory errors/problems that can lead to image update failures:
Resolution:
For the first problem (0x70/200 code), perform a hard reset (turn the phone on while pressing the * and # keys). This clears the file system and allows the image update process to complete successfully on the next attempt.
For the second problem (0xd/200 code), install Cumulative Update 1 (CU1).
Issue:
If the user selects the hands-free or headset audio mode, or takes the handset off the hook, and then receives an incoming call, the call can only be answered using the device user interface by pressing the Answer soft key. In this scenario, switching audio modes while the device is ringing will not answer the call.
Resolution:
There is no workaround. This scenario is working as designed.
Issue:
When a Lync 2010 Phone Edition device is paired with a computer over USB, adjusting the volume on the device does not affect the volume setting on the computer.
Resolution:
There is no workaround. This scenario is working as designed; computer volume changes should be made on the computer.
Issue: The USB host port on Lync 2010 Phone Edition devices is not currently functional and is reserved for future use.
Resolution:
Not applicable.
Issue:
When a Lync 2010 Phone Edition device restarts, the network Pass-Through mode also resets, and there is a momentary interruption in the Ethernet connection between the device and the computer to which it is connected.
Resolution:
Not applicable.
Issue:
Lync 2010 Phone Edition supports up to eight calls at a time; one of these calls can be active, and the rest are on hold. When this maximum is reached, it is not be possible to make a new call, accept an incoming call, or join a conference.
Resolution:
There currently is no workaround for this issue.
Issue:
PIN-based authentication requires the user to enter the telephone number or extension and PIN on the phone. The phone then issues a "DHCP Options 120" query to determine the Lync Server 2010 pool FQDN to connect to. However, the pool FQDN must match the user's SIP domain for security purposes. Also, this mechanism will work only for one SIP domain in the current release.
Resolution:
There currently is no workaround for this issue.
Issue:
If there are more than (approximately) 1,000 contacts in any Contacts folder (other than the SenderPhotoContacts folder), processing those contacts takes a lot of time just after signing in. This blocks certain key operations on the desk phone and a watchdog time-out is triggered, which causes the phone to restart. This issue will occur every time the user automatically signs in to the desk phone after it restarts.
Resolution:
Reduce the number of contacts as much as possible, preferably below 500. This will prevent the watchdog time-out from triggering while the contacts are being processed. Note: A solution not requiring a reduction of contacts will be provided in a later release of the product.
Issue:
Desk phones provisioned using PIN-based authentication will not work from outside the network if the external DNS SRV records point to an Office Communications Server 2007 or Office Communications Server 2007 R2 Access Edge Server.
Resolution:
Modify the external DNS SRV records for your enterprise to point to a Lync Server 2010 Access Edge Server that has its next hop as a Lync Server 2010 Director or a Lync Server 2010 pool. The desk phone will still need to be provisioned internally within the enterprise before using it from outside. Alternatively, users can connect the desk phone to a computer using a USB cable. Make sure that Lync 2010 is running on the computer. Then users can sign in with their Windows credentials by using the pop-up box in Lync 2010.
Issue:
The Phone Edition for Polycom CX700 may get stuck in a continuous reboot cycle when you use Power over Ethernet (PoE).
Note: Lync Phone Edition for Polycom CX700 supports PoE and Link Layer Discovery Protocol-Media Endpoint Discovery (LLDP-MED). To make use of this technology, the customer site must have switches that support PoE 802.3AF (PoE Standard) and LLDP-MED 802.1AB.
Resolution:
Use the power adaptor that is shipped with the device, instead of PoE, to power the device.
Note to IT administrator: Please send the Lync team the name of the switch that doesn't work.
Issue:
The serial number that appears on the screen of the Phone Edition for Polycom CX600 when you select System Information is incorrect.
Resolution: The correct serial number appears on the label on the back of the phone.
Issue:
The Phone Edition for Polycom CX600 may crash and then reboot when transitioning from the system idle state to an active state when you use Power over Ethernet (PoE).
Note: Lync Phone Edition for Polycom CX600 supports PoE and Link Layer Discovery Protocol-Media Endpoint Discovery (LLDP-MED). To make use of this technology, the customer site must have switches that support PoE 802.3AF (PoE Standard) and LLDP-MED 802.1AB.
Resolution:
Use the power adaptor that is shipped with the device, instead of PoE, to power the device.
Note to IT administrator: Please send the Lync team the name of the switch that doesn't work.
Issue: An intermittent buzzing sound is heard on the transmit and receive paths when using the Netcom GN1200 adapter plus the GN2000 headset with the Aastra 6725ip phone when the phone is being powered by the wall power adapter.
Resolution:
To resolve the buzzing sound on the headset, install Cumulative Update 1 (CU1). When CU1 is installed, the buzzing sound heard by the other party during transmission is reduced, but may still be present in some cases. To resolve the transmission buzzing, switch to Power Over Ethernet (PoE) and remove the wall power adapter from the phone. You can also use the Plantronics HW251N and HW261N headsets to avoid this problem.
Issue:
Microsoft Lync 2010 Phone Edition can download updates without authentication, using the hard-coded DNS query of UCDevices-R2. However, you must use one of the public trusted certificates that are preinstalled on the device for image update and log upload to work.
This scenario only applies to device out-of-the-box, first-run behavior, without any prior user sign-in. Once a user has successfully signed in to the device, image update and log upload will function without the public trusted certificate.
Resolution:
In an environment where a private Enterprise root certificate is used, a device can download the root certificate with the following workaround:
A device requires an initial authentication to trigger the bootstrapper to download the root certificate. It does not matter whether the authentication passes or fails.
Once the root certification is in place, the image update and log upload for UCUpdates-R2 will work without user authentication.
Issue: To enable Text Telephone (TTY), the instructions on the Settings screen currently tell the user to plug the telephone typewriter device into the headset port. This is incorrect, and the device will not function correctly if this is done.
Resolution: Place the handset on the TTY device, as per instructions provided for the TTY device.
Issue:
If the phone number normalization rules change on the Lync Server and Exchange contact synchronization is enabled (via the EnableExchangeContactSync in-band setting or user option), Lync creates duplicate Outlook contacts for phone-only contacts that currently appear in your Lync Contacts list.
Resolution:
Remove each phone-only contact from your Lync Contacts list, and then re-add it.
Issue:
If the Session Initiation Protocol (SIP) of the person who organized an online meetings changes, joining or changing the meeting will no longer be possible.
Resolution: This is not supported. There is no workaround.
Issue:
The Activity Feeds feature works for federated contacts except for Note History. Normally you see the last N notes someone entered in the Activity Feed, but if they are a federated contact you only see their most recent note (in addition to any OOF note, title change, photo change, and office location change).
Resolution: There currently is no workaround for this issue.
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.
© 2010 Microsoft Corporation. All rights reserved.
Microsoft, Active Directory, Internet Explorer, MSN, Outlook, SQL Server , Windows, Windows Live, and Windows Vista are trademarks of the Microsoft group of companies.
All other trademarks are property of their respective owners.