[wpkg-users] WPKG for remote / offline clients (who are never local)

[Patrick CAHILL]

Hi All,
if the size of your updated WPKG distribution is going to larger than is efficient or economical on remote internet connections, why not put the files required on a flash drive or external hard drive and have it posted?
 
Since I assume you are in the UK and that you currently are not updating WPKG often this might be the most time effective way of doing it, if the Royal Mail / courier service has a fair price for shipping something that small in a fast timerame. 
 
You can have a simple robocopy script update the local WPKG installation with the files on the usb.
This will eliminate possible 3G charges and tying up a slow link for an extended period.
 
If you only have a limited supply of external disks you could have them send it on to the next closest remote user.
 
It may be a step backward from doing everything online and having it available instantly, but if updates are large or infrequent it may be an appealing option. 
 
--
 thanks
-Pat Cahill
M: Berserker Street SS
T: Glenmore SS
W: Berserker Street SS
T: Glenmore SS
F: Parkhurst SS

 
On 05/08/14, Dave Evans <dave.evans at goodness.co.uk> wrote: 
>  On 04/08/2014 16:01, Marco wrote:
> >Hello,
> >
> >I am new to the list, thus it might be a stupid question.
> >
> >On which level do you develop your solution:
> >
> >New WPKG Windows Client ?
> >A "execute before" script/program in the WPKG client ?
> >A "Custom script" in the WPKG client (off-line mode)?
> >Changes in wpkg.js ?
> others (Heiko & Rainer) have suggested that it might be not be a good idea, or at least there are things to be careful of before you do it.
> the work I've done so far has been to create a separate script probably .js (like wpkg.js) or PowerShell.
> Like I said, I would expect to have a local copy of the wpkg folder, and run from that
> the clever part is how you keep it up to date.
> I'm not clever enough to do a re-write of any of the existing code :-)
> 
> Dave
> >
> >Greetings ...
> >  Marco
> >
> >
> >On 04.08.2014 15:53, Dave Evans wrote:
> >>we have a number of users with laptops who work out of the office most
> >>of the time (i.e. they come into the office 1 or 2 times a year).
> >>others are remote desktops which never come to the office
> >>
> >>what I want is for the client to:
> >>
> >>   * connect to a central server somewhere (could be via VPN or a
> >>     restricted server on the internet)
> >>   * download any new or changed files in the background (like Windows
> >>     Updates)
> >>   * execute wpkg (possibly next boot to avoid killing running
> >>     applications whilst we update them)
> >>   * (optionally) send the log file back up to the central server
> >>
> >>
> >>I initially thought that off-line / laptop mode was for this, but on
> >>reading further I realise it's to stop the clients trying to access the
> >>server when they can't, useful, but no help here.
> >>I looked around to see if there was anything that anyone had already
> >>done to help in this scenario - but I can't find anything helpful.
> >>So I've started to code a solution, I'm getting on well, but there's a
> >>lot of work to do, and I thought it was about time I checked with the
> >>mailing list in case someone else knows something that will already do this.
> >>It may be that it's obvious, but just called something my brain won't
> >>think of (so I'll never find it using search)
> >>
> >>I've considered using offline files to make the remote folder structure
> >>available locally, but I've no way of ensuring that things will be
> >>updated locally in the correct order to make them execute right.
> >>My current idea is to run wpkg at boot as normal, then as the last task
> >>download any new/changed files using BITS (the part of Windows Updates
> >>which does the trickle download of new patches) then these new versions
> >>should get installed next boot.
> >>
> >>Does anyone know of anything that will do what I'm after already?
> >>and if not
> >>Would anyone else be interested in using this when I get it ready?
> >>
> >>--------------------------------------------------------------
> >>Dave
> >>
> >>
> >>
> >>-------------------------------------------------------------------------
> >>SSLrack gives free SSL certificates for open source projects (and cheap for everyone else)!
> >>http://www.sslrack.com/promo/free-ssl-certificates-open-source-projects
> >>
> >>-------------------------------------------------------------------------
> >>wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
> >>_______________________________________________
> >>wpkg-users mailing list
> >>wpkg-users at lists.wpkg.org
> >>http://lists.wpkg.org/mailman/listinfo/wpkg-users
> >>
> >-------------------------------------------------------------------------
> >SSLrack gives free SSL certificates for open source projects (and cheap for everyone else)!
> >http://www.sslrack.com/promo/free-ssl-certificates-open-source-projects
> >
> >-------------------------------------------------------------------------
> >wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
> >_______________________________________________
> >wpkg-users mailing list
> >wpkg-users at lists.wpkg.org
> >http://lists.wpkg.org/mailman/listinfo/wpkg-users
> 
> -------------------------------------------------------------------------
> SSLrack gives free SSL certificates for open source projects (and cheap for everyone else)!
> http://www.sslrack.com/promo/free-ssl-certificates-open-source-projects
> 
> -------------------------------------------------------------------------
> wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
> _______________________________________________
> wpkg-users mailing list
> wpkg-users at lists.wpkg.org
> http://lists.wpkg.org/mailman/listinfo/wpkg-users
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wpkg.org/pipermail/wpkg-users/attachments/20140812/f86ed4c8/attachment-0003.html>