![]() Step #3 – Configure the registry of the Lync VDI plug-in on the End Point with Lync Server information Lync is trying to use your local audio and video devices when you hover the mouse over the icon or click on it: Restart the thin client and you’ll notice that when you connect to your VDI, you will see a new small icon at the bottom right hand corner indicating: Then run the setup.exe executable to install the plugin: Proceed by extracting the package with the command: I never had much luck just running the install on a HP t610 and Wyse clients as the install will fail once the files are extracted: The package you’ll receive is named lyncvdi.exe with a size of 223,651 KB: Proceed to download the Microsoft Lync VDI 2013 plugin 32-bit and install it onto the thin or thick client that will be used to connect to the virtual desktop: Step #2 - Install Microsoft Lync VDI Plug-in Set-CsClientPolicy -identity Global -EnableMediaRedirection $trueĮxecuting the Get-CsClientPolicy -identity Global cmdlet will now show the following: Proceed by using the following cmdlet to enable it: **Note in the above screenshot that EnableMediaRedirection is not enabled. The environment for this demonstration has all the users using the Global policy so executing the Get-CsClientPolicy -identity Global cmdlet will show the following: Step #1 – Enable EnableMediaRedirection on Lync 2013 Serverīegin by ensuring that the Lync Client Policy of users who will be redirecting to local devices has EnableMediaRedirection enabled. With the prerequisites out of the way, the following outlines the steps for the deployment. VMware View Agent: Needs to be 5.2 or higher Virtual Desktop’s Lync Client: Can be 32 or 64-bit Lync VDI Plug-in installed on End Point OS: Must be 32-bit Lync VDI Plug-in To avoid confusion, I will itemized the following important considerations:Įnd Point Operating System (e.g. This is obviously quite disappointing and may not be an option in some environments depending on the type of work the user performs with files such as spreadsheets but this is a limitation with no workaround. Using the plug-in on a thin client isn’t usually an issue since Office does not need to be installed but if you are using a regular thick client such as a PC, then you absolutely would need to install the 32-bit version of Office. This could either be because the Windows Operating System is 64-bit or because the installed Office 2010 or 2013 is 64-bit which would not allow you to install the 32-bit Lync VDI Plug-in. One of the most common mistakes I’ve seen for deployments is when the administrator downloads and installs the 64-bit Lync VDI Plug-in onto either the thin client or PC that would be using the VMware Horizon View Client to connect to the virtual desktop.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |