Rainer Meier wrote: > Hi Joe, <snip> > This is absolutely correct due to the fact that WPKG 1.x does not waste > system resources any more by flushing an incomplete wpkg.xml after each > package. > > If you really need to get the absolutely latest version of the local > wpkg.xml I recommend putting a batch file onto the server and have WPKG > client running that batch file instead of wpkg.js directly. > > This allows to launch wpkg.js and then copy wpkg.xml with the batch script. > > Oh wait, I just found another option. Put the command (cmd /C copy > %SYSTEMROOT%\system32\wpkg.xml \\server\wpkg-xml\%COMPUTERNAME%.xml /Y) > to a batch script and add it to WPKG client configuration within the > "Execute after" configuration. This should do the trick. > > br, > Rainer Ok... Thanks... I was going crazy for a bit trying to figure out why the files never matched. Might want to add this to the docs on http://wpkg.org/Viewing_software_installed_on_workstations |