*Patch and reboot LOTS of computers, simultaneously, with just a few clicks
*Monitor status in real-time with progress indicators and integrated pinging
*DRAMATICALLY reduce the amount of time you spend deploying updates
*BatchPatch PAYS FOR ITSELF! *See what some of our customers have to say*
Stop dreading Microsoft’s Patch Tuesday every month and finally take control of your patching process! Whether you’re responsible for just 50 computers or more than 1000 computers, BatchPatch will save you a LOT of time. No more logging on to each computer to initiate the update installation. No more manually rebooting each machine and launching numerous ping windows to keep track of the reboot process. Finally, an app that lets you load a list of computers, and then kick off the Windows update installation and reboot process on all of them, simultaneously. You can now sit back, relax, and watch your computers update themselves.
- Initiate the download and / or installation of Windows updates on MANY remote computers simultaneously from a single console (works with your own WSUS server or Microsoft’s server). Watch this video tutorial for details.
- Deploy standalone Microsoft or third-party patches such as Adobe or Java updates, as well as registry keys, scripts, and just about anything else to remote hosts: (.msi .msp .msu .exe .reg .vbs and more). Take a look at this remote installation tutorial or this video tutorial or this Help page for more info.
- Reboot or shutdown remote hosts and monitor status in real-time with integrated pinging
- No remote agent installation required! Simply launch BatchPatch and start patching
- Integrated job queues: You can create a set of actions to execute sequentially on remote hosts, which allows you to run scripts before and/or after reboot, or string together multiple patch and reboot cycles etc.
- Execute your own custom scripts locally or remotely or add them to job queues for full automation flexibility
- Integrated task scheduler: Launch any task or job queue on a specific date and time
- Retrieve the last boot time from remote hosts (very handy when rebooting computers)
- Retrieve the used/free C: disk space from remote hosts (make sure the remote hosts have enough space available for patch installations)
- Retrieve the list of services that are set to “Automatic” but not currently running on the remote hosts (diagnose bootup issues)
- Launch remote desktop connections to hosts in the grid
- Wake on LAN
How it works
BatchPatch was designed to be simple and intuitive. Special attention was paid to keeping the app as slim as possible. No installation necessary– just launch the EXE and you’re ready to go! You start by loading a list of computer names, IP addresses or MAC addresses (MACs are required for Wake on LAN). Then highlight one, some, or all rows in the grid to perform actions on just the selected hosts. Either right click on the currently selected rows or use the Actions menu to select an action to perform. It doesn’t get much easier than that!
BatchPatch is an IT Admin’s Best Friend!
- BatchPatch is the simplest and most cost-effective of all patch management tools
- You get all the raw horsepower you need for Microsoft Windows patch management without the overhead of tools like SCCM. When it comes to patch management software with integrated monitoring, BatchPatch is without a doubt the best value and the easiest to implement
- It is the only patch tool that provides full real-time control of the patching process, filling in the gap where WSUS leaves off
- In addition to remote Windows Update, BatchPatch also provides 3rd party patch deployment functionality, remote script execution, remote reboot, and wake on LAN capabilities, plus advanced automation and sequencing options
- BatchPatch allows you to ditch your tedious remote desktop patch process for an efficient, automated, singular patch tool
- BatchPatch was written using a combination of C#.NET and native C++. In order to use the software you must have the .NET Framework 4.0 installed on the computer you’re running it from. Target hosts do NOT need to have .NET installed.
- For most actions, you’ll need to use an account that has local administrator access on the target remote hosts.
- For Windows Update actions, the oldest supported OS for target hosts is Windows 2000 SP3. All newer (post-Windows 2000) versions of Windows are compatible, but anything pre-Windows 2000 SP3 will not work as a BatchPatch target for Windows Update actions.
- Microsoft’s Sysinternals PsExec must be saved to your Windows system path or in the directory that you launch BatchPatch from. If you’re unsure about modifying your system path, you can simply drop psexec.exe into C:\Windows and that should do the trick. Launch psexec.exe one time to accept the license agreement.
- Target computers’ firewalls need to allow “Remote Administration” and “File and Printer Sharing” as explained here: Using BatchPatch with Windows Firewall
- The installation of Windows updates is performed by executing a process (using PsExec) on the remote machine(s). If you have specified alternate logon credentials (this means that you have disabled Integrated Security in BatchPatch for a specific host or set of hosts) when you choose a WSUS or Windows Update task from the actions menu, PsExec will send the specified credentials in clear text to the remote machine. However, if you enable Integrated Security (impersonates the currently logged on user) your credentials will not be passed in clear text. It is strongly recommended to always use Integrated Security whenever possible. It’s more secure and more reliable.
- Windows is a registered trademark of Microsoft Corporation in the United States and other countries.