[1703, cu] 1703 Lock screen, still no fix?

[3s-gtech]

My combination of hacks kind of works on existing builds and upgrades - but sometimes I just get a plain blue screen. I think that's a consequence of my policies deleting the accursed cave picture so the workstations throw a strop, but they'll live. The correct background sometimes shows up on these machines semi-randomly.

[DavR]

Update - I've built over a hundred workstations this week, and my luck seems to be holding!

 

Only oddity is that it take a few reboots to apply. First boot after deployment I get a background image (August update seems to have introduced a moose of some kind to replace the cave), then after a reboot this goes away, but may have a grey-screen effect for a bit before my chosen image (I went for plain blue because I lack imagination) takes hold.

 

It's never just simple is it.... still, better than running scripts or staring at that cave!

[Oaktech]

This may be of interest still...

 

There seems to be an issue with image size of backdrop. When you get a background image over about 3.5mb in size the group policy results become inconsistent. I reduced the DPI from 96 to 72 at 1920x180 which dropped the file size from 4 to 3.1mb and the results became consistent - a test group of 35 machines, every one showed the backdrop. Returning to 4mb image and the results became inconsistent on first reboot with only 2 machines out of the test group of 35 displaying.

[3s-gtech]

My images are only 150KB or so. I did find another fault recently with my setup, in that I'd misspelt the UNC path to the background. That didn't help! Working consistently here, but only with my 'fix' running once when the machine is built.