[wpkg-users] New WPKG features vs. report tool

[Rainer Meier]

Hi Stefan,

I've implemented /query:s and /query:l to query these tags from the (l)ocal host 
or the (s)ettings database and print it on screen. So a reporting tool could 
point it to a settings file using /settings:<path> /query:s to fetch all host 
attributes.

NEW: Implemented new query parameters:
          s - List host attributes from settings (wpkg.xml).
          l - List host attributes read from local host.
      The "s" option is mainly implemented for statistical and reporting
      purpose. If the local settings database (settings.xml) is copied to any
      host, then this option allows to query the host information attributes
      stored in wpkg.xml. It's supposed to be used with the /settings:<path>
      option therefore.
      e.g. wpkg.js /settings:\\server\share\wpkg-<HOSTNAME>.xml /query:s
      This will show the host attributes of of <HOSTNAME> as enclosed within the
      XML datastructure.
      The "l" option has been mainly implemented for testing purposes. It can
      be used to debug the host attribute parameters read by WPKG. It will
      always read the host attributes from the host wpkg.js is run on.


br,
Rainer


On 21.10.2011 20:59, Stefan Pendl wrote:
>>>
>>> Sure it would be much easier, if we could use a command
>> line switch for this.
>>> In addition we would need another command line switch,
>> which instructs wpkg.js to retrieve the host attributes from
>> the specified
>>> wpkg.xml file instead of the current host.
>>>
>>
>> Too slow....
>> /settings:<path>  is already implemented since a couple of minutes.
>>
>> However reading the hostname from the settings file is not
>> planned yet as the
>> hostname is most likely used in the wpkg.xml filename like
>> wpkg-[HOSTNAME].xml
>> filename. So the hostname is available to the program calling wpkg.js.
>>
>
> Rainer,
>
> thanks for that, I have been at work, so I was not able to give my two cents any earlier.
>
> ----
>
> I was not talking about the hostname at all, but about architecture, lcid and such, which is included in the wpkg.xml file of the
> client.
>
> Example:
> <wpkg hostname="satellite" architecture="x64" os="microsoft windows 7 home premium, , sp1, 6.1.7601"
> ipaddresses="0.0.0.0,192.168.56.1,0.0.0.0" domainname="" groups="" lcid="c07" lcidOS="407">
>
> The above information is needed to make /query work correctly for a server-side reporting tool.
>
> ---
> Stefan
>