|Brian Stempin on 8 Feb 2009 12:51:12 -0800|
Correct -- Windows XP Pro will not deactivate due to hardware changes (sorry for the now/not typo).
If the only things that you are syncing between the machines are documents, source code, etc, then your job will be pretty easy -- you can use something like Microsoft SyncToy (http://en.wikipedia.org/wiki/SyncToy).
If your situation is more complicated (ie, replicating software installs, etc), then your job becomes pretty impossible. Ripping a physical machine into a virtual one forces the newly created VM to have a different UUID than its clone. If you're running AD, this will force you to change host names and re-join the domain. If you're not running AD, you'll still most likely have to change hostnames.
This causes problems becuase it changes the Windows registry. That means that if you install software on one machine, you can't simply copy over the entire registry (or a diff) because some things are suppsed to be different.
To sum it up -- this is a good backup mechanism, but the ability to bounce back-and-forth between the 2 machines is not a problem that I can think of a solution for.
On Sun, Feb 8, 2009 at 3:32 PM, Steven Phillips <email@example.com> wrote:
I understood the original poster wanted to use his installed WinXP as both a VM and a native os alternately. My understanding was that he wanted to bounce between using the same install as a vm and as a "boot into" os. The problem was making any changes persistant, whether made in the vm or in the native "boot into".
___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug