Hi, Adam --

I ran into this once when trying to administratively update an image
created by a client -- I could only fork it and create a new image set, not
"update."

Is it possible that the account you're using is not the "owner" of the
original image (hence you cannot update it / create a revision, but can
only create a new image)?  Check your permissions to make sure that the
admin account (or whatever account you're using) has permissions to update
images owned by... whomever owns your base image.

Regards,
Mike
--
*Mike Haudenschild*
Education Systems Manager
Longsight Group
(740) 599-5005 x809
m...@longsight.com
www.longsight.com



On Fri, Jun 8, 2012 at 12:12 PM, Hechler, Adam <hec...@rpi.edu> wrote:

>  Happy Friday everyone,****
>
> ** **
>
> I am trying to update an image (Windows XP) but the “Update Image” radio
> button is greyed out (step 5 below).****
>
> ** **
>
> I started with a Windows XP vm and captured it to create a Base Image.****
>
> Then I created a new image from that Base.  ****
>
> I then created another new image from that image. (I was building on
> previous software installs but it’s for a different set of users hence the
> two different images).****
>
> ** **
>
> Any quick tips for what I might be doing wrong?****
>
> ** **
>
> ** **
>
> I am following these steps: ****
>
> ** **
>
> 1. Create an Imaging Reservation using an existing image****
>
> 2. Load the image and make the desired changes to the image****
>
> 3. Disconnect from the image and proceed to the Current Reservations page*
> ***
>
> 4. Click on the Create Image button****
>
> 5. Choose whether to create a new image or update an existing image****
>
> 6. Accept the Installer Agreement****
>
> 7. Fill in the image name and optional image notes****
>
> 8. Start the image creation process****
>
> ** **
>
> Thanks,****
>
> Adam Hechler****
>
>   Senior Analyst /****
>
>     PC Systems Administrator****
>
>       hec...@rpi.edu****
>
>         (860) 548-2446****
>
>            Rensselaer at Hartford****
>
> ** **
>
> ** **
>
> ** **
>

Reply via email to