We have a wierd issue that when deploying a VM from a template it doesnt appear to create a new vmdk, rather the new machine seems to almost be writing changes to the new vmdk but uses everything from the old one, and then when you delete the template you shaft every vm that was deployed from that template, Im sure it never used to be like this..
Any suggestions as to why this is happening??
David
maybe this will be helpful?
That seems to fit, however It was doing it before without clicking edit hardware which is strange, we have since however just started upgrading from esx to vsphere, so the vcenter server has just been upgraded to the new version, so I wonder if this has adressed the issue I was previously seeing.
David