So, after scouring around, breaking things and several late nights at work, I've come up with a solution that works. Using Windows-based installation tools ensures that the proper boot information gets written right the first time in the way Microsoft intended, no matter whether you are imaging a Legacy or UEFI-style installation of Windows. There are other deployment tools out there for putting Windows on a Mac, but few are as flexible and modular as MDT-and things get even trickier in some ways with newer Macs that don't support Legacy booting, as their boot information is written to the EFI partition.
Several folks cite their LiteTouch Task Sequences failing with this error or that ever since they upgraded from 2010 to something more modern. Over the years-judging by the date of some of the posts I've seen on the topic-it seems that using MDT or SCCM to install BootCamp on a Mac en masse was more common in the past than it is now. So, you have a Windows Deployment Server and you'd like to use Microsoft Deployment Toolkit to image your Windows partitions on your dual-boot Macs. #Deploying BootCamp with DeployStudio & MDT/LiteTouch
0 kommentar(er)
