In most cases, end users are not required to manage the ISOs that are attached to the deployed virtual machine in the Surgient environment. After the virtual machine is torn down, the ISO will automatically be detached from the virtual machine. It appears like you have a use case that requires ISOs to be attached to virtual machines and then detach after installing the necessary software, perhaps not wanting the end users to access the software. BTW, in our 6.0 product, we have the ability to run post deployment actions against a virtual machine after it has been deployed. Post deployment actions are basically any executable or scripts you write that is uploaded to a deployed virtual machine and executed. You can utilize this in a manner of installing software, setting up personalizations in the virtual machine, etc...
A known way of detaching an ISO is from the vcsadmin command line. I know that you have use this in the past and is familiar with the usage. Again, I would just caution any actions or commands you do in the vcsadmin interface. The vcsadmin command that will help you is a command called: commandrun HOSTxyz attach-media. You can see the syntax of this command by running: commandshow attach-media
I have provide a documentation explaining how to attach and detach an ISO using the vcsadmin. It's a bit tricky, but can be done.
Please let me know if this helps.
Thanks,
Viloun