Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
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?
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
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.
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
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?
You don't need to Sysprep, remove from domain, because all you are doing is POWERING OFF THE VM, Exporting the VM, Importing the VM, POWERING ON THE VM!
Why do you need to remove from domain, or sysprep - you don't!
Stop over complicating it.
Just Power off, Export and Import - Simple - DONE!
Exporting and Importing is just a COPY!
(just do not power on the original VM, delete it after importing to new site)
Premium Content
You need an Expert Office subscription to comment.Start Free Trial