Found out the issue. The problem was that the drive was wiped on the machine, (some bad page navigation triggered the link ?node=host&sub=deploy&id=32&type=19 instead of ?node=host&sub=deploy&id=32&type=1 which is a full disk wipe. Note: Even though the Wipe Full Disk wasn’t visible, it was a callable and listed link on the Basic Task page.
So the error presented was due to the partition on the computer being zeroed out and not of the image.
The capture was successful, (only listed Partition 1 to be captured), as I would expect.
Some things to improve the process.
A remote wipe of the disk seems to easy to do, especially when the image Captured is only of one partition.
The error message presented can be less cryptic… maybe a listing of the expected partition table and the existing partition table and a suggestion on where and what to check would help, (currently we only dump the command used and expect the user to figure out what to do next).
I would like to see an ability to check the image integrity, (some checks to indicate if the image is corrupt or not). Not helpful in my case but prevents people from spinning their wheels.
Overall, @Sebastian-Roth thanks for your quick reply and assistance.