VMware

Automated desktop pools contain many desktops that are created automatically by VMware View.
A template virtual machine created in vCenter (with a snapshot) is used to create several unique copies of the same desktop.
If using Composer linked clones are created. This uses a parent disk (aka replica), instead of full clones. This creates what is known as a "diff disk" of the differences between the parent disk and itself. Without the parent disk the linked clones will not work.
In this example a Windows 7 template virtual machine created using Part 6 - VMware View 4 - Windows 7 Deployment Guide is being used to deploy several Windows 7 VMs in an automated desktop pool, using Composer and linked clones.

For an overview of the components of VMware View see VMware View 4 - Intro and Components.

Read more ...

CapacityIQ is an add-on to vCenter. CapacityIQ is used to assess virtual resource capacity based on current usage and what-if scenarios.

It can be used to determine under utilised or over allocated resources, so that waste can be re-allocated and bottlenecks can be removed.

Because CapacityIQ is used via a vCenter plugin, it is accessed via a single pane (aka the vSphere client).

Read more ...


When configuring networking on an ESX/ESXi server it is important that you plan and configure it correctly.
Doing so will ensure you get the best reliability, performance and security within your virtual network.

Depending on your requirements the configuration will vary slightly. For example if network storage such and iSCSI and NFS will be used the setup will need to plan for this.
I will explain the different setups for these needs.

Currently there is no VMware provided View Windows 7 Deployment Guide, so here is one I have created.

There are a few specific things that are required to allow Windows 7 to work with VMware View (especially with View Composer).

These are the steps I follow, it is based on Windows 7 Enterprise x86, the same should apply to Business/Ultimate.

Read more ...

As time goes by your vCenter database will grow, its a fact we all know and accept. However we dont want to retain unnecessary old data in the database which causes disks to eventually fill up and backups to for run longer periods. So what can we do about it? Change the vCenter database retention policy of course...

Read more ...

Share this blog post on social media:

Latest Blog Posts

Popular

Social Links

Disclaimer

All advice, installation/configuration how to guides, troubleshooting and other information on this website are provided as-is with no warranty or guarantee. Whilst the information provided is correct to the best of my knowledge, I am not reponsible for any issues that may arise using this information, and you do so at your own risk. As always before performing anything; check, double check, test and always ensure you have a backup.

Copyright ©2008-2021 Andy Barnes - Please do not copy any content including images without prior consent!

Designed and Hosted by Andy Barnes

We use cookies

We use cookies on our website. Some of them are essential for the operation of the site, while others help us to improve this site and the user experience (tracking cookies). You can decide for yourself whether you want to allow cookies or not. Please note that if you reject them, you may not be able to use all the functionalities of the site.

Ok Decline