I will not into how to do WUfB in this blog post. So when we have control over the updates in our Enterprise environment we also what some kind of control over the driver updates, and yes we what to update drivers on our devices. To get total control of what we are doing I create dynamic devices groups with each hardware model.
Assign it to the dynamic hardware model specific groups you need to control the driver updates for. First download the latest firmware and drivers for Surface devices :. You are commenting using your WordPress. You are commenting using your Google account. You are commenting using your Twitter account. You are commenting using your Facebook account. Notify me of new comments via email.
Notify me of new posts via email. This site uses Akismet to reduce spam. Learn how your comment data is processed. A few are worth calling out:. The hardware ecosystem for Windows devices comprises hundreds of partners who continuously build new drivers and deliver updates to existing ones.
All drivers must be certified by the Windows Hardware Dev Center and signed by Microsoft in order for Windows to install them, and most are also published to Windows Update. Microsoft enforces a robust publishing process that aims to grant only the highest quality drivers to Windows Update. Post-publishing rollout monitoring is used to find issues fast and mitigate them with the hardware partner who published the update.
Hardware components benefit from regular software updates, when available, to improve performance and interoperability with other components, and are often required for new OS versions to unlock new functionality. The IT admins we frequently meet with mention how difficult it is to identify the right drivers required for their devices. Windows Update does this automatically by evaluating the information sent by a device when it scans the service and identifying drivers on the service that are better than those already installed on the device.
A combination of factors like driver version, driver date, and targeting information such as Hardware ID and Computer Hardware ID is used to inform the selection process. Microsoft continuously collaborates closely with the hardware ecosystem to bring more and eventually all driver updates to Windows Update.
Firmware and hardware issues are one of the most active areas of enterprise security. We are all familiar with recent incidents that impacted end-users and enterprises around the globe in the past few years. Hackers take advantage of increasingly sophisticated attacks that are often mitigated with drivers. However, the complexity of driver servicing and the prevalence of parallel servicing practices for drivers and other Windows updates generate additional friction for IHVs, OEMs, and enterprises at a time when mitigations are most urgent.
Investments in ongoing servicing for operability optimization and better functionality also set you up for success when the next security incident hits. The goal was to learn how you think about drivers, how you make servicing decisions, and how you act on these decisions. Intune admins, who have adopted cloud servicing and point their devices to scan Windows Update, can choose to accept drivers whenever they become available on the service or instruct Windows Update never to offer these updates.
Admins set a policy in Intune that is, in turn, set on each device. The policy choice is communicated to the Windows Update service as part of the daily scan from the device.
Windows Update will only offer drivers it determines to be better than what is on a device only if the policy to allow driver updates stipulates it. Configuration Manager customers must rely on OEM updaters and other processes to address their driver servicing needs. This means that admins lack the same level of control over deployments they are used to for all other updates from WSUS. Based on feedback, IT admins need help to learn when updates are available for devices, which ones should be deployed to which devices, and support for the servicing mechanism that is already in place for other Windows updates.
Usually, Configuration Manager admins delay driver servicing until forced, generally during OS upgrades. These tend to be infrequent, so driver servicing is also infrequent with all the benefits of ongoing servicing forgone. However, some admins feel reluctant to move all their Windows updates management to Windows Update in one fell swoop. They want to connect to Windows Update for drivers only, while evaluating a gradual move to Windows Update for all other Windows update when the time is right.
Sneak peek: this co-management capability is included in what we are announcing today! Keep reading. This approach, when adopted, means that whenever a driver becomes available in Windows Update, it will be offered to scanning devices with no notice to admins.
Since the hardware ecosystem publishes drivers on an irregular cadence, there is also no control over the timing of such deployments. For more information, see Viewing Hidden Devices.
Device Manager provides detailed information in the Properties dialog for each device. Select and hold or right-click the name of the device, and then select Properties. The General , Driver , Details , and Events tabs contain information that can be useful when you debug errors.
For more information, see Device Manager Details Tab. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info.
0コメント