Theike
Hot Shot
Hot Shot

We have the same issues on several of our customers locations.

What we do is that we have lists of active applications, as well as 'old' applications. The sandboxes get renamed for every new release of a virtualised application (we don't re-use existing sandboxes as for example updated isolation modes would not be applied). This makes that the number of  unused sandboxes is in general larger than the number of active ones.

In our case we advise our customers to place sandboxes on some share using a general naming policy (in general by setting the sandbox redirect environment variable). The sandboxes are thus stored in something like \\server\share$\% username %\sandboxes\(sandboxname).

Now we have 2 simple scripts:

The first one loops through the folderstructure that matches a given naming policy. This dumps sandboxname, size and last access date

This can be imported i excel, access or whatever 'inteligent' tool to determine the extreme sandboxes (old (aka: unused apps), large (invalid sandbox policy applied), average size, total size/sandboxname, ...)

The second script is cleaning up sandboxes, matching sandboxes in the given location agains a list of sandboxnames to be cleaned. This is only used to delete ALL sandboxes for a given application (sandbox identifier). Individual sandboxes are removed only manual (for example when extreme in size due to updating the virtualised app, which should never be done by a user)

These scripts do need adaption for every location, but are simple to create yourselves. I have done similar actions in VBscript as well as Powershell and the basis should operational within a few hours for a handy scripter.

Kind regards,

Michael Baars - Comprehensive ICT Solutions (NL)

(Please mark the question answered if so and reward points to those who helped you)

Michael Baars - Comprehensive ICT Solutions (NL, Weert) (Remember to mark the post answered and reward points to those who helped you...)