BatchPatch http://batchpatch.com The Ultimate WSUS Companion Tool Sat, 19 May 2012 23:38:45 +0000 en hourly 1 Using BatchPatch with Windows Firewall http://batchpatch.com/using-batchpatch-with-windows-firewall http://batchpatch.com/using-batchpatch-with-windows-firewall#comments Thu, 18 Aug 2011 01:28:41 +0000 doug http://batchpatch.com/?p=80 BatchPatch uses a combination of Windows Management Instrumentation (WMI) and PsExec to access remote computers, plus ICMP for pinging.  If you need to use BatchPatch in an environment where your remote computers have Windows Firewall enabled, here’s what you need to do to make everything work.

It is sufficient to use Group Policy to allow “Remote Administration” and “File and Printer Sharing” on the remote computers.

 

However, if Group Policy is not an option and you instead need to manually adjust the remote computer settings, here’s how:

 

When the remote system is Windows 2008:

Go to Control Panel > Windows Firewall > Change Settings >Exceptions > check the box for “File and Printer Sharing” and “Remote Administration” and then click “Apply” or “OK.”

 

When the remote system is Windows 2003:

1. Go to Control Panel > Windows Firewall >Exceptions > check the box for “File and Printer Sharing” and then click “OK.”

2. Open a command prompt and type:

netsh firewall set service type = remoteadmin mode =  enable
]]> http://batchpatch.com/using-batchpatch-with-windows-firewall/feed 0 How to push .NET (or just about anything) to remote hosts using BatchPatch http://batchpatch.com/how-to-push-net-to-remote-hosts http://batchpatch.com/how-to-push-net-to-remote-hosts#comments Fri, 15 Jul 2011 19:34:32 +0000 doug http://batchpatch.com/?p=67 Here’s how to use BatchPatch to push the .NET framework to remote hosts that don’t already have it installed.  You can easily modify this example to push Adobe updates, Java updates, or just about anything else to remote hosts.

When the remote host is XP/2003:

1.  Add your remote host(s) to the BatchPatch grid, highlight the row(s), and then choose “Create/modify patch deployment”

2.  Select the .NET installer and add “/q /norestart” to the parameters field

3.  Choose “Execute patch deployment” to begin the process.  The installer file will be copied to the remote host and executed.

4.  After a few minutes, we see “Exit code: 0,” which signifies success.  If you receive a different exit code, you should Google it to find out what it means.  Windows installers can return a host of different numbers to indicate various things like “reboot required,” for example.

 

When the remote host is Windows 2008:

Windows 2008 makes .NET a “feature” that you can install from the command line, so we simply have to execute the proper command on the remote host(s)

1.  Add your remote host(s) to the BatchPatch grid, highlight the row(s), and then choose “Create/modify custom PsExec command”

2.  Type “servermanagercmd -install net-framework” with no quotes, of course, in the field.

3.  Choose “Execute custom PsExec command” to begin the process.

4.  After a few minutes, we see “Exit code: 0,” which signifies success.  If you receive a different exit code, you should Google it to find out what it means.  Windows installers can return a host of different numbers to indicate various things like “reboot required,” for example.

]]> http://batchpatch.com/how-to-push-net-to-remote-hosts/feed 0