SCCM Task Sequence Fails with errors: 80072ee2, 80072efe, 80070002

Rodolfo Pena Cedeno 26 Reputation points
2022-11-28T08:42:55.51+00:00

Dear Brothers and Sisters of the IT World,

I trust this finds you and your family very well.

ALL THE Screenshots can be found in the attached file (Comments below). Sorry but i couldn't paste the pictures or attache the file in the question because i was always getting an error.

Please find the general info for the analysis below!

  • Please find the SCCM version below: Pdf File below
  • Concerning the OSD Image, We haven’t checked the following, but, everything works fine for more than 40 models, therefore, we are not planning to active it: Pdf File below
  • The Network Access account is working fine because as I said before, with any old model everything works properly.
  • The communication info: Pdf File below
  • We haven’t configured Enhanced HTTP yet; we are planning to do it next year.

Server info: Pdf File below

  • In our company we have SCCM and we are managing more than 40 Dell models. That means that we have 40 driver packages in SCCM and all the models are able to be reimaged without facing any issues. Nevertheless, we have got 3 new DELL models and after creating and distributing the driver’s packages, we are not able to install the task sequence because of multiple errors.
  • We tested with two OLD models to verify if there was a problem with the TS and everything works as a charm…
  • What we did to solve this incident was creating the following variables in the TS:
    SMSTSDownloadRetryCount
    SMSTSDownloadRetryDelay

More info can be found here about this:
https://msendpointmgr.com/2014/06/25/downloadfilewithranges-failed-80072ee2-on-packages-in-configmgr-2012-r2/

Thx to this fix, now the TS step “Apply Operating system” has been properly applied.

However, we still don’t understand why we had to do this workaround for these new models when everything works fine with the other 40. Can anyone answer this?

  • We thought that everything was going to be ok after the Apply OS Step was successful, however, now the applying driver Package is giving us Errors…
  • At first, we created and distributed the Driver Packages without the following options since more than 30 driver packages works without it:
  • But since the drivers were not being installed, we activated it: Pdf File below
  • We tried to install the Drivers with and Without DISM: Pdf File below
  • And this is the error that we were getting: Pdf File below
  • When we accessed the Shared, we found that the package PKG00109 source was not present in the Shared: Pdf File below
  • But we verified and the package was properly distributed.
  • These are the errors that we are getting now:
  • As you can see, the Network Access account is working properly.

Can someone please help us understand what is happening in our environment? First, it was the Apply OS Step and now the Apply driver step.

Thank you, best regards, and have an amazing day.

Peace

Microsoft Configuration Manager Deployment
Microsoft Configuration Manager Deployment
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Deployment: The process of delivering, assembling, and maintaining a particular version of a software system at a site.
907 questions
Microsoft Configuration Manager

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Simon Ren-MSFT 30,506 Reputation points Microsoft Vendor
    2022-11-29T08:44:59.293+00:00

    Hi,

    The error 80072ee2 means "The operation timed out". The error 0x80070057 means "The parameter is incorrect".

    1,==>When we accessed the Shared, we found that the package PKG00109 source was not present in the Shared.
    But we verified and the package was properly distributed.

    Do you have multiple DPs in your environment? If yes, please make sure you have distributed the package PKG00109 to the DPs you want. Also make sure the boundary groups are configured correctly and you have associated correct DPs and MPs to your boundary groups.

    2,If possible, we can try to remove the driver package from the distribution points, and then create a new driver package and task sequence for test purpose.

    Thanks for your time. Have a nice day!

    Best regards,
    Simon

    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

  2. Rodolfo Pena Cedeno 26 Reputation points
    2022-11-30T10:06:34.253+00:00

    Hi Simon,

    I hope u r doing good today.

    Thank you for your help and support.

    What we don't understand is:

    • We take an old model, we reimage it and the Steps (Apply OS and Apply driver pkg) are executed very quickly and without any issue.
    • We try with the new model and only in those two steps (Apply OS and Apply driver pkg), it takes like 20 more times to apply those two steps. And it only works at the moment because we used the variable as explained before.

    We can confirm that the CPU and the memory are largely available and that this is not the related to the incident.

    How is it possible that this is only been faced with this new model?

    Thank you very much again for all your time.

    Have an amazing day,

    Best regards,

    Peace