Hi Marco, Marco Gaiarin wrote: > Some times ago i've asked for a WPKG.js wrapper (in JS) that can run the > real wpkg.js only if the 'client' belong to exactly one of our office > branch. > > Practically, i've setup common configuration within 3 branch, where > servers, share, ... have the same names/alias and so i can buld the > same configuration and simply copy around. > But clearly not *exactly* the same, so some portable system when moved > got some package continuously installed/uninstalled. Just to answer that part as well... I think you also got some hints that time how this could be solved even without having to invent something new. - Using DNS entries to point to the local WPKG server - Use the same WPKG config on all these servers You might also use a pre-execution script (supported by WPKG client) which is simply doing your verification in a simple *.cmd script and then skip execution it the machine does not belong to that system. br, Rainer |