Question on Cloning tools

[Guest]

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.

 

[KM]

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).

 

[Guest]

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]

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.

 

[Guest]

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.

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]

S.J.,

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.

Actually seems like I had understood your correctly.

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.

This part above I couldn't understand. What you mean you are changing the device hostname at first auto login session?
Could you describe the exact procedure?
At the logon time the hostname has been already read by the running network stack from regisry.

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

As been said, Cloning tools will change both - computer name and host name that are usually match.

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

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.

:

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.

 

[Guest]

Hi, KM:

Changing computer name requires reboot, it will not apply to my case.
but changing hostname seems working fine dynamically, actually
I just change the following three registry key values:
[HKEY_LOCAL_MACHINE\XPE\CurrentControlSet\Control\ComputerName\ComputerName]
"ComputerName"=
[HKEY_LOCAL_MACHINE\XPE\CurrentControlSet\Services\Tcpip\Parameters]
"Hostname"=
"NV Hostname"=

For me, it's wired why cloning changs computername and hostname at each login
sesion but not only at boot time.

is there the way to disable cloning after bootup?

Thanks,
S.J.

S.J.,

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.

Actually seems like I had understood your correctly.

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.

This part above I couldn't understand. What you mean you are changing the device hostname at first auto login session?
Could you describe the exact procedure?
At the logon time the hostname has been already read by the running network stack from regisry.

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

As been said, Cloning tools will change both - computer name and host name that are usually match.

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

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.

:

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.

 

[KM]

S.J.,

I just realized I have misread your previous post. My bad.

Are you saying that the hostname is changing every time you *logon" to the device?
What it is changing it to? Is it returning it back to original? Or is it always generated randomly?

Btw, this is not a good practice to change the hostname on fly. When you do that you have to make sure the entire TCP/IP stack is
down, which is a bit hard to do especially on remotely booted image.

--
Regards,
KM

Hi, KM:

Changing computer name requires reboot, it will not apply to my case.
but changing hostname seems working fine dynamically, actually
I just change the following three registry key values:
[HKEY_LOCAL_MACHINE\XPE\CurrentControlSet\Control\ComputerName\ComputerName]
"ComputerName"=
[HKEY_LOCAL_MACHINE\XPE\CurrentControlSet\Services\Tcpip\Parameters]
"Hostname"=
"NV Hostname"=

For me, it's wired why cloning changs computername and hostname at each login
sesion but not only at boot time.

is there the way to disable cloning after bootup?

Thanks,
S.J.

S.J.,

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.

Actually seems like I had understood your correctly.

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.

This part above I couldn't understand. What you mean you are changing the device hostname at first auto login session?
Could you describe the exact procedure?
At the logon time the hostname has been already read by the running network stack from regisry.

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

As been said, Cloning tools will change both - computer name and host name that are usually match.

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

:

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.

:

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.

 

[Data Recovery Expert]

If you want to learn about Partition, Hard Disks, File systems and Data
Recovery, Book "Data Recovery with & without Programming"

You can see the contents of the book on following Link:



http://www.DataDoctor.biz/author.htm



Regards

TT

 

[Data Recovery Expert]

If you want to learn about Partition, Hard Disks, File systems and Data
Recovery, Book "Data Recovery with & without Programming"

You can see the contents of the book on following Link:



http://www.DataDoctor.biz/author.htm



Regards

TT

 

[Guest]

Hi, KM:

each time logon, host and computer change to new random name.

And after I change hostname, I do ipconfig /release and /renew to clean
up network.

Thanks,
S.J.

S.J.,

I just realized I have misread your previous post. My bad.

Are you saying that the hostname is changing every time you *logon" to the device?
What it is changing it to? Is it returning it back to original? Or is it always generated randomly?

Btw, this is not a good practice to change the hostname on fly. When you do that you have to make sure the entire TCP/IP stack is
down, which is a bit hard to do especially on remotely booted image.

--
Regards,
KM

Hi, KM:

Changing computer name requires reboot, it will not apply to my case.
but changing hostname seems working fine dynamically, actually
I just change the following three registry key values:
[HKEY_LOCAL_MACHINE\XPE\CurrentControlSet\Control\ComputerName\ComputerName]
"ComputerName"=
[HKEY_LOCAL_MACHINE\XPE\CurrentControlSet\Services\Tcpip\Parameters]
"Hostname"=
"NV Hostname"=

For me, it's wired why cloning changs computername and hostname at each login
sesion but not only at boot time.

is there the way to disable cloning after bootup?

Thanks,
S.J.

S.J.,

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.


Actually seems like I had understood your correctly.

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.

This part above I couldn't understand. What you mean you are changing the device hostname at first auto login session?
Could you describe the exact procedure?
At the logon time the hostname has been already read by the running network stack from regisry.

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

As been said, Cloning tools will change both - computer name and host name that are usually match.

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

--
Regards,
KM

:

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.

:

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.