On Fri, Oct 11, 2013 at 11:41 AM, Junaid Ali <[email protected]> wrote:
> Hello, > > We are currently using one software per Windows 7 image within VCL (VMware > hosts). > I assume that by "software" you mean an application (such as Maple, or Matlab) > As we move forward with adding additional software into the VCL > environment we are planning to deploy multiple software within one image. > Why would you do this? Our experience is that the user (assuming what we call "desktop augmentation") wants *one* application to be made available. E.g. the user who wants Maple probably wants only Maple and not also ArcGIS or Cadence. Sometimes a small "cluster" of applications might be needed - e.g. a spreadsheet along with ArcGIS - but even that is typically only two applications. What this does is produce an array of smaller images, which will individually load faster, rather than on huge image containing many applications. Note that one of the reasons for the original development was that there are, too often, conflicts between different applications (e.g. "DLL wars") which are installed together. Even if they are invoked one at a time, there can be many problems which then take a *lot* of support time to solve - when they can be solved. We now have over a hundred applications on our VCL, and it would create a *huge* mess if we tried to install them all in one image - and there is no need to do so. > This will increase the size of our image from 30 GB (currently) to 100 GB. > > I was wondering what the average VMware image sizes are used by the > community and if anyone faced any issue with larger VMware image sizes. > The larger they are, the slower they load, and the bigger load they place on the system. Somebody else should comment on actual sizes and to what extent compression can help cope with image size. --henry > > > Thanks. > > Junaid Ali > > >
