Do not use sysprep -clean before resealing.
What that does is remove all -non present hardware- drivers from the critical driver section in the registry, so they won't load on boot.
You should only do a -clean in runonce when the image is already deployed.
Besides that, I think I know what your problem is. I've had this problem before myself when I built my master-image in VirtualPC. It worked fine on a normal pc when I didn't include the virtual pc additions, but when I installed them in the virtual pc I wouldn't have working keyb/mouse on the deployed machine.
I don't know VMWare, but I suspect it has some kind of additional feature -like the additions in VPC- which will install it's own virtual keyboard/mouse drivers/service, but for which there is no hardware-emulator present on the real deployed pc!
So it's probably not the case that your input-drivers are not present in the image, but there's actually a virtual mouse/key driver loaded that wants to handle it. There's a driver/service too much!!!
The likely solution is to NOT-install or just remove the additional easy-input functionality at all in the virtual machine, before you sysprep and clone it. That way the virtual input driver is not present and not loaded in the deploy pc.
Let us know if it worked.
This post has been edited by Scrapple: 06 November 2005 - 06:05 PM