OK, so what was their reasoning for making Windows Vista and 7 so difficult to deploy in an enterprise (domain) environment? It's exponentially more difficult than deploying Windows 2000 or XP. Here's what I hate the most so far:
A hack / script is required to name the computer before joining it to the domain during mini setup. Microsoft does not officially support any way to do this. Pre-stage in AD (like I want to find GUID's for them all), or accept the default (retarded) name given to the machine.
XML files for unattended setup and sysprep. Apparently plain text INF files were too easy to read and understand.
Copying the default user profile so everyone gets the configured desktop, icons, etc... is a PIA. The copy profile part of sysprep does not work well at all, especially in 7. You have to manually copy the profile you want as the default profile to a new folder, delete the old, then rename the copy back to default. 2000 and XP allowed you to do it from the user profile tool, which is still there in 7, but useless.
Windows Automated Installation Kit (1.6GB download BTW) is a joke. What was wrong with the setup manager for 2000 and XP? It doesn't need to be nearly that complicated guys.
Enough for now.... I realize Vista and 7 are totally different, being imaged based installs vs file copy, but wow... put at least a little effort in to making enterprise deployment a little easier.
Here at Tom's, the great great majority of posters are casual/hobbyists. So the pool of people who may be able to address the substance of your post is limited. At least there you have a chance that Microsoft employees/engineers may take note. They do not monitor this website. Not to mention a much higher liklihood an MVP may provide the needed tool or trick...