Runing Autopatcher from remote PC
metalinspired
29 Aug 2008
Hi all,
I've been using Autopatcher for quite some time now and it's one of the best tools I encountered. However, it's missing something that, by the way I see it, is a mayor drawback. I putted a copy of Autopatcher on my company server and I copy it every now and then to remote pc's and update them. However it's taking to much time to do copying process on every pc and if I run it directly from server it takes even more time. There should really be an option to skip cheking of releases integrity. This way instead of having to copy all files to remote pc I could just start autopatcher.exe on that pc and do everything as if I was running it from CD.
I've been using Autopatcher for quite some time now and it's one of the best tools I encountered. However, it's missing something that, by the way I see it, is a mayor drawback. I putted a copy of Autopatcher on my company server and I copy it every now and then to remote pc's and update them. However it's taking to much time to do copying process on every pc and if I run it directly from server it takes even more time. There should really be an option to skip cheking of releases integrity. This way instead of having to copy all files to remote pc I could just start autopatcher.exe on that pc and do everything as if I was running it from CD.
James
05 Sep 2008
Hi metalinspired
AutoPatcher will always check the release integrity, because that confirms that no-one has altered any files and that you will be installing genuine updates.
However, if the network is slow this could be because AutoPatcher is checking many small files. There's also some Windows bugs that give slow file copying on a network.
Sometimes it is quicker to create a large ZIP archive of the AutoPatcher files on the server and transfer everything over the network as one large ZIP file.
--
AutoPatcher will always check the release integrity, because that confirms that no-one has altered any files and that you will be installing genuine updates.
However, if the network is slow this could be because AutoPatcher is checking many small files. There's also some Windows bugs that give slow file copying on a network.
Sometimes it is quicker to create a large ZIP archive of the AutoPatcher files on the server and transfer everything over the network as one large ZIP file.
--
metalinspired
05 Sep 2008
Hi James.
Creating a large ZIP file is double sided blade. It will speed up copying over network, but will also require additional time to extract the same archive. Also every time I update Autopatcher I will need to create ZIP file again. Even if we ignore those two drawbacks of this method there is one that is, by my opinion, bigger than those two. Don't you think it would be a waste of time to copy 2,5 GB file over network and wait for extraction to finish only to make few updates to PC? I could simply run Autopatcher on server machine once, only to check release integrity, and if all goes well I would simply disable checking release integrity on client machines when running Autopatcher on them.
Creating a large ZIP file is double sided blade. It will speed up copying over network, but will also require additional time to extract the same archive. Also every time I update Autopatcher I will need to create ZIP file again. Even if we ignore those two drawbacks of this method there is one that is, by my opinion, bigger than those two. Don't you think it would be a waste of time to copy 2,5 GB file over network and wait for extraction to finish only to make few updates to PC? I could simply run Autopatcher on server machine once, only to check release integrity, and if all goes well I would simply disable checking release integrity on client machines when running Autopatcher on them.
James
05 Sep 2008
Yes, I realised that creating a large ZIP file has its own problems.
It depends how big the ZIP file is. I was thinking 400 MB not 2.5 GB! Probably best only if you have a really slow or busy network but are copying to really fast hardware.
I understand what you are asking for.
AutoPatcher already has other options that are "advanced" or "dangerous" so I think another advanced option of "nointegrity" (or something like that) can be justified.
Not sure when it will happen though. We are all trying to make APUP work better at present.
--
It depends how big the ZIP file is. I was thinking 400 MB not 2.5 GB! Probably best only if you have a really slow or busy network but are copying to really fast hardware.
I understand what you are asking for.
AutoPatcher already has other options that are "advanced" or "dangerous" so I think another advanced option of "nointegrity" (or something like that) can be justified.
Not sure when it will happen though. We are all trying to make APUP work better at present.
--
metalinspired
05 Sep 2008
James, on Sep 5 2008, 01:36 PM, said:
I understand what you are asking for.
AutoPatcher already has other options that are "advanced" or "dangerous" so I think another advanced option of "nointegrity" (or something like that) can be justified.
AutoPatcher already has other options that are "advanced" or "dangerous" so I think another advanced option of "nointegrity" (or something like that) can be justified.
James, on Sep 5 2008, 01:36 PM, said:
Not sure when it will happen though. We are all trying to make APUP work better at present.
