OSD Task Sequence issues after recovering Configuration Manager 2403 Secondary Site

Bojan Zivkovic 486 Reputation points
2024-12-21T17:13:23.1933333+00:00

Hi, I had irreparable OS failure on Configuration Manager 2403 Secondary Site Server and managed to successfully recover Secondary Site on new server. Having redistributed content to new server I have complaints from Help Desk team that OSD Task Sequence fails at Apply Operating System step:

User's image

Also, they were not asked to enter password here as they always were:

User's image

They say all content referenced in this OSD TS has been redistributed to new server (boot image, operating system image, driver packages ...).

Are there any post-recovery tasks not documented needed to be done here to rectify this problem? Thanks in advance.

Microsoft Configuration Manager
0 comments No comments
{count} votes

4 answers

Sort by: Most helpful
  1. Simon Ren-MSFT 37,401 Reputation points Microsoft Vendor
    2024-12-23T02:31:11.7166667+00:00

    Hi,

    Hope everything is going well.

    The error 0x80070002 = The system cannot find the file specified. Kindly help check if the distribute point of the Secondary Site is working well.

    1,As with all task sequence issues and troubleshooting, it's firstly recommended to examine the smsts.log on the target system.

    Please refer to the following article:

    SCCM: How to copy SMSTS.log when a Task Sequence fails

    Note: This is non-Microsoft link, just for your reference.

    2,==>Also, they were not asked to enter password here as they always were:

    Just go to administration > Distribution Points on the right-hand side select the Distribution point you're imaging from, click on the PXE tab and confirm if the option is selected "Requires a password when computers use PXE".

    3,We can also create a new task sequence that is the same as before, and then distribute and deploy it. Verify whether the new task sequence can work or not.

    4,We can also monitor Secondary Site Recovery process by reviewing the ConfigMgrPrereq.log and ConfigMgrSetup.log located on root drive of secondary site server, and confirm if the secondary site recovery is complete successfully.

    Hope it helps. 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.

    0 comments No comments

  2. Bojan Zivkovic 486 Reputation points
    2024-12-23T12:11:37.8466667+00:00

    This is status message:

    The task sequence execution engine failed executing the action (Apply Operating System) in the group (Install Operating System) with the error code 2147942402

    Action output: ... \e\src\client\OsDeployment\ApplyOS\installimage.cpp,1915)

    Apply(), HRESULT=80070002 (D:\dbs\sh\cmgm\0502_134106\cmd\e\src\client\OsDeployment\ApplyOS\installimage.cpp,2158)

    installer.install(), HRESULT=80070002 (D:\dbs\sh\cmgm\0502_134106\cmd\e\src\client\OsDeployment\ApplyOS\installimage.cpp,2233)

    ReleaseSource() for C:_SMSTaskSequence\Packages\US2003BF.

    The user tries to release a source directory C:_SMSTaskSequence\Packages\US2003BF that is either already released or we have not connected toit.

    Http result: 404

    SendResourceRequest() failed. 80190194

    Download() failed. 80190194.

    Failed to resolve pkg source

    Installation of image 1 in package US2003BF failed to complete..

    The system cannot find the file specified. (Error: 80070002; Source: Windows)

    InstallImage( g_InstallPackageID, g_ImageIndex, targetVolume, ImageType_OS, g_ConfigPackageID, g_ConfigFileName, bOEMMedia, g_RunFromNet ), HRESULT=80070002 (D:\dbs\sh\cmgm\0502_134106\cmd\e\src\client\OsDeployment\ApplyOS\applyos.cpp,523). The operating system reported error 2147942402: The system cannot find the file specified.

    NOTE: https://DPFQDN/NOCERT_SMS_DP_SMSPKG$/us2003bf (Windows 10 OS Image) returns:
    User's image

    On other hand, OS for Win 11 image is there:
    User's image

    I have redistributed us2003bf successfully to this DP (Secondary Site Server) but it seems it is still somehow missing in NOCERT_SMS_DP_SMSPKG$.

    0 comments No comments

  3. Bojan Zivkovic 486 Reputation points
    2024-12-24T15:19:16.9033333+00:00

    Sorted out.

    0 comments No comments

  4. Simon Ren-MSFT 37,401 Reputation points Microsoft Vendor
    2024-12-25T06:02:02.2533333+00:00

    Hi,

    Thanks for your information.

    Kindly review the DistMgr.log, PkgXferMgr.log and SMSDPProv.log on the site (primary/secondary) where the DP resides to ensure that us2003bf (Windows 10 OS Image) was distributed successfully. For more detailed troubleshooting steps, refer to:

    Troubleshoot content distribution

    If the problem is solved, could you please share your solution to help more people?

    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.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.