This question came up in the Embedded newsgroup a while back, and since then I've been interested in finding the answer. Here's the scenario:
Say you have a number of computers that you want to boot from CD (via El Torito), and all of these computers need to have access to the same network. The solution would seem to be that you'd simply prepare an El-Torito CD, clone it for as many machines as you need, and boot them all via El Torito.
Unfortunately, it's not that simple. Each copy of the OS will have the same exact information - namely, the same security ID information and the same computer name. If you attempt to boot more than one system in this state on the same network, the networking features will only work for one computer.
So, what about using System Cloning to get around this problem? Unfortunately, there's an issue with this as well: If you run "fbreseal" and reboot when indicated, you will reseal the machine without doing the final preparation for the El Torito CD. Meanwhile, for El Torito, if you run "etprep -all", the system reboots automatically and you don't get the benefit of System Cloning.
The solution is to run both utilities at the same time, before having either one of them reboot the system. Since fbreseal gives you a prompt to reboot the system, you can leave this message on the screen as long as you need to while you go back and run etprep. For this, you can use "Start >> Run" to enter both commands, or you can open two CMD windows. When you get to the point where you're ready to commit the runtime to CD, do the following steps:
First, reseal the system. Type "fbreseal -keepmounted" (the -keepmounted switch is important, because you do not want System Cloning to mess around with your drive letters). You can also use the -keepuser, -keepnet and -keepdomain switches if you want to preserve user, network and domain settings for your runtime. When fbreseal prompts you to reboot, do NOT press OK - leave the dialog on the screen. Here's more detail on all fbreseal commands.
Next, type "etprep -all". This will take care of the final steps of preparing your system for El Torito, including enabling EWF on the next boot. The system should reboot automatically at this point - close the fbreseal dialog if necessary.
Now, make sure that you don't go back into the runtime. Instead, boot into the safebuild and prepare your ISO image of the runtime partition, burn to CD, and verify that you can boot the computer from the CD. If all goes well, you should have a properly functioning system, and you can use a CMD window to verify that the computer's name has changed. The system should also be able to access the network. If you then burn multiple copies of your boot CD, you should be able to boot all of your target systems at the same time with unique IDs for each system, thus enabling all of them to get on the network.
Disclaimer: Because I have not fully tested this scenario yet, I cannot guarantee that this will work for everyone. I am interested in your feedback however, and will be happy to answer any questions you may have about this solution.
PingBack from http://findsongbylyricsblog.info/embedded-windows-team-nt4e-xpe-vista-embedded-preparing-an/