Hi,
Here is a synario we have a VM running on Virtual Box 4.1.18 r78361 with the guest being Windows 2000 workstation.
Current Config: Host Windows 7
Virtual Box: 4.1.18-78361 running Windows 2000 Client that is a AD domain member.
AD Configuration: Windows SBS 2008 (Build 6002: Service Pack 2)
Domain and Forest Level: Windows Server 2003
Target Platform: Windows 10 Pro (new machine)
Virtual Box: 6.0.8
Steps to migrate:
Do an Appliance Export from old machine.
Import to new machine.
Remove Windows 2000 Guest from Original Machine (only migrated one will be used).
Concerns:
SIDs: Am I going to have an issue with Virtual Box changing the SID on the Windows 2000 guest and not being able to log in.
Any way to preserve this?
New Version: Any issues with bringing the OVA into the new version of Virtual Box. Any additional steps I need to do.
Thanks,
Ward
Virtual Box Migration Synario - AD Machine SID
-
- Site Moderator
- Posts: 39156
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Virtual Box Migration Synario - AD Machine SID
Howto: Move a VM. Summary: there's no reason to use "export appliance" unless the target is a different VM app such as VMWare. Simply copying the VM folder retains all the VM UUIDs, hence this is also how you would back up a VM. Cloning or exporting will change them all.
p.s. My OCD is itching, so, I'm forced to mention that the word is "scenario".
p.s. My OCD is itching, so, I'm forced to mention that the word is "scenario".
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Virtual Box Migration Synario - AD Machine SID
Virtualbox also does not know or alter what happens in the guest OS's data. So, no, moving the guest to a different host will leave you exactly the same guest SIDs and all other guest data.