Lync 2013, SQL, and low RAM situations

Great article from Chris and Robin’s Technology blog on SQL and low RAM situations..

http://blog.chrislehr.com/2014/04/lync-2013-sql-and-low-ram-situations.html

Lync Codecs

I had some time today to catch up on things so was checking the usual blog list that I read and came across this excellent article by Johan Delimon.

Flashback from Lync Conference : What audio codes does Lync actually use (Now a Dead Link)

It looks like this comes from the MEET400 (Meetings and Media) session from the Lync conference..  I will be checking out the video release once they are released to the public..

Lync Control Panel Font

So with the release of the Lync 2013 October 2013 CU (CU3) the font of the control panel changed to be horrible, Times New Roman, as shown below.

There have been a few posts on Twitter lately with people solving the issue.

New blog post: Resetting the Font in #Lync Server Control Panel - Goodbye Times New Roman! http://t.co/uGjskZSJFr
— Pat Richard (@patrichard) January 20, 2014

Here is the link to Lync MVP Pat Richard's site (ehloworld.com) for the fix..

http://www.ehloworld.com/2448

SIP_E_AUTH_NTLMMISMATCH

Have come across this error again today whilst deploying an 2013 Edge server and users wont able to log in.

In the SIP traces from the Edge server after the usual 3 attempts or registration, the client wont login and one of the last message in snooper is:

ms-diagnostics: 1000;reason="Final handshake failed";HRESULT="0xC3E93EE4 (SIP_E_AUTH_NTLMMISMATCH)";source="FE Server"

The fix is to change the local security policy for the Lync servers to allow for no minimum for NTLM SSP session security.

From the local security policies on the Lync servers remove the tick from the "Require 128-bit encryption"

 

SEFAUtil GUI

This will be a nice addition to the Lync Toolkit.

SEAFUtil GUI written by Johan Veldhuis..

http://johanveldhuis.nl/en/sefautil-gui/

Default Installation and SQL Paths in Lync Server 2013

Came across this great post today from Tim Harrington whilst looking to SQL install paths for Lync.

http://howdouc.blogspot.com.au/2012/11/exploring-default-installation-and-sql.html

Though I would re-port so I remember where it is for next time I need the information.

Office Web Apps Server - Patching

The process of patching a Office Web Apps Server is simply enough, the latest patch KB2760445, can be found at http://www.microsoft.com/en-us/download/details.aspx?id=36981.

The thing to remember is that the as part of the upgrade process you will need to break and re-create the server farm.

This article, http://technet.microsoft.com/en-us/library/jj966220.aspx, has the steps involved for both a single server farm and for multiple server farm.

But basically its:

1. Down load the patch
2. Remove the Server from the farm Remove-OfficeWebAppsMachine
3. Install the patch
4. Re-create the server farm New-OfficeWebAppsFarm -InternalURL "http://...." .....

Lync and QoS

Nice article of enabled QoS by Exchange MVP Elan Shudnow.

Part 1.
http://www.shudnow.net/2013/02/16/enabling-qos-for-lync-server-2013-and-various-clients-part-1/

Logging/Tracing in Lync Server 2013

In Lync Server 2013 the way to enable tracing has changed there is no longer GUI to enable the tracing, its done via command line.

The command is “ClsController.exe” and is located in “C:\Program Files\Common Files\Microsoft Lync Server 2013\ClsAgent\” on the Lync 2013 Server, in Lync 2010 you ran the “Lync logging Tool” and selected components that you wished to trace, started the trace and re-created the problem, stopped the trace and then “Analysed” the trace with the snooper tool.

Lync 2013 doesn’t allow you to select the components that you wish to trace, you now select a scenario that you wish to trace/

The flow is now:

• ClsController.exe -start –scenario –pools
• Reproduce the Issue
• ClsController.exe -stop –scenario –pools
• ClsController.exe -flush –pools
• ClsController.exe -search –pools –components –loglevel

 Today I came across this post by Richard Brynteson at MasteringLync.com

http://masteringlync.com/2012/08/02/centralized-logging-in-lync-2013/

The output file is created on the desktop of the user logged in running the bat file, then you can use snooper from the Lync Debug Tools to open the file

All Lync Server 2013 have the ClsAgent running on them, so you only need to run the ClsController.exe once and it will collect from all servers in the pool identified.

Lync 2013 Client Address Book Update

The Lync client by default will download the address book from the Lync FE server after a random amout of time once the address book is more that 24 hours old.

There is a Registry Key that can be updated to set the initial delay to 0 mins, in other words as soon as your local file is either: 

1. Not on the PC (has been deleted)
2. Or is more that 24 hours old

The following reg add is the key, its slightly different to from the 2010 client as Lync 2013 policies now reside under the office 15.0 side of things.

reg add HKLM\Software\Policies\Microsoft\Office\15.0\Lync /v GalDownloadInitialDelay /t REG_DWORD /d 0 /f

The address book files on the client are now also stored at a different location.

%userprofile%\AppData\Local\Microsoft\Office\15.0\Lync\sip_<lync_signin_address>

Lync Server 2013

There has been some information released overnight with a preview release of Lync 2013.  Hoping to have some time over the next few days to get it installed in my lab and see how it looks.


Some links if you are after more information.

• Lync Server 2013: http://technet.microsoft.com/en-US/evalcenter/hh973393
• Lync 2013 Client: http://technet.microsoft.com/en-US/evalcenter/hh973391 (need to install the Office 2013 cloud software to get the client)
• Technet Articles: http://technet.microsoft.com/en-us/library/gg412892%28v=ocs.15%29