yo_bee
asked on
SCCM 2012 PXE not working
I have a new SCCM 2012 to replace my SCCM 2007.
I have the new server setup as a Site Server, DP that is also host PXE.
When I add an unknown machine to the new system and try to PXE boot I get the follow error.
In the SMSPXE.log it does show that it is connecting to the new SCCM 2012 for a PXE, but it thinks it has no advertisement.
Client boot action reply: <ClientIDReply><Identifica tion Unknown="0" ItemKey="16777220" ServerName=""><Machine><Cl ientID/><N etbiosName /></Machin e></Identi fication>< PXEBootAct ion LastPXEAdvertisementID="" LastPXEAdvertisementTime=" " OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDRe ply>
SMSPXE 5/5/2016 5:05:51 PM 3252 (0x0CB4)
XX:XX:XX:XX:XX:XX, 555F0942-FC19-099C-6976-7E 1AF351137A : no advertisements found SMSPXE 5/5/2016 5:05:51 PM 3252 (0x0CB4)
Client boot action reply: <ClientIDReply><Identifica tion Unknown="0" ItemKey="16777220" ServerName=""><Machine><Cl ientID/><N etbiosName /></Machin e></Identi fication>< PXEBootAct ion LastPXEAdvertisementID="" LastPXEAdvertisementTime=" " OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDRe ply>
SMSPXE 5/5/2016 5:05:51 PM 3240 (0x0CA8)
XX:XX:XX:XX:XX:XX, 555F0942-FC19-099C-6976-7E 1AF351137A : no advertisements found SMSPXE 5/5/2016 5:05:51 PM 3240 (0x0CA8)
Client boot action reply: <ClientIDReply><Identifica tion Unknown="0" ItemKey="16777220" ServerName=""><Machine><Cl ientID/><N etbiosName /></Machin e></Identi fication>< PXEBootAct ion LastPXEAdvertisementID="" LastPXEAdvertisementTime=" " OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDRe ply>
SMSPXE 5/5/2016 5:05:51 PM 3248 (0x0CB0)
XX:XX:XX:XX:XX:XX, 555F0942-FC19-099C-6976-7E 1AF351137A : no advertisements found SMSPXE 5/5/2016 5:05:51 PM 3248 (0x0CB0)
Client boot action reply: <ClientIDReply><Identifica tion Unknown="0" ItemKey="16777220" ServerName=""><Machine><Cl ientID/><N etbiosName /></Machin e></Identi fication>< PXEBootAct ion LastPXEAdvertisementID="" LastPXEAdvertisementTime=" " OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDRe ply>
SMSPXE 5/5/2016 5:05:51 PM 3244 (0x0CAC)
XX:XX:XX:XX:XX:XX, 555F0942-FC19-099C-6976-7E 1AF351137A : No boot action. Aborted. SMSPXE 5/5/2016 5:05:51 PM 3240 (0x0CA8)
XX:XX:XX:XX:XX:XX, 555F0942-FC19-099C-6976-7E 1AF351137A : no advertisements found SMSPXE 5/5/2016 5:05:51 PM 3244 (0x0CAC)
XX:XX:XX:XX:XX:XX, 555F0942-FC19-099C-6976-7E 1AF351137A : Not serviced. SMSPXE 5/5/2016 5:05:51 PM 3240 (0x0CA8)
XX:XX:XX:XX:XX:XX, 555F0942-FC19-099C-6976-7E 1AF351137A : No boot action. Aborted. SMSPXE 5/5/2016 5:05:51 PM 3252 (0x0CB4)
XX:XX:XX:XX:XX:XX, 555F0942-FC19-099C-6976-7E 1AF351137A : Not serviced. SMSPXE 5/5/2016 5:05:51 PM 3252 (0x0CB4)
XX:XX:XX:XX:XX:XX, 555F0942-FC19-099C-6976-7E 1AF351137A : No boot action. Aborted. SMSPXE 5/5/2016 5:05:51 PM 3244 (0x0CAC)
XX:XX:XX:XX:XX:XX, 555F0942-FC19-099C-6976-7E 1AF351137A : Not serviced. SMSPXE 5/5/2016 5:05:51 PM 3244 (0x0CAC)
XX:XX:XX:XX:XX:XX, 555F0942-FC19-099C-6976-7E 1AF351137A : No boot action. Aborted. SMSPXE 5/5/2016 5:05:51 PM 3248 (0x0CB0)
XX:XX:XX:XX:XX:XX, 555F0942-FC19-099C-6976-7E 1AF351137A : Not serviced. SMSPXE 5/5/2016 5:05:51 PM 3248 (0x0CB0)
Client boot action reply: <ClientIDReply><Identifica tion Unknown="0" ItemKey="16777220" ServerName=""><Machine><Cl ientID/><N etbiosName /></Machin e></Identi fication>< PXEBootAct ion LastPXEAdvertisementID="" LastPXEAdvertisementTime=" " OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDRe ply>
SMSPXE 5/5/2016 5:05:57 PM 3248 (0x0CB0)
XX:XX:XX:XX:XX:XX, 555F0942-FC19-099C-6976-7E 1AF351137A : no advertisements found SMSPXE 5/5/2016 5:05:57 PM 3248 (0x0CB0)
I have tried restarting the WDS Service, Rebooting the Server, Removing the device and re-adding to SCCM,
It is part of a collection that has an advertisement assigned to it.
Not sure where I am going wrong here.
I have the new server setup as a Site Server, DP that is also host PXE.
When I add an unknown machine to the new system and try to PXE boot I get the follow error.
In the SMSPXE.log it does show that it is connecting to the new SCCM 2012 for a PXE, but it thinks it has no advertisement.
Client boot action reply: <ClientIDReply><Identifica
SMSPXE 5/5/2016 5:05:51 PM 3252 (0x0CB4)
XX:XX:XX:XX:XX:XX, 555F0942-FC19-099C-6976-7E
Client boot action reply: <ClientIDReply><Identifica
SMSPXE 5/5/2016 5:05:51 PM 3240 (0x0CA8)
XX:XX:XX:XX:XX:XX, 555F0942-FC19-099C-6976-7E
Client boot action reply: <ClientIDReply><Identifica
SMSPXE 5/5/2016 5:05:51 PM 3248 (0x0CB0)
XX:XX:XX:XX:XX:XX, 555F0942-FC19-099C-6976-7E
Client boot action reply: <ClientIDReply><Identifica
SMSPXE 5/5/2016 5:05:51 PM 3244 (0x0CAC)
XX:XX:XX:XX:XX:XX, 555F0942-FC19-099C-6976-7E
XX:XX:XX:XX:XX:XX, 555F0942-FC19-099C-6976-7E
XX:XX:XX:XX:XX:XX, 555F0942-FC19-099C-6976-7E
XX:XX:XX:XX:XX:XX, 555F0942-FC19-099C-6976-7E
XX:XX:XX:XX:XX:XX, 555F0942-FC19-099C-6976-7E
XX:XX:XX:XX:XX:XX, 555F0942-FC19-099C-6976-7E
XX:XX:XX:XX:XX:XX, 555F0942-FC19-099C-6976-7E
XX:XX:XX:XX:XX:XX, 555F0942-FC19-099C-6976-7E
XX:XX:XX:XX:XX:XX, 555F0942-FC19-099C-6976-7E
Client boot action reply: <ClientIDReply><Identifica
SMSPXE 5/5/2016 5:05:57 PM 3248 (0x0CB0)
XX:XX:XX:XX:XX:XX, 555F0942-FC19-099C-6976-7E
I have tried restarting the WDS Service, Rebooting the Server, Removing the device and re-adding to SCCM,
It is part of a collection that has an advertisement assigned to it.
Not sure where I am going wrong here.
For PXE clean installs, you are probably missing the identifiers in AD that allow WDS to know the device. The easiest way to solve that is to have an advertisement for the two "unknown" devices in SCCM. At the time they are PXE booting, the agent us not yet running so the device is genuinely not known.
ASKER
The TS is also advertised to All Unknown Devices as well with no luck.
ASKER
I also added the device manually as I did previously in SCCM 2007
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
resolved it myself