FileWave Alliance

The Official Community Forum
  • Page:
  • 1

TOPIC: Client Renaming

Client Renaming 14 Jun 2017 14:39 #2574

  • Wes Goins
  • Wes Goins's Avatar Topic Author
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 7
  • Thank you received: 0
I would like to rename a number of our clients to bring in line with our new naming scheme. I know that if I use a fileset to perform the renaming, then the clients will no longer check in under the same entry once the name is changed. In the past, I got around this by creating a duplicate entry with the new name and same associations before performing the rename. However; this time I do not have a list of the serial numbers of the clients to match with the new names.

Is there an easy way to pull the serial numbers from these systems so that I can change the Name column in Filewave before re-imaging them?
(These are Windows clients.)

Client Renaming 14 Jun 2017 17:42 #2575

  • Bao Tran
  • Bao Tran's Avatar
  • Offline
  • FileWave Staff
  • FileWave Staff
  • Posts: 103
  • Karma: 4
  • Thank you received: 13
You could try the custom fileset I uploaded here - www.filewave.com/index.php?option=com_ku...2&id=1827&Itemid=246 - that lets you populate a string custom field of your choice with the PC serial number/service tag. Not sure but that sounds like what you're looking for.

Client Renaming 14 Jun 2017 20:31 #2576

  • P-M Lejon
  • P-M Lejon's Avatar
  • Offline
  • 5th level - Black Belt
  • 5th level - Black Belt
  • Posts: 92
  • Karma: 3
  • Thank you received: 15
Can't you get the client's serial numbers using an inventory query?

If you then rename the clients and do a model update, they will still connect with their old name as well as their new name.
We did this a couple of years ago and got help from FileWave with a nice sql command renaming clients based on a csv file with old and new name if I remember correctly (we renamed 700 clients in one model update :-o ).
P-M Lejon
System Administrator
BonnierNews
Sweden

Client Renaming 14 Jun 2017 20:39 #2577

  • Bao Tran
  • Bao Tran's Avatar
  • Offline
  • FileWave Staff
  • FileWave Staff
  • Posts: 103
  • Karma: 4
  • Thank you received: 13
Unlike Macs, Windows clients don't report the actual device serial number/service tag but something that resembles a hex ID combined with a MAC address.

Attachments:

Client Renaming 14 Jun 2017 20:42 #2578

  • Wes Goins
  • Wes Goins's Avatar Topic Author
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 7
  • Thank you received: 0
I was just about to say that... You beat me to it. I'll try your suggestion as soon as I get the chance.

Client Renaming 15 Jun 2017 13:34 #2580

  • Wes Goins
  • Wes Goins's Avatar Topic Author
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 7
  • Thank you received: 0
This will work for me. However, it seems to only work on ones that I am manually running the utility on the client. Any ideas on what I may be missing? I didn't change any of the settings after importing the fileset.

Client Renaming 15 Jun 2017 13:49 #2581

  • Bao Tran
  • Bao Tran's Avatar
  • Offline
  • FileWave Staff
  • FileWave Staff
  • Posts: 103
  • Karma: 4
  • Thank you received: 13
The FWCustomFields.exe is set up to run as a verification script rather than as an activation script so that means it only executes 1) when the system is rebooted 2) the verification interval passes [normally every 24 hours] or 3) you force a verification. You can force a verification, and thus the custom fields to update, via the Client Monitor or the Client Info window for that device. Both have a Verify button. Or you could reboot the device or just wait 24 hours.

Attachments:
Last Edit: by Bao Tran.

Client Renaming 15 Jun 2017 14:41 #2582

  • Wes Goins
  • Wes Goins's Avatar Topic Author
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 7
  • Thank you received: 0
Looks like I have a few starting to check in with it now. It may actually be due to the client version running on them. The ones checking in have client version 11.2.1 on it, which the others have an older 10.1.1, which I think was before the tiered scripts were added? I guess it's time up update my clients. Been trying to hold out until I update the server. Thanks much for your help.
  • Page:
  • 1