Install the MSI package, and confirm the installation in Control Panel.

Choose the appropriate version, 64- or 32-bit.

Now, you see the Lync SDK folder, which has a security catalog file and two Windows installer files.

To bypass it, we came up with a small tweak which follows. Yes, the Lync 2013 SDK will look for Lync 2013 client and Visual Studio 2010 components, which you don’t want to install. The system requirements to install the Lync SDK are a real challenge. Its available in the Microsoft Download Center. Note: Install Lync 2013 SDK only if required. However, the Lync 2013 SDK (client) is fully supported for Lync 2013, Skype for Business, and Skype for Business online.Īll the previous articles are focused for software developers, but what can system administrators can do with the Lync 2013 SDK to work with Skype for Business client? Well, the answer is: A lot more by using PowerShell. Why should you use the Lync SDK for the Skype for Business client? Because there is no Skype for Business application API released for Windows. This blog post shares insights about how to extend PowerShell with the Lync SDK to explore Skype for Business 2016 client. Some organizations might have built customized Skype for Business client applications or integrated Skype for Business with custom applications for their business needs.

By using Skype for Business, you can send IM or call a known person, which saves time at work.

The Skype for Business 2016 client helps you stay connected with known people by using instant messaging, audio, video call, email, persistent chat rooms, online meetings, and presentations. MVP Chendrayan Venkatesan is back again to show us how to get started with the Lync 2013 SDK and do some really cool stuff with PowerShell and Skype for Business! How do I integrate Windows PowerShell with the Lync SDK to manage Skype For Business client? Summary: Get started with the Lync 2013 SDK by using PowerShell to manage Skype for Business 2016 client.

Microsoft lync 2013 sdk download