Ok sure. I'm just trying to do what I've done hundreds of times before with Windows 2000. I'm making an image to be deployed across a ton of identical Dell Latitude D600 laptops.
The only difference is that this time around I have to set the machines with hardware profiles to prevent XP from having any way of bridging the connections and violating enterprise security policy.
After configuring the machine exactly how I want it there are 2 main problems after sysprep'ing the machine.
1. The hardware profiles still exist, but are no longer configured how I want them. After being sysprep'd and the machine runs through its mini config the profiles have all the hardware enabled while before the sysprep certain devices were disabled in each one.
2. The WLAN configuration (SSID & WEP Key) are no longer configured after running through the mini setup. Before the sysprep they were configured and worked for any new domain user who logged into the machine.
I need the mini setup to run so that I can give each machine a unique machine name to join the domain with.
If you did it with win2k then you've assumed XP will be the same? XP is a TOTALLY different system as far as setting things up go.
I wish I could help you, I had a complete app to setup and promo/join machines with unnatended setup. But I think you'll have to find different way of doing things instead of going around doing setup after setup, even though if it is what you have to do, then you'll have to deal with it.
One suggestion though, you can make your image with .cmd file in the startup folder to run "netdom.exe" (I hope they still have it on CD in admin pack) to join PCs to a domain, rename them, etc. Besically it is figurable thing, it is just not helpfull to help from such a "distance". After you ran that, the .cmd file can write different one, or start different one for the next task at next reboot (I hope you know the shutdown.exe thingy as well;)
..this is very useful and helpful place for information...