While you already have Microsoft® Windows Server® Update Services (WSUS) in your IT environment for deploying Microsoft product updates to your Windows workstations, have you thought about patching non-Microsoft software that you run on your enterprise computers? These non-Microsoft software products, such as Oracle, Java®, and Adobe Reader®, may expose your corporate environment to vulnerability exploits when left unpatched.
The question is: How do you ensure timely and automated patching of non-Microsoft, third-party software with just WSUS to keep your network and IT infrastructure protected from unpatched software vulnerability?
SolarWinds® Patch Manager extends the capabilities of Microsoft WSUS by offering a powerful solution for deploying, managing, and reporting on Microsoft and third-party patches on tens of thousands of workstations and servers across your enterprise.
Here are the top 13 reasons why you need to have SolarWinds Patch Manager added to your WSUS deployment.
|#||Reason||Microsoft WSUS||SolarWinds Patch Manager|
|1||Patching Microsoft Software Updates||Yes||Yes – Via WSUS or SCCM|
|2||Patching Non-Microsoft third-party Software Updates||No||Yes - See a list of supported third-party products.|
|3||Visibility into Application Inventory||Limited Hardware Inventory; No Software Inventory||Yes – Microsoft & other third-party applications, hardware inventory, disk space & other metrics|
|5||Reporting Visibility into Patched & Unpatched Systems and Software||Limited||Yes – Granular Visibility Custom reporting requires no SQL programming or scripting|
|8||Notification of Failed Updates||Limited – Does not provide information on why the update failed||Yes – Provides information via the client log file as to why the update failed.|
|9||Patch Scheduling||Limited – Basic patch scheduling such as choosing a particular hour of the day, and optionally a single day of the week, with the hope the target machine is actually powered on at that time||Yes – Push patches at discrete times to accommodate different time zones and network impacts of patching large numbers of endpoints.|
|10||Wake-on LAN for booting target systems for patch management||No||Yes|
|11||Third-party Pre-built & Tested Packages||No||Yes – For many common applications|
|12||Custom Package Creation||No||Wizard driven – Package Creation Wizard for complex before and after deployment scenarios|
|13||Client Health Diagnosis & Remediation||No||Yes – Repair WMI, WUAgent, and Configuration Manager Agent|
SolarWinds Patch Manager maximizes your investment in Microsoft WSUS and allows you to patch both Microsoft and non-Microsoft third-party applications with more visibility, control, and reporting from the simplicity of a single central intuitive interface.
Patch Manager gives you key management capabilities that help you simplify the entire patch management process from patch notification, to import/synchronization, to publishing, approvals, deployment, scheduling, reboots, and more.
WSUS lacks the ability to patch applications outside of Microsoft products.
WSUS is an excellent tool, but it lacks the ability to effectively schedule patches and report on patch status and inventory.
The time between the discovery of an operating system or application vulnerability and the emergence of an exploit is decreasing.