When you run Sysprep on one platform and deploy the image to another platform, you would ordinarily expect Plug-and-Play to handle any hardware differences (assuming that the machines use the same version of Ntoskrnl.exe and Hal.dll).
I just had a customer with an issue where after restoring an image from a machine of identical hardware, they could not get a USB storage device to install correctly.
I ran across this issue the other day with a customer who was trying to do a remote client install onto one of his machines. The install failed with the error code mentioned in the title.
