Use the 2016 version of the Office Deployment Toolkit here to download the new 2016 version of Office 365 ProPlus locally. You then can customize the updates, the settings, and point users to a local share/site, roll this custom build into machine images, or deploy via SCCM.
When you’re migrating on-premises mailboxes to Office365, there are a lot of factors that can impact overall mailbox migration speed and performance. This post will help you investigate and correct the possible causes by using the AnalyzeMoveRequestStats.ps1 script to analyze the performance of a batch of move requests to identify reasons for slower performance.
The AnalyzeMoveRequestStatsscript provides important performance statistics from a given set of move request statistics. It also generates two files – one for the failure list, and one for individual move statistics.
Visit the Office 365 Service Descriptions in the TechNet library for detailed descriptions of the services and features that are available with Office 365. The feature tables in the Office 365 Service Descriptions also include footnotes that provide additional information about specific plans.
ECPA is a PII free and an extensible tool to collect network diagnostics from end user machine to O365 data centers. The tool is to be run from customer location to better understand the cause of latencies (if any) and to collect and upload all the diagnostic data to Microsoft (Client GUID is provided for reference). ECPA does not collect any Personally Identifiable Information (PII) data but it does need to know the physical datacenter location of the user’s mailbox, which is running the test. Once the right location is identified, the tool runs a series of performance related tests. Any valid O365 credentials can be used to login.
Microsoft released a custom intranet site for Lync 2013 it can be found here
The Lync 2013 Custom Intranet Site contains sample webpages to help you create a dedicated Lync intranet site for your organization. The sample site uses HTML source code for all pages. This download includes short how-to videos, help topics, Microsoft PowerPoint training presentations, links to instructor-led training, and other resources currently available online.
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 :