Also, a mismatch of network drivers and firmware on network hardware, such as switches, can cause issues.

Potential problems include loss of connectivity during the upgrade. You should consider additional precautions the following types of driver categories, due to the impact on the end users: You might want to consider a long-term servicing channel approach and deploy driver updates every two or three years on these machines. Examples of these devices include factory machines and computers in health services. Machines that should not receive continuous servicing updates.

Microsoft Office applications and web-based services are the most important programs on these machines and To help with driver management, you should divide your machines into different categories: It's a reasonable practice to keep tight control of driver versions on devices, but this can lead to outdated drivers on many devices, which can open the organization to vulnerabilities or cause stability problems on the machine. Many times, the drivers are only updated when IT identifies critical security or stability issues. But, in my experience, most organizations fail when it comes to driver servicing once the device is in the user's hands. The latest versions of drivers are often installed during operating system deployment. In the enterprise, driver installation occurs during two phases of the lifecycle of a machine: during the bare-metal installations via driver packages in an SCCM task sequence and when a machine is up and running. How are drivers typically deployed and managed with SCCM? This article will focus on using HP tools, but the main concepts of driver management are generally the same among vendor utilities. Most hardware vendors supply their tools to complement SCCM's out-of-the-box features for driver management.

Plantronics drivers windows 10 hp