When evaluating Patch Management, what aspect do you think is the most important to look for?

Ariel Lindenfeld - PeerSpot reviewer
  • 1
  • 17
PeerSpot user

2 Answers

Ravi Khanchandani - PeerSpot reviewer
Top 5Leaderboard
Dec 9, 2021

1. Visibility of Patching requirements for the entire environment - desktops, laptops, servers - physical or virtual, VM hosts.

2. Distributed processing for identification of patches at each endpoint, instead of a scan-based approach. A scan-based approach may load the network and/or endpoint plus will not be real-time. If each client can look up a central repository and identify its own patch requirements, it will reduce the burden on the server.

3. Endpoints are pulling patches, instead of the central server pushing the patches. This will ensure a lean mean central server architecture.

4. Good patch compliance reports that stand the test of auditors - internal, external and regulatory authorities.

Search for a product comparison in Patch Management
May 21, 2020

Up to date - near real-time reporting from the devices. A solution that does a SCAN (when you have a large number of devices), simply fails.

Find out what your peers are saying about Microsoft, HCLTech, Kaseya and others in Patch Management. Updated: February 2024.
757,198 professionals have used our research since 2012.
Patch Management
What is a patch management process? Patch management is the process of acquiring, testing, and installing many patches (code modifications) on current applications and software tools on a computer.
Download Patch Management ReportRead more

Patch Management experts

AANKITGUPTAA - PeerSpot reviewer
Sachin Vinay - PeerSpot reviewer
Hussein Taha - PeerSpot reviewer
VivekSaini - PeerSpot reviewer
Mario Del Toro - PeerSpot reviewer
BENDER BENEDICT - PeerSpot reviewer
OğuzKalaycı - PeerSpot reviewer
Gaurav Chandola - PeerSpot reviewer