Tuesday, December 16, 2014

Increase the size of Lync Server Log

A large customer of mine asked how the size of Lync Server Log in EventViewer can be increased. The request made sense for them since so many events are registered on single server per hour that tracking past events older than one day is practically impossible.

The first and (easiest) method that comes to mind is GPO. However, in Group Policy we find only the native Application, Security and System logs properties.

We have three options to achieve this task:

1. Do it manually on each server

***The default value is 16MB. In this example, the log size was increased to 80GB (81920KB)

2. Use wevtutil.exe (http://technet.microsoft.com/en-us/library/cc732848.aspx).

wevtutil sl "Lync Server" /ms:83886080

***Note that here we express the desired log size in Bytes (80MB = 83886080 bytes)

3. The last (and preferable) option is… GPO. But wait, GPO does not have this option?!?
We can use New Registry Item with Update option to push the new value to all Lync servers in our environment.

The “Key Path” is SYSTEM\ControlSet001\Services\EventLog\Lync Server and the Value data is our new log size in Bytes.

This is it. Apply the new GPO accordingly and either force gpupdate or leave the servers to do so natively.

One last note: Log file sizes must be a multiple of 64 KB. If you enter a value that is not a multiple of 64 KB, Event Viewer will round he log file size up to a multiple of 64 KB.

Monday, July 7, 2014

Q3 2014 Atlanta Lync Users Group Meeting anounced

The Atlnata Lync Users Group will be conducting their next meeting Thursday, July 31, 2014. This meeting will include two sessions, the first session will cover Lync Gateways and Session Border Controllers (SBCs).  The second session will dive into Deployment and Best Practices for Quality of Service (QoS) and Quality of Experience (QoE).

Industry Experts will be on site to deliver these presentations and help answer any questions related to Lync Server.

Food, beverages and additional door prizes courtesy of the Lync Users Group and our sponsors.

Please arrive early. There is Visitor Registration process in place.Informational sheet can be downloaded from this link : Coca-Cola Technology Plaza_Visitor Information

Friday, April 4, 2014

You cannot remove Lync 2013 pool from Topology - Users or contacts are still homed on a pool that would be deleted

Recently I’ve migrated my Lync lab to Windows Server 2012 R2 where I’ve build new site and pools and proceeded with decommissioning the old pool.

After moving all users and objects as recommended, I proceeded with removing the pool and publishing Topology.

Bummer! The log showed there are users or objects “still homed on this pool”

I did check checking everything suggested by the log (Get-CsUser, Get-CsExUmContact, Get-CsCommonAreaPhone, Get-CsAnalogDevice, Get-CsRgsWorkflow, Get-CsDialInConferencingAccessNumber, Get-CsAudioTestServiceApplication, Get-CsTrustedApplicationEndpoint, Get-CsPersistentChatEndpoint) and got the correct output – no objects.

After looking in the RTCLOCAL database of a front end server, I did indeed found ONE object

Found the object in AD...

...and turned out to be... LRS.

Ouch - I forgot that about a month ago I did provision Lync Meeting Room (LRS) to test LRS Portal installation.

Ran Move-CsMeetingRoom and… Topo publishing completed.

In conclusion, I am sure Microsoft will update the code to suggest Get- CsMeetingRoom in the Topo log, but meanwhile, if you have LRS in your environment already, make sure you move it prior to decommissioning Lync 2013 pool if it was homed there.