Difference between revisions of "Viewing software installed on workstations"
m |
m |
||
| Line 26: | Line 26: | ||
priority="0" | priority="0" | ||
execute="always"> | execute="always"> | ||
| − | + | ||
<install timeout="15" cmd='cmd /C copy %SYSTEMROOT%\system32\wpkg.xml \\server\wpkg-xml\%COMPUTERNAME%.xml /Y' /> | <install timeout="15" cmd='cmd /C copy %SYSTEMROOT%\system32\wpkg.xml \\server\wpkg-xml\%COMPUTERNAME%.xml /Y' /> | ||
| − | + | ||
</package> | </package> | ||
[[category:Documentation]] | [[category:Documentation]] | ||
Revision as of 13:38, 22 June 2006
If you have WPKG runing on your workstations, you will probably want to see the software installed on each of them, even if the workstations are turned off.
As WPKG keeps its own "database" on each machine (it's in %SYSTEMROOT%\system32\wpkg.xml, it's enough to copy it to a special share on your server.
If you use Samba, a share may be configured like this:
[wpkg-xml] comment = WPKG workstation XML path = /home/samba/wpkg-xml browseable = no valid users = unattended, Administrator write list = Administrator guest ok = no
Make sure you create the appropriate directory (path = above) with correct permissions. After that, check if you can write to this share as the user which normally runs WPKG.
Additionally, you have to make sure that wpkg.xml file is copied to this share, with a proper name. We use copy command to copy the file, and %COMPUTERNAME% variable with .xml extension for the destination file.
You can do this with WPKG of course:
<package
id="wpkg-xml"
name="wpkg.xml files from workstations"
revision="1"
priority="0"
execute="always">
<install timeout="15" cmd='cmd /C copy %SYSTEMROOT%\system32\wpkg.xml \\server\wpkg-xml\%COMPUTERNAME%.xml /Y' />
</package>