I wrote a blog post a while ago on a tool my college Johan Schrewelius has published which sets the OSDbackground during OSD and gives us the possibility to troubelshoot without F8 support enabled which should be avoided. An update of OSDBackground is now published with som bug fixes like:
1. Added Management Point to Wallpaper.
2. Made “ComputerNameVariable” Case Unsensitive.
3. Masked sensitive TS Variables in Debug mode.
4. Added support for Error background.
5. Moved background pictures to sub folder
The error background is a great addition, using this we use OSDBackground with a specific background when a Task Sequence fails and then we can access a Command Prompt or Cmtrace without F8 support enabled. We need to have a section in our Task Sequence with steps that are executed when a TS fails, I will write a post on that later this week. Configuring the “SMSTSErrorDialogTimeOut” variable to for example 28’800 =8 hours is a good idea so we have time to catch the computer with the error still present.
Adding a step to our TS failed section like this:
Then we get the following dialog when the Task Sequence fails.
OSDBackground can be downloaded here Onevinn – Applications (schrewelius.it)
9 thoughts on “New version of OSDBackground published with support for a specific background on error”
thanks from Brazil, this is very usefull.
Does this work in MDT as well?
Haven’t tested it but should work if .net is added to the boot images.
I have noticed one problem for use, we use hidden collection variables in our OSD collection. And when you are goning into debug mode the hidden collection variables are shown in clear text
We have just started using this in our task sequence in our organization and I must say it is amazing. You have made something really amazing here!
One issue I do have is and it is only a small issue is that after the first reboot and the background comes back up the mouse cursor is no longer visible on screen. Is there something I can do to fix this?
That is a known issue in WinPe, here is a fix for it. https://blogs.technet.microsoft.com/system_center_configuration_manager_operating_system_deployment_support_blog/2017/02/23/no-mouse-cursor-during-configmgr-osd-task-sequence/
When I opne CMTrace, or SMST logs in WinPE, I get an error about machine mismatch, and it won’t open CMTrace. Once the OS is installed, then I can open Cmtrace and the SMSS logs. How do I fix this?
I wanted to than you for the work you did and let you know that I was using it successfully for the last 4 years. Now I’ve updated ADK to 2004 and Win10 1909 and looks like it’s not compatible.
Any plans to update it? Will be much appreciated.
Never mind, my bad. Added .Net to boot image and now looks good. Thanks