Feb 3, 2017
1 min read
Mostly used for deploying Operating Systems through SCCM, these cheeky guys bring some fresh hell to your learning burden.
I had a sequence much like the below (apologies this is not my actual screen shot as I don’t get the error anymore,I took this off Microsoft.com somewhere).
The objects referenced in the task sequence cannot be found. Verify that the objects exists and that the task sequence references the correct object name and location.
What you mean can’t be found. I added it from a list you nugget!
So I googled, much as you are doing now o humble seeker of knowledge.
I found a lot of smart people with a lot of great solutions that worked for lot of other people but my solution was not there.
It turned out to be surprisingly simple.
You might not know but I learnt from the great Mick Pletcher that you could create an application that didn’t have any content location.
This bit. SCCM Application Deployment Type
Like so.This means you don’t actually pull anything down to the local machine to install. It’s handy for v fat apps.
That being said, it causes the above error in task sequences.
So all I did was make the content location a folder with a small text file, just so it had something and boom. Task Sequence in SCCM was all fine.