AutoPatcher Client Service
Posted 02 December 2008 - 03:05 AM
First, if this is not an appropriate place to post this, I apologize and hope the moderators/admins will understand and place this where it should be, or of course remove it.
Since finding AutoPatcher and found it a darn good platform for updating PCs without need of MicroSoft auto update or manual update or an active Internet connection on a client PC, AND needing to update numerous PCs easily and without hassle, I wrote a Windows NT service application to do just that.
You can download version 1 (beta) from:
It takes a minute to connect and start so be patient if using a web browser.
Contact information to report bugs, thoughts, kudos, suggestions and etc. is located at the end of the readme file (a pdf).
Here is some of the information from the readme file.
AutoPatcher Client Service (December 1, 2008)
The purpose of the AutoPatcher Client Service is to provide a Windows NT based Service
Application that will check for a new AutoPatcher Answer File (.aaf) on a remote file share so
that network client PCs can receive a customized Windows update via AutoPatcher.exe.
First, apup.exe is run to gather up all of the available updates for a particular OS, or for all OSes
if needed. A network administrator would then customize an answer file using AutoPatcher.exe
from that particular OS, and as an example Windows XP. He would then select what he wants
AutoPatcher to install or update in Windows XP and create a WinXP.aaf answer file. This file
and ALL AutoPatcher files would be placed on a file share on some ‘server’ pc on the network.
The service will then check this location every hour for an updated aaf file. If the service is
running Windows XP it will look for WinXP.aaf. If the client PC is running Windows 2000 it
will look for a Win2000.aaf file and if it is running Vista, it will look for a Vista.aaf file. If the
service sees a new .aaf file it will run AutoPatcher.exe silently and minimized from the share by
first creating a network drive which starts from the upper end of the alphabet, drive Z. This
mapped drive is only available to the service account under which the service is run. After the
install is finished, the mapped drive is removed and the PC goes on as it would after any
AutoPatcher update. The service continues to check for a changed .aaf file.
USE THIS SOFTWARE AT YOUR OWN RISK! As of December 2008, this software is
considered to be a BETA release. I have made a reasonable attempt to write this program to do
what it says it will do and do so safely. It works for me! However I cannot guarantee how it is
used or whether it is fit for any particular application or purpose. There is no warranty expressed
or implied and I assume no responsibility for corrupted data or other loss of use through the use
of this software.
I have tested this software on Windows 2000 and Windows XP. I have yet to test this on
Windows Vista but will do so when I can.
Support is limited as it is Freeware!
The two applications making up this service, AutoPatcherClientService.exe and SetReg.exe are
Freeware. You can copy them and provide it to others provided that all of the files, the EULA
and this file are distributed with it.
Posted 02 December 2008 - 03:04 PM
You are welcome. I hope someone else can use it.
As it matures I may add a control panel applet to:
1. set update frequency or time
2. set file share location
3. manual check i.e. check for update now
4. set custom aaf file. (some PCs may not want a standard XP update.
Again, it is Beta and may have some bugs on different systems. So hopefully anyone who uses it will let me know via my web page contact.
Thank-you for AutoPatcher!
Posted 16 December 2008 - 05:33 PM
Posted 24 December 2008 - 05:17 PM
If I can get this to work, it would be great! Make keeping my local PCs up-to-date a lot easier!
Edited by jackson334, 24 December 2008 - 05:18 PM.
Posted 30 December 2008 - 12:42 AM
If you would, please go to my website and provide me your contact info via my contact page.
I have not a clue what would be 'flooding' your network. As long as all is set correctly you should see in your NT Application log every hour the service attaching and checking.
There are not TCP streams etc being used. Simple file sharing really.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users