Re: Problem with the System Cloning Tool

Tech-Archive recommends: Speed Up your PC by fixing your registry

Rob,

During the cloning you should see the FBA blue screen with some information on it regarding the system preparation (progress bar
text).

Even if you happen to have the same MAC address on all machines (very unlikely) and the same seed for generator there is a bunch of
other parameters involving in the generating unique SIDs (time, etc.) and I doubt you are going to get 15 machines with the same
names out of 80 (the probability of the same values would probably be very very less).

--
Regards,
KM, BSquare Corp.

PS. By blue screen I don't mean BSOD screen but just a blue screen with some text on it.


> The cmiGenerateComputerName is set to 1, there is an ewf, but prior to
> cloning it is not enabled (this is done via calls to ewfdll.dll and then the
> ewfmgr at a later date). There were no blue screens or anything that looks
> wrong. The names are generated, they just seem be generated the same, also
> this morning I noticed yet another name clash. How is the name generated? Is
> it based on the MAC address, or does it just use the random number generator
> in windows? My concern is that if it uses the windows random number
> generator, then all the machines will have the same seed and the same entropy
> sources, which will never allow a random enough number.
>
> Also, the machine name, how does it work in a remote boot environment, is
> there any kind of arbitration, or does the remote boot manager set them as it
> sends the image out?
>
> Cheers,
> Rob
>
>
> "KM" wrote:
>
> > Rob,
> >
> > Was the cmiGenerateComputerName advanced property of the "System Cloning Tool" component set to "1" in your Configuration?
> > Are you sure those 15 terminals were cloned properly? (did you see the FBA blue screen on the first boot after the cloning)?
> > Do you use EWF and if you do - do you commit after the seal?
> >
> > --
> > Regards,
> > KM, BSquare Corp.
> >
> > PS. Are you planning on remote booting the 1000 terminals with MS RBS? Please be aware that it only supports unicast TFTP and
> > wouldn't be a good solution for booting > 10 devices (this certainly depends on network environment, capacity, etc.).
> >
> > > I'm using the System Cloning Tool to name my machines, now I seal the image,
> > > clone the drives and put the drives in our terminals. However, on a sample of
> > > only 80 images we've had about 15 network name clashes. Is there a setting
> > > that I have to have change, or is there a top limit that the machines will
> > > safely clone to?
> > >
> > > My concern is that we are toying with the idea of using remote boot systems
> > > that will have in the order of a 1000 units. Will we end up in the situation
> > > where large numbers of our terminals will have name clashes?
> > >
> > > Thanks for any information you might have.
> > > Rob
> > > --
> > > .Net Development Engineer
> > > ECM Systems Ltd
> >
> >
> >


.

Relevant Pages

  • Re: Problem with the System Cloning Tool
    ... Also, the machine name, how does it work in a remote boot environment, is ... (did you see the FBA blue screen on the first boot after the cloning)? ... Are you planning on remote booting the 1000 terminals with MS RBS? ... >> I'm using the System Cloning Tool to name my machines, now I seal the image, ...
    (microsoft.public.windowsxp.embedded)
  • Re: Problem with the System Cloning Tool
    ... If you are doing the cloning procedure properly this is what you should see. ... FBA begins, restarts, FBA continues, you should get a message that says ... > there any kind of arbitration, or does the remote boot manager set them as it ... >>> I'm using the System Cloning Tool to name my machines, now I seal the image, ...
    (microsoft.public.windowsxp.embedded)
  • Re: Problem with new image.
    ... The problem is one image doesn't fit all machines. ... the BIOS so that it could boot from CF. ... it gave me blue screens or ... error messages that suggest it couldn't find an operating system. ...
    (microsoft.public.windowsxp.embedded)
  • Re: windows xp crashes
    ... No blue screen, no stop code, nothing in the event logs. ... This morning there were 5 machines, ... "Will Denny" wrote: ... > Any error messages or Blue Screens - a Stop Code from the latter may help. ...
    (microsoft.public.windowsxp.general)
  • Re: Building 1 XP image for all PCs
    ... Chances are 99% that these machines have SATA/RAID disk controllers. ... Please confirm machine types and disk controller types. ... because my image blue screens on anything except where is was created. ...
    (microsoft.public.sms.tools)