If you want to know what aspects of Microsoft Lync® are supported in the VDI environment, vague data does not give the straight facts necessary to make informed decisions. At least, apples to apples comparisons are not possible when information is unclear.
So, I am writing to rectify this situation. Allow me to shed some light on the various platforms (client operating system, and versions of Microsoft Lync) to shed, that are supported by Citrix XenApp and XenDesktop. This can help you to make your own decision when it comes to comparing what VMware Horizon 6, to what extent the support supports Citrix offers.
make Hopefully accuracy of your choice easily.
The Actual Scoop
Citrix supports Windows, Linux and Mac clients. In contrast, VMware supports only a limited subset of Windows endpoints. VMware does not support Lync on RDS servers is performed while Citrix is doing.
Microsoft released the Lync 2013 VDI Plugin (Media Engine), an optimized architecture for Microsoft Lync will provide 2013 Microsoft VDI Plugin available from both Citrix and VMware supported. Thus, the support provided in each case identical. Therefore, the VDI Plugin is the recommended solution for Windows-only implementations.
support for non-Windows end points (Linux, Mac) in your area
Consider having we optimized for Lync 2013 Citrix solution. Also, if you need Lync 2010 support, is the only available optimized Lync solution of Citrix HDX RealTime Optimization Pack 2010. applies to Microsoft Lync As a rule, you should hairpinning (read the footnote at the bottom for more information) to avoid and here implement optimized transmission of Lync audio and video data stream, where possible
is a look at the optimized support for Microsoft Lync by Citrix and VMware virtual platforms .:
Note: used in the tables in this post, is Citrix XA refers to Citrix XenApp version 6.0 and higher, while XD XenDesktop version 7.1 and later refers. In both cases it is the HDX Real Time Optimization Pack version 1.5 or higher. VMware Horizon referred Horizon View version 5.2 or higher.
Obviously there is a big difference in the supported platforms .
This is because the support provided by VMware Horizon, which is limited to the capabilities of Microsoft Lync VDI Plugin. On the other hand supports Citrix both the Microsoft Lync VDI plug-in and its "own HDX RealTime Media Engine (RTME), which is 2010 to 2013 compatible with Lync Server
To one of the operating systems support with a marker "x" to them next in VMware column:
- to the Citrix HDX realTime Optimization Pack use for Microsoft Lync and install the RTME on Linux, Mac and (if desired) on your Windows device.
- This support extends to optimize Lync voice and video telephony on Linux Thin clients and Mac OS X operating systems, allowing users the flexibility to access Lync from all these devices .
- in addition, contains the RTME component both Microsoft proprietary and industry-standard codecs allows interoperability with Lync endpoints and third-party products that register with the Lync Server as Cisco, Tandberg and Polycom in room videoconferencing systems.
Likewise the significant difference
[1945001Die"OptimizationPack"] allows Lync as a shared application and as part of a common desktop on shared hosted desktops running. You can not just Windows desktop operating systems use Lync Server but Windows server operating systems as well as to run. This allows greater consolidation - which * Although Windows Server 2012 [R2] not listed at a higher user density and increased resource use efficiency in data centers 
as fully supported. Microsoft at http://technet.microsoft.com/en-us/library/gg412781.aspx commented Eason Wang Microsoft TechNet Community Support on this Lync TechCenter page " should work just fine ... "and we have confirmed in our own tests.
Last but not least is the fact that with Citrix a series of Lync Server versions can be used, giving you the flexibility to install the version that best suits the needs of your environment.
By the way, supporting the Citrix Lync Online (Office 365 Lync hosted) in the new version 1.6 of HDX RealTime Optimization Pack for Lync includes AD Federation. So user accounts on the site in the company without password synchronization can be maintained in the cloud.
a list of all functions to obtain that are supported by each of the various methods, generic, Lync VDI Plugin and the Optimization Pack, see the CTX products - http://support.citrix.com / article / CTX0279
the Key Take-aways
As the above discussion clearly shows what you need Citrix XenApp and XenDesktop with HDX Real time Optimization Pack, if one or more of these situations in your VDI environment be present:
- users are not only to Windows endpoints access to get to the Microsoft Lync
- you want Lync on Windows server operating systems
- you would like voice and video streams transmission optimized for Lync 2010 or 2013.
footnote to run on hairpinning
generic unified communications (UC) technologies capture media from the terminal and encode and stream to the client, but this results in latency, audio and video quality and to increase the server load, reducing server density. This happens because of "hairpinning". Hairpinning is when media is detected in the terminal of origin and to the server (Lync) is sent to code before it is sent to the target client on the mobile device for playing back down. This is especially noticeable in offices, where you can call someone in a building few blocks away sit, but could feel the audio and video delay, as if they were half a world away.
The way to avoid hairpinning to capture the media data directly to the terminal without the participation of the server in the processing and process. This leads to the reduction of bandwidth consumption and of the server and the server lower CPU load than the encoding and decoding is now done on the clients. This is what we call optimal delivery (see / blogs / 07.18.2012 / delivery softphones-and-uc-apps-with-HDX Realtime Technologies /). Below to see a graph of how the optimization works:
Note: 5 is where all audio and video traffic are completely intended to prevent circumvention server so that bandwidth consumption within the firewall and latency between clients to reduce.
0 Komentar