Changing Persistent Disk Space - Shrink View 4.6 Linked Clones

[cprawitz]

So in deploying our linked clones with persistent data disks I originally set the size for 10GB just to be sure that there was enough space. Now that our users' files are all migrated over to the new system the most a user uses is like 1GB because most files are stored on the network. Is there a way that I can shrink their "D" drives without having to start from scratch? I went into the view admin > pools > edit  and changed the disk size to 5GB but neither refresh nor re-compose did the trick. Any suggestions or places that I should look for information.

View 4.6

[Linjo]

Since these disks are already created and in use View will not do anything about them, I would expect that all new desktops have the new size you specified.

// Linjo

[cprawitz]

I was afraid of that. Anyway to move the users entire to include the hidden folders ect to a new persistent disk so that they keep their individual certificates fro websites ect?

[mittim12]

Aren't the disk used with persistent disk created as thin disk?

Sent from my iPhone

[cprawitz]

Yes they were created as thin disks but no matter what I do I cannot get them to shrink. I can expand them no problem but cant shrink them.

[mittim12 · Accepted solution]

Yeah but if they are thin disk and only using 1GB of space then it should only be 1 GB in size.   Unless of course the migration spiked it to 10 GB and then it dropped back down to 1GB.    In typical thin disk configurations (server) the only way to reclaim is to run something like sdelete inside the disk and then utilize storage vmotion to shrink it.