Abstract: Microsoft Support has released a cumulative update for Lync 2013 Desktop Client for Windows, which includes new functionality.

Microsoft has released a cumulative update for Lync 2013, which includes new features and fixes of bugs. You can see all the November cumulative update details on the Microsoft Support site:

 

Client feature enhancements include Photos of Sender/Receiver, URL Photo Experience, pChat Escalation, Login Trace Files and New Recording Options. Read the Lync Team Blog for full details about the Lync 2013 desktop client updates:

Note that while some features work out of the box, others require changing settings on Lync Server.  If a feature is dependent on server configuration we have added detailed steps below so that it can be enabled.

The feature works out of the box and does not have any server dependency.

 

By default, client policies do not contain an entry where you can enable or disable the feature. If you do not add the policy, end users cannot see the field where they can add their own photo and their interface will look the same as in the previous versions of the Lync 2013 Client.

In order to get feature work you need to create custom policy entry, by using the following script:

$a=New-CsClientPolicyEntry -Name EnablePresencePhotoOptions -Value True

Set-csclientpolicy -Identity EnablePhotoUrl -Policyentry $a

 

The script assumes that you created policy called EnablePhotoUrl, also you can modify Global policy.

After assigning the policy to the clients and signing into the client, your users will see the new option, which allows adding own URL photo.

 

There is no server dependency for the feature; it just works after applying updates on the clients.

After applying updates, participants will see the new button at the bottom of Lync Chat Room Interface.

 

There is no server dependency for the feature; it just works after applying updates on the clients.

After applying updates you can find new item “Sign-in logs” when click Lync Icon in the taskbar.

 

There is no server dependency for the feature; it just works after applying updates on the clients.