question

FranzSchenk-2502 avatar image
0 Votes"
FranzSchenk-2502 asked FranzSchenk-2502 commented

Can't redeploy systems

Have SCCM 2103. And (most probably since the SCCM Upgrade), we are unable to redeploy systems.

  • The existing System is deleted in SCCM, as well as in AD

  • The MAC address of the NIC is listened in the Hierarchy settings of the site (Duplicate Hardware identifiers)

  • The TS is deployed to "all unknown computers to "only media and PXE" and with the option "always rerun program"

  • Have executed "clear required pxe deployments" on the "all unknown computers" collection. Don't know what this is doing. But the TS deployment is not deleted, and the problem is not solved with that.

When PXE booting the client, we get "PXE-E16 - no valid offer received". Ans SMSPXE.LOG has the following entry:

Client Boot TS reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="2046820353" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><TSInfo DeploymentID="SLA20052" PkgID="SLA000C4" BootImageID="SLA0005B" Architecture="9" Required="1" AlreadyRun="1" ForPXE="1" Disabled="0" PackageAvailable="1" FutureAvailability="0" Expired="0" UEFIArchitectureMismatch="0" ArchitectureMismatch="0"/></ClientIDReply>

"Already Run="1"" will be our problem. But have no idea where SCCM is getting this information, because the previousely deployed device is deleted in SCCM.

Thank you in advance for any advice

Franz





mem-cm-osd
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

HanyunZhu-MSFT avatar image
0 Votes"
HanyunZhu-MSFT answered FranzSchenk-2502 commented

Hi @FranzSchenk-2502,

Thanks for posting in Microsoft Q&A forum.

We could check two options first:
1) Have you distribute both x86 and x64 boot image. It will not work properly if they are not both available.
2) Confirm that DHCP is configured correctly, or it may provide a wrong gateway for the device.

If there is no problem with the above checks, we could try the following solutions:
1) Verify IP Helpers
If the DHCP server or WDS/PXE-enabled DP is not in the same subnet or VLAN as the client computer, they will not see or hear the PXE request broadcast from the client. Therefore, the server will not respond to PXE requests.
For the detailed steps, please refer to this article:
https://docs.microsoft.com/en-us/troubleshoot/mem/configmgr/troubleshoot-pxe-boot-issues#solution-1-verify-ip-helpers
2) Reinstall PXE
In many cases, errors during installation or configuration are the cause by PXE boot problems and reinstalling PXE may be the most effective and least time-consuming solution.
To do it, please follow the steps in below link:
https://docs.microsoft.com/en-us/troubleshoot/mem/configmgr/troubleshoot-pxe-boot-issues#solution-2-reinstall-pxe-use-only-if-solution-1-didnt-resolve-the-issue

Hope the information can help you.


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.


· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @HanyunZhu-MSFT

Thank you for your explications. Probably, my question was not clear: We do not have a PXE boot problem. We can deploy new systems over PXE. And we can even deploy existing systems when we delete them in SCCM (normal, always required), and then add them manually with the MAC address and add them to a collection on which we deployed the TS.

The problem is that SCCM does not recognize the previousely deployed and then deleted systems in SCCM as "unknown systems". Like I wrote in my initial question, the difference in the smspxe.log is the flag AlreadyRun="1". This flag is logged when PXE booting a system that was deployed before (but deleted in SCCM). When we boot a new system that was never deployed before, this flag is set to AlreadyRun="0", and the system starts the TS.
This flag makes the difference, despite we have configured the TS deployment with the option "always rerun".

0 Votes 0 ·
HanyunZhu-MSFT avatar image
0 Votes"
HanyunZhu-MSFT answered FranzSchenk-2502 commented

Hi,

Thanks for your feedback, I noticed that there was an error "PXE-E16 - no valid offer received" so that I inferred from the beginning that it might be a PXE problem.

To clear the flag AlreadyRun="1", we could right-click the device object and choose Clear Required PXE Deployments.
123419-1.png
Or do it on the collection the device object is in.
For more details, please check:
https://docs.microsoft.com/en-us/powershell/module/configurationmanager/clear-cmpxedeployment?view=sccm-ps


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.


1.png (76.1 KiB)
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,

Like I wrote in my initial question, this was one of the first things that we already tried. The "Alreadyrun=1" flag is not cleared with this action. And I have no idea why this flag prevents a new deployment, because the TS deployment has the parameter "always rerun program" set.

0 Votes 0 ·