Replaced Windows Shell, now resolutions are not automatically detected.

[Guest Ryukotsei0]

The Story: I am deploying Windows Thin PC using MDT(Microsoft Deployment Toolkit) 2012 beta 2. These deployments are going to be for our VMWare View thin clients. They are deployed from the custom wim that has View and a program I made to be a full screen interface to connect using View. The computer is locked down and through Group Policy the Shell's exe(by default set to explorer.exe) is changed to my programs exe through "SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell". Everything works fine besides the resolution, no matter what monitor, is always set to the OS default which is 1024x768. So far I'm guessing this is because something inate in explorer.exe automatically looks for this and I am not able to take advantage of it.

I have correct drivers installed and even the Nvidia nView suite installed. I can go into control panel and change it to be correct through there.

There are a lot of things I could do to fix this but not without adding steps. I want this to be very simple: insert disk, wait 13 min and bang thin client is ready to go. Which is where I am at now minus the Default OS resolution ordeal.

I need a script of sorts to run at startup that would detect the max monitor resolution and then set Windows to that or possibly there is a variable for AutoMaximumMonitorResolution in the registry or a value like that i could use in MDT for the xresolution and yresolution fields such as xresolution: %MAX%.

Thanks for any help guys.

 

Continue reading...