Updated August 2, 2013: Got a super-tips from Kevin Reed (thanks)
As you probably know MDT 2012/2013 and ConfigMgr 2012 defaults the screen resolution to 1024 x 768, but can be customized via the following rules in CustomSettings.ini
BitsPerPel=32
VRefresh=60
XResolution=1280
YResolution=1024
If specified, these settings will be written to the unattend.xml file during deployment by the Configure action (ZTIConfigure.wsf script).
Supertip! – Enable Auto Dectection
Previously, I have been using a script that simply deletes the default values from the unattend.xml if the resolution was not specified in CustomSettings.ini, but Kevin Reed gave me a supertip.
For the models you want to have screen resolution autodetection enabled on, simply set the screen resolution to a really low value. This will force Windows setup to autodetect the resolution:
Example with auto detection enabled for all models
[Settings]
Priority=Default
[Default]
BitsPerPel=32
VRefresh=60
XResolution=1
YResolution=1Example with auto detection enabled for all models but the HP Elitebook 8540w
[Settings]
Priority=Model, Default
[HP Elitebook 8540w]
BitsPerPel=32
VRefresh=60
XResolution=1920
YResolution=1080
[Default]
BitsPerPel=32
VRefresh=60
XResolution=1
YResolution=1
/ Johan
Superior tip, thanks… I will update the post with that info later this week. Do you mind if I list your name in the update? (credits, where credits are due 🙂 ).
/ Johan
A handy trick I've picked up is to user model-specific resolutions sparingly (I try to keep CustomSettings.ini as short and to the point as possible, as I won't always be the one managing the servers I work with). To force autodetection of screen resolution (at least in OSs Vista and above, may work with earlier OSs, but I haven't had the need to try it as yet!) set the XResolution and YResolution variables to 1 in CustomSettings.ini. When Windows tries to set that resolution, it seems to realise how ridiculous it would be to have a screen resolution of 1×1… Read more »
If you are leveraging the MDT database to specify resolution settings for a particular model, then this script is not required, correct?
FYI for anyone that may be struggling with the same issue. The problem ended up being the comments added to the model sections in my customsettings.ini file. This was an oversight on my part as I read a post on technet that incorrectly had them included after the section closing bracket. This will cause the section to be skipped, and instead the comments must be added on their own line like this:
; Lenovo M91P
[0266B7U]
BitsPerPel=32
VRefresh=60
XResolution=1280
YResolution=1024
Once I made this change it worked like a charm…. Thanks Johan!
Log files sent to your email as requested. Thank you sir!
Can you send me the ZTIGather.log and ZTISetScreenResolution.log file? email them to the arwidmark alias on gmail…
/ Johan
Hi Johan, Thanks for sharing your knowledge, I have followed many of your articles during our Windows 7 Deployment and transition to MDT from our old desktop imaging solution. I always find your posts extremely helpful, however I am having a difficult time getting this to work. I have the customsettings.ini file set up as you have above, specifically the section on screen resolutions is listed below: [Settings]Priority=Model, DefaultGateway, Default [0266B7U] ; Lenovo M4BitsPerPel=32VRefresh=60XResolution=1280YResolution=1024 I have added the ZTISetScreenResolution.wsf to the scripts directory, and also added the task sequence step to run the file per your instructions in the article.… Read more »
Hi Johan, Thanks for sharing your knowledge, I have followed many of your articles during our Windows 7 Deployment and transition to MDT from our old desktop imaging solution. I always find your posts extremely helpful, however I am having a difficult time getting this to work. I have the customsettings.ini file set up as you have above, specifically the section on screen resolutions is listed below: [Settings]Priority=Model, DefaultGateway, Default [0266B7U] ; Lenovo M4BitsPerPel=32VRefresh=60XResolution=1280YResolution=1024 I have added the ZTISetScreenResolution.wsf to the scripts directory, and also added the task sequence step to run the file per your instructions in the article.… Read more »
I have posted a step-by-step article on the driver injection here:
https://deploymentresearch.com/Blog/tabid/62/EntryId/69/The-Drivers-Saga-continues-How-to-Master-Drivers-in-ConfigMgr-2012.aspx
/ Johan
Hi Johan,
Thanks for the info it really worked for me.
Need you help regarding Inject Drivers Total Control please share the steps.
Sahil
Haven't seen a master list, and you don't really need one either… You are only supposed to set the screen resolution for the exceptions. e.g. for the models that doesn't autoconfigure correctly… For a company with 30 models, this is often no more than 3 – 5 models that needs resolution set…
/ Johan
Thanks for the info about [Model], but is there some resource on Internet where you can find a list of "all" computer models and screen resolution settings? Would be nice to just copy and paste.