• Describe three tools that are available to network and server administrators to ensure that system patches and data backups are occurring effectively.
• Describe important things to consider when deploying system patches.

 

Describe three tools that are available to networks and server administrators to ensure that

system patches and data backups are occurring effectively.

Step-by-step explanation

Describe three tools that are available to networks and server administrators to ensure that

system patches and data backups are occurring effectively.

SolarWinds Patch Manager: Patch Manager (PM), the award-winning solution from

SolarWinds, is well rounded and a breeze to work with In addition to Microsoft patching,

SolarWinds PM provides support for a wide range of third-party applications, simplifying

and centralizing the whole patch process, from downloading to publishing to patching.

SolarWinds PM can automatically patch systems based on custom schedules by integrating

with WSUS and the Microsoft update agent (Midtrapanon, & Wills, 2019). No issue, as

SolarWinds Patch Manager integrates with SCCM cleanly, adding value adds such as on-

demand patching, filtered views, updates, and more to your installation. Using a simple point-

and-click wizard to build personalized packages.

LANDesk Patch Manager: Among the systems and asset management software vendors,

LANDesk is well known. One part in the suite of products provided by the company is

LANDesk Patch Manager. As an agent-based install, Patch Manager is most powerful, giving

you deep visibility into our network. In a standalone mode or as an add-on to the LANDesk

Management Package, LANDesk Patch Manager can be deployed, providing seamless

integration for complete systems and asset management, ticketing and more (Kansal, Kapur, &

Sachdeva, 2019).

 Shavlik: For Patch Management, Shavlik has two offerings: Empower + Shavlik Protect and

Shavlik Patch. Shavlik Protect is a complete solution for patch management that provides

agentless patching, patching of OS and third-party applications, inventory, and much more.

Shavlik Patch maximizes your investment in SCCM by adding a native add-on solution to

SCCM for third-party patching. This eliminates risk from third-party applications that are

unpatched (Kansal, Kapur, & Sachdeva, 2019).

Describe important things to consider when deploying system patches?

Awareness: One of the most significant things for you to do when it comes to patching is to

be conscious of what is out there. Many of the big suppliers have mailing lists that you can

subscribe to so that patch updates are received. It won't hurt to subscribe to any of the other

mailing lists that let you know when bugs exist, even when fixes aren't out yet, like those

from SANS or Bugtraq. To ensure that nothing is lost when everyone is on holiday, subscribe

to the delivery list of your IT or protection team. For links to some of the big mailing lists,

see the end of this article.

Include applications: The applications that open or execute file types take advantage of an

increasing number of exploits. Windows Update will take care of your operating system and

Microsoft apps, but there will be third-party applications on almost any device on your

network, including PDF readers, media players, and other business applications. For all the

applications that are part of your image, make sure you stay aware of patches.

Test before you deploy: Until launching them, both vendors test their patches, but it is nearly

impossible for a vendor to test any possible combination of hardware, program, and driver,

and they will not test the internally developed proprietary applications. Have a collection of

devices that you first install patches and monitor to make sure the systems don't have any

issues. When you can, take advantage of virtualization technology or use your IT department

and secondary servers if you have to just make sure you test all updates before rolling them

out to the whole company or main servers.