The Lync Team announced today on their blog that the Office SP1 update released is the February Lync Desktop Client update (CU5). I haven’t seen anything pertaining to a standalone download or install. Will update this article if I find out anything else about this.
Features included in the February Update:
- Toggle pictures of sender/receiver
- Support of high-resolution monitors (200% scaling mode)
- Transfer files and pictures in a Persistent Chat room
The version number of the client has changed to 15.0.4569.1503 and MSO 15.0.4569.1506.
Another thing that I noticed has changed are the emoticons.
Pre SP1 Post SP1
Here is the KB about the Description of Microsoft Office 2013 SP1
- 2919506 Can't hear the first few words that a callee speaks when they answer a call in Lync 2013
- 2919507 The "Program Events" sound setting is reset to the default value after you restart Lync 2013
- 2919508 Can't rotate the screen orientation of a video window in a Lync 2013 video conference on a Windows 8.1-based device
- 2919510 A pie chart clock icon appears in the "Conversations" tab as a meeting icon in Lync 2013
There are a few issues that pertain to Lync within the release of SP1.
Persistent Chat file transfer fails between an external user and an internal user in Lync 2013
Assume that a user (user A) installs Microsoft Office 2013 Service Pack 1 (SP1) on a Lync 2013 client. Then, user A tries to send a file to another user (user B) in a Persistent Chat room by using the client. In this situation, user A may encounter the following issues:
- If user A is an external user and user B is an internal user, user A cannot send the file. Additionally, user A will receive error ID 70.
- If user A is an internal user and user B is an external user, user A cannot send the file. Additionally, user A will receive the following error message: error in transfer
To work around this issue, you must publish an A record to point to the public IP address of the router on the external Domain Name System (DNS) side. The router port must be forwarded to the external IP of Threat Management Gateway.
Note This workaround does not apply to all environments. For example, the internal DNS name may not be publishable in external DNS in some environments.
Memory leak occurs during a video call or when you rest the mouse pointer on a video icon in Lync 2013
Assume that you install Microsoft Office 2013 Service Pack 1 (SP1) or the November, 2013 update for Lync 2013 on a computer. The computer uses accelerated H.264 video encoding based on Intel chipsets that have HD Graphics 2000 or a later version. Then, you make a video call or you rest the mouse pointer on a video icon in Lync 2013. In this situation, at least 60 megabytes (MB) of memory will leak in Lync 2013. The memory leak will persist until you restart Lync 2013.
This issue may be resolved in the Lync 2013 update that is dated April 2014.