vastidea.blogg.se

1. #MICROSOFT LYNC 2013 64 BIT INSTALL#
2. #MICROSOFT LYNC 2013 64 BIT UPDATE#
3. #MICROSOFT LYNC 2013 64 BIT FULL#
4. #MICROSOFT LYNC 2013 64 BIT WINDOWS 8.1#
5. #MICROSOFT LYNC 2013 64 BIT DOWNLOAD#

We can't install the 32-bit version of Office because we found the following 64-bit programs on your PC: When I try to install the 32-bit version, I get this message:

#MICROSOFT LYNC 2013 64 BIT WINDOWS 8.1#

I am using a 64-bit Windows 8.1 system, and I have tried installing both the 32-bit and 64-bit versions of Microsoft Lync Basic 2013. Unable to log into Lync Server 2013 Edge server wi.I need to install Microsoft Lync.Configuring Citrix Profile Management 5.2.0 for Xe.Citrix XenDesktop and XenApp 7.5 / 7.6 Microsoft S.

Troubleshooting Citrix NetScaler LDAP Authenticati.Securing a Citrix NetScaler IP (NSIP) GUI Access w.Lync Server 2013’s Deploy Monitoring Reports wizar.Sorry about the brevity of this post but I just wanted to quickly demonstrate that this configuration also works with XenApp 6.5. It is likely that these registry keys would need to get created if the computer was not joined to the domain. I believe the reason why is because the desktop I was using to connect to XenApp already had Lync 2013 installed on it and although the registry key above did not contain any of the items that had to get manually added to the thin client, the redirection still worked. "ServerAddressExternal"="" <-String Value "ServerAddressInternal"="" <-String Value HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\15.0\Lync

#MICROSOFT LYNC 2013 64 BIT FULL#

Note that unlike the thin client I was working with in my other post, I did not have to set the following registry keys on the Windows 7 full desktop I was using: Lync is all set to use your local audio and video devices. Restart the thin client and you’ll notice that when you connect to your VDI, you will see a new green small icon at the bottom right hand corner with a white checkmark:

#MICROSOFT LYNC 2013 64 BIT DOWNLOAD#

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: The 64-bit version is not compatible with Citrix Receiver for Windows since the bitness of the VDI Plug-in must match the bitness of the Receiver. The 64-bit plug-in is not supported and will not work as described in the following Citrix article:Ĭitrix Receiver for Windows requires the 32-bit version of the Microsoft Lync VDI Plug-in on the device, even on a 64-bit Windows machine. **Note that at the time of writing this post, only the 32-bit version of the Microsoft Lync VDI Plug-in is supported and will work for redirecting audio and video. Step #3 - Install Microsoft Lync VDI Plug-in on the client connecting to XenApp 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 #2 - Enable EnableMediaRedirection on Lync 2013 ServerĮnsure that the Lync Client Policy of users who will be redirecting to local devices has EnableMediaRedirection enabled.

#MICROSOFT LYNC 2013 64 BIT UPDATE#

Step #1 - Update Citrix Receiver on the HP t610 thin client to version 4.0īegin by checking the existing version # of the Citrix Receiver installed onto the client connecting to the XenApp 6.5 server and update it to a version later than 4.1.02. I haven’t actually been working with XenApp 6.5 over the last few months and so never tested the configuration but as I to do so today for a client with the legacy architecture, I thought I’d write this short blog post about the configuration. XenDesktop, XenApp and Citrix Receiver Support for Microsoft Lync 2013 VDI Plug-in … may know that although the requirement for XenDesktop 5.6 is to use the XenDesktop 7 VDA, which renders XenDesktop 5.6’s Desktop Director unusable because it does not support 7.x VDAs, XenApp 6.5 published desktops is a supported configuration as outlined in the following Citrix document: Those who may have come across my previous post about integrating Lync 2013 audio and video redirection to the local client:ĭeploying Microsoft Lync 2013 audio and video within a Citrix XenDesktop 5.6 VDI