Lync September 2013 Update New Feature & Fixes

Microsoft has finally brought spell check to their 2013 Lync client through the 2013 September client update.  The update was initially released as part of the normal Microsoft second Tuesday of the month patch cycle on September 10th, but was quickly removed after some customers reported that it inadvertently disabled some Windows features.  The update was re-released on September 20th and brings the following features and fixes:
1.   Spell check is now available, which was a highly requested feature:
It is important to note that by default spell check will only work if you have Office 2013 installed.  Here is a workaround if you have Office 2007 or 2010 with the Lync 2013 desktop client:
If spell checking is not working and you have Office 2013 installed, check the settings in Lync:
2.  The presence icon returns to the system tray.  This was changed in the July 2013 update as documented by Microsoft:
Post July 2013 update
Post September 2013 update
3.   Additional fixes:

  •  2880161 ( / )

You can’t drag a contact from Lync 2013 to another application

  • 2880163 ( )

Proxy authentication dialog box appears when you sign in to Lync 2013

  • 2880164 ( )

Instant message sent from Lync Web App displays wrong symbols in Lync 2013

  • 2880167 ( )

Can’t sign in to Lync 2013 when a user logs on to a computer by using an account from a different AD forest

  • 2882812 ( )

A proxy authentication dialog box appears when you upload a PowerPoint presentation in Lync 2013

  • 2882813 ( )

Can’t sign in to Lync 2013 on a computer that is running Windows 7

  • 2882814 ( )

Extended character is displayed incorrectly in a disclaimer in Lync 2013

  • 2854650 ( )

4.   Broken feature:  Presence from OutlookExchange will NOT update your Lync presence to “In a meeting”.  Microsoft’s recommended workaround is to set your presence to “Busy” until this feature is fixed in a future update.
To determine if you already have the September 2013 update or to download it, check out the official Microsoft KB article here: