What do your package definitions look like? Are you using WPKG Client? How is it configured?
It's best-practice to declare a variable in the settings.xml that points to the server share for package files, and then use that instead of hardcoding server paths in packages.xml. <install cmd='"%SOFTWARE%\apps\firefox\Firefox Setup %version%.exe" -ms' /> It would also be a good idea to configure WPKG Client to look for wpkg.js at a generic name such as \\wpkg\wpkg.js and use a CNAME record in DNS to alias the "wpkg" hostname to whatever server actually holds the files. (I didn't do this but now I think I should...) On Tue, May 17, 2011 at 10:00 AM, Kenny Bayless <kbayl...@gmail.com> wrote: > Please excuse the n00b question... I'm sure there is a simple answer... > > We have several packages installed with WPKG, and all has been running > nicely. However, recently we had to change fileservers, and now all the > local WPKG.XML files point to the previous server. Is there a simple way to > simply refresh the local XML files? > > -- > Kenny Bayless > > ------------------------------------------------------------------------- > wpkg-users mailing list archives >> > http://lists.wpkg.org/pipermail/wpkg-users/ > _______________________________________________ > wpkg-users mailing list > wpkg-users@lists.wpkg.org > http://lists.wpkg.org/mailman/listinfo/wpkg-users > > ------------------------------------------------------------------------- wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ _______________________________________________ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
