FileWave Alliance

The Official Community Forum
  • Page:
  • 1

TOPIC: Custom fields

Custom fields 10 May 2013 14:39 #1276

  • sebastien.tomasi
  • sebastien.tomasi's Avatar Topic Author
  • Offline
  • User is blocked
  • User is blocked
  • Posts: 7
  • Karma: 1
  • Thank you received: 4
The integrated inventory of FileWave 6 is nice and more powerful than the Asset trustee. However you can't add custom fields in your inventory.
Those custom fields can give you an indication on the machines location for instance or a special tag you attribute to the machines.

It'll be awesome to add an unlimited number of custom fields, which can run a command line or a script on the client machine. Obviously, it'll be great to manage them on the console.
With a feature like this, i think the inventory could be a real asset to a filewave environment.

Regards

Sébastien Tomasi
The following user(s) said Thank You: nwurzel

Re: Custom fields 05 Nov 2013 13:43 #1340

  • nwurzel
  • nwurzel's Avatar
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 56
  • Karma: 1
  • Thank you received: 2
Well,

with Filewave 7 we now have custom fields in inventory. But at the moment they are quite useless because you can't edit them after the client is installed. At least I didn't found out how.

Since we use installation images with an already installed FW client for the imaging of new machines we never have the possibility to change these custom fields.

It would be great to be able to change these either via the Client Monitor application or - even better - by the SuperPrefs.

Kind Regards
Norbert Wurzel

Re: Custom fields 05 Nov 2013 14:04 #1341

  • Christian Glattfelder
  • Christian Glattfelder's Avatar
  • Offline
  • FileWave Staff
  • FileWave Staff
  • Posts: 37
  • Karma: 7
  • Thank you received: 14
Hello Norbert,

thank you for your suggestion. It is already in our database, Ticket Number is
FW-9156 "As an Admin, I want to edit custom inventory field information remotely"
I have added your name to the ticket.

For the time being, the content for the custom fields is stored in the FileWave Client directory ( /var/FileWave ; C:\ProgramData\FileWave\fwcld ) in a file called custom.ini.
Please find attached an example fileset for Mac that automatically puts the last logged in username into the custom_string_20 field. I hope that can be used as an example on how to use those fields in a more automated way. Please note that the custom fields are only scanned and submitted to the server at verification time - so if you want to test the fileset , remember to send a verification command / reboot the test client before checking inventory for the result.

Best Regards,
Chris
Attachments:
Christian Glattfelder
Systems Engineer
FileWave (Europe) GmbH

Re: Custom fields 12 Nov 2013 12:02 #1343

  • nwurzel
  • nwurzel's Avatar
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 56
  • Karma: 1
  • Thank you received: 2
Hello Chris,
thank you for the fileset. It's nearly perfect.

But it always returns "root" as the last logged in username because the script is executed as root.
If you change the second line of /usr/local/etc/scripts/lastloggedinuser.sh
into
USERNAME=$(who | sed -ne "1p" | cut -d\ -f1)

it works fine.

Thanks again!
Norbert.

Re: Custom fields 12 Nov 2013 12:09 #1344

  • Christian Glattfelder
  • Christian Glattfelder's Avatar
  • Offline
  • FileWave Staff
  • FileWave Staff
  • Posts: 37
  • Karma: 7
  • Thank you received: 14
Hello Norbert,

thank you for your feedback. May I ask if you have made any other modifications to the fileset ? Also , what OS generation are you testing this on ? I had tested the fileset on 10.6 - 10.9 before sending it out. The script being triggered as a LaunchAgent should ensure that the script itself is run as the user that is in the process of logging in.

Best Regards,
Chris
Christian Glattfelder
Systems Engineer
FileWave (Europe) GmbH

Re: Custom fields 13 Nov 2013 08:26 #1345

  • nwurzel
  • nwurzel's Avatar
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 56
  • Karma: 1
  • Thank you received: 2
Hello Chris,

I guess your're right. I set the script to "Execute once when activated".

With the unmodified fileset it works as expected.

Kind regards
Norbert.
  • Page:
  • 1