Do not miss this eye candy, TSBackground for ConfigMgr, that
also adds security to your deployments.
We are all familiar with the ConfigMgr standard TSProgresUI,
which makes a great job but perhaps is not so aesthetically appealing.
TSBackground is the successor of “OSDBackground” that we published a couple of years ago. This new version addresses known issues as well as adds a lot of new functionality requested, including replacing the built-in ProgressUI. The first picture shows a design that we recently made for a customer. Apart from the more complicated controls, such as the progress bars, everything is customizable. TSBackground can show fixed text in combination with the content of any TS variable in any color, font and location you desire.
TSBackground has password protected debug features built in.
Just right click the upper left corner of the screen, type your password and gain
access to the debug tools.
This makes it possible to disable the F8 command support that we technicians love but frequently forget to turn off once a new boot image is put in production. This is a huge advantage as anyone with the right skills will be able to dump sensitive information from your environment so long as it is enabled.
TSBackground is fully configurable with respect to graphic layout, you can make it appear in almost any way or fashion that you like. This comes with the price of not being done just as easily as it was with the old “OSDBackground”, but if you willing to spend a little time and read the manual carefully you will surely get what you want.
When the application is launched the layout is loaded from .xaml files located in a dedicated sub folder. There are some “rules” that needs to be honored, naming is one, including the standard xmlns namespace in every top grid is another. Study the included standard files (General.xaml and Status.xaml) and consult the manual for more in-depth information on how to modify or create these files. A “Design Viewer” is available in the “Tools and Script” folder, this will help you assure that your file(s) are valid before tested in a Task sequence.
To avoid having to download the binaries TSBackground is best included in the boot image and later, in the Task sequence, transferred to the OS disk just before “Setup Windows and ConfigMgr”.
The manual explains how to add the files to the Boot image,
this is done on the “Customization” tab.
Launch in PE
The recommended method to launch the application is by
injecting a custom winpeshl.ini file into the boot wim – this sounds difficult
but is only a matter of placing a file (included in the download) in a folder,
update the image and then remove the file. The manual explains this. This method
is preferred and recommended as the injected file, including the launch command,
automatically runs on every boot to Windows PE. This means we do not have to
bother about putting in extra steps to start the application after for example
a bios update or configuration.
Start in full OS (Windows)
To re-start TSBackground at the earliest possible moment when
the computer enters full OS we recommend adding a “RunSynchronousCommand” to
the “unattend.xml” file.
This is very well described here, so we will not spend more time on it:
As you understand this tools / utility does not solve any
technical issues, but it does add an extra security layer with regards the F8
Command support and it sure looks nice. We have already seen some very nice custom
layouts and backgrounds circulating on Twitter, one that really stuck out was
made by the admins over at Minnesota IT Service (Chris Molstad).
Privacy & Cookies Policy
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.