![]() This is one component I've found does not install properly with the older version. ![]() Remove AppleBluetoothBroadcomInstaller64.exe from the BC4 package(found in Drivers\Apple\圆4), change its name to AppleBluetoothInstaller64.exe and overwrite the exe in the BC5 driver package. We'll be using a Bootcamp 5 driver package and a Bluetooth driver from this BootCamp 4 driver package. This is by no means completely airtight, however I've had success so far in seeing most models from 2009 onwards be well-supported using this method. I'm going to detail both of these methods. ![]() Or maybe you're still installing Windows 7 for some reason and need a way of installing those packages quickly from a local repo that resides on your MDT server, for maximum deployment speed. If you're crazy like me, you might want to do things like attempt to support Windows 10 outside of Apple's "supported models" matrix by installing legacy BootCamp drivers, and hodgepodging them together to make sure system devices work properly. If you're installing Windows 10 on 2012 or newer Mac hardware, the above section will work fine-Brigadier does a great job of differentiating hardware and grabbing the appropriate package. Immediately after this, add another "Restart Computer" step, as the BC drivers will want that-I have had cases of actually using the built-in 'Restart Now' button on the BootCamp driver installer borking the Windows install-so generally it's better to automate these things.Īt this point you're done with Apple-specific hurdles, you're executing your driver installers automatically, and all that remains are any additional customizations you want to make to your deployment. This will store the drivers in our C:\BootCamp directory so that if the end-user has any hardware issues(or some drivers fail to install, which can happen), the drivers can be manually repaired by re-running the setup exe. Fill it out like this: C:\BootCamp\brigadier.exe -install -keep-files -output-dir=C:\BootCamp Next we want to add another Run Command Line step, immediately after, called "Run Brigadier". This will copy all files within the specified folder and create a destination folder called "BootCamp" on the target machine's root drive. Mine looks like this: xcopy.exe "?ployroot%\BootCamp\Brigadier\*.*" "c:\BootCamp" /Q /H /E /I /Y Fill out the Command line field in the Properties pane with an xcopycommand, referencing your folder where Brigadier is stored. Create a "Run Command Line" item inside and name it "Copy Brigadier". I use a BootCamp folder to hold various packages within their own subfolders, like so: ?ployroot%\BootCamp\BrigadierĬreate a new Group/Folder called BootCamp in the State Restore phase of your Task Sequence. I've found that Brigadier works best with MDT when it is copied to the local machine-I've had cases of it not executing properly/failing the Task Sequence when run as an Application or from the network share.ĭownload Brigadier and place it in a folder in the root of your deployment share. It's even possible to point Brigadier at an internally hosted mirror of Apple's Software Update repositories, hosted with something like Reposado, to reduce the amount of outbound network traffic and increase the speed of driver downloads.įor Windows 7 it may be more efficient to actually download specific bootcamp driver packages and poll model info to install the BC drivers directly with MDT, as that is the fastest way of getting our files onto client machines.įor newer versions of Windows, Apple has shifted from making the BootCamp driver packages directly available from a webpage, and although you can download them with BootCamp Assistant or Brigadier, it's difficult to know which drivers will work for which model.īrigadier automates this for us anyway, so generally going forward, the best solution is to use it in tandem with an internally hosted repository(although it works quite well without, just not quite as speedy). One of the best is using Brigadier, a great tool made by Tim Sutton that automates the download and installation of Apple BootCamp Drivers from Apple's own software repositories.īrigadier polls the local machine for its model info, and grabs the appropriate BootCamp software package, just like BootCamp Assistant on OSX, but in an automate-able fashion that resides entirely in Windows, so there's no need to monkey around with copying drivers to USB keys and then back again. It's during this we can do important customizations of the live OS, and pretty much automate anything that you want, install additional drivers, packages, scripts etc.Īnyway, we're going to be installing BootCamp drivers. ![]() Once we're booted into Windows proper, the computer enters what's known as the State Restore Phase of the Task Sequence. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |