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.

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

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

Hi, Thank you for the reply. I had a look into the smsts log file and compared a working vs non working device when remote imaging. It shows : "Error. Received 0x80072ee7 from WinHttpSendRequest." "unknown host (gethostbyname failed)" "Sending with winhttp failed; 80072ee7" After a search online, looks like server name or address could not be resolved? (unknown host (gethostbyname failed) : 80072ee7 Failed task sequence 0x80004005 - Microsoft Q&A) These warnings are actually also on the device that "worked" with remote imaging but cleared itself, whereas this one repeated the error. The strange thing is though, it then seems to carry on and completes the next step of partitioning the disk (process completed with error code 0) , which matches the "working" device with no further warnings or errors. I cant see anything else relating to a failure although I saw it fail in person, is there another log I can look into? Another thing that was strange was in the logs the time went from 11:49 to 20:52 (although this was not the correct time - I am not sure where it pulls the time/date from - only that in the log it mentioning setting time zone just before this occured) Once this failed, we tried manually kicking off the device F12 and PXE booted which worked fine.

We run Server 2019 on site and usually image using PCs by PXE boot. We have an issue now where we need to image a lot of PCs and remote imaging would be really useful. I have tested remote imaging but only seem to be getting a success rate of around 50% at the best of times. I created a collection with the test devices in, deploy a required task sequence to this collection and make this available to media and PXE and clients and put the start as asap and I then set an expiry date to ensure the TS doesn’t rerun for a short time after. I also put the action to always rerun. I then check the TS log in SCCM and can see the devices receive the TS deployment and in my first test it actually kicked off 8 devices however 4 then failed shortly after. Is there any advice? Or has anyone experienced similar? Is it likely to be issues my with setup above or possible network issues? I have copied some logs from one which successfully imaged and one which failed but haven’t managed to review them yet. Thanks in advance