Vm provisiong using custom image

[#1]

"Hey Morpheus team,
I have uploaded my custom Windows Server image in the Library > Virtual Images section. I have also created a node type, layout, and instance type, and defined the image in the node type. However, it is not provisioning. How can I resolve this issue? Please guide me.

[cbunge]

If these exist in yoru vCenter, there is no need to directly upload any of these to Morpheus. Morpheus will inventory synced templates and make them consumable. Typically, you are selecting the VMDK as the deployment option.

[#3]

please guide how to upload my own custom windows server image and how to use it properly to create instance from that image . I have convert the vm to template using vmware workstation when i convert the vm to template i got 4 types of files
1 vmdk
2 iso
3 ovf
which one i should upload to Morpheus to create instance .

[#4]

i have followed the same procedure but when i create template of the vm from vmware i got three types of images first one is iso , second is vmdk and third is ovf which one should upload to Morpheus as virtual image and provision instance from this uploaded virtual image

i have created node type instance type and layout as well

[Ollie-Phillips]

The requirements for the templates can vary by cloud type. You may be able to find info to help in one of the getting started resources. For example this doc (for VMware) covers the requirements for the template, and the Morpheus Virtual image settings for Windows and Linux instance types.

https://docs.morpheusdata.com/en/latest/getting_started/guides/vmware_guide.html#prepping-an-image

There is also this detailed guide which is specific to VMware

https://docs.morpheusdata.com/en/latest/integration_guides/Clouds/vmware/vmware_templates.html?highlight=custom%20images#creating-a-morpheus-vmware-image

[#6]

Typically, there are three files exported from vCenter (.vmdk, .nvram, .ovf) that need to be imported if you’re using Morpheus to distribute Templates to different vCenters.

Sometimes an ISO file is also exported. This can happen if you forgot to unmount the ISO file from the VM in vCenter. Could you check if an ISO is mounted and unmount it before exporting?

As Chris mentioned, there is no need to export if you are using the template only on one and the same vCenter. If needed, I recommend using a Content Library that spans over multiple vCenters. Of course, this should only be done if it complies with firewall rules and security requirements.