PENDING OS deployment task sequence problem

[MdKnightR]

I've recently run into an issue with our OS deployment task sequence in SCCM. We are running version 2107 of Configuration Manager (updated on September 3, 2021). The issue began before the upgrade from the previous version, with the first reported instance being on August 27th when one of our technicians imaged a laptop and discovered that the Cisco Anyconnect client didn't get installed. We didn't think must of it at the time and it was easy enough to push it after the fact.

Then, last week, I tested out a new OSD task sequence that I customized for imaging Surface Go devices with Windows 10 LTSC and discovered that other applications were missing too. These devices only need Outlook instead of the full Office suite, but it didn't install. After this discovery, another of our technicians decided to look more closely at a laptop he had been setting up for a new employee and discovered the entire Office 2019 suite was missing from it too.

Next, I grabbed a brand new laptop and ran our primary Windows 10 Enterprise deployment on it. This time, Office, Anyconnect, VLC Media Player, and Jabber were all missing, which accounts for about half of the software titles that should have gotten installed. It is odd that these task sequences works fine otherwise and I am still able to push the missing software after the imaging process. I'm stumped. Any help would be much appreciated.

 

[MdKnightR]

This worked for me....

I found this thread for the same issue on version 2006. Apparently it cropped up again in 2107.

TS application install fail after 2006 upgrade - Microsoft Q&A​

Microsoft Q&A is the best place to get answers to all your technical questions on Microsoft products and services. Community. Forum.
docs.microsoft.com

The Readers' Digest version - you have to add an administrator comment to each deployment type then update content on each. It doesn't matter how long it is (for example, "SCCM2107Fix"). There was also mention of the issue affecting applications that have operating system requirements. Incidentally, every one of mine that weren't getting installed had these requirements, so I cleared them out for good measure.

Now my primary OSD task sequence works great! However, I still had an issue with a new task sequence that I put together prior to the ConfigMgr 2107 update. It was made for imaging Surface Go devices with LTSC. For their purpose, the users only need access to email, so I had created a deployment of Outlook 2019 only. The little trick mentioned above did not work for it, so I had to go and create a brand new application using the SCCM's built-in Office Customization Tool. Now it installs with the OSD task sequence as expected.