brigadier
brigadier copied to clipboard
iMac 15.1 (5k retina) not installing the AMD graphics drivers for Win7 Bootcamp installation
Hi Tim, We have used Brigadier in our Organization for a couple of years to run in the firstruncommands section of an OOBE windows 7 Boot Camp image we created and it generally downloads all windows 7 drivers fine. However, we have recently bootcamped (windows 7 64 bit installation) some 5k iMacs (iMac15,1 models) and our techs are reporting that it installs all drivers fine, except the AMD vga drivers. I am told (as I have not personally had a chance to test myself) that It does not give any indication of error and actually appears to all run successfully but no specific AMD drivers are installed. We tried the latest 0.2.2 Brigadier exe but it did not resolve the issue. Any ideas of what may be happening?
Many Thanks, Alan Martyn (UAL IT Dept. London)
Hello Alan. Been a while.
Has James been enabling all the bootcamp packages on your reposado sus? Unless you changed how you're doing the brigadier builds then it's still pointing at that.
Hi Richard, Nice to speak to you again and hope you are doing well! I was under the impression that when we run Brigadier.exe in windows, it just goes out to Apple for bootcamp packages, there is no way to point it to our internal apple sus? BTW James/Callum have enabled latest reposado bootcamp packages anyway.
Hi,
There was one version where it did point to the SUS. No idea if you're still using that though. Assuming you're not, best work around is to use the current unattend.xml file to manually install the drivers, which you'll have to manually put on the system.
Obviously you'll have to experiment with the switches to make it do a quiet unattended install. You'll also need to get the latest boot camp installer to extract the ATI drivers.
Don't worry about it installing on non ATI machines. I've seen boot camp installing Nvidia drivers on those, doesn't seem to make a difference.
That's your workaround until Tim having time to investigate.
On 19 Jun 2015, at 12:30, clientconfig [email protected] wrote:
Hi Richard, Nice to speak to you again and hope you are doing well! I was under the impression that when we run Brigadier.exe in windows, it just goes out to Apple for bootcamp packages, there is no way to point it to our internal apple sus? BTW James/Callum have enabled latest reposado bootcamp packages anyway.
— Reply to this email directly or view it on GitHub.
Since I might be getting a 5K iMac soon-ish, I may actually have a chance to test this. There are definitely a few cases where the installation of the MSI via msiexec (with the options we've been using in Brigadier) has an issue with a package or two, and unfortunately I'm far from knowledgeable about how to debug MSI installation issues.
That said, assuming I can give this a go on real hardware, stay tuned...
Thanks Tim.
Hi,
We've just found this occurring with the latest 13" MacBook Pro's (12,3) as well.
What switches are you using for the ATi drivers? In the past I eventually found the unholy combination of "Setup.exe /UNATTENDED_INSTALL /FORCE_HIDE_FIRST_RUN /AUTOACCEPT /FORCE_CLOSE_WHEN_DONE /ON_REBOOT_MESSAGE:NO" would work. Not sure if that's still the case, but should be a good starting point.
Not sure if this is still an issue or not, but I've had better luck creating a scheduled task to run as the SYSTEM account to mimic the way Bootcamp Assistant works. I've found the install of Bootcamp Services to be much more reliable and not hang since switching to this method. Might be something to test out.