Jump to content


  • 0
Tobie

Screen resolution during OSD with SCCM (MDT integrated)

Question

Hi,

 

Google tends to be my friend but we do not agree today. I have searched all over the Inernet but I cannot find what I'm looking for.

 

I wonder if you can change the existing screen resolution during OSD, the current resolution is 640x480, the same resolution as the winpe.bmp picture (e.g. \\<server_name>\SMS_DSG\OSD\bin\i386\winpe.bmp). I want to use the same resolution as the screen can handle, e.g. 1280x1024.

 

Can i do this with TS or do need to configure something else?

 

Thanks in advance!

 

/Tobias

Share this post


Link to post
Share on other sites

8 answers to this question

Recommended Posts

  • 0

The problem disappeared when i had updated my GFX driver in my winPE image so I dont need to change this values manually for now. But, I'm still interested of how to it and I'll gett back when I know :D

Share this post


Link to post
Share on other sites

  • 0

The problem disappeared when i had updated my GFX driver in my winPE image so I dont need to change this values manually for now. But, I'm still interested of how to it and I'll gett back when I know :D

Use an unattend.xml

create a package, no program en ad it to the distribution point.

in the apply operating system step select the Use an unattended or sysprep, select the package and enter the unattend.xml file.

 

For example:

 

<?xml version="1.0" encoding="utf-8"?>

<unattend xmlns="urn:schemas-microsoft-com:unattend">

<servicing>

<package action="configure">

<assemblyIdentity name="Package_for_KB935509" version="6.0.1.9" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="" />

</package>

<package action="configure">

<assemblyIdentity name="Package_for_KB937287" version="6.0.1.18000" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="" />

</package>

<package action="configure">

<assemblyIdentity name="Package_for_KB938371" version="6.0.1.25" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="" />

</package>

</servicing>

<settings pass="specialize">

<component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<StartPages>

<StartPage wcm:action="add">

<StartPageUrl>http://www.google.be</StartPageUrl>

<StartPageKey>Home</StartPageKey>

</StartPage>

</StartPages>

<CompanyName>BlaBla</CompanyName>

<Home_Page>http://www.google.be</Home_Page>

<IEWelcomeMsg>false</IEWelcomeMsg>

<TrustedSites></TrustedSites>

</component>

<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<Display>

<HorizontalResolution>1920</HorizontalResolution>

<VerticalResolution>1200</VerticalResolution>

</Display> </component>

</settings>

<settings pass="windowsPE">

<component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<Display>

<HorizontalResolution>1920</HorizontalResolution>

<VerticalResolution>1200</VerticalResolution>

</Display> <DynamicUpdate>

<Enable>true</Enable>

<WillShowUI>Never</WillShowUI>

</DynamicUpdate>

</component>

</settings>

<settings pass="oobeSystem">

<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<OOBE>

<HideEULAPage>true</HideEULAPage>

</OOBE>

</component>

</settings>

<cpi:offlineImage cpi:source="wim://sccm/packages$/test-xml/install.wim#Windows Vista BUSINESS" xmlns:cpi="urn:schemas-microsoft-com:cpi" />

</unattend>

Share this post


Link to post
Share on other sites

  • 0

Kinom's example will set the resolution in the OS not in PE,

 

in PE you can use SETRES.exe

 

then copy that file to your MDT scripts folder (in the mdt files package), once done create a step called Use Toolkit package before the set screen resolution step, dont forget to update your Distribution Points with a new copy of the MDT files package after doing this,

 

you could of course create a separate package for the program setres.exe and add a step to use that package prior to the next line...

 

create a run command line task in your task sequence call Set Screen Resolution that has a command line which reads

 

cmd /c "%scriptroot%\SETRES" h1024 v768 b16

 

setres.jpg

 

done !

Share this post


Link to post
Share on other sites

  • 0

Setres has not work for me ...

 

That is why I searched for an alternative and came across Qres.exe ....

 

So I created a packet with the "Source Files" and create program with the following parameters

 

Command line: Qres.exe /X: 1400 /Y: 1050 /C: 32

 

It changes the resolution during the deployment and operating system itself!

Share this post


Link to post
Share on other sites

  • 0

I did it this was http://schnitz76.blogspot.com/2008/01/desktop-resolution-problems.html

 

Added 5 different "Run Command Line" with different resolutions and just ran for example "dc.exe -width=1600 -height=900 -depth=32 -quiet"

if the resolution isnt supported it skips it. maybe not the best way but it works if you wanna set the best resolution and have different monitors / laptops.

 

Dont forget to "Continue on error" for each, if the resolution isnt supported the task sequence stops

 

 

 

This works quite well but you have to add the PNPDeviceID for each monitor modell / Laptop

http://systemcenterideas.com/2009/10/automatically-setting-display-resolution/

Share this post


Link to post
Share on other sites

  • 0

Why dont you use the Inbuilt Set Task Sequence Variable action with Variabel name :Xresolution and value:1280 and similar to Yresultion as well.

You can also do this Via Creating XML file with WSIM.

does this chnage the resolution in WINPE?

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.