Event banner
Event details
Will there be an option (assuming there isn't) to force endpoint to update the manufacturer drivers during or post OS install? Either by getting the drivers directly from the Dell website or by allowing us, on the admin side, to manually update those drivers.
Hardware vendors are supposed to now publish their drivers through Windows Update, using https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/. Though OEMs are allowed to inject drivers into their image, it is preferred that boot-start devices can use a generic Windows driver, that is later replaced through Windows Update. Drivers for new device are installed by Plug and Play, from Windows Update. If the driver has a user interface, it will automatically be installed and maintained by the Microsoft Store. As the vendor releases updates to their drivers, they are QA flighted through Parter Center and installed through Windows Update.
We have had fair success with Dell drivers. After a couple incidents, we have received a promise from support that we can hold them accountable if we find any new devices without drivers published in this way.
Where on the other hand, Lenovo refuses to publish their drivers through Windows Update and requires us to use their own update mechanisms.
Though my company is fine with drivers updating whenever hardware vendors make them available, some time ago, the Intune team announced they will have a mechanism for controlling when device drivers are made available. Haven't seen it yet.
Here are two links to bookmark for finding devices with drivers published in the modern way before purchasing them. Wish there was a more reliable way to make this determination. Maybe the community should create a list of PCs (and devices) that really are "Autopilot ready".
- https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/windows-certified-products-list
- https://www.catalog.update.microsoft.com/Home.aspx
We're relying on Windows Updates for Business (incl. drivers) for approx three years now
70% Lenovo, 30% Dell machines across the globe.
Vendor tools like Lenovo ThinkVantage and Dell Command Update aren't allowed due to its often vulnerabilities and they become removed if found.
Contribution
- Lenovo is contributing to WUfB, even BIOS and Firmware updates
We haven't bricked any device yet ... and we have up-to-date BIOS across Lenovo devices - Dell isn't contributing
Drivers
Lenovo and Dell devices are receiving the OEM drivers like Intel, Realtek, ELAN, Synaptics, NVidia via WUfB quite nicely. We neither need the vendor update tools nor their driver packages
NVidia surprised us twice in the past, they offered a driver through WU which caused black screen on some Dell CAD machines and rollback to an older driver was needed.
For NVidia scenario I'm desperately waiting for the public preview of the driver management via Intune portal (right now there is only the Microsoft Graph implementation)
Deployment service for driver updates public preview coming soon - Microsoft Tech Community
- Olaf, would you mind sharing more details about the specific models being deployed? I have started a shared spreadsheet for the community to share their experiences with "Autopilot Ready" PCs, Peripherals and Software. Maybe this will help admins find the rare gems and push our industry to get with the times. https://1drv.ms/x/s!AgG_boPR-xfWjN9i2Z_y_8ErM6t--A #AutopilotReady
We have agreement with Lenovo and Dell, onboarded those vendors to our tenant and they deliver the hash to Intune when device is shipped from factory.
So any of the ordered devices over the last approx. two years are Autopilot ready, meaning OOBE will point directly to our tenant and user logs in with work account. The rest is done by Intune and the configured Autopilot profiles.
The models need to have certain items in the bill of material like Autopilot registration, clean OS image (without bloatware). Of course this is charged with 5 to 15 USD per machine (I don't know the exact prices from vendors). At the end it is some kind of customize to order (CTO) model.Doesn't work with models directly purchased from the nearest electronic shop.
If we would have ordered the Lenovo Yoga from your spreadsheet through our channels then it would do the Autopilot well.The other angle of Autopilot ready is the re-installation due to failure (e.g. replaced SSD).
You can apply the vendors recovery image but this differs across models and not easy to handle by end users. Here seems https://www.osdeploy.com/ by David Segura the best approach as most of the part is dynamic (OS image, drivers, etc) and you just send 1GB pen drive to user and everything relies on his/her Internet connection. At the end you are at OOBE and start with your work account again.
Thank you for sharing your experience!
You are going to make our IBM Lenovo fans, who still love that form factor, very happy. Though... they have been the ones who have argued they MUST have the Lenovo updater re-packaged and installed. I wonder if your success has been with certain or new models only.As the Windows Compatible Products List is not cutting it, I have been considering creating a shared spreadsheet for the Autopilot community to share insights like this. Both the good and the bad. It would definitely help us find "Autopilot Ready" devices. And maybe it would put some positive pressure on companies to get with the times. Unless someone else wanted to take this on (hint-hint Microsoft), what types of things should such a spreadsheet track? Or is there a Wiki that might host this information and more?
Until Microsoft (or someone else) creates a better resource, I have started a spreadsheet to provide a knowledge base of PC, Peripheral and Software readiness for this Autopilot dream.
Please contribute any additions or updates.
cc Olaf_Thyssen
- Lenovo is contributing to WUfB, even BIOS and Firmware updates
