Systems Deployment

Login scripts are assigned to the user account or the OU the users are in. If the company is reorganizing its AD structure, then I would check (or have someone else check) to ensure that the scripts are assigned properly.

Startup scripts are applied to PCs or OUs with PCs in them. If you find a startup script is not running, you should again check to see if the AD reorganization has caused any changes with policies.

I'd also try manually adding a machine to the domain then moving its account into your target OU. See if the proper settings are applied then. If the scripts run when everything is done manually, then try troubleshooting the imaging process. In your case, I'd be more inclined to suspect that the problem is caused by the Active Directory changes than the imaging process.

Give us more details, buddy.
Are you running kix / vbs / dos scripts?
Are scripts logon or startup, as Dr Soup mentioned?
Are they assigned via user profiles, or through GPOs?
Are machines Win2K or XP?

Not getting login script = it never runs, or runs sporadically, or errors out, or runs invisible?

The issue was that the MachineObjectOU line in sysprep never joins the domain properly for me. After testing it out I was able to log into the domain and manually map my drives, but in AD nothing was shown. Its like I wasn't there. I did a search and found out that I was in a workgroup still. I think that it was too funky so I ended up writing a VBScript to move the object to the right OU after sysprep. So far so good.

Thanks for your advice

On a different topic, Hardware Profiles are user based, but in the registry? I need to keep my wireless disabled when its docked and enable it when its not. I've narrowed it down to registry entries just wanted to confirm with you guys to see if that is true or not?