Windows PowerShell Module for Lync Online allows management of a Lync Online deployment and Lync Online user accounts through the use of Windows PowerShell.
If the original release of Windows PowerShell Module for Lync Online (version 5.0.8643.0) was previously installed, you will need to install this latest release (version 5.0.8892.0) of the module. To receive future updates of the module, you must download and install the version 5.0.8892.0, found on this page. Installation will uninstall the old module and install the new one.
To validate the capacity planning requirements of a Lync Server 2013 deployment, we recommend that you perform a stress testing exercise using The Lync Server 2013 Stress and Performance Tool (LSS). This document will take you through the steps required to plan and conduct a Lync Server stress testing exercise.
Microsoft released the October Update yesterday, this updates enables the “operator assistance” feature during a PSTN dial-in conference in a Lync Server 2013 environment. http://support.microsoft.com/kb/2882802
The update enables administrators to provide support for the *0 Dual Tone Multi Frequency (DTMF) command in a public switched telephone network (PSTN) dial-in conference in a Microsoft Lync Server 2013 environment. After the update is installed, a PSTN caller is able to be transferred to an operator number that the administrator defines.
Microsoft has a KB article written about removing the last active attribute for the away state, this can be useful for company’s where the employees have the feeling they are being “watched” or many other reasons .
These attributes can be removed on the server side. so changes on the client side are not necessary.
The KB article of MSFT is telling us it can be done on Lync 2010, but a customer is going to Lync 2013 so I’ve tested it on Lync 2013 as well and it working just fine.
How this can be done.
You have to create a text file on all the front-end server in the following directory.
Lync 2010 %Installation Folder%\Microsoft Lync Server 2010\Server\Core\
Lync 2013 %Installation Folder%\Microsoft Lync Server 2013\Server\Core\
The name of the text file has to be : Rtcaggregate.exe.config . include the following configuration entry :
What’s New in the Planning Tool for Lync Server 2013?
The Planning Tool now allow user to have up to 10 sites, including central site and disaster recovery site
Lync Server Planning Tool 2013 offers the capacity guidance for Lync Server 2013 new and updated features, including below areas. User can answer the question regarding these features through Planning Tool, and then the suggested topology will contain the information, e.g hardware, network, DNS, certificate, IP, etc, according to the Lync Server 2013 user model.
Archiving with Exchange integration
High Availability and Disaster Recovery
Office Web Apps
Lync Server Planning Tool 2013 allow user to have IPv6 IP address
Planning Tool identifies the IP conflicts across sites in the suggest topology. User can choose to show or hide IP conflict in the topology.
Planning Tool offers a more user friend FQDN/IP/Port editing dialog
Planning Tool updates the suggested hardware requirement, DNS and certificates with Lync Server 2013 changes
Planning Tool updates the planning steps and deployment steps with Lync Server 2013 changes
Lync Server Planning Tool 2013 support the better accessibility requirement
Lync Server Planning Tool 2013 offers the better exported Visio and Excel files. Visio file matches the suggested topology diagram in Planning Tool well.
Lync Server Planning Tool 2013 does not support the below features any more
Had to do some testing/troubleshooting on our experience environment which is running Lync Server 2013 I stumbled upon some issues.
I was testing the Lync Edge server 2013 with a client on my corporate laptop. My corporate laptop has Window 8 installed and is connected to a Lync Server 2010 environment. Also I have installed the Lync 2013 Debugging tools.
When opening the logging file under “C:\Users\Joost\AppData\Local\Microsoft\Office\15.0\Lync\Tracing” with Snooper 2013 it crashed, tried this on several machines.After some troubleshooting and trying around I found the problem.
Snooper 2013 can’t open logfiles from an Lync server 2010 environment, when throwing away the logfile and then login to lync again (to the Lync server 2013) it was all working.So keep in mind you have to first delete the log files because standard the log files are set to full in a Lync client 2013. Than open the appropriate Snooper version to go troubleshoot the issues.
Installed both the resource kit Lync 2010 and the debugging tools on my Windows 8 laptop but when you want to pin Snooper to Start they are both the same name. is solved this by renaming the files to Snooper 2010 and Snooper 2013 and the pinned it to Start.