VMware Horizon Community
philric
Contributor
Contributor

VDI and VSI on the same physical infrastructure

Hello everybody,

For some reasons related to the sudden change user's need, we have to install 2 virtual desktops (Win10). Normally, we are using Microsoft RDS through Thin clients or physical laptop. It is starting to be complicated to give a good service to our users with RDS.

At a short term and because of the urgency, we are considering to install simply the 2 virtual desktops on our VSI and linked manually the thin clients to them. For the mid term (1year), it is going to grow to 20 virtual desktop. In the long term (2-3 years), 120 virtual desktops will be installed. Our infrastructure has a lot of free CPU, RAM, Disk space and the workload is low. By financial and time reason, it would be a pity to dedicate an infrastructure only to the VDI. SCCM is used to install the laptop and deploy the applications and is planned to be used to install the virtual deskops.

What are the possible solutions in this case ? Running the VDI and VSI on the same infrastructure ? If yes, is there any best pratices or advices for that ? What would be the licenses to choose ? Horizon Add-on ?

Do not hesitate to share the link of existing discussions if they are related to my case 😉 I could not find any at that time.

Thank you in advance for your help.

2 Replies
sjesse
Leadership
Leadership

The reason its a good idea to separate servers and desktops is they are different work loads. Desktops have more random workloads which mean  things like DRS are going to be more active.  This means if you a cluster of hosts your servers might start migrating repeatedly based on how your users are working. If your using Horizon and linked clones the recompose process if very intensive and you will put stress on the hosts as well which can affect your server workloads

There are other reasons but thats the main one. At a minumum if you can spare 2-3 hosts you can share the existing vcenter, and just make a desktop cluster, you can share everything else. Over time the strain on vcenter will require a dedicated vcenter, but I think thats when you have a over 1000 concurrent users I think.

philric
Contributor
Contributor

First of all, thank you for your answer.

I understand the reason of separating the VDI and VSI. At short term, the workload will be low 20 virtual desktops and for sure it is planned to have a separate infrastructure in 2-3 years (Budget is most of the time -> the issue...)

What should be done in those 2 scenarios ?

All our applications are managed through Microsoft App-V and SCCM. All the profiles are managed through UEV (Microsoft User Experience Virtualization). The VDI will be only use for internal purpose, no cloud, no mobile clients (ios-android)

1) VSI and VDI on the same cluster

     Licences. Which ones?

Which steps for the deployments ? I suppose :

2) VSI and VDI on separated cluster

     Licences. Which ones?

Which steps for the deployments ? I suppose :

I am going to install a lab environment to play a bit with it.

Thank you very much for your feedback

0 Kudos