Changes between master run- time image and cloned image

  • Thread starter Thread starter Gereon
  • Start date Start date
G

Gereon

I need to deploy a set of hardware- identical PC platform- ish devices. The
only differences between the platforms will be hardware serial numbers and
MAC addresses. In this case, does the cloning process just make a new SID
and computer name in the registry on each one? If so, is there a way I can
just store an SID and a Computer Name in a ROM chip or something, run each
of them off an identical CD ROM, and just set the SID and name into the
registry before they ever get used?
 
Gereon,

It is doable. But instaed of "ROM chip or something" you may just have a raw
partition on the client devices that contains necessary settings and perhaps
some code. You will also have to develop a boot driver that read the
partition (or any other storage) data and "restores" (sets) the computer
name in registry before network stack is up to read the machine name. Not
sure about SID, though.

I have seen similar implementations.

Anyway, why would you need that? What do you want to change in the cloning
procedure?

KM
 
It is doable. But instaed of "ROM chip or something" you may just have a
raw
partition on the client devices that contains necessary settings and perhaps
some code.

Sorry, I forgot to mention, there is no hard disk in this (currently
hypothetical) system. Without a hard disk, it's a bit tougher to have a raw
partition. But the system would have custom hardware, so a ROM chip is an
easy place to store identifying information.
Anyway, why would you need that? What do you want to change in the cloning
procedure?

I'm not sure what I want to "change" in the cloning procedure. I think what
I want to do is avoid it altogether. If I'm not mistaken, if I made a
master image and deployed it to each one, I would need to set up the EWF on
a hard disk partition, just so the system could create and remember its own
computer name and SID on it in an overlay.

Instead, it seems to me that all the machines could boot from identical
CD-ROMs (using the EWF running from RAM), as long as somewhere in the
process the data that they need to make them different can be set up. From
what I've learned so far, that data amounts to just a computer name and SID.
 
Gereon,
I'm not sure what I want to "change" in the cloning procedure. I think what
I want to do is avoid it altogether. If I'm not mistaken, if I made a
master image and deployed it to each one, I would need to set up the EWF on
a hard disk partition, just so the system could create and remember its own
computer name and SID on it in an overlay.

Instead, it seems to me that all the machines could boot from identical
CD-ROMs (using the EWF running from RAM), as long as somewhere in the
process the data that they need to make them different can be set up. From
what I've learned so far, that data amounts to just a computer name and SID.


What's your goal? To have persistent but unique SID and computer name per device?
If so, then yes, you will have to have a separate persistent storage for the data including SID, machine name, anything else you may
need. It could be whatever storage you are willing to add to your hardware (a flash, etc).
Again, you will need to develop a driver to set these data up in registry in early boot phase. The driver will work with your custom
"storage" hardware. This is doable.
 
What's your goal? To have persistent but unique SID and computer name per
device?

Not quite. They are the results of the research, but not the goal. The
goal is to determine what is required to have our machines properly boot
from identical media (El- Torito CD-ROMs), without hard disks in them. So
far, I have identified the SID and computer name as things I would need to
be able to supply from a separate source, and apparently can do. But there
may be other things.

Can you think of anything besides these 2 items that would be different
between 2 cloned machines, running identical hardware configurations?


KM said:
Gereon,
SID.


What's your goal? To have persistent but unique SID and computer name per device?
If so, then yes, you will have to have a separate persistent storage for
the data including SID, machine name, anything else you may
need. It could be whatever storage you are willing to add to your hardware (a flash, etc).
Again, you will need to develop a driver to set these data up in registry
in early boot phase. The driver will work with your custom
 
Hi Gereon,

Same hardware does not mean same serial numbers for certain hardware pieces.
MAC addresses for instance.

Best regards,
Slobodan
 
Same hardware does not mean same serial numbers for certain hardware
pieces.
MAC addresses for instance.

Indeed. So would an image that was put together on platform A still work on
platform B, which was identical in all respects except MAC address? Or, if
platform A got a new network card that was identical except for the MAC,
would the image still work?
 
Gereon,

If you don't need persistent SID and computer name, then go with resealed image on the bootable read-only media (El Torito, etc.).
Upon boot new unique SID and computer name will be generated by FBA on each device (no reboot should be required).
On next boot, though, the SID and computer name will be different (but unique again).
 
Hi Gereon,

Usually PnP can handle "new" hardware and install same drivers that are required.

I can't tell you how network adapter will be seen you will have to try this. But it will be either seen as new driver in which case
you will have to set it up (if you wish). Or less likely it will be seen as same adapter and no PnP will be used.

Anyhow there are perhaps few less important things left, but you will see that depending on needed level of options that XPe must
support.
For now if you need unique and persistent computer names you can make your application that will calculate them based on MAC address
that is always unique.

Best regards,
Slobodan
 
Back
Top