![]() ![]() #AutoIt3Wrapper_Res_Comment=AutoIt installer to automate dialog boxes The script is stored in SkyDrive and replicated below so you can take a look (note the location of the Boot Camp install files is C:\DRIVERS) #Region **** Directives created by AutoIt3Wrapper_GUI **** Unfortunately time was against us to test this out, maybe one for later on. The only issue I’ve had is it doesn’t seem to grab the final OK button to restart, seems like the AutoIT program times out and closes before the install process completes but I reckon a mandatory sleep of say, 10 minutes would do the job as I’ve included in the script snippet below. I found it needs the little delay initially to allow for the installer GUI to fully load (especially on 5400rpm HDD Mac Minis) but then picks up and does the job. That seemed far too much like hard work trawling through each Mac model and testing to make sure we didn’t miss anything so set about finding a plan B that could make use of the Apple installer.Īs always our good friend AutoIT comes up trumps, quite a simple one in the end really using a mixture of the Window Info tool (AU3Info.exe) and sending the correct sequence of keystrokes to whizz through the installer. Googling revealed that the Boot Camp software itself seems to be in MSI \ MSP format but drivers need to be extracted manually and installed by either DPInst or sysprep. ![]() The only downside was no built-in silent install switch (knew it was going too well!) so I set about looking at other options. ![]() I’d never seen the Boot Camp support software before so was pleasantly surprised that it seems to have been made with a bit of common sense (unlike some Windows-based Apple software I can think of!) and already has enough intelligence to install drivers for any Mac hardware it comes across via a single package. As with our PC imaging process the drivers need to go on before anything else in order to get a working NIC and needs to be hardware independent. This meant we’d have to build the base image again for the Macs (not a biggie as it’s very basic) but the question arose on how to automate the Boot Camp support software and drivers, followed by the usual ZCM scripts and Bundles. With that out the window our resident Mac expert Tristan Revell recommended sticking with the DeployStudio method we used successfully last year. Initially we did some brief experiments to see if ZCM could do the trick but that soon failed due to lack of PXE support on Macs (tried iPXE from CD with no success) plus the fact ZCM can’t process any sort of Mac file system. Having cracked the PC side of our Summer imaging project thoughts then turned to Macs and upgrading our existing dual-boot systems to match the nice shiny Windows 7 image deployed elsewhere. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |