PXE boot almost working - HELP!

[rik1471]

After several difficult weeks I have finally reached the tantilising stage of successfully PXE booting my SCCM clients for OS deployment.

 

I am at the stage where the client responds to an F12 request; the SCCM server responds and the PXE log file shows communication.

 

The problem I have is the advertisment just won't start. Initially it wouldn't detect unknown machines so I created a manual association.

 

What is very strange, however, is the way it just sits there, looping around and never getting beyond the boot screen.

 

The PXE log file shows the following, if I were to leave it the bottom line would just keep repeating itself with my client not passing the stage: “Contacting Server 192.168.210.240...........”:

 

Any help would be greatly appreciated.

 

 

 

Getting boot action for unknown machine: item key: 3 smspxe 1/11/2010 3:55:06 PM 428 (0x01AC)

 

Executing GetBootAction(3, SRFT-SCCM) smspxe 1/11/2010 3:55:06 PM 428 (0x01AC)

 

vLastPXEAdvertisementID is NULL smspxe 1/11/2010 3:55:06 PM 428 (0x01AC)

 

vLastPXEAdvertisementTime is NULL smspxe 1/11/2010 3:55:06 PM 428 (0x01AC)

 

GetBootAction: MAC: SMBIOS: SMSID:ad3377f2-0c05-4804-880c-943cd9471e40 LastAdv: smspxe 1/11/2010 3:55:06 PM 428 (0x01AC)

 

Advertisement results: OfferId:SRF20001 OfferTime:11/01/2010 15:53:00 PackageID:SRF00007 BootImageID:SRF00002 PackageVer: PackagePath:\\SRFT-SCCM\SMSPKGE$\SRF00002\ Mandatory:1 smspxe 1/11/2010 3:55:06 PM 428 (0x01AC)

 

Advertisement results: OfferId:SRF20001 OfferTime:11/01/2010 15:53:00 PackageID:SRF00007 BootImageID:SRF00002 PackageVer: PackagePath:\\SRFT-SCCM\SMSPXEIMAGES$\SMSPKG\SRF00002\ Mandatory:1 smspxe 1/11/2010 3:55:06 PM 428 (0x01AC)

 

ProcessDatabaseReply: Using Advertisement found in DB: SRF20001 smspxe 1/11/2010 3:55:06 PM 428 (0x01AC)

 

[192.168.210.240:4011] Recv From:[010.137.065.001:68] Len:299 23bef2c smspxe 1/11/2010 3:55:26 PM 2692 (0x0A84)

 

MAC=00:25:B3:D3:60:83 SMBIOS GUID=EDCD59D4-09E1-11DE-BBDA-B3D360830025 > Device has been accepted. smspxe 1/11/2010 3:55:26 PM 2696 (0x0A88)

 

[192.168.210.240:4011] Recv From:[010.137.065.001:68] Len:299 23bffe4 smspxe 1/11/2010 3:55:45 PM 2692 (0x0A84)

 

MAC=00:25:B3:D3:60:83 SMBIOS GUID=EDCD59D4-09E1-11DE-BBDA-B3D360830025 > Device has been accepted. smspxe 1/11/2010 3:55:45 PM 3288 (0x0CD8)

 

[192.168.210.240:4011] Recv From:[010.137.065.001:68] Len:299 23c109c smspxe 1/11/2010 3:56:05 PM 2692 (0x0A84)

 

MAC=00:25:B3:D3:60:83 SMBIOS GUID=EDCD59D4-09E1-11DE-BBDA-B3D360830025 > Device has been accepted. smspxe 1/11/2010 3:56:05 PM 3276 (0x0CCC)

 

[192.168.210.240:4011] Recv From:[010.137.065.001:68] Len:299 23c2154 smspxe 1/11/2010 3:56:25 PM 2692 (0x0A84)

 

[192.168.210.240:4011] Recv From:[010.137.065.001:68] Len:299 23c320c smspxe 1/11/2010 3:56:45 PM 2692 (0x0A84)

 

[192.168.210.240:4011] Recv From:[010.137.065.001:68] Len:299 23c42c4 smspxe 1/11/2010 3:57:04 PM 2692 (0x0A84)

 

[192.168.210.240:4011] Recv From:[010.137.065.001:68] Len:299 23c537c smspxe 1/11/2010 3:57:24 PM 2692 (0x0A84)

 

[192.168.210.240:4011] Recv From:[010.137.065.001:68] Len:299 23c6434 smspxe 1/11/2010 3:57:44 PM 2692 (0x0A84)

 

[192.168.210.240:4011] Recv From:[010.137.065.001:68] Len:299 23c74ec smspxe 1/11/2010 3:58:04 PM 2692 (0x0A84)

 

[192.168.210.240:4011] Recv From:[010.137.065.001:68] Len:299 23c85a4 smspxe 1/11/2010 3:58:23 PM 2692 (0x0A84)

 

[192.168.210.240:4011] Recv From:[010.137.065.001:68] Len:299 23c965c smspxe 1/11/2010 3:58:43 PM 2692 (0x0A84)

 

[192.168.210.240:4011] Recv From:[010.137.065.001:68] Len:299 23ca714 smspxe 1/11/2010 3:59:03 PM 2692 (0x0A84)

 

[192.168.210.240:4011] Recv From:[010.137.065.001:68] Len:299 23cb7cc smspxe 1/11/2010 3:59:23 PM 2692 (0x0A84)

 

[192.168.210.240:4011] Recv From:[010.137.065.001:68] Len:299 23cc884 smspxe 1/11/2010 3:59:43 PM 2692 (0x0A84)

 

[192.168.210.240:4011] Recv From:[192.168.210.240:9000] Len:274 23cd93c smspxe 1/11/2010 3:59:49 PM 2692 (0x0A84)

[rik1471]

Managed to resolve this one (I am moving quickly now ) by changing the boot media to x86.

 

Now I am getting the error:

 

BOOTMGR IS MISSING

PRESS CTRL&ALT&DEL

 

Any advice?

[Vida Aceves]

Just a quick message to say that I have finally got this working.

 

Thank you for your advice.

 

I now have another issue, although I suspect this is easier to resolve.

 

The task sequence bombs out with the following error:

 

It is not supported to deploy an x86 architecture OS from a amd64 boot image ApplyOperatingSystem 1/14/2010 11:03:59 AM 1432 (0x0598)

 

Hello,

How did you resolve the problem? I am receiving these errors? HELP

WARNING: _SMSTSSiteSigningCertificate Not Set. This might cause client failures in native mode. smspxe 2/9/2010 2:57:44 PM 6560 (0x19A0)

WARNING: _SMSTSRootCACerts Not Set. This might cause client failures in native mode. smspxe 2/9/2010 2:57:44 PM 6560 (0x19A0)

WARNING: _SMSTSCertStoreName Not Set. This might cause client failures in native mode. smspxe 2/9/2010 2:57:44 PM 6560 (0x19A0)

WARNING: _SMSTSCertSelection Not Set. This might cause client failures in native mode. smspxe 2/9/2010 2:57:44 PM 6560 (0x19A0)

[Peter van der Woude]

WARNING: _SMSTSSiteSigningCertificate Not Set. This might cause client failures in native mode. smspxe 2/9/2010 2:57:44 PM 6560 (0x19A0)

WARNING: _SMSTSRootCACerts Not Set. This might cause client failures in native mode. smspxe 2/9/2010 2:57:44 PM 6560 (0x19A0)

WARNING: _SMSTSCertStoreName Not Set. This might cause client failures in native mode. smspxe 2/9/2010 2:57:44 PM 6560 (0x19A0)

WARNING: _SMSTSCertSelection Not Set. This might cause client failures in native mode. smspxe 2/9/2010 2:57:44 PM 6560 (0x19A0)

 

These are not errors, but just warnings. They could cause failures, if you are running in Native Mode.

 

Besides this do you get other errors or notification?