Expanding a linked clone vPC thin provisioned disk

[DADBVM]

We have the following:

ESXi 5.0.0 build 1311175

vCenter Server 5.0.0 Build 455964

vSphere Client 5.0.5.0.0.37933

View Horizon 5.1.0 Build 704644

View Compose 3.0.0.691993

vShield Manager 5.0.2- 791471

VMware Tools version 8.6.15 Build 2495133

The Windows 7 image has 2 drives of interest:

C:\ OS (30GB Thin Provisioned)

D:\ user profile (10GB Independent Persistent disk)

The issue is the C drive is 30GB Thin Provision in total, with 6GB of free space.  I have disabled the disk defrag, system restore is 3% (900MB).

The only thing that gets installed are the Windows updates on patch Tuesday.  The programs we use are static they don't really change.

So no new installs of any kind except for updates to Java and Adobe.  I install one piece of software once a year.

The users don't have rights to install software on their vPC.

I regularly run the disk cleanup for the C drive, but find that not much space is reclaimed.

I would like to expand the C drive of the 30GB but option is grayed out for the vPC (See attached screenshot).

I went into the VMware View Administrator to see if I can expand the C drive about unable to locate the area where I can expand it.

I do see the area where I can expand the persistent disk but not for the OS disk.

The plan was to expand the OS disk then recompose the specific desktop as the need arise.

Can you please advise if this is possible to expand the OS 30GB in VMware view?
Also this vPC's are from a Linked clone

[a_p_]

In order to resize a virtual disk it must have no snapshots, i.e. you need to delete all exiting snapshots and expand the base virtual disk.

André

[DADBVM]

Thanks Andre for replying.

On the Parent image I have been making snapshots as time goes on.

Updating adobe, java and windows updates.

Here is a screenshot of the what I have been doing. (Parent image)

On the specific vPC it doesn't have any snapshots (vPC snapshot)

Will I have to consolidate snapshots on the Parent image in order for me to edit the pool or specific desktop?

[a_p_]

Snapshots (as well as linked clones, which actually are snapshots too) contain data blocks with a reference to the position in the original/base virtual disk's .vmdk file. This unfortunately makes it impossible to resize a virtual disk with existing snapshots.

André

[DADBVM]

So I would have to delete everything, go back to the base image then expand the disk?

[a_p_ · Accepted solution]

Unfortunately yes. Alternatively you may create a full clone from the VM's current state and use this as a new base disk. This may not only be faster than to delete all the snapshots, but also allows you to maintain the current VM's state in case you need it later.

André

[DADBVM]

Thanks Andre.

I see your point.

I will update this discussion once I complete the making the full clone from the most current snapshot.

[DADBVM]

Thanks Andre

100 percent correct.

I took the last good snapshot.

Cloned it at which point I was able to expand the C drive.

My next steps will be to remove the old parent from view.

Add the new one.

Removed the old snapshot

Add the new one.

Recompose and all existing vPC will get the new disk increased.