I have 2 scenarios that allows techs to determine the computers state. When the task sequence fails or when a Lab computer hasn’t been added to a lab group. It’s easy to enable the oembackground and rename a jpg picture. Group policy reg can disable the background picture.
For the first scenario you enable ‘Continue on Error’ for the very first group and have a catcher group at the end of the task sequence that runs only if TSVariable ‘_SMSTSLastActionSucceeded’ = False. MDT Task sequences are setup like this by default. It is best if the captured wim you are deploying already has the background file in it for scenarios where it fails due to not having any network access.
In the catcher group you will need 3 steps:
1. Copy jpg: Run command line with disable 64-bit file system redirection using a package with the jpg file (Not needed if jpg is in the captured wim):
cmd.exe /c xcopy Fail-Wallpaper.jpg C:\Windows\System32\oobe\info\Backgrounds /i /y
2. Rename jpg: Run command line with disable 64-bit file system redirection
cmd /c ren C:\Windows\System32\oobe\info\Backgrounds\Fail-Wallpaper.jpg backgroundDefault.jpg
3. Enable OEMWallpaper: Run command line with disable 64-bit file system redirection
cmd /c reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\Background /v OEMBackground /t REG_DWORD /d 1 /f /reg:64
I can expand and provide scripts on how I determine whether the computer is part of a lab ou/group based on name and ad object. Let me know!
Edit: This entry is for Windows 7, In Windows 8.1 you should do similiar but use the lockscreen – See the post on Windows 8.1 setting lockscreen and wallpaper for more information