Re: Question on Cloning tools

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hi, KM:

Thanks for your replys.
I might not make this clear.
what I want is all devices have to boot up with the different names;
the name per device doesnt' have to be persistent at each boot.
as long as tha devices boot with different names, I will change hostname
(not computername ) throught DHCP server to the fixed name per device
at first auto login session. this method is working fine.

the problem is hostname keeps changing at every single time remote login
afterwards.

So if hostname will not change any more after bootup, it will be perfect.

Thanks,

S.J.



"KM" wrote:

> S.J.,
>
> If I understood you correctly, you want all the devices to have different names but make it persistent per device no matter how many
> times you boot the device remotely with RBS, right?
>
> Well.. it is more a concept problem for you and you will unlikely find a solution using just Microsoft implementation.
>
> When the cloning happens and the device is getting a new name you obviously can't change the SDI loaded from server to "update" the
> name there. Not just because the SDI is likely available for read only but also that the same SDI you sue for many devices.
> So.. the only "workaround" for you I see is that you should refuse using System Cloning tool so that it does not generate a new name
> on each boot. Then you create a early boot phase load driver that will change the name on the device (similar to what the System
> Cloning tool does). Your responsibility would be to either:
> - [easiest] generate the computer name consistently (e.g., using MAC address but no random formula), or
> - save (pre-set) the computer name somewhere on the device (e.g., in CMOS area or on a hidden partition area on persistent
> storage on the device, or etc.),
> - or have a database of the names on the server. But then the driver would be more complicated to implement as it would
> require the network stack up and running to be able to communicate with the server.
>
> The first two option I've seen implemented.
> The last one is also out there but may be wise to go with a 3rd party product.
>
> --
> Regards,
> KM
>
>
> > Hi, KM:
> >
> > I still need to have the different names for all the devices right after
> > boot up.
> > but I don't want hostname changed after each time login.
> >
> > Thanks,
> > S.J.
> >
> > "KM" wrote:
> >
> >> S.J.,
> >>
> >> To keep the same name of the computer for all devices you deployed the image to you should do:
> >> - Type in the computer name in the "Computer name" field of "System Identification" section on your HAL component settings
> >> page
> >> (Standard PC, etc.)
> >> - For the "System Cloning Tool" component, if used, set cmiGenerateComputerName=0 (advanced/extended property) or use related
> >> switch of fbreseal.exe (-keepall).
> >>
> >> --
> >> Regards,
> >> KM
> >>
> >>
> >> > Hi,
> >> > I am trying to use single image to boot multiple targets. so I run fbreseal
> >> > and then
> >> > create remote boot sdi image.
> >> > basically, everything is working fine, all the targets are able to boot from
> >> > the
> >> > same sdi image with the different hostname, for me, the cloning is working.
> >> > BUT, I got the problem. the those image with cloing installed keep changing
> >> > the hostname after every single time remote login.
> >> >
> >> > for our applications, we have dependancy on the hostname, but if hostname is
> >> > only
> >> > changing on boot time, it will be OK for me to handle it. but it changes
> >> > each time
> >> > login, it will cause the problem to our application.
> >> >
> >> > how can I overcome this?
> >> > Thanks very much!
> >> > S.J.
> >> >
> >> >
> >>
> >>
> >>
>
>
>
.

Relevant Pages

  • Re: Question on Cloning tools
    ... times you boot the device remotely with RBS, ... Not just because the SDI is likely available for read only but also that the same SDI you sue for many devices. ... Cloning tool does). ... >>> same sdi image with the different hostname, for me, the cloning is working. ...
    (microsoft.public.windowsxp.embedded)
  • Re: Fedora failure pattern
    ... make sure that the hostname in /etc/sysconfig/network ... You are likely using a e3fs file system, ... copy of "Tom's Root n Boot" from a sunsite mirror. ... micro distribution that fits onto a single 3.5 inch floppy. ...
    (comp.os.linux)
  • Re: Re.: Modem Problem.
    ... hostname into /etc/hosts. ... starting when the systems tries to boot. ... If your system can not resolve the FULL hostname from the /etc/hosts file, ... The nameserver has to be reachable NOW ...
    (comp.os.linux.misc)
  • Re: Question on Cloning tools
    ... but I don't want hostname changed after each time login. ... >> I am trying to use single image to boot multiple targets. ... >> same sdi image with the different hostname, for me, the cloning is working. ...
    (microsoft.public.windowsxp.embedded)
  • Re: Question on Cloning tools
    ... > I am trying to use single image to boot multiple targets. ... > same sdi image with the different hostname, for me, the cloning is working. ... > the hostname after every single time remote login. ...
    (microsoft.public.windowsxp.embedded)