I am going to re-install my VC configuration to shift it to VMs. I wanted to double check what happens to the templates managed by VC when you re-install it/create a new VC server. I imagine that the templates will no longer be visible through the VI client connected to the host but will remain on the host that they where created on. When I connect the ESX server back to a VC server it will re-sync and I will be able to see the templates from the new VC.
Can some one please confirm this ?
Even if you'd not "see" your template anymore, you'd be able to re-register them.
Even if you'd not "see" your template anymore, you'd be able to re-register them.
You will have to add your templates back in your invetory of the new VC server. Templates should be removed from the host you have built them on.
I assume you mean 'should not' ?
Sorry about the typo. Yes you are corect the templates should not be removed. You just add them back into your invetory on the new VC server
Ok, I thought as much, just wanted to check before doing something stupid!
Just re-installed VC, how do I add the templates back in ?
Configuration > Storage ... right click on the datastore where your templates are and "Browse Datastore ...". Right click on the vmtx file, "Add to inventory".
Perfect, Thanks !
Hi
Can you help please? I have SCP'd a template file over to a new ESX3.0.1 host from an existing ESX3 host. When trying to add this template (.vmtx file) to the inventory using the VI Client wizard, I am prompted to supply a name but then I receive the following error :-
"The operation is not supported on the object"
The VI client is connected directly to the ESX server is this particualr case because we are having response difficulties between the VC2 sever and the ESX server (hence our SCPing the template over in the 1st place).
I have also tried using the vmware-cmd -s register method but that results in a Soap Error 1588...
Thanks
I am not sure why you are having the problem but before I added the templates the correct way I was creating a new VM, using the existing VMDK from the template and then converting the VM back to a template.
Ah.. interesting... I'll give it a shot... thanks