SCCM - Task Sequence "deployment not yet started" Please HELP

[Newb]

Hi,I have deployed a new Task Sequence as a required deployment to a collection containing 30 devices. I have set the scheduling as I normally do when this has worked in the past. I have also put the "Rerun" behaviour as "never rerun deployed program" as this is a new Task Sequence.

 

The Task sequence however doesn't start. In the config manager log, I am receiving the error "The deployment has not yet started because the content for the package "****" has not been acquired". This package it is referencing is the Config Mgr Client.The Client is successfully distributed to this DP.

 

Has anyone got any ideas why this is happening please?

 

Some things I have tried so far :

- Validating the package again to this DP (successful)

- Testing a reimage manually which works fine, if the package was an issue it would be highlighted?

- I have had mixed results when testing a different Task sequence that uses the Config Mgr Client, sometimes it works and gets passed this stage, sometimes it doesn't - so its been hard to pinpoint the issue.

- Tried changing the "Rerun" behaviour to "always redeploy"- I have been able to image remotely at a different site that uses a different DP but the same Config Mgr Client.

- I need to read up more on Boundry Groups, however the config I see looks OK and worked fine on our last automated deployment.

- I have logged into one of the devices, and watched this in Software Centre and it stays stuck on Downloading.

- I have tried running a Config Mgr Client repair

Edited August 20, 2024 by Newb
layout

[Sibrows]

It’s a few years since I’ve fought with SCCM this sounds like the content wasn't distributed before the package was assigned.

You will have to start from scratch with the package.

[Newb]

Hi

 

Thank you for the response.

 

I have been able to manually reimage a device, if this was the case wouldnt it have shown the error then?

 

When you say start again, as in removing the package and redistributing to that DP?

 

Thank you

[Sibrows]

It’s a few years since I’ve had reason to troubleshoot this kind of issue but I’ve seen issues like this when things when things aren’t done in 100% the right order.

- Create package

- Distribute package

- Assign package

I’ve previously burnt hours trying to troubleshoot this kind of thing.

There is nothing stopping you creating an identical package with a different source folder to avoid waiting any effort you’ve already put in (as I’m keen to emphasise it’s 3 years since I’ve pushed anything out using SCCM).

[junz]

Had this error and turned out the IP's my devices were getting were not in the boundary group.

 

Worth double checking this if you haven't already.

[Newb]

Thats great, thank you both for the suggestions.

 

I will look into the boundry groups as I have read a few similar articles mention this too.

 

I will also look into creating another package as mentioned above too.

Edited August 20, 2024 by Newb

[gaz350b]

We had a similar issue we had to run a command on sql to clear the error. Tech found the fix.

 

Sadly I’m off today and he’s also off sick!

 

Not much help but might get you on the right path.