Deploying Lync 2013 Conversation Translator via SCCM 2012

2017-12-04T11:07:56+00:00 April 17th, 2014|Skype|

We wanted to get Lync Translator out to our user base however it requires some extra registry entries to work for Lync 2013 in addition to the original install so we decided to implement this via SCCM, here’s how we did it.

Firstly download Lync Translator http://www.microsoft.com/en-us/download/details.aspx?id=26136. The additional registry entries you will need are below:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USERSoftwareMicrosoftOffice15.0LyncAddins{2b26edf9-92e0-4d9c-9d7a-f772fcd4f31b}]

“Name”=”Lync Conversation Translator”

“Parameters”=””

“ExtensibilityApplicationType”=dword:00000000

“ExtensibilityWindowSize”=dword:00000001

“DefaultContextPackage”=dword:00000000

“InternalURL”=”http://go.microsoft.com/fwlink/?LinkID=68810&Lync=y”

“ExternalURL”=”http://go.microsoft.com/fwlink/?LinkID=68810&Lync=y”

 

[HKEY_CURRENT_USERSoftwareMicrosoftOfficeLyncSecurity]

[HKEY_CURRENT_USERSoftwareMicrosoftOfficeLyncSecurityTrusted Sites]

[HKEY_CURRENT_USERSoftwareMicrosoftOfficeLyncSecurityTrusted Sitesconversationtranslator.cloudapp.net]

“http”=dword:00000001

“https”=dword:00000001

 

First things first save the above as a .reg file we created a script to get the registry entries in:

@echo off

reg import LyncTranslator.reg

exit /b %errorlevel%

Save the above as install.cmd – the above import method ensure the entries go in as the current user not as an admin and also the error code enables us to utilise SCCMs install function to check it went in ok.

Next create an application for the registry keys. Deploy the application as a Script use most of the default options however for the detection method specify the below:

Ensure the Installation behaviour is Install for user and the Installation program visibility is Hidden. Also ensure the below Return Codes exist:

You can deploy and test this separately if you wish.

That’s the hard bit over! Next do a new application for the translator itself – because its an MSI accept the default values – I also add the following switches for completeness /passive /norestart. In addition add a Dependency for the registry entries:


Give it a test:


Hope it helps!