Why Image TS PXE successfully but failed from Software Center

Iris 1 Reputation point
2022-06-20T19:33:08.33+00:00

Why Image TS PXE successfully but failed from Software Center.
When running from Software center, all steps running well (same as PXE):
Install Operating system
Apply Device Drivers
Setup Operating System

But after restarting multiple times then it cannot boot to Windows but goes to PXE step, if disabling Network boot then stops at the Boot menu.
Have tried VM and PCs, same thing.
Please advise. Thanks.

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.
1,030 questions
Microsoft Configuration Manager
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Simon Ren-MSFT 38,676 Reputation points Microsoft Vendor
    2022-06-21T08:35:38.327+00:00

    Hi,

    Thanks for posting in Microsoft MEM Q&A forum.

    1,Can we look at the smsts.log and find any useful information?

    2,May we know what version of MECM you are using and what version of Windows you are deploying? Here is a similar thread for your reference, the solution is to upgrade the ConfigManager client agent version to match the version of MECM.
    ConfigManager unable to perform OSD that starts from Software Center, on machine with TPM, using HTTPS

    Hope it helps. Thanks for your time.

    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. Iris 1 Reputation point
    2022-07-12T19:49:39.677+00:00

    Hi Simon,

    220048-bcdboot1.png220053-bcdboot2.png

    Can you see the attached 2 images? They are from the smsts.log.
    We got bcdboot errors from the smsts.log files:
    .\bcdboot.exe is not recognized as the name of a cmdlet, function,... (please see the first image: bcdboot1.png)
    (Not sure why this is a problem when running image TS in Software Center, but working fine from PXE)
    Then we modified a bit the TS, and added a PS script:

    Set drive letter S:

    Add-PartitionAccessPath -DiskNumber 0 -PartitionNumber 1 -AccessPath S:

    Create Boot files using BCDBoot.

    Start-Process -FilePath "C:\Windows\System32\bcdboot.exe" -ArgumentList "C:\Windows /s s: /f UEFI"

    then Remove drive letter S.

    Although it still shows error code 0x000000C1 at above step (Please find the second image bcdboot2.png for details), at least now it can bring us to the login window (connected to our domain, which is correct). How to fix the "Unexpected token '\bcdboot.exe' in expression or statement"?

    Is this the right way to go? any suggestion? Thanks.
    Iris

    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.