Download Jvdi Client

[Margaretha Palone]

Ihave Jabber running on a Citrix virtual workstation and JVDI running on the physical workstation. I am trying to make a utility / script that would effect pulling a Jabber Problem Report without user input from the virtual workstation. I am able to gather all of the information I need, except for the VXC client logs, as those reside on the physical workstation, along with JVDI.

Jabber for VDI is a privileged solution for UCCE/UCCX Contact Center agents in order to replace the out-of-support Cisco IP Comunicator.

Actually, we already have been using Cisco Jabber as a softphone for UCCE agents who work from home through VPN. The newer implementation in the environment is regarding the VDI.

In the environment I have worked, we use a Citrix farm running version 7.8 with Virtual Desktop.

So we installed the 3 pieces of software that forms the whole Jabber for VDI solution :

Jabber for Windows and JVDI Agent on the Ctrix Hosted Virtual Desktop farm aka HVD.

and

JVDI Client on the thin client running Windows OS.

Afterwards, there comes the Firewall matrix that should be implemented so the solution works.

As Cisco document states, roughly, media ans signaling is passed through to the thin client. However for the other ports (CTI, Service Discovery and TFTP), unfortunately Cisco is explicitly specifying which component communicates with CUCM.

I put both our thin client and the Citrix farm in a golden cage and I found some interesting facts:

Jabber for VDI uses the JTAPI port 2748 so that the Citrix farm connects to CUCM.

This has been surprising because to sum up : Jabber for VDI is actually a chained couple of Jabbers :

Good day everyone. Running UD3 with LX 11.04.240, and our Jabber client is unable to connect. Here is a screenshot of the client / agent versions. Worked fine before the upgrade. Also worked fine for JVDI client version 12.8. Any ideas?

This link leads to the machine readable files that are made available in response to the federal Transparency in Coverage Rule and includes negotiated service rates and out-of-network allowed amounts between health plans and healthcare providers. The machine-readable files are formatted to allow researchers, regulators, and application developers to more easily access and analyze data.

While we are pleased to have you contact us by telephone, surface mail, electronic mail, or by facsimile transmission, contacting Kilpatrick Townsend & Stockton LLP or any of its attorneys does not create an attorney-client relationship. The formation of an attorney-client relationship requires consideration of multiple factors, including possible conflicts of interest. An attorney-client relationship is formed only when both you and the Firm have agreed to proceed with a defined engagement.

DO NOT CONVEY TO US ANY INFORMATION YOU REGARD AS CONFIDENTIAL UNTIL A FORMAL CLIENT-ATTORNEY RELATIONSHIP HAS BEEN ESTABLISHED.

If you do convey information, you recognize that we may review and disclose the information, and you agree that even if you regard the information as highly confidential and even if it is transmitted in a good faith effort to retain us, such a review does not preclude us from representing another client directly adverse to you, even in a matter where that information could be used against you.

Because of this, I strongly recommend reading the Jabber VDI guides as they are a bit more detailed than the Webex Virtual Desktop guide as it pertains to the installation process for the agent and client.

Do you have firewalls on your internal network between branch sites, the data center, and your Expressway-C? If you use internal firewalls, refer to the admin guide to ensure you have rules enabled to support the flow of traffic between the affected devices. These communication paths were not previously required in your environment, so there is a high probability you will need to configure the new ports/protocols on your firewall.

We made it. Launch that client from your Thin Client and be expected to authenticate given one of the three scenarios covered in your SSO section earlier. Once you make it past authentication, the WSF client device should be registered in CUCM, and your thin client will be ready to join meetings and broker their SIP signaling and media through the CUCM + Expressway path, completely bypassing your HVD server pool.

If you have remote (home worker) thin clients, you need to deploy Mobile & Remote Access (Collaboration Edge) in order to use the virtual app and redirect media through the Expressways. The deployment of the virtual app is essentially the same, but we do not cover the installation/configuration of MRA here.

This is one of the longer articles, but hopefully you have a decent picture of how Webex + VDI will work, the backstory of the JVDI roots, and you know the teams you need to engage within your company to get it deployed.

The first reason an iPad might make a good virtual desktop infrastructure (VDI) client is that today's tablets offer screen resolution rivaling that of desktop PCs from a couple years ago. The iPad display is up to the task of presenting desktop applications to users. We've also moved from 2G to 4G mobile networks that provide LAN-like speeds. So, the pieces seem to be in place for mobile access to corporate desktops without a laptop.

Before you begin an enterprise iPad deployment, however, decide who needs them in your organization. In some organizations, it's people who don't work regular hours and could be called on at any time. Senior management, project managers, on-call staff and conference attendees are obvious candidates. These people will have their iPad wherever they are and usually prefer not to keep a laptop on hand at all times. They can connect to a VDI session with their iPad and have instant access to a Windows desktop.

For many, the iPad desktop is more of a secondary VDI client, used until access to a larger screen is available with a proper keyboard and mouse. But what about employees who don't normally have a laptop or iPad and usually sit behind a desk using a PC?

I recently spoke to a colleague who finished a successful VDI rollout at numerous customer service centers -- specifically using iPads as VDI clients. At the service centers, staff use desktop computers behind long counters in front of a line of customers. The business deployed iPads to allow staff to be in front of the counter, talk to individual customers and show the customer detailed information. Staff can use the iPad desktop to access exactly the same CRM application that's available on their PC.

When I heard about the VDI client project, I thought it was a typical iPad fashion venture, conceived at board level with little understanding of real use. I assumed staff would eventually find that using Windows applications on the iPad desktop and keyboard is too difficult to use all day, every day.

Surprisingly, staff engagement with customers is so valuable that helpdesk leaps into action the moment the system is unavailable. Using the iPad as a VDI client means customers can ask much more open questions and get answers immediately. Most importantly, users get the full corporate application, whereas it requires a huge amount of effort to bring a large application to a new platform natively. Using a native iPad app probably wouldn't have met the business needs, and mobile applications often end up being very feature limited.

But, is an iPad always a good VDI client? Common iPad complaints are that the iPad desktop has a small screen and it doesn't support a mouse. Plus, VDI operating systems (Windows XP or Windows 7) don't have great touch interfaces and aren't well-supported over remote protocols. I doubt anyone wants to use an iPad as their full-time VDI client.

Still, that doesn't mean an iPad isn't a valid choice for a VDI client. It worked well in the case of the customer service centers. If you're at a conference with just your iPad and need urgent access to an enterprise application, an iPad gets you there. It's probably a better choice than going to an Internet caf and using their questionable device or Wi-Fi to access corporate systems.

The iPad won't replace most people's desktop thin client, but the VDI client can enable access in more situations. VDI from an iPad isn't always the best technical solution, but it can be the best business solution. Don't be surprised if you're greeted by customer service staff with an iPad in the future, and don't assume they have some watered-down mobile application.

Editing the registry incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.

As a security precaution, when a user logs on to Citrix Virtual Apps and Desktops, by default, the server maps client drives without user run permission. To enable users to run executable files residing on mapped client drives, override this default by editing the registry on the server.

If Always prompt for password is enabled, users must enter credentials on the VDA when they start a remote session. If this setting is disabled, users automatically connect to the remote session without providing credentials on the VDA.

This setting disables and removes the warning message for users reaching the idle session timeout limit on a Windows 2004 or later multi-session OS. To remove the warning, set the following registry value on the VDA:

MTU Discovery allows EDT to automatically determine the Maximum Transmission Unit (MTU) when establishing a session. Doing so prevents EDT packet fragmentation that might result in performance degradation or failure to establish a session.

By default, we support redirection of the following URL types: HTTP, HTTPS, RTSP, RTSPU, PNM, and MMS. You can add URL types to the list by creating the following registry key and values on the Windows client.

3a8082e126