FileWave Alliance

The Official Community Forum
  • Page:
  • 1

TOPIC: Filewave renameing Imaged machines

Filewave renameing Imaged machines 28 Mar 2016 14:24 #2228

  • Byron Gerber
  • Byron Gerber's Avatar Topic Author
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 9
  • Thank you received: 1
I thought that if a client is in Filewave, and I re-image it with an image that has the filewave client in it. Filewave would rename the client with the name that is in Filewave.
I can't get this process to work, has anybody done this successfully? If you have can you tell me what the process is so I figure out what I am doing wrong?

Thanks,
Byron

Filewave renameing Imaged machines 29 Mar 2016 07:25 #2232

  • Pierre-Nicolas Rigal
  • Pierre-Nicolas Rigal's Avatar
  • Offline
  • Administrator
  • Administrator
  • Posts: 81
  • Karma: 12
  • Thank you received: 30
Hi Byron,

First questions: which version of Imaging / FileWave, and which target platform (OS + version) ?

On windows, we change the name in the registry - directly and via sysprep script.

For OS X, we run:
/usr/sbin/chroot /Volumes/<volume> /usr/sbin/scutil --set ComputerName <name>
/usr/sbin/chroot /Volumes/<volume> /usr/sbin/scutil --set HostName <name>
/usr/sbin/chroot /Volumes/<volume> /usr/sbin/scutil --set LocalHostName <local_name>

Where name and local_name are based on FileWave client name, just made acceptable by the system ; if changing the name would fail, the whole imaging process would fail too - so I'm guessing that worked.

One thing to verify is if the client name has correctly been transmitted to your IVS - it is prepared by fwxserver and IVS will get the information from there via embedded fwcld ; you can log in to the web interface of the IVS and check if the name is correctly set for the corresponding mapping.

Filewave renameing Imaged machines 29 Mar 2016 11:28 #2235

  • Byron Gerber
  • Byron Gerber's Avatar Topic Author
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 9
  • Thank you received: 1
So if we aren't using an IVS this won't work for windows or OS X?

Thanks,
Byron

Filewave renameing Imaged machines 29 Mar 2016 11:34 #2236

  • Pierre-Nicolas Rigal
  • Pierre-Nicolas Rigal's Avatar
  • Offline
  • Administrator
  • Administrator
  • Posts: 81
  • Karma: 12
  • Thank you received: 30
I'm now a bit confused - what are you using for Imaging ?

we provide thunderbolt based, one-by-one imaging solution with Lightning (OS X only), and Network based imaging, now integrated with FileWave Management Suite, based on IVS (Imaging Virtual Server).

If you have Windows and OS X, you must be using IVS, right ?

Filewave renameing Imaged machines 29 Mar 2016 11:36 #2237

  • Byron Gerber
  • Byron Gerber's Avatar Topic Author
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 9
  • Thank you received: 1
Sorry for the confusion, we are using lighting for the OSX and an old solution for windows. I haven't configured an IVS yet.

Sorry,
Byron

Filewave renameing Imaged machines 29 Mar 2016 14:12 #2239

  • Pierre-Nicolas Rigal
  • Pierre-Nicolas Rigal's Avatar
  • Offline
  • Administrator
  • Administrator
  • Posts: 81
  • Karma: 12
  • Thank you received: 30
Ok - then no, Lightning is a completely independent product.
I've been told that very early versions could make use of some scripts that would read csv files with mapping name <> serials, but it's not maintained these days.

So here your best solution is to go via IVS - we added bunch of new cool things in version 4.0 - you may want to give a try to the beta.

Filewave renameing Imaged machines 29 Mar 2016 15:47 #2240

  • Byron Gerber
  • Byron Gerber's Avatar Topic Author
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 9
  • Thank you received: 1
Thanks for the info, sounds like I have something to work on. ;)
  • Page:
  • 1