By default we will capture and deploy all partitions that exist on a drive with imagew v2.0.
so you dont need to do anything to make this work
Just tried this and it did do that successfully. The follow-up problem though is that when I run sysprep on the primary partition (the x86 one) so that LanDesk will then properly name the computer and setup the LanDesk client, it blows away the entire boot.ini file and messes up the entire dual boot process. Is there any way around that part of the process to fix it?
You could just overwite the boot.ini file again at the end of the process with the one you want it to use. That way LANDesk gets what it wants and so do you.
Mark Star - MarXtar LANDesk Enhancements
Home of Power State Notifier & Wake-On-WAN for LANDesk
New Updated Power State Notifier Pro!