My Background is not showing after re connect

[Sravan_k]

Hi,

I am facing one problem with Background image,

If I log-off and log-on my desktop background image is showing, but if I disconnect and re connect to VDI my background is showing as Black

Thank you,

Vkmr.

[ijdemes]

What are you seeing in the Personalization --> Background settings at that moment? Do you see the correct background there? Is this occasional or repeatedly? What happens if you reconnect without UEM? Do you experience the same issue then?

[Sravan_k]

Hi Ivan,

At that moment, when I go to "Personalization --> Background settings" it is showing as black.

"What happens if you reconnect without UEM?" How can I re connect without UEM?

How to fix this issue through UEM?

Thank you,

Vkmr.

[ijdemes]

I just wonder if this is related to UEM. Therefore my advice is to rule out UEM and see what happens than. Unless you have something specific configured that is triggered at a reconnect, nothing else is normally done by UEM at reconnect as far as I know. As the initial application of the background has already been done at logon (which works!), I just wonder which component is causing this issue.

One other thing I'm curious to know is, what happens when you.

1. Logon to new VDI

2. Background picture is applied

3. Change background to something else

4. Disconnect from VDI

5. Reconnect to VDI

What is the result? Also a black background, or.....?

[Pim_van_de_Vis]

Are you running Windows 7 and not activated? If that's the case I've seen it before. You need to activate the Windows machines to be able to personalize the wallpaper, this is a known Microsoft limitation.

[Sravan_k]

1. Logon to new VDI  ------ No change in Background

2. Background picture is applied ------ Yes

3. Change background to something else ----- I changed to windows default Img/ personal img

4. Disconnect from VDI ---- Did disconnect

5. Reconnect to VDI ------ On Reconnect I can see Windows default Img as default/ personal img

I think the Image that I am using in past is from network share, now I moved that image to desktop and tested, which is working

[ijdemes]

I managed to partly reproduce the issue, however not on disconnect/reconnect. I still don't understand that issue.

Anyhow, I believe it comes down to what you already described in your last comment, which is the location of the background image file. However, the location may vary depending on the way the background image is applied.

For instance, when you right click an image and select "Set as desktop background" a reference is made to the location where the selected background image resides in the registry --> HKCU\Control Panel\Desktop\WallPaper. As long as the image exists in that location, all is fine. I tested with both local and network locations.

When you browse to a website in Internet Explorer and you right click an image which you want as your background and select "Set as background", that file is saved to the following location --> <AppData>\Microsoft\Internet Explorer\Internet Explorer Wallpaper.bmp. As long as you save that file, which isn't done by the "Wallpaper" template by default, you're good and the registry (HKCU\Control Panel\Desktop\WallPaper) points to that background image file which is now saved/restored.

Long story short , as long as you save the background image file and restores to the location your registry is pointing to, you're good to go.

I think with Windows 10 the behavior is different compared to Windows 7, where I think the image file used was always the transcoded wallpaper file (location).

[Sravan_k]

Yes, finally I found the root cause for it.

What happening is, user is coping picture from file-server to desktop and making it as a default background and deleting the picture from desktop!!!!!

Guess what, when user starts new session, he can see the background but if he disconnected session and reconnected to same session, user will see the black screen.

try to test it......

[ijdemes]

Update: I managed to reproduce the issue using the steps you provided on Windows 10 (1703). It also happens when reconnecting using RDP and with and without UEM installed.

Like I mentioned in an earlier reply, I still believe that the background image file Windows/Personalization refers to needs to be in place. If it moves or it is deleted, you will have the issues like you specified. Please have a look at the steps below that, I believe, proves my point.

Header 1	Header 2
I have a desktop (using RDP) that has a solid black background.
I personalize the desktop and choose "Picture" and use "bg1.png" from my home drive.
I close "Personalize" and the background image is applied.
When I go back to "Personalize" you can see that it still contains the background image.
NOW, when I delete the background image file "Personalization" is referring to....
...and I now open "Personalize", you will see that even though the "Background" setting is still "Picture", the background is actually black.
Now when I disconnect and reconnect (which somehow seems to trigger a refresh of the "Personalization" settings) and go back to "Personalization", you will see that the "Background" setting is set to "Solid Color" with a black background.
This behaviour does NOT occur, as long as you leave the background image file in place at the location "Personalization" expects it to be.

[Sravan_k]

Yes Ivan, I am with your illustration with table.

This table is really cool, thank you