• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 645
  • Last Modified:

Effort estimation for VMware VDI

I would like to know the effort required for the VMware VDI implementation in 3000 desktops envirnment. Including all installation and configuations (ESX, VMware view, Broker agent..etc)
Also please advice me in the prerequisites.

Thanks in Advance
  • 2
1 Solution
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Could you expand on the environment at present you are trying to replicate with VMware View

e.g. Desktop OS, Applications installed or ThinApp deployed, Network, current desktops, any current GPO in place for desktops, profiles, folder redirection.

we would antcipate a program of this magnitude would take us 1 man year effort to complete and deliver. However the rollout would take much longer, unless you can provide more floor walkers.
Using the new versions of View makes this setup relatively easy.  Based on the information provided, here is a rough draft of the final setup:

VMware View 5.0
** Max VDI Desktops: 4,000 (VMware View supports 2,000 desktops per cluster)
** vSphere Datacenters: 1
** vSphere Clusters: 2 (each cluster supports up to 2000 VDI desktops)
** ESX Hosts: 16 (8 hosts per cluster limit for Vmware View)
** VMware View Brokers: 2 to 5 (recommended up to 4 active, with 1 deactivaed as standby)
    --> Brokers are very efficient, so I recommend starting with 2 and using a hardware load balancer for connection redundancy.  You can easily add additional replicated brokers as needed.
   Supporting Servers:
** vCenter: 1 dedicated to VDI (must be a member of domain; View Composer installed on this vCenter)
** Domain: Active Directory domain for authentication
** DB Server: 1 SQL server (needed for View Composer and View Event databases; can also house the vCenter database)

You could likely get by with less hosts since you're planning on supporting 3,000 desktops.  The rule of thumb for this is 8 hosts per 2,000 desktops.

Hope this helps! :)
Also, as far as time goes... this could likely be completed within two to three months once all components are available (and depending on resource availability).  My last project was similar (6,000 desktop environment) and took 4 months from start to finish.

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now