Skip to main content

Hello All,



This is a very unique question but I'm hoping that someone else has encountered this annoyance.
Our organization owns 40 MacBook Pros - 11.1 (Late 2013), each of these laptops needs to be setup to dual-boot both Mac and Windows. Pretty standard right?



After imaging, I'm left with two working partitions and a perfect Mac/ Windows dual boot laptop except...
BootCamp drivers 5.1.5640 and our specific model of MacBook Pro (11.1, Late 2013) apply driver settings for each new user.



Our domain users (students) need to login to these machines in less than a minute. The combination of required bootcamp drivers and our MacBooks make it so that each 'new' Windows user must wait about 15 mins before they are prompted to reboot and then may finally login (the process applies drivers in the background per each new user). Our students can not spend 1/3 of the time in class waiting for BootCamp to configure Windows drivers and settings.



Uninstalling the BootCamp Service allows domain users to login in under 20 seconds but the trackpad drivers are not applied. As such, students can not right-click or scroll using the trackpad. I can remap one of the command keys to the Windows application key which would give students a "right-click key" but this is far from ideal.



Has anyone else encountered this very specific issue? All of our other model MacBooks and iMacs have working BootCamp drivers that apply to every user on first install - it looks like BootCamp 5.1.5640 drivers apply to each user on first login which is very time consuming.



Thanks,
Joe

Just to gather some info that may help someone else who tries to comment ( I haven't dealt with BootCamp in a while), but how did you create the Windows image?



How is it being deployed/restored to the Mac?



How are you installing the drivers (manually, through sys prep answer files, or something else)?



Also, what version of Windows?



It could be that Apple introduced something in the new drivers that cause it to re-install for each new user, but that doesn't sound right. Never heard of drivers behave in that manner.

Same from me unfortunately. I was installing dual boot at most schools I went to a few years ago. These days it doesn't come up as a requirement.



The only other workaround I can think of would be to try slightly different versions of the drivers. You might find there is a earlier or newer version of the drivers that works correctly.

@bpavlov I've actually ran into this issue before using two different methods of deployment, manual using the bootcamp utility and using WinClone and Casper Imaging. Drivers are either installed manually or using Tim Sutton's Brigadier tool on first logon (sysprep scripting)



This affects both Windows 7 and Windows 8.1 - Windows 7 displays the BootCamp driver install window and Windows 8 hides it behind the fancy color window which reads "almost ready".



It's odd, all of our older and newer Apple computers install BootCamp drivers on the entire system, no need to configure per user.



@davidacland I wish I could say the same, the Windows image is hardly used. I'm attempting to install older version of BootCamp now.

Given the time remaining for deployment, I've settled on using AutoHotkey and removing the bootcamp service post configuration.



Removing the bootcamp service allows new domain users to login quickly. Of course removing the bootcamp service also disables bootcamp drivers from configuring upon logon.



We've setup a AutoHotkey script to run on logon which enables control+click to act as a right-click in the system. Users are notified prior to login about the change in operation. This is hardly the ideal solution, Trackpad++ looks like a viable option but the required updates seem problematic. I'd like to see an update to the 5.1.5640 BootCamp drivers but I think Apple would have little incentive to develop a fix.

Reply


Terms & ConditionsCookie settings