Settings for default wallpapers of OOBE

Question

 

Hi all,

need advice as to how to set the wallpapers located in C:\Windows\System32\oobe\info\backgrounds. I have all the relevant wallpapers and their dimensions set, all files are below 256kb, but for some reason, the files are cleaned out to very basic light blue background images after installing from the image. Why is this so? I don't understand.

Themes -> DesktopBackground is set to the path above + backgroundDefault.jpg (which is 1280x720).

Path in DS for the wallpapers are stored in this folder structure: ..\Windows Embedded Standard 7\DSSP1\$OEM$ Folders\Backgrounds\$OEM$\$$\System32\oobe\Info\Backgrounds

My BackgroundsPath -> Path is C:\Windows\System32\oobe\Info\Backgrounds under Embedded Enabling Features -> Custom Logon Desktop Background Images

 

Any other information needed, I would gladly provide. Please advise, thank you very much!

P.S. I have 3 other files that are not of the standard dimensions, they were copied over, so it shouldn't be the case of my path being wrong or something I guess?

(For additional information, I set DesktopBackground at Pass 4 ONLY. I'm not sure of the significance of detailing the different settings in different paths, could use some enlightenment also. I think I lost the CTP1 manual or something as well if anyone is thinking to ask me to refer to it...:P)

Edit2: After I generated the IBW image from Answer File, I notice that in the Specialize folder of AutoUnattend_Files, it contains a similar folder structure pointing into oobe all the way to backgrounds. It's blank inside. Is this a reason why? If so, I couldn't find the place to point it during Pass 4...

Answer 1

The standard blue backgrounds are stomping on the file you placed in the DS folder. You have to copy the files into the path after the installation process has installed the defaults. This requires the background files to be placed in a temporary folder. A script can perform this action during installation. I demonstrate a manual setup in EX701 in my book.

I asked MS about this one and there was some issues on the mechanics of the process. I was hopping to point the package to files to be copied, but it didn't sound too practicle.

-Sean

 

---

www.sjjmicro.com / www.seanliming.com / www.annabooks.com, Book Author - ProGuide to WES 7, XP Embedded Advanced, WEPOS / POS for .NET Step-by-Step

Answer 2

i recommand the methode to use the default folder and replace the orgiginal files with the branded one.

in setupcomplete.cmd - rd the oobe\info\backgrounds and than move my file (backgroudndefault) to the folder.

---

"Mark/Propose As Answer" if you got one.

Answer 3

Thank you Sean and KNARZ. I would think that this process could be automated from default, guess we would still have to have some manual work done after installation. Thanks for clarifying!

 

Hi guys, this is weird, I now point and place the wallpapers to C:\Windows\Wallpapers from initial installation(OEM folders), and I found these exact wallpapers copied to C:\Windows\System32\oobe\info\backgrounds as well, in their real forms. I did set in my OEM folder 2 destination folders to copy the wallpapers to.

I wonder if you guys have any idea why this is the case? It's like a double win for me, but I'm quite curious as to why this is the case.

 

Just a recap:

- My $OEM Folders$\Backgrounds folder has 2 destination paths:

-- $OEM$\$$\Backgrounds

-- $OEM$\$$\System32\oobe\info\backgrounds

- Now I have the actual wallpapers in both C:\Windows\Wallpapers and C:\Windows\System32\oobe\info\backgrounds

- Previously, I only have one instance and they are the standard light blue backgrounds in the System32\oobe\info\backgrounds folder.

 

Can I somehow conclude that C:\Windows\Backgrounds is my 'temp' folder and for some reason that got copied over correctly into C:\Windows\System32\oobe\info\background?

 

Thanks!

Answer 4

I had a similar problem but i found a simple solution after a pretty long search.

Have you already tried to set a ThemeName under the Themes section in ICE?

In combination with the DesktopBackground option (the path to your 'temp' folder with the picture) this should do the trick.

The ThemeName could be any name e.g. test or branding just don't use a standard theme name of Windows.

The xml answer file should look like this:

    <settings pass="specialize">
                <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <Themes>
                <DesktopBackground>%systemdrive%\Temp\Branding\mydesktopbackground.jpg</DesktopBackground>
                <ThemeName>mybackground</ThemeName>
            </Themes>

...

 

Have fun :)

 

P.S. To set the Windows Logon Background or both backgrounds you need a total different method!

Answer 5

i don't see any problems... you still can run a script or something to copy your file to a specific location. (e.g. setupcomplete.cmd)

 

---

"Mark/Propose As Answer" if you got one.

Answer 6

I just wanted to show the method to create an image/configuration with a custom background image (via ICE) without using a script.

Why you wanna use scripts when there are options in ICE to do this? (Rhetorical question)

 

Kind regards

 

 

Answer 7

sry, haven't slept that much. i had in mind that there is a question how to manage an automatism for setting one wallpaper for both stages (login + logon). and of course setting those settings in ice are well. ;)

---

"Mark/Propose As Answer" if you got one.

Answer 8

I'm trying to set the wallpaper based on the current user registry key. HKCU\ControlPanel\Desktop\Wallaper

However, the wallpaper is not displayed I just have a blue background (not the embedded logo background).  I can see the wallpaper is set properly under Control Panel\Personalization. Any idea what could possibly hide the wallpaper? 

EDIT: it says: "Unsaved Theme" under Control Panel\Personalization?

Answer 9

Are you using a custom shell or Explorer Shell? If custom shell, then the custom shell has to set the wall paper on each startup.

-Sean

---

www.annabooks.com / www.seanliming.com / Book Author - Pro Guide to WES 7, XP Embedded Advanced, Pro Guide to POS for .NET

Answer 10

Thank you Sean, I'm using a custom shell. So when I get back in a week I will look into it.

Answer 11

Sean,

Can you provide any pointers on what the custom shell needs to do?

Thanks,

Dean

Answer 12

I researched this once a year or two ago and forget the specific. It has to do with the setting the wallpaper registry keys each time the custom shell launches. Sorry, I don't have the specifics.

---

www.annabooks.com / www.seanliming.com / Book Author - Pro Guide to WES 7, XP Embedded Advanced, Pro Guide to POS for .NET