Deployment Solution

I'm using a scripted install to deploy Windows 7 Enterprise to PCs. This is a fairly rudimentary functionality of DS 7.6, and it works like a charm.

Here's the problem I'm running into: I don't always want the screen resolution to come up the same. I have computer monitors with native resolutions of 1024*768, 1280*1024, 1280*720, 1600*900, 1920*1080, ... you get the point.

What I'd like to see when Windows 7 comes up is to have the resolution set to the monitor's "recommended" resolution...that is, the attached monitor's native resolution:

My cohorts in other departments on campus that use MDT report that this can be done by editing CustomSettings.ini to an invalid resolution, thus forcing the adapter to autodetect its native resolution:

BitsPerPel=32
VRefresh=60
XResolution=1
YResolution=1

Is this something that can be done in DS via a configuration file? I found a PowerShell trick at http://www.serveradventures.com/the-adventures/set-native-resolution-in-windows-using-powershell-mdt-2010-2012, but the script fails to set the resolution properly, so that's an obvious no-go.

Thanks!

I see that I can do a custom unattend.xml for my scripted install, but that leaves me with two unanswered questions:

1- Where's the unattend.xml that DS uses to do the scripted install when you're not using a custom unattend.xml? Is it the one that winds up in C:\Windows\Panther on the installed PC? It would be nice to have a starting template.

2- Is there a list of everything I need to do to unattend.xml to get a scripted install to work? Would https://www-secure.symantec.com/connect/blogs/windows7-untangling-scripted-installs-sysprep-and-configuration-passes do the trick?

Thanks!