{"id":1643,"date":"2014-11-21T15:37:40","date_gmt":"2014-11-21T14:37:40","guid":{"rendered":"http:\/\/sccmfaq.wordpress.com\/?p=1643"},"modified":"2014-11-21T15:37:40","modified_gmt":"2014-11-21T14:37:40","slug":"sccm-2012-display-special-lock-screen-when-osd-was-unsuccessful","status":"publish","type":"post","link":"https:\/\/blog.hosebei.ch\/?p=1643","title":{"rendered":"SCCM 2012 – Display special lock Screen when OSD was unsuccessful"},"content":{"rendered":"

Hi, here’s Martin again with a blog about how to Display a Special Lock Screen, when the Operating System Deployment Task Sequence Fails. When you are using System Center 2012 Configuration Manager, you might want to have an easy solution to see, if a OSD was successful or not. Normally you see this Picture after a Windows 8.1 OSD:
\n\"Windows<\/a>
\n
\nSo even if there are better and more robust Solutions through Status Message rules, sometimes you would like just to get a visible check. In this blog, I’ll Show you an easy way to achieve this.<\/p>\n

The following steps has to be taken:
\n1. Create a failure Picture
\n2. Copy the Scripts to the Package Location
\n3. Create the Package
\n4. Add the Steps to the Task Sequence<\/p>\n

1. Create a failure Picture<\/strong>
\nThis is easily done through paint:
\n\"Paint<\/a>
\nSafe the Picture as jpg with the Name “OSD_Failed.jpg” in the designated Package Directory.<\/p>\n

2. Copy the Scripts to the Package Location<\/strong>
\nKnow create at the Package Location two files, the first one is named SetFailed_Background.bat which will set the failed LockScreen. The Content of this Batch is:
\ntakeown \/f C:\\Windows\\Web\\Screen
\ntakeown \/f C:\\Windows\\Web\\Screenimg100.jpg
\nicacls C:\\Windows\\Web\\Screen \/grant:r *S-1-5-32-544:F
\nicacls C:\\Windows\\Web\\Screen\\img100.jpg \/grant:r *S-1-5-32-544:F
\ncopy C:\\Windows\\Web\\Screen\\img100.jpg C:\\Windows\\Web\\Screen\\img100.old \/Y
\ncopy \"%~dp0OSD_Failed.jpg\" C:\\Windows\\Web\\Screen\\img100.jpg \/Y<\/code><\/p>\n

My script is derived from (https:\/\/yorkitacademy.wordpress.com\/2012\/11\/20\/customising-the-default-lock-screen-image-in-windows-8\/). I just added the “%~dp0” variable to work in every Situation in SCCM, and also Changed the ACE to a SID, because on other languages, you can’t use “Administrator”.<\/p>\n

And here is the second file, to set back the Standard LockScreen, Name the file SetStandard_Background.bat:
\ntakeown \/f C:\\Windows\\Web\\Screen
\ntakeown \/f C:\\Windows\\Web\\Screen\\img100.jpg
\nicacls C:\\Windows\\Web\\Screen \/grant:r *S-1-5-32-544:F
\nicacls C:\\Windows\\Web\\Screen\\img100.jpg \/grant:r *S-1-5-32-544:F
\ncopy C:\\Windows\\Web\\Screen\\img100.old C:\\Windows\\Web\\Screen\\img100.jpg \/Y
\n<\/code><\/p>\n

Your<\/strong> Package Directory should now Looks like this:
\n\"Package<\/a><\/p>\n

3. Create the Package<\/strong>
\nNow just create a Package with source Content of the Folder you created. Then add two programs to the packages, one for each Batch file. Your Package should then Looks like this:
\n\"SCCM<\/a><\/p>\n

4. Add the Steps to the Task Sequence<\/strong>
\nNow add the steps to the Task sequence, and in the correct order. This means, we will set after the Windows Installation the failure Background as Standard LockScreen. And only if the Task Sequence reaches the end of the TS, the original LockScreen will be restored.
\nAdd the Steps as marked out in this example TS:
\n\"TS<\/a> \"TS<\/a><\/p>\n

If now the Client has a error with installing an application or something else, when the OS was installed, your Windows 8.1 Machine will present you your LockScreen Picture:
\n\"OSD<\/a><\/p>\n

Hope this helps.<\/p>\n","protected":false},"excerpt":{"rendered":"

Hi, here’s Martin again with a blog about how to Display a Special Lock Screen, when the Operating System Deployment Task Sequence Fails. When you are using System Center 2012 Configuration Manager, you might want to have an easy solution to see, if a OSD was successful or not. Normally you see this Picture after […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[27,35],"tags":[],"class_list":["post-1643","post","type-post","status-publish","format-standard","hentry","category-operating-system-deployment","category-sccm-2012"],"_links":{"self":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/posts\/1643","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1643"}],"version-history":[{"count":0,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=\/wp\/v2\/posts\/1643\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1643"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1643"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.hosebei.ch\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1643"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}