• No results found

How to deploy Lync 2013 client using SCCM

N/A
N/A
Protected

Academic year: 2021

Share "How to deploy Lync 2013 client using SCCM"

Copied!
15
0
0

Loading.... (view fulltext now)

Full text

(1)

In this doc we will see how to deploy Lync 2013 client using SCCM. There are two versions of the Lync 2013 client available, Lync Basic 2013 and Lync 2013. Lync Basic 2013 provides all the basic functionality that’s available in the full version of Lync 2013 except some of these. The Lync Basic client includes enhanced presence, contacts, instant messaging (IM), Lync meetings, and basic voice functionality. Features not supported in Lync Basic include multiparty video, OneNote integration, virtual desktop infrastructure (VDI) support, skill search, recording, Enterprise Voice features, and advanced call handling.

To compare the features and capabilities of Lync 2013 clients you can read Client comparison tables for Lync Server 2013

Where can I download the Lync 2013 clients?

Lync Basic 2013 is available on the Microsoft Download Center and comes in two versions: Microsoft Lync Basic 2013 (64 Bit)

Microsoft Lync Basic 2013 (32 Bit)

Lync 2013 is available via the Microsoft Volume Licensing Service Center for customers with a Volume Licensing agreement.

You can download the Lync 2013 client from VLSC or you could use OCT to customize the Lync 2013 which comes with Office 2013. To customize client installation in Lync 2013, you can click on this link. So my Lync configuration file consists of few lines of code. I have saved this file with name config-pd.xml inside the folder lync.ww. You can download the configuration file here. As an example, in this post we will see Lync 2013 32 bit client deployment. You could follow the same procedure to deploy Lync 2013 64 bit client deployment.

How to deploy Lync 2013 client using SCCM

Copy the Lync setup folder to the sources folder or any shared folder on the ConfigMgr server. Launch the Configuration Manager console, click Software Library, under Application Management right click Applications and click Create Application.

(2)
(3)
(4)
(5)
(6)
(7)

For the Content Location, provide the path where the Lync 2013 files are present. The next step is to specify install and uninstall command. Specify the Installation Program and Uninstall Program as shown in the below screenshot.

(8)

On the Detection Rule window, choose Setting Type as File System. Under Specify the file or folder to detect the app, set the following

Type – File

Path –%ProgramFiles%>Microsoft Office >Office15

File or Folder name – lync.exe

(9)

Click on Add Clause. On the Detection Rule window, choose Setting Type as Registry. Under Specify the registry key or value, set the following

Hive – HKEY_LOCAL_MACHINE

key– SOFTWARE>Microsoft>Office>15.0>Registration>{0EA305CE-B708-4D79-8087-D636AB0F1A4D}>ProductName

Value – Microsoft Lync 2013

(10)

In the above steps we have added 2 rules to detect the presence of the app. One of these rules to detect the app is also fine. So under Connector field change And operator to Or. Click Next.

(11)

Selection the Installation behavior as Install for system if resource is device; otherwise install for user, Logon requirement as Whether or not a user is logged

(12)
(13)

Right click the Lync application and click on Distribute Content. Add the Distribution Point and complete the wizard. After you distribute the application to DP, right click on the Lync application and click on Deploy. Choose the Collection where this application is to be deployed and click Next. Under Deployment settings, set the Action as Install and Purpose as Available. Click on Next and complete the wizard.

After few minutes the Lync 2013 app can be seen in the Software Center under Available Software. Select the app and click on Install Selected. The app is downloaded from the DP and installed.

(14)

The Lync 2013 client is installed successfully.

The Lync 2013 client has been installed on the computer. If you want to what’s going in the background during the client installation, you can open the AppEnforce.log file on the client computer using CM Trace tool. If the app fails to install you can check this file for troubleshooting purpose.

(15)

References

Related documents

This module describes how to plan, design and deploy Lync Server 2013 Persistent Chat to the enterprise. It describes the fundamental process required to create and manage a Lync

SQL SERVER OR LYNC SERVER 2013 ROLE ROLE-TYPICAL SQL SERVER PERMISSIONS AND GROUP MEMBERSHIP ROLE-TYPICAL LYNC SERVER 2013 PERMISSIONS AND GROUP MEMBERSHIP PERMISSIONS

Configuring Exchange Server 2013 UM to work with Lync Server 2013 Enterprise Voice Configuring Lync Server 2013 Interoperability with Exchange Server 2013 Unified Messaging...

In Lync Server 2010, virtual gateways must be defined to allow connectivity from multiple MS pools to the same Session Border Controller (SBC) Fully Qualified Domain Name (FQDN)

Open Lync Server 2013 Topology Builder and define a PSTN gateway in the Mediation Server to be used between Lync 2013 and Aastra 400. To define the PSTN gateway, expand

This module describes how to plan, design and deploy Lync Server 2013 Persistent Chat to the enterprise. It describes the fundamental process required to create and manage a Lync

This module describes how to plan, design and deploy Lync Server 2013 Persistent Chat to the enterprise. It describes the fundamental process required to create and manage a Lync

This module describes how to plan, design and deploy Lync Server 2013 Persistent Chat to the enterprise. It describes the fundamental process required to create and manage a Lync