Setting up a security server for our organization. Initially I was excited because I imagined that most of our users could potentially connect to our View farm with no client install needed, and simply make use of the RDP client in Windows. However, it quickly became obvious that the VMware View Client needs to be on the system before connecting. If the View Client simply uses RDP to connect to the View farm anyway, why is a client download necessary? This would be a huge advantage over Citrix if it were made possible.
Philip
You can have your users go to your connection server's web address and log in that way. It will automatically install the client. Would that work for you?
Without the client, there is nothing to do the brokering/desktop assignment. It's a rather vital piece of the puzzle.
Can you describe your environment/type of pools you want to use/etc a little more? Perhaps we can suggest an alternative or provide some ideas?
Microsoft Terminal Services does it just fine without a client. They download a .rdp file from a web server and you're done. The server is what does the actual brokering, not the client. I understand why Local Mode would require a client, but to simply kick off a rdp session shouldn't require a client.
You can have your users go to your connection server's web address and log in that way. It will automatically install the client. Would that work for you?
I'll mark your question as answered, because what I'm after is not presently possible. What if a user wants access from a hotel business workstation? Typically, they don't have admin rights----What I want is a true clientless solution, and perhaps an optional download for performance optimization.
it's a bootable USB/CD. you can boot it up provided that the hotel has a cdrom/usb drive and also the network does not have certain firewall rules that block off the needs of vmware view.
we also looking for Clientless as well ,for running the X2 or anything on USB or CD you need access to the computer sometime this kiosk computer are lock under the table and they are not accessible .
last week I had the idea to put the thinapp clinet on different URL and ask my Clint to download from their but then I have to publish a new URl for them, I wish the View web site was customable and I could build it to it, but is not
another idea is MAC, the view is using java base client on that OS ,I was thinking if we can use that on PC it will be cool but I couldn’t trick the IE to do that ,does anyone know the full path to JAVA client for view ,I know it will work because I put that “clinetlunch.jnlp” on PC from a Mac and it work .
Here is a link to what we ended up doing. In short, I ThinApp'd the View 4.5 client, as well as our SSL VPN connection, and delivered them on a USB stick. It works well; the only thing you lose is USB redirection.
http://communities.vmware.com/message/1670272#1670272
We're also working on embedding a link to the ThinApp'd View client right in the home page of our VPN portal. I'm about 90% of the way there. This will give our users the ability to "bring your own PC", without the need for the USB stick.
We thinapped the old view 3 client and placed it on a thumbdrive which only does RDP. This keeps the client from becoming confused in having to change from PCoIP and RDP which are the options on the 4.5 client.
have you tried terminal services - we are testing TS as a solution to host the view client and let the users run it from there.
thank you VMSF ,I never think about TS to host the client ,that is good idea .the USB and CD people lose them or they forgot to take them is not the best option but we still have one option which we have to provide two link ,do think VMware will come with some option to make view portal more customizable
VMware is planning on releasing a view client over http/s, so you can access it through a web client, which definitely will help. Also, there is already a client for IOS and Android devices.
The Android client is $15, and I don't think is made by VMware. Helpful nonetheless. I'm really liking the idea of using Terminal Services to simply launch the client. We may use that.
Philip