Can anyone confirm if Jabber for Windows or CUPC is supported within a Microsoft VDI environment, or whether there is a roadmap for future support?
My customer is moving most users (approx. 2000) to Microsoft VDI.
In this case the users will have IP desk phones, so only require the Presence/IM/Desk phone control features – not necessarily the voice/video softphone parts.
The following CUPS client VDI support is specified in the relevant datasheets and release notes, but none of them mention Microsoft VDI:
So, the questions are:
Unless I can find a solution, the customer may have to deploy Microsoft Lync for Presence and IM, and configure RCC for desk phone control.
Also, does anyone have any experience that CUPC or Jabber for Windows will actually work OK with Microsoft VDI, even though it may not be officially supported by Cisco?
Thanks for any advice.
Message was edited on April 19, 2013: Lisa Marcyes from the Cisco Collaboration Community Team added community category and tags for greater ease in filtering (no change to content).
Support for Microsoft VDI will not be supported with CUPC but is on the backlogfor Jabber for Windows.
However, we have yet not committed a release of Jabber for Windows for such support.
Can you please respond with additional specifics (relevant version numbers etc...) ?
Sorry to latch onto your post Gareth but continuing the theme of virtualised desktop support.
Is there an estimated release date for Jabber for Windows with support for VMware View?
Are you referring to this? Of course for full UC experience you have to look at VXC. 6215 supports Jabber in UC mode
Cisco Jabber for Windows supports the following:
Cisco Jabber for Windows supports the following functionality in virtual environments:
Yeah just wondering if there was anything new for companies, those 99% that don't use Cisco VDI today . I see that Lync 2013 has some native development going on with Citrix and could be a good selling point for them.
Yep already raised that issue today with the VXC BU today ☺
The issue is you have to terminate audio/video stack locally and so both Lync and Cisco have their stance. Cisco is using the 2100/2200/6215 to terminate audio/video locally especially the 6215.
Lync is using their Lync VDI connector to redirect audio/video locally through Citrix.
Of course Cisco has been doing it longer
PRO for Lync
HW independent(looks like it from reading articles)
Pro for Cisco
End to end solution(tested design guides right from the DC to the endpoint)
Video. This is unknown for Lync. Citrix is licensing their RT Video codec which is proprietary but in 2013 Lync announces support for SVC which again may not be standards based. Jabber with 6215 will support 720 standards based video which is a big plus
CC support. This is where Lync has no story and if Cisco blesses finesse quickly with 6215 it will be a killer.
We have a requirement where customer is already running Citrix Xenapp 6.5 and Xendesktop 5.6 over Dell Wyse T10 (Thin Client) and lync 2010 for IM and Presence.
We are proposing Cisco UC solution over there want to confirm Following:
· Over above Infra can we deploy CUCILync / Jabber for IM, presence and Deskphone Control
· Remote Call control integration (CUCM and Lync 2010) is the only solution.
Jabber is supported in deskphone control in these enviroments below
If you plan to run in soft phone mode then today it is supported on the 6215 and soon in the future on Wyse Z50D
CUCI Lync is supported in 6215
Thanks for valuable information.
Pls clarify following doubt as well:
Will CUCI-LYNC be a supported integration only for IM, Presence and Deskphone Control feature over mentioned Virtualized Desktop environment (Citrix Xenapp 6.5 and Xendesktop 5.6 over Dell Wyse T10 (Thin Client)?
Thanks in adv.
Outside of VXC I am not sure if it is supported. It may work but the issue is TAC support. I would ping Heather Paunet you will see her posts on the community since she heads up this client