In an automated image (Ivanti Automation) process I create a new vDisk of a VM from a base snapshot (snapshot 1).
Then some applications are installed and another snapshot of the VM is made (snapshot2 ).
To then proceed with a custom installation, I resize the disk and take another snapshot (snapshot 3). That all goes fine, but when I want to go back to snapshot 2, the UUID of the disk has changed compared to snapshot 1 and my scripts that deal with commands for the disk no longer work.
Does anyone know if you can leave the UUID fixed? Or how to read the UUID from a disk and put it in a parameter?
Question
Marcel Zunnebeld
Hello,
In an automated image (Ivanti Automation) process I create a new vDisk of a VM from a base snapshot (snapshot 1).
Then some applications are installed and another snapshot of the VM is made (snapshot2 ).
To then proceed with a custom installation, I resize the disk and take another snapshot (snapshot 3). That all goes fine, but when I want to go back to snapshot 2, the UUID of the disk has changed compared to snapshot 1 and my scripts that deal with commands for the disk no longer work.
Does anyone know if you can leave the UUID fixed? Or how to read the UUID from a disk and put it in a parameter?
Thanks in advance!
Link to comment
9 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now