Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've red this article published by VMware and this blog post and neither actually explain what a template is. Why would one bother making and using a template, why not keep cloning a base image?

share|improve this question
up vote 1 down vote accepted

That's basically what a template is, a base image that doesn't change much. Basically, marking a VM as a template just prevents it from booting up. Think of it as your "gold" image that you can deploy multiple copies from.

You can always convert back to a VM to make changes, but templates make management a little bit easier.

share|improve this answer
Oh ok so the difference really is small, and in a sense is nontechnical because now everyone knows not to change it and wont get changed by accident? – Celeritas Jul 19 '13 at 17:48
Basically. A clone makes an exact copy of a VM at the moment the clone occurs. A template is a point-in-time image that doesn't change. – Jim G. Jul 19 '13 at 18:24

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .