Re: Problem with the System Cloning Tool

Rob,

I am taking back some of my previous statements about how FBA generates computer names.
A quick journey in to FBA just showed me that the algorithm is extremely simple. No use of MAC, and the seed is the same but just
updated with the local time current to the call.
It they happened to use CRT's srand/rand then the generated pseudo-random names are not random at all.

Since all your target are the same it might have happened that you turned them on the same time and get the same seed for some (15)
of them.
This is all just a guess of mine, of course.

But I'd recommend you to come up with your own good algorithm for generating computer names and use APIs like SetComputerNameEx.

--
Regards,
KM, BSquare Corp.

PS. There are even some obvious bugs in the FBA gen name algorithm implementation but this is irrelevant to your problem.


> 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


.

Loading