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?
waltforbesSenior IT SpecialistAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
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.
waltforbesSenior IT SpecialistAuthor Commented:
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
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
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)

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

waltforbesSenior IT SpecialistAuthor Commented:
Hi Andrew,

Your answer is most wonderfully clear, definitive - and supremely reassuring. You make the world a better place, sir! :-)
I submit all the thanks to you I can muster!

All gratitude,
Walt
waltforbesSenior IT SpecialistAuthor Commented:
Hi Andrew, I am very grateful for your clear advice and guidance. You rock!
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
not a problem!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.