At 2X, our main concern is making your experience with our product the smoothest, simplest, and enjoyable whenever possible. We constantly work hard to improve our products and make them even faster, reliable, and easy to use. In this article, we take a look at the way the 2X Templates has been improved, and how the new settings and configuration can make it even easier to administer and deploy.
For those of you that are not familiar with the 2X Templates, it is basically a feature that allows you to automatically create and deploy Guest VMs whenever needed.
In simple words, you will only need to create a VM once and then you’ll be able to use it for all your users. Therefore, with the aid of 2X Templates you can better utilize host resources!
The simple steps to create a Template are the following:
- Create a Virtual machine, the way you want it to be for all/any specific user/s with your virtualization technology.
- Select that machine (which from now on we are going to refer to as the Guest) as the designated 2X Template.
- The Guest will be converted to a 2X Template.
- The Application console will then verify the presence of the agent on the Guest, and if not present, install it for you.
New guest clones are created on the fly for any user who has access to the published item. (I replaced a line) You also will be able to view the information about the clones created from the templates info.
So, what is so cool about it and how did 2X improved this feature?
With 2X ASXG, you will be now able to modify the Guest/s whenever needed, without the need of creating a new one every time. All you need to do is simply switch the template to Maintenance Mode (meaning that no cloning will be performed while the VM can be booted to change the system), apply all the changes you want, and once ready, switch the template back to normal mode. The great advantage of doing this is that no information will be lost, whatsoever, saving precious time to yourself and the company. Always keep in mind however that any changes on the Template will not be replicated on the cloned VMs previously created.