Hello Experts,
Do we have any documentation or instructions for preparing Windows images for Nutanix Cloud?
I am facing some issues that Morpheus didn’t apply hostname, create user accounts while VM Network uses DHCP.
Thanks,
Aung
Hello Experts,
Do we have any documentation or instructions for preparing Windows images for Nutanix Cloud?
I am facing some issues that Morpheus didn’t apply hostname, create user accounts while VM Network uses DHCP.
Thanks,
Aung
Hi Aung,
Here’s a document that walks you through creating Windows 2019 and Ubuntu 20.04 templates in Nutanix.
Create OS templates in Nutanix
Let us know if you still have any issues.
Thanks
Deepti
Hello @dgaharwar,
Thank you so much for sharing.
I tried following the document. However, Morpheus didn’t create user account and apply hostname.
In the environment, I am using Prism Central Cloud Plugin and converted template at Prism Central console by using GUI method.
This is provisioned VM state in Prism Central Console.
Thanks,
Aung
Hi,
we already followed the instructions but still hostname and IP address didnt apply to the provisioned VM. is there any reason at all??
in my case, i use OVF template from subscribed Content Library.
For the first, I believe the latest Nutanix plugin solves issues with Windows provisioning. I’m unsure if you were still stuck on that @aungkyawthu
@Azizan are you talking about VMware provisioing (OVF + content library)? Windows? Is the template sysprepped and shutdown (sysprep.exe /generalize /shutdown /oobe), or does it need to be sysprepped on creation?
@cbunge Yes, it is already resolved.
@cbunge Yes its VMware Windows OVF template on content library (local and subscribed). it needs to be sysprepped after creation. strangely when i use VM Template format in content library, the hostname and IP can get changed after creation, but not OVF. is there limitation to OVF templates?
i see on Morpheus 7 have this new update on VMware OVF properties… will this fix my problem?
Edit: after i update the Template with the Monthly cumulative patch, upgrade VMware tools and convert it back to VM Template and upload as OVF in the Content Library, the hostname and IP is not being passed to a new VM deployment. This is what i observed.