Several customers are reporting an issue after installing the July 2013 Security Update for Lync 2013 related to icons not be rendered correctly or missing entirely. This issue has been found to be related to other updates missing on the workstation, as those other updates are NOT part of the July 2013 Security Update…but are required for other changes in the Lync 2013 Client to work properly.
In addition to the July 2013 security update for Lync 2013 (KB2817465), you MUST also install the latest Office 2013 updates for MSO.DLL and MSORES.DLL (KB2817491). These are available from Windows Update or downloaded via the KBs.
We are working to have the KB for the July 2013 Security Update for Lync 2013 (KB2817465) updated to include this information.
Update December 4, 2013: In the November 2013 update for the Lync 2013 Client, they changed the icon for the Upcoming Meetings list to a mini calendar:
--------------------------------------------------------------------------------------------------------------------------------------------------
As I mentioned in my other post about the change to the Lync 2013 System Tray Icon, that change was part of a larger number of changes planned for Lync 2013 Cumulative Update 2 (CU2) but went into effect as part of the July 2013 Security Update for Lync 2013.
However, unlike that change which caused a lot of negative responses from customers (and is now planned to be changed), there are a couple of other features related to CU2 that also are exposed in the client once the July 2013 Security Update is installed that are neat new features. I wanted to make you aware of them...
This new feature adds a new Icon in the main Lync window that when clicked upon, displays a new tab that shows you upcoming meetings (meetings in the next 24 hours):
With this new tab/feature, users do not have to rely upon Outlook (or other clients) to see their upcoming meetings or to join them. Now, a user can simply use the Lync client to see and join the meetings. Lync pulls this information out of Exchange via Exchange Web Services (EWS). It checks for new meetings every 10 minutes.
This feature adds a new options section called "Lync Meetings" to the Lync Options area. In this new section you can configure:
Updated: September 16, 2013 : As mentioned in the comments, the September 2013 update for Lync 2013 reverts the System Tray functionality back to the pre-July 2013 update. HOWEVER, as also mentioned...a bug causing issues with Outlook was found and the release has been pulled. They are working on fixing the update and will re-release it shortly.
UPDATED July 10, 2013 : Based on negative feedback from customers, the Lync Product Group is planning on reverting this change. No ETA / Target CU has been given.
As part of Cumulative Update 2 for the Lync 2013 client, the Lync Product Group has made a change that users will need to be aware of.
Since Live Communications Server (LCS) and the Communicator client, the Lync System Tray Icon has always changed colors to indicate your status as it's seen by others (e.g. Green means available, Red means busy, Yellow means away, etc).
Starting with the July 2013 Security Update for Lync 2013 and Cumulative Update 2 for the Lync 2013 Client (not yet released as of this post's writing on July 9, 2013)...the Lync 2013 System Tray icon has been changed to simply be the blue Lync 2013 logo:
It no longer will change colors to show your status. To see your status, you will need to hover your mouse over the icon:
This change was made to align Lync 2013 with the overall Office 2013 design standard for the System Tray icons. I wanted to make people aware of this change as it is something users will see after the July 2013 Security Update is deployed and is a major change in the way the Lync System Try icon works.
One of the great things the Exchange Product Group did, starting with Exchange 2007, was to start generating informative log files as part of the installation/upgrade process. Gone are the days when you had no log files and you got 75% of the way through and the setup program bombed with some generic error and that's all you got (maybe an event in the Event Viewer as well, but still not a whole lot to go on). These logs are written to C:\ExchangeSetupLogs by default.
However, I recently worked on an issue with one of my customers on an Exchange 2010 SP3 upgrade. They had all the setup logs, but hadn’t followed any of the best practices I’m about to talk about. This resulted in having to deal with VERY large log files in the C:\ExchangeSetupLogs directory that had everything in them since the server was first built. So, I wanted to post some information out on best practices related to these files…
One of our best practices *is* to keep all your setup logs…which most customers do. However, there are a few related best practices I wanted to share that go along with this:
The biggest advantage to following these best practices is simply that if you run into issues with an upgrade (or after), you’re not dealing with the huge log files (especially if opening them with Notepad) or a directory with hundreds and hundreds of files in it. This can make troubleshooting a little easier. Hopefully, you’ll never need these files, but that never seems to be the way it works out.
As I mentioned in the Current Cumulative Updates for Office - Q3 2012 post, each quarter I will post information on the latest updates for the Office for Windows and Office for Macintosh products.
The information below is being provided regarding the most currently available updates available for the supported Windows and Macintosh versions of Office as of July 1, 2013.
As a reminder on why I'm providing this information and how it should be used, please see my Keeping Up with Office Updates post which discusses the cumulative updates for Office (and Outlook in particular) that companies need to be aware of and push out to their users.
Note: Each of the KB articles includes the list/links for all the Office products (Word, Excel, Outlook, etc). Most of you focus on Outlook and that’s the only ones required and is also provided separately but I wanted to provide the larger “Office” list in case you want it.
As a reminder, Microsoft Update does *NOT* make the cumulative updates available to users. These have to be downloaded and either installed independently or deployed using tools such as WSUS, SCCM, etc.
Note: Each of the KB articles includes the link for downloading the package which updates ALL Office Products…there are not separate updates for each of the various components of Office as there is with the Windows releases.