Is VMware OVA Supported for Windows Domain Member Servers?
Points of My Scenario:
1. I need to convert a Windows domain member server to OVA and deploy it on a second vCenter instance at a separate site
2. The second site is part of the same Windows domain (a Domain Controller is there)
QUESTION: What must I do to ensure the OVA-packaged Windows member server (i.e. domain-joined Windows server) works at the new location?
1. I need to convert a Windows domain member server to OVA and deploy it on a second vCenter instance at a separate site
2. The second site is part of the same Windows domain (a Domain Controller is there)
QUESTION: What must I do to ensure the OVA-packaged Windows member server (i.e. domain-joined Windows server) works at the new location?
QUESTION: What must I do to ensure the OVA-packaged Windows member server (i.e. domain-joined Windows server) works at the new location?
1. Shutdown, Power off the virtual machine.
2. Export to OVA (wait and be patient, can take 25-60 minutes to export).
3. Import at new site.
4. Power On.
5. Change internal networking if applicable.
Senior IT Specialist
Hi Andrew Hancock,
I asked my question poorly: please forgive me.
QUESTION: Should I be concerned about Windows SID (security identifier) when using VMware's OVA packaging? Will I have to do sysprep on the imported VM? Or would I have to un-join it from the domain and re-join it? Or is OVA packaging non-impacting to Windows SIDs?
With gratitude & anticipation,
Walt
I asked my question poorly: please forgive me.
QUESTION: Should I be concerned about Windows SID (security identifier) when using VMware's OVA packaging? Will I have to do sysprep on the imported VM? Or would I have to un-join it from the domain and re-join it? Or is OVA packaging non-impacting to Windows SIDs?
With gratitude & anticipation,
Walt