P2V Migration Toolkit components - what’s going on behind the scenes part 2?

Sorry I’m a bit late in posting this, but as promised in the previous post. Here is part two.

The table shown below lists the genericized steps of a task sequence created by P2V Migration Toolkit. The main thing to note, that isn’t reflected in this table, is the inherent failsafe built in to the task sequence in that if any of the virtualizations steps fail (non-zero return code), the task sequence will exit. This is designed to ensure that, for any reason, the physical-to-virtual migration was not successful the task sequence will not continue on with the re-installation of the operating system.