Skip to content

RohinSidharth/Windows-Patching-Assistant

Repository files navigation

Windows-Patching-Assistant

Windows Patching Assistant tool based on PowerShell built for SCCM Environment.

Version 3.2 : Added Software Center View Added Ability to refresh remote SCCM Client Added functionality to clear cached credentials while exiting. Added Use of individual Credentials in input file. Added RDP function Added Cell Highlighting option

HOW TO USE

Input File: An input file can be generated from the tools menu>Export Template File. Takes 3 Columns:

  1. FQDN column is mandatory.
  2. Domain user and Password column is optional.

In case of Workgroup machines, the username should be in the format MachineName\username. Make Sure that the account you run this on or the User account provided on Input file has Admin access on the target machines.

Begin button will start the monitoring. Will prompt for the input file if not already selected using the browse button.

Once the monitoring is started, the data will start getting populated. Give it about 3 minutes. The refresh time of the screen can be controlled by the up-down counter on the right side panel.

Double clicking a record on the monitoring screen will select it and activate the individual server control panel on the bottom. This gives you the ability to do micro management on that machine.

The “Enable Options” check box on the right side panel will grant you the ability to Install patches (if available to be Installed on the target software center) and Reboot servers (if reboot is pending and no patches are installing/waiting) automatically on all the machines on the main monitoring screen. [Use with caution as this setting applies to all machines].

NOTE: The App does not come with a certificate, hence your machine will warn you that this is 'Suspicious'.

If you are running the Ps1 version from Powershell, you may have to set the PowerShell Execution policy correctly. Usually, setting it to ‘unrestricted’ would work.