The difficulty of setting up a virtualized client to function with Lync 2013 was the order of steps then the method used to install the necessary bits. Please follow vendor specific information to determine the way your particular thin client needs to be provisioned. In my instance, I used a WYSE X90M7 thin client with Windows 7 Embedded as the Operating System. In this article WYSE refers to the physical client and VDI client refers to the virtual machine that will run on the Wyse.
My particular set up was a VDI in a box 5.3 setup with Hyper-V as the hypervisor. I have Server 2012 on all servers, Windows 7 SP1 embedded is running on the WYSE, and the VM is going to be windows 8. All but the embedded machine support RDP 8.0 natively. Lync 2013 is on Server 2012 as well and July updates have been applied.
Prerequisites include a fully functional Lync environment with correct EWS functionality. With this in place, the steps to get Lync 2013 running across multiple virtualization technologies with RDP 8 is laid out as follows.
WYSE TERMINAL SETUP
- The Server for Lync Needs to be 2012 or, if you have 2008 R2 server, updates for Server 2008 R2 and windows 7 need to be applied. This includes any windows 7 machines, including a VDI client like WYSE- running Windows 7 embedded.
- The Wyse client needs the latest update (KB2574819)
- Please keep in mind the Wyse updates procedure requires 3-4 restarts in and out of admin mode. Here are the sub steps for the two needed updates:
- Boot WYSE to admin mode (hold down the shift key after splash and hold until you admin login. administrator and Wyse#123 for the password
- use the FBWF filter. Disable it. This should be a red ICON on the desktop. Restart back into ADMIN mode.
- Install the above 2 updates.
- Restart into admin mode
- The next update is to the VDI (Wyse machine) client. This Lync 2013 plug-in will be X32 or X64
- Warning: the VDI client and the physical client must be on the same “bitness”. In other words, the x32 Wyse, means I am using a VM that is 32 bit windows 8, with lync 32 bit client installed.
- The plug-in needs to be extracted to a flash drive, before being installed in the physical VDI hardware. In my case, the hard drive was small. I ran the command lyncvdi.exe /extract:pathfolder and then ran the installer from the USB. The Lync plug-in was about 750 MB.
- Now RDP 8 and Lync VDI client are installed on the Wyse terminal. If RDP is installed your connection will look like this:
If you don’t see it installed, then you can also download the plug-in for RDP 8 from the Wyse support site for your model. Use the ADMIN mode to install the update. Once you have all the bits in the correct location, The other prerequisites can be accomplished.
- Log in as Admin mode (WYSE), Go to the mmc-file->add remove snapin->certificates->local computer and import the internal and external pool FQDN certificates, Root CA certificate, and other certificates as required by your organization.
- On the Wyse client- add the following Registry Key- HKLM\Software\Policies\Microsoft add a key called office, Add a Key under that called 15.0. Add a key under that called Lync. Create a new string in the Lync folder called “TrustModelData”. The values here will be the pool FQDN, and any FQDN for all Lync servers in the organization that need to have a trust to the endpoint.
- On the Lync server enable the redirection policy- New-CsClientPolicy -Identity 2013Lync -EnableMediaRedirection $true
- Configure GPO Redirection as per this article on local audio redirection (mmc->group policy object editor) of WYSE and Domain Policy (gpmc.msc)-
- Set terminal services RDP to allow redirection
- Set fDisableAudioCapture to 0 in the registry location – HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp
- On Lync Server, set the existing policy or create a new policy to allow media redirection. An Example: New-CsClientPolicy -Identity VDI -EnableMediaRedirection $true
Next, is it time to move to the VDI instance and details. I had to set the Wyse machine default RDP settings to use the remote computer and do not record. I then set the Virtual client (VDI in a box client) to play on this computer and enable audio redirect. QOS is beyond the scope of this article, but needs to be considered if you are planning to use the VDI in production. See TechNet for More information on its setup. The VDI client needs to be setup like the following.
VDI CLIENT SETUP CHECK
- The virtual client needs to be the same bitness as the Wyse terminal it will be connecting from.
- If Windows 7 install hot fix 2592687 and 2574819 as explained above. In my case the Windows 7 VDI client is joined to the domain.
- For Windows 7 or 8, install the Lync VDI module and Lync full client, with latest patch. The basic client will not work.
- Install Integration services for hypervisor, or VMware tools or Citix Agent, depending on the virtualization used.
- VDI plug-in Charts overview
- Verify the local or domain policies default to RDP 8.0. If not they must be set manually. Here is a good walk through on this subject at blogs.msdn.com
Once this is completed, if you have not finished bringing the WYSE terminal out of admin mode by restarting in Admin Mode and Enable the FBWF filter . Restart the client into admin mode and make sure you have anything else done you want to complete. login to regular mode and login to VDI machine with RDP 8. Start your
client and make a call to it. It will look like this when it works: