Using XP embedded as a hardware testing OS

[carol.roberts]

I would like to use XP embedded on a project as a hardware testing
OS. The OS would _not_ be distributed with the system. My conundrum
is just how this test OS will look in the domain that the test systems
will be running in? Here is the setup (to the best of my knowledge so
if you need additional information let me know) I'm not a Windows
Administrator type of person so bear with me and please keep that in
mind on your answers.
1. XP embedded image modified to do strictly basic hardware functions
for ensuring the hardware is functioning properly.
2. XP embedded image will be converted to a Ghost image for deployment
to the units that will be tested.
3. Units to be tested will be connected to the network that sits in a
Windows domain. Of course there is a PDC in this domain and a DHCP
server (the DHCP server is actually separate from the PDC)
4. These units will PXE boot to get the XP embedded test OS.
5. Testing will occur.
6. Units will have the hard drives reconfigured and the distributable
OS put on them.

I know there are issues with SIDs, unique computer names, etc. when
running in a Windows domain which is why folks use Sysprep, but I
can't help but think that there is a more simple way.

thank you for your assistance

 

[KM]

Let me see if I got it right. You are planning on remotely boot into your XPe test image on the target hardware?
You didn't mention Remote Boot feature use in your list but mentioned PXE.

Anyway, the SID issue in domain environment may not be a problem to you if your testing doesn't include domain specific operations.
Sounded like you are planning to test and prepare the hardware with the image, right?
Also, keep in mind, that the non-unique SID issue is more a security problem in Workgroup environment, not domain:
http://technet.microsoft.com/en-us/sysinternals/bb897418.aspx

Also, check out the XPe docs on fbreseal (image cloning & deploying). It will help you to prepare the image so that it will have a
unique SIDs on each deployed machine. (fbreseal is sort of sysprep analog in XPe world)

 

[carol.roberts]

KM,

Thank you SO much for your insight! First, let me clarify the remote
boot you mentioned... no remote booting. Techs will be ensure the
NIC is set for PXE support in the BIOS and simply power the system
on. The PXE server will answer the broadcast. Maybe it is a
difference in terminology but I don't call that remote booting.

After reading your references, I'm thinking that the SID issue won't
be a problem. I'm thinking my systems don't need a unique SID
because:
1. Our testing has nothing to do with any domain operations. We test
physical hardware only. All my testing cares about is that the unit
has a MAC and an IP.
2. Security and any domain related features are not a concern as this
is merely a _test_ OS and not something that would be used outside of
the test environment. No end user would ever see this system with
this OS and it is in an isolated lab environment. We don't need to
access anything from a domain perspective, we simply need to have
network connectivity and perhaps DNS in order to access server(s) on
the same LAN segment. I don't need domain "features" in order to map
a drive or UNC to a server.

Do you concur or am I really missing a major point?

Again, thank you for your help!

 

[KM]

Thank you SO much for your insight! First, let me clarify the remote
boot you mentioned... no remote booting. Techs will be ensure the
NIC is set for PXE support in the BIOS and simply power the system
on. The PXE server will answer the broadcast. Maybe it is a
difference in terminology but I don't call that remote booting.

In XPe this features is called Remote Boot: http://msdn2.microsoft.com/en-us/library/ms838569.aspx

After reading your references, I'm thinking that the SID issue won't
be a problem. I'm thinking my systems don't need a unique SID
because:

Do you concur or am I really missing a major point?

Yup, I certainly do.