Hardware Binding..XP Embedded

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

Guest

Hello all,
I am now at the position of deploying some OS to my client.
And i want those images to be bind to hardware after FBA.( I mean once the
image is up, it should not be booted on any other hardware of even same make.
So is there something which we can implement in XP Embedded for the same.
 
Are you trying to bind the image to just those specific machines, even if
the HW profile of some future machines were exactly identical? I'm not sure
how to bind it, unless you used WMI to query some custom information in the
BIOS of the machines you ship.

Or are you trying to ensure that no future HW (like a new but different
network card) will not work on that machine? Now this is a little easier, if
the drivers are not on the box and if the policies are locked down to
prevent the user from installing new drivers you could lock it down so the
image will only work with the original drivers you had in the image.

--
Andy

Check out the Embedded team blog: http://blogs.msdn.com/embedded/

This posting is provided "AS IS" with no warranties, and confers no rights.
 
yes ...you got me right..
I want my image to be bind to that specific hardware on which it boots for
the first time.
Is it possible n if yes than can you suggest me some way.
Thanks For Reply

And i had done this system Cloning, i got the message of "Please wait
windows is starting" after cloning,
but later i found that the files fbreseal.exe and setupcn.exe were still
present in my image though they are supposed to be deleted once cloned.
Is there something i m doing wrong.
i had very much gone with the steps as is given on MSDN

--

Amit S. Kadam
India


Andy Allred said:
Are you trying to bind the image to just those specific machines, even if
the HW profile of some future machines were exactly identical? I'm not sure
how to bind it, unless you used WMI to query some custom information in the
BIOS of the machines you ship.

Or are you trying to ensure that no future HW (like a new but different
network card) will not work on that machine? Now this is a little easier, if
the drivers are not on the box and if the policies are locked down to
prevent the user from installing new drivers you could lock it down so the
image will only work with the original drivers you had in the image.

--
Andy

Check out the Embedded team blog: http://blogs.msdn.com/embedded/

This posting is provided "AS IS" with no warranties, and confers no rights.
Click to expand...
 
Back
Top