PENDING Imaging Task Seq Skips Base Software Installs Step After 2103 Update

[cohtech]

I recently inherited the SCCM duties here, so if my verbiage is rudimentary/lacking, I apologize.

I have been in charge of SCCM for a few weeks now and recently started trying to migrate our PCs to the newest W10 versions. In order to do so, had to download the ADK/PE files, and discovered that we were on 1902. After doing a handful of incremental updates (since 2103 requires at least 1910 to update from), I ran a test task sequence of a base Windows and while Windows installed fine, I have none of my programs.

Before, when I'd run this TS, I would get the normal SCCM splash screen that applies W10, drivers, etc, then reboots. Then, I'd get a Dell splash screen that had a dialog box on it, that showed me step by step each application it was installing. If an application was no good, I'd get an error. Now, I don't even get that screen. Nothing about the TS has changed at all, but I don't get any dialog box, no errors....just reboots to Dell splash screen after installing Windows, does a "Getting Ready..." for a minute, then I sit at a "Just a moment" blue screen for 30-45 minutes while...nothing happens?

For the SCCM updates, my steps were to uninstall the old ADK/PE files, download the new SCCM updates and install (no errors), install new ADK/PE files (no errors), and updated distribution points (no errors). So at this point, as somebody who has a cursory knowledge of SCCM, I'm scratching my head as to what to troubleshoot, as up to that point, everything seems to be behaving. I figure if something in the TS is causing it to bomb out, I'd bet an error like I normally do, and the only thing that has changed is the boot file and SCCM version, but as of this moment I've told the TS to continue everything on error on every step just to see what happens as I post this. Any help would be greatly appreciated.

 

[Prajwal Desai]

Did you examine the log file to see why this could be happening ?. https://www.prajwaldesai.com/copy-smsts-log-file-during-task-sequence-failure/

 

[cohtech]

FWIW, the "continue on error" did not resolve the issue. I wonder if there's some other thing I have not updated to the distribution point. I have a simple setup here with only one server, so its the sole distribution point, so I haven't missed one. Just a feeling that I have missed updating a portion of this somewhere, but I know I followed your step by step guide on updating to the letter, so those portions have definitely been updated at the DP.

The entire contents of my log file:

<![LOG[Succeeded loading resource DLL 'C:\WINDOWS\system32\_SMSOSDSetup\1033\TSRES.DLL']LOG]!><time="16:30:14.506+300" date="08-11-2021" component="TSProgressUI.exe" context="" type="1" thread="2424" file="util.cpp:1011">
<![LOG[Successfully loaded resources from package source]LOG]!><time="16:30:14.506+300" date="08-11-2021" component="TSProgressUI.exe" context="" type="1" thread="2424" file="winmain.cpp:474">
<![LOG[Registering class objects]LOG]!><time="16:30:14.506+300" date="08-11-2021" component="TSProgressUI.exe" context="" type="1" thread="2424" file="winmain.cpp:479">
<![LOG[Entering message loop]LOG]!><time="16:30:14.506+300" date="08-11-2021" component="TSProgressUI.exe" context="" type="0" thread="2424" file="winmain.cpp:136">
<![LOG[Starting ProgressDlg::OnInitDialog()]LOG]!><time="16:30:14.662+300" date="08-11-2021" component="TSProgressUI.exe" context="" type="1" thread="2424" file="tsprogressdlg.cpp:613">
<![LOG[No State Wait.]LOG]!><time="16:30:14.662+300" date="08-11-2021" component="TSProgressUI.exe" context="" type="1" thread="2424" file="tsprogressdlg.cpp:526">
<![LOG[Debug shell is enabled]LOG]!><time="16:30:14.678+300" date="08-11-2021" component="TSProgressUI.exe" context="" type="1" thread="2424" file="tsprogressdlg.cpp:648">
<![LOG[Spawning system message loop thread.]LOG]!><time="16:30:14.678+300" date="08-11-2021" component="TSProgressUI.exe" context="" type="0" thread="2424" file="tsprogressdlg.cpp:238">
<![LOG[Waiting for system message loop to initialize.]LOG]!><time="16:30:14.678+300" date="08-11-2021" component="TSProgressUI.exe" context="" type="0" thread="2424" file="tsprogressdlg.cpp:247">
<![LOG[Signaling initialized event.]LOG]!><time="16:30:14.678+300" date="08-11-2021" component="TSProgressUI.exe" context="" type="0" thread="4832" file="tsprogressdlg.cpp:277">
<![LOG[Entering system message loop.]LOG]!><time="16:30:14.678+300" date="08-11-2021" component="TSProgressUI.exe" context="" type="0" thread="4832" file="tsprogressdlg.cpp:282">
<![LOG[Successfully enabled debug command shell support.]LOG]!><time="16:30:14.678+300" date="08-11-2021" component="TSProgressUI.exe" context="" type="1" thread="2424" file="tsprogressdlg.cpp:251">
<![LOG[Server is no longer in use. Shutting down.]LOG]!><time="16:33:41.695+300" date="08-11-2021" component="TSProgressUI.exe" context="" type="1" thread="2424" file="winmain.cpp:154">
<![LOG[Leaving message loop]LOG]!><time="16:33:41.695+300" date="08-11-2021" component="TSProgressUI.exe" context="" type="0" thread="2424" file="winmain.cpp:172">
<![LOG[Unregistering class objects]LOG]!><time="16:33:41.695+300" date="08-11-2021" component="TSProgressUI.exe" context="" type="1" thread="2424" file="winmain.cpp:498">
<![LOG[Shutdown complete.]LOG]!><time="16:33:41.695+300" date="08-11-2021" component="TSProgressUI.exe" context="" type="1" thread="2424" file="winmain.cpp:515">

 

[cohtech]

So on further review, it looks like SOME of the applications are getting installed, and some aren't. Why is this process in the background now? Before I upgraded to 2103, the dialog box would pop up and tell me what programs were installing in real time. I'm seeing about half of the apps I have in the TS installed, but I monitored the past 3 test images like a hawk and saw no evidence of anything being installed. It would certainly help to see that dialog box to know if/when something is failing.

 

[Prajwal Desai]

Can you upload the entire log file. Also, you can do a small test on a VM first.

 

[Prajwal Desai]

Probably the TS is failing before the applications are installed. Again, without looking at log files you cannot conclude anything.

 

[cohtech]

Can you upload the entire log file. Also, you can do a small test on a VM first.

That is literally the entire smsts.log file. I'm trying to disable the apps 1 at a time that weren't installing to see where my point of failure may be so I don't have the local file anymore. I don't get a failure screen like your blog link, but the smsts.log file that remained was simply those few lines there.

 

[kchusa]

I recently inherited the SCCM duties here, so if my verbiage is rudimentary/lacking, I apologize.

I have been in charge of SCCM for a few weeks now and recently started trying to migrate our PCs to the newest W10 versions. In order to do so, had to download the ADK/PE files, and discovered that we were on 1902. After doing a handful of incremental updates (since 2103 requires at least 1910 to update from), I ran a test task sequence of a base Windows and while Windows installed fine, I have none of my programs.

Before, when I'd run this TS, I would get the normal SCCM splash screen that applies W10, drivers, etc, then reboots. Then, I'd get a Dell splash screen that had a dialog box on it, that showed me step by step each application it was installing. If an application was no good, I'd get an error. Now, I don't even get that screen. Nothing about the TS has changed at all, but I don't get any dialog box, no errors....just reboots to Dell splash screen after installing Windows, does a "Getting Ready..." for a minute, then I sit at a "Just a moment" blue screen for 30-45 minutes while...nothing happens?

For the SCCM updates, my steps were to uninstall the old ADK/PE files, download the new SCCM updates and install (no errors), install new ADK/PE files (no errors), and updated distribution points (no errors). So at this point, as somebody who has a cursory knowledge of SCCM, I'm scratching my head as to what to troubleshoot, as up to that point, everything seems to be behaving. I figure if something in the TS is causing it to bomb out, I'd bet an error like I normally do, and the only thing that has changed is the boot file and SCCM version, but as of this moment I've told the TS to continue everything on error on every step just to see what happens as I post this. Any help would be greatly appreciated.

Hello, I have 2103, been managing for several years, I also use Dells for our computers.
I run the Task sequences i manage.
I have also noticed on all my provisioning, that on the Dell, I used to see more status messages and now I see a restart the Dell logo, and getting ready in a blue background for about 30 minutes. this occurs on all my 4 task sequence but ALL are Successful just no messages after applying drivers basically. Like i said successful, prior to 2103 more information would be displayed. these are usually new Dell laptops or desktops, all exhibit the same. Also i watch the logs for each task and monitor the deployment so all is good on each. thanks.

 

[cohtech]

More info: I have several different TSs that can be used based on department. The one I've been testing is the "main" one with just our base installs and most used applications. I picked another at random, and lo and behold, it gives the verbose dialog box that I am accustomed to, and all apps completed fine. So I copied that TS and removed the more specific apps for that dept back down to what the "main" TS looks like, and again, the dialog doesn't appear and I get that blue "Just a moment" screen while everything installs in the background. I'm at a total loss as to why. The only changes are the removal of some apps from one TS to the other, but it definitely isn't showing progress bars anymore for some reason. OS settings and everything up to installing the client are 100% the same.