VMware Horizon Community
bunice
Contributor
Contributor

VMware Infrastructure for Workstation

Hi,

I write this post because we are losing in VMWARE product jungle Smiley Happy

We are a public institution and we need a formation room with arround 60 computers. We want to build a VWMARE infrastructure to mangage this room; but we are not familliar with the environnement so we would like to start with "simple" independant ESX Server without SANE. Our provider propose USX ESX Standard produt wich included ( ESX Serveur for 2 cpu, VMFS for 2 cpu, VirtualCenter Agent, Virtual SMP 2 cpu, Update Manager, Consolidated Backup, High Availibility).

In first instance, this is not a problem for us if we have long manual configuration as I think that in the first time virtual machine will be accessing by thin-client with RDP protocol. So we will use script to copy and register a vmare image on the servers, run all VM, assing an IP adress and then configure each Thin-client to access a VM throught RDP.

But in nearest futur, we would like to build a VDM structure (wich require Virtual Desktop and VDM product, so that (I think) our thin-client will be able to access and open session with their integred Firefoxbrother (wich support JAVA plug-in); So I would like to know some opignion about this plan? Do you think that we will be limited by ESX standard componement to upgrade our virtual architecture? Also in case we use VDM to access a pool of VM: what about mapping USB key from thin-client to Virtual Machine?

Also it's hightly probable what we run only Windows XP product for Virtual Machine; do you think it will be better for us to buy some VDI kit?

Sorry because my English is full of faults.

MANY THANKS TO ALL READERS AND HELPERS

Message was edited by: Ken.Cline to remove ALL CAPS from subject

0 Kudos
3 Replies
Texiwill
Leadership
Leadership

Hello,

We are a public institution and we need a formation room with arround 60 computers. We want to build a VWMARE infrastructure to mangage this room; but we are not familliar with the environnement so we would like to start with "simple" independant ESX Server without SANE. Our provider propose USX ESX Standard produt wich included ( ESX Serveur for 2 cpu, VMFS for 2 cpu, VirtualCenter Agent, Virtual SMP 2 cpu, Update Manager, Consolidated Backup, High Availibility).

If no SAN or no more than 1 host then High Availability is not useful. HA moves loads between hosts when one host dies. Experimentally it can reboot VMs however but in general it is used to provide for host level failures.

In first instance, this is not a problem for us if we have long manual configuration as I think that in the first time virtual machine will be accessing by thin-client with RDP protocol. So we will use script to copy and register a vmare image on the servers, run all VM, assing an IP adress and then configure each Thin-client to access a VM throught RDP.

Definitely doable.

But in nearest futur, we would like to build a VDM structure (wich require Virtual Desktop and VDM product, so that (I think) our thin-client will be able to access and open session with their integred Firefoxbrother (wich support JAVA plug-in); So I would like to know some opignion about this plan? Do you think that we will be limited by ESX standard componement to upgrade our virtual architecture? Also in case we use VDM to access a pool of VM: what about mapping USB key from thin-client to Virtual Machine?

There are many connection brokers out there and most end up using RDP, so whatever RDP supports they will support. NComputing makes a hardware device that works for this as well. That way you have a thin client that is a keyboard, monitor, mouse, their device that uses its own tool to access the VDI system. Or you can use a straight RDP session. Secure RDP, etc.

Also it's hightly probable what we run only Windows XP product for Virtual Machine; do you think it will be better for us to buy some VDI kit?

That works.

There are many ways to do VDI, and how you do it depends on your VM need, management needs, and configuration needs. You can setup 'static' VMs for each user. Pools of VMs, or even check out/check in style VMs. What you use depends on your needs and the connection broker used. VDM is one option. THere are 20 or so others as well.


Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.

CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354

As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

--
Edward L. Haletky
vExpert XIV: 2009-2023,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill
0 Kudos
bunice
Contributor
Contributor

Thank you very much for you answers.

But just a little question:

As I understand VMWARE client use RDP protocol to connect to Vitual Machines so we got all advantages of this protocol (like map a usb key or a local printer device) ? Is it right?

0 Kudos
Texiwill
Leadership
Leadership

Hello,

That depends on the client and server parts. If it is RDP then yes. If it is not, then no. I have moved this post to the VDM forum for clarification. Please remember to award points for helpful and correct answers.


Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.

CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354

As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

--
Edward L. Haletky
vExpert XIV: 2009-2023,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill
0 Kudos