We successfully use a handful of imaging, scripting, and partitioning methods to automate deployment, backup, and restoration of hundreds of PCs. Lately, due to a combination of some twichy software we really can't throw overboard (due to our $$$ of exposure with it and the things it *DOES* do well enough...) changing drive technologies and some more finicky BIOS/ATA Controller/HD combos, some post-imaging system results are twitchy. Specifically, a system being reimaged may pull down the image fine, but the resulting partition table lists no active partition (yea, that's kind of a problem!). Once we manually enter into FDISK and set it to active, all's well. But this wastes a lot of time when the systems could otherwise be boxed by chimps and sent off as "like new" with no need for further IT administration.
We use automated FDISK scripts and have been for some time; they are great for wiping the MBR out, deleting partiions, and particularly for restoring OEM/Diagnostics partitions and essentially ensuring that no matter what wizardry users or over-caffeinated sysadmins have performed on a PC during its tenure, that all system are restored to their original state prior to returing to the leasing agents. However, the one thing we have been having a hard time determining is how to script FDISK to set a given partition to ACTIVE. I am hoping this is possible. I am not opposed to using something like FreeFDISK or AEFDISK, but if this is feasible with FDISK, I'd rather just stick with that since we're already using it with great success.
Here is a thread that helped us get going with that originally:
Here is a page that lists some helpful FDISK scripting/FDISK Batch file basics: