I really wish it worked like that, but it doesn't. Let's say I build an image for a Dell Optiplex 755 with the built in video card. I build it on a 4:3 19" monitor at 1024x768. I use the newest driver from intel and make sure the machine works correctly. Now lets say I deploy that image on another Dell Optiplex 755 with the exact same hardware but with a 16:9 22" wide monitor. The machine will boot up and discover the monitor but will set the display to 1024x768 not even close to the native resolution of the monitor.
That, I'm afraid, is an error in the Intel display driver. When the display driver loads for the first time on the new Optiplex, the PnP manager is supposed to detect the old monitor is gone and a new monitor is present, and set the resolution accordingly.
What you are describing is a situation where the display driver either (a) cannot recognize the new monitor or (b) insists on configuring the new monitor with the old monitors's settings - both of which are Intel errors.
I would contact Intel and see if they have a registry value you can set on your master before imaging, which corrects this behavior. For example:
1. You create your master on a 4:3 19" monitor at 1024x768
2. When you are done finalizing the master, go into Windows Display properties > Settings and set the resolution to 640x480
3. Now go into Device Manager and delete all entries under "Monitors"
4. Now create your image for deployment
If I'm not mistaken, when the deployed image first boots on a machine with a 16:9 22" LCD, the Windows PnP manager will automatically pick this up as new hardware. And because the last resolution is 640x480, Windows will automatically ask the user if they want to switch to a better resolution. And that resolution should be 1600x1050 (assuming the norm for 22" ws) or whatever the optimal resolution is in the EDID.