Upload
others
View
7
Download
0
Embed Size (px)
Citation preview
Patch Connect Plus for
3rd Party Automate Patch Management
Document Introduction
This document contains steps to install and configure the Patch Connect Plus.
By using web portal patch connect plus, manage automate 250+ Application patch management
Patch Connect Plus Architecture
The below diagram will provide overview of Patch Connect Plus connectivity with SCCM and work flow
Requirements
The installation machine should contain WSUS server or WSUS admin console which should be compatible with the primary WSUS server.
Note: Ensure that the WSUS server is of version 3.0 SP2 with WSUS-KB2720211 installed.
Hardware* Supported Platform Supported Browsers
CPU: intel core i3,
2.0 GHz Â
RAM: 2 GB
Hard Disk Space:
10 GB
System version:
only 64 bit
CPU: P4, 1.5 GHz
Windows XP
Windows Vista
Windows 7
Windows 8
Windows 8.1
Windows 10
Windows Server 2008
Windows Server 2008 R2
Windows Server 2012
Windows Server 2012 R2
Windows 7
Internet Explorer
Google Chrome
Mozilla Firefox
Installation P-Connect-P Now, Installation of Manage Patch connect Plus. Download from here..! 30 Days trail available.
Double click on exe file and follow the screen shots below, all are by default as recommended by ManageEngine
Installation completed, On Desktop, Can see ManageEngine Patch Connect Plus icon & also in Taskbar.
Configuration P-Connect-P Open the local-host of Patch-Connect-Plus web console. As like below and follow the snapshot.
Setup the proxy settings as per environment
WSUS Configuration, Directing to WSUS server host name with port number
Choose the product/application what need to patch to end user client machines.
Just confirmation page.
Configure the certs, As per environment, In my case going with self-signed certs.
Certs Configuration confirmation page.
Provide the SCCM Server host name with login Credential where can access SCCM Console with full rights.
Just SAVE & FINISH the configuration settings.
Now, P-Connect-P syncing with Vendor sites of those products (in my case, Notepad++ & 7Zip) and publishing to SCCM via WSUS.
Deployment with SCCM So, in SCCM Console, the both products is appearing move on and do the synchronization updates of them then download and deploy on end user machines.
WSYNCMGR.log file provide the information about product sync status
The updates of those prodcut reflected in All Software Updates
Created the software groups
Finally Deploy the 3rd party patches.
Reference
https://www.manageengine.com/sccm-third-party-patch-management/
https://www.manageengine.com/sccm-third-party-patch-management/getting-started-with-patch-connect-plus.html#setup https://www.manageengine.com/sccm-third-party-patch-management/support.html https://www.manageengine.com/sccm-third-party-patch-management/get-quote.html