In case you missed it and have good Lync ideas that you would like to share, please visit the site: http://lync.ideascale.com Here you can enter your own ideas as well as "vote" for ideas you like. So far I have posted 5 ideas and have a few more in mind.
Lync Edge and User Replicator
It seems as the Lync Edge server is running the User Replicator without actually needing it. In some cases it even causes the Lync Server 2013 Access Edge service to fail to start or hang. You can read more about it in the KB article:
Now since the Edge server sits in the DMZ, and for performance reasons, you want to run as few services as possible on this server. So, the recommendation would be to always switch off the User Replicator on the Edge server.
Working with the Edge server, many are the occasions when you need to check, and double-check, ports.
This can be done with PortQry and PortQryUI, which is a user Interface for PortQry. This tool gets even cooler if you download a PortQueryUI Config.xml File for Lync from Flinchböt. The config file is for Lync 2010, but can easily be modified to work with Lync 2013.
...and a question that came up about the difference between OCSlogger and OCStracer?
OCStracer is the cmd line version of OCSdebugger. For example you could use...
OCSTracer.exe List /Filter:All
OCSTracer.exe start /Component:SIPStack
OCSTracer.exe stop /Component:SIPStack
...rather than using the GUI.
Lync client logging
Some logging settings were added to the client policy in Lync 2013.
Got a good question on Lync Contacts from a friend (thanks Robert!) Here is how Lync Contacts works for a user that is disabled or removed from Lync. If the user is "Temporarily disable for Lync Server" in CSCP (Set-CsUser -Enabled $False) and then enabled again - the user WILL retain the list of Contacts in the Lync 2013 client.
However, if the user is "Remove from Lync Server" in CSCP (Disable-CsUser) and then added to Lync again - the user WILL NOT retain the list of Contacts in the Lync 2013 client.
Being an active PADI Rescue diver with some 250 logged dives, I like to dive... deep...
and this week I am diving into Lync :-)
Diving in the kelp forests at Catalina or into Lync - same thing!
I recently passed the 74-338 Lync 2013 Depth Support Engineer exam, and this week I am attending a training class on the subject. Good course, and I think I will learn a lot this week. I will try to summarize some questions and good points day-by-day.
Why should we not mix physical and virtual servers in a Lync Enterprise Edition pool?
(and why should we not mix physical and virtual server pools in pool paring?)
Mixing physical and virtual servers in the same pool is not a supported configuration.
The reason has not so much to do with the actual virtualization technique, but rather the fact that all servers in a pool should have about similar performance. So it would be just as bad to keep an old slow server in a pool with new high performing servers, users would get inconsistent response times and would maybe complain about this. Even virtual servers should have equal performance capabilities. Also, things like latency and virtual servers competing for resources on a physical host play into this. (The same reasons even apply to pool pairing.)
However, reading this great old article on DNS Load Balancing in Lync Server 2010, we learn that the order in which these are returned to the client is irrelevant. The client chooses an IP address from the list of returned IP addresses at random.
So, the conclusion must be that for DNS Load Balancing in Lync, using round robin or not on the DNS server does not matter at all.