Jwatson

THanks for the suggestion...I checked the host file just now, however, and it looked just fine.

I have a computer here which cannot log into Windows (XP Pro) using the domain it was set up with, but it can log in locally. The crazy part is I can log in remotely, so I know it has network access. Has anyone ever encountered this sort of problem before? I apologize for the vagueness, but I don't have the owner's login information in front of me so I can't work on it further, but I will post more details as soon as I have them. [EDIT] I've looked at it a bit more, and here's the scoop: when the machine is logged onto the network of origin, it cannot log in via the domain, but can log in locally. When Ethernet is unplugged, it CAN log in to the domain using cached settings. The problem isn't server-side, because the user can use her log in on any other computer on the network and the domain logs it on just fine. Thoughts? Thanks very much, Jon

It's not always true the hotfix installs with the audio drivers...SOMETIMES that's the case, but rarely. As far as the issue at hand, I'm not aware of any ways to do it without resysprepping it...it doesn't take long though, does it?

I need to be able to enter in the product key and specify a username while in Factory mode, so that when I reseal and the customer boots up for the first time, all they have to do is accept the EULA. I have user-specific preconfigured settings (a customized background, for example) that rely on the username "Owner", so I can't have the customer specify their own name. I already know the switch to leave Windows preactivated after resealing, and it still asks for the product key... I created a sysprep.inf file that has the product key in it, but something must be wrong about my syntax or SOMETHING, because it didn't do a thing. Is there a line in that .inf file that you can specify the user file? Thanks for your help ahead of time! Jon