Suggest the Problem if any(Cloning)

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello All,
I had a cloned image, I copy it on CF and boot it on a Hardware. It shows
the message "Windows is starting........". After sometime the windows starts
and its ready to use.
Now my question is if after this process I take that CF and connect it to
any other machine with same hardware configuration, will it work properly. Or
is there some problem in doing such thing.
Its a confusion for me, please suggest me about it.
Actually few of my clients had done so, and at one place the image is not
working properly.
Can anybody tell me what can go wrong in it. If i do so.
At my work environment i dint find any issue with it. such images are
working fine.
Plz Suggest.....
Thanks
 
AmitK said:
Hello All,
I had a cloned image, I copy it on CF and boot it on a Hardware. It shows
the message "Windows is starting........". After sometime the windows
starts
and its ready to use.
Now my question is if after this process I take that CF and connect it to
any other machine with same hardware configuration, will it work properly.
Or
is there some problem in doing such thing.
Its a confusion for me, please suggest me about it.
Actually few of my clients had done so, and at one place the image is not
working properly.
Can anybody tell me what can go wrong in it. If i do so.
At my work environment i dint find any issue with it. such images are
working fine.
Plz Suggest.....
Thanks
Click to expand...


Amit,
You can take that compact flash and install on any hardware that is exactly
the same and it will work as if it were on the original device.
This means IP Address (If Static), Machine Name and so on.

I actually use this method since all our machines have the exact same IP
Address and Machine Name I do not bother with the Cloning Component. The
only networking that is done is via Crossover cable and remote desktop so
it's safe doing it the way I am.

I make 1 image, let it run thru FBA, tweak any thing I need to, then I make
a Master Image. I then mass produce this master image, partitions, boot
sector and all using DD. This image is then installed on hundreds of
devices with are the same. (I use a Linux box with CF Adapter and it's sole
purpose in Life is to run DD and duplicate CF and is much easier than trying
to use ghost and all the other tools since you do not have to reboot afer
every CF card).

I hope this helps.
Richard
 
Sorry Richard,
i think u dint get me, What I am doing is after cloning I am bootin the
cloned image on one machine and after that I had connected this CF to
different machine though it has same hardware.
I want to kno that is it right or some problems may arise with this.
See, i copied the cloned image and booted it, once its booted than i take
this CF and using it on different machine with same hardware.
I want to ask is..Can anything go wrong with this process
 
Amit,

AFAIK, this wouldn´t be any problem as long as you´re not using these CFs in
the same network group.

As an example: First you let two (2) CFs run the "little FBA" (where it
generates computer name, SID etc) on the same HW and then deploy them on 2
different machines.
Later if you put these 2 machines in the same network you would end up
getting a conflict between them because they would have the same computer
name, SID´s etc.

However, this is just my best guess. Hopefully some expert or MS people
could comment this (and let me know if I´m correct ;-) )

BR,
Rob
 
To address the scenario where you want to put multiple cloned images on the
same network, this is one of the many scenarios that the System Cloning Tool
component addresses. To make sure that each cloned runtime has a unique SID
and computer name, you would clone the runtime to your target devices
immediately after resealing the image (which you can do either manually by
running fbreseal.exe, or automatically (default) at the end of FBA). After
reseal, the next time the image boots, it will receive a new,
randomly-generated SID and (unless specified otherwise) a new random
computer name. By copying your runtime just before this post-reseal step,
you can have as many devices as you want (within the limits of your
licenses, of course) boot up and each have a different ID. Then they can
all coexist on the network without colliding with each other (assuming they
don't all have the same static IP address, of course - that's another
issue).
 
Back
Top