Troubleshooting SCCM Part VII .......... OSD .... Part I

아티클
09/20/2013

Part I : PXE boot

Many have been asking to write a blog on how to tracks the logs for OSD so here it is . It is in two parts. Part I is PXE boot and Part II is After the Pxe Boot to Full blown OS. Since we are already in 2012 and 2007 has become obsolete, I will be taking 2012 logs to explain

Before we start troubleshooting OSD with Configuration Manager I would always say it saves a lot of time many times if the pre-requisites are to be checked, Especially if you find client is not PXE booting or if it fails after PXE boots immediately .

If the client is not PXE booting checking the SMSPXE.log on the server where you have the WDS and confirm if the WDS is initialized. You could start the WDS service and check the log flow.

This is how it should be

You would see Provider loading
It will show you the boot images in the WDS which will be opened ,files extracted and copied to boot folders which constitute the boot files for the WDS
Then you will find PXE provider finished loading

================= PXE Provider loaded. ===================== SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

Machine is running Windows Longhorn. (NTVersion=0X602, ServicePack=0) SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

Cannot read the registry value of MACIgnoreListFile (00000000) SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

MAC Ignore List Filename in registry is empty SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

Begin validation of Certificate [Thumbprint D04F5BDFFB9390BFEF89053A315F9D700462DAF5] issued to '02d1e460-a438-493c-b6c7-583601b1e087' SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

Completed validation of Certificate [Thumbprint D04F5BDFFB9390BFEF89053A315F9D700462DAF5] issued to '02d1e460-a438-493c-b6c7-583601b1e087' SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

PXEClientKey certificate valid. SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

Initializing PXEPerfObject. SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

Failed to get logging settings for 'ccmperf' from Registry (80070002) SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

Could not load logging configuration for component ccmperf. Using default values. SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

Client is set to use HTTPS when available. The current state is 224. SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

CLibSMSMessageWinHttpTransport::Send: URL: CM2012SP1.sudilab.com:80 GET /SMS_MP/.sms_aut?MPKEYINFORMATIONEX SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

CLibSMSMessageWinHttpTransport::Send: URL: CM2012SP1.sudilab.com:80 CCM_POST /ccm_system/request SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>

SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

Adding LAB00004.5 SMSPXE 20-09-2013 23:43:00 7068 (0x1B9C)

Adding LAB00005.3 SMSPXE 20-09-2013 23:43:24 7068 (0x1B9C)

Found new image LAB00004 SMSPXE 20-09-2013 23:43:45 7068 (0x1B9C)

Opening image file C:\RemoteInstall\SMSImages\LAB00004\boot.LAB00004.wim SMSPXE 20-09-2013 23:43:45 7068 (0x1B9C)

Found Image file: C:\RemoteInstall\SMSImages\LAB00004\boot.LAB00004.wim

PackageID: LAB00004

ProductName: Microsoft® Windows® Operating System

Architecture: 0

Description: Microsoft Windows PE (x86)

Version:

Creator:

SystemDir: WINDOWS

SMSPXE 20-09-2013 23:43:45 7068 (0x1B9C)

Closing image file C:\RemoteInstall\SMSImages\LAB00004\boot.LAB00004.wim SMSPXE 20-09-2013 23:43:45 7068 (0x1B9C)

Creating BCD store: C:\RemoteInstall\SMSTemp\2013.09.20.23.43.45.01.{C48BA2BD-1E88-443D-9A6C-B06835F1BABF}.boot.bcd SMSPXE 20-09-2013 23:43:46 7068 (0x1B9C)

StoreFilePath: \??\C:\RemoteInstall\SMSTemp\2013.09.20.23.43.45.01.{C48BA2BD-1E88-443D-9A6C-B06835F1BABF}.boot.bcd SMSPXE 20-09-2013 23:44:02 7068 (0x1B9C)

Skipping creation of variables file for image LAB00004 SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\PXE\pxeboot.com to install queue SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\PXE\pxeboot.n12 to install queue SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\PXE\bootmgr.exe to install queue SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

File C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\PXE\bootmgr.exe has version info: 6.2.9200.16384 SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

File C:\RemoteInstall\SMSBoot\x86\bootmgr.exe has version info: 6.2.9200.16384 SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\PXE\wdsnbp.com to install queue SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\PXE\abortpxe.com to install queue SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\PXE\wdsmgfw.efi to install queue SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

File C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\PXE\wdsmgfw.efi has version info: 6.2.9200.16384 SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

File C:\RemoteInstall\SMSBoot\x86\wdsmgfw.efi has version info: 6.2.9200.16384 SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\EFI\bootmgfw.efi to install queue SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

File C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\EFI\bootmgfw.efi has version info: 6.2.9200.16384 SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

File C:\RemoteInstall\SMSBoot\x86\bootmgfw.efi has version info: 6.2.9200.16384 SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\Fonts\segmono_boot.ttf to install queue SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Copying font file C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\Fonts\segmono_boot.ttf->C:\RemoteInstall\Boot\Fonts\segmono_boot.ttf.

SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\Fonts\segoe_slboot.ttf to install queue SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Copying font file C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\Fonts\segoe_slboot.ttf->C:\RemoteInstall\Boot\Fonts\segoe_slboot.ttf.

SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\Fonts\segoen_slboot.ttf to install queue SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Copying font file C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\Fonts\segoen_slboot.ttf->C:\RemoteInstall\Boot\Fonts\segoen_slboot.ttf.

SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\Fonts\wgl4_boot.ttf to install queue SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Copying font file C:\RemoteInstall\SMSTempBootFiles\LAB00004\WINDOWS\Boot\Fonts\wgl4_boot.ttf->C:\RemoteInstall\Boot\Fonts\wgl4_boot.ttf.

SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Found new image LAB00005 SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Opening image file C:\RemoteInstall\SMSImages\LAB00005\boot.LAB00005.wim SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Found Image file: C:\RemoteInstall\SMSImages\LAB00005\boot.LAB00005.wim

PackageID: LAB00005

ProductName: Microsoft® Windows® Operating System

Architecture: 9

Description: Microsoft Windows PE (x64)

Version:

Creator:

SystemDir: WINDOWS

SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Closing image file C:\RemoteInstall\SMSImages\LAB00005\boot.LAB00005.wim SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

Creating BCD store: C:\RemoteInstall\SMSTemp\2013.09.20.23.44.09.02.{B509443D-7FF2-42BD-A182-600F7D65F4BC}.boot.bcd SMSPXE 20-09-2013 23:44:09 7068 (0x1B9C)

StoreFilePath: \??\C:\RemoteInstall\SMSTemp\2013.09.20.23.44.09.02.{B509443D-7FF2-42BD-A182-600F7D65F4BC}.boot.bcd SMSPXE 20-09-2013 23:44:26 7068 (0x1B9C)

Skipping creation of variables file for image LAB00005 SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\PXE\wdsnbp.com to install queue SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\PXE\abortpxe.com to install queue SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\PXE\pxeboot.com to install queue SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\PXE\pxeboot.n12 to install queue SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\PXE\bootmgr.exe to install queue SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

File C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\PXE\bootmgr.exe has version info: 6.2.9200.16384 SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

File C:\RemoteInstall\SMSBoot\x64\bootmgr.exe has version info: 6.2.9200.16384 SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\PXE\wdsnbp.com to install queue SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\PXE\abortpxe.com to install queue SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\PXE\wdsmgfw.efi to install queue SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

File C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\PXE\wdsmgfw.efi has version info: 6.2.9200.16384 SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

File C:\RemoteInstall\SMSBoot\x64\wdsmgfw.efi has version info: 6.2.9200.16384 SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\EFI\bootmgfw.efi to install queue SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

File C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\EFI\bootmgfw.efi has version info: 6.2.9200.16384 SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

File C:\RemoteInstall\SMSBoot\x64\bootmgfw.efi has version info: 6.2.9200.16384 SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\Fonts\segmono_boot.ttf to install queue SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Copying font file C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\Fonts\segmono_boot.ttf->C:\RemoteInstall\Boot\Fonts\segmono_boot.ttf.

SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\Fonts\segoe_slboot.ttf to install queue SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Copying font file C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\Fonts\segoe_slboot.ttf->C:\RemoteInstall\Boot\Fonts\segoe_slboot.ttf.

SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\Fonts\segoen_slboot.ttf to install queue SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Copying font file C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\Fonts\segoen_slboot.ttf->C:\RemoteInstall\Boot\Fonts\segoen_slboot.ttf.

SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Adding file: C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\Fonts\wgl4_boot.ttf to install queue SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Copying font file C:\RemoteInstall\SMSTempBootFiles\LAB00005\WINDOWS\Boot\Fonts\wgl4_boot.ttf->C:\RemoteInstall\Boot\Fonts\wgl4_boot.ttf.

SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Begin validation of Certificate [Thumbprint D04F5BDFFB9390BFEF89053A315F9D700462DAF5] issued to '02d1e460-a438-493c-b6c7-583601b1e087' SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

Completed validation of Certificate [Thumbprint D04F5BDFFB9390BFEF89053A315F9D700462DAF5] issued to '02d1e460-a438-493c-b6c7-583601b1e087' SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

PXEClientKey certificate valid. SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

PXE Provider finished loading. SMSPXE 20-09-2013 23:44:31 7068 (0x1B9C)

If you see errors please act accordingly and make sure that the PXE provider finished loading

Few pointers

Make sure that Boot images are send to PXE point or DP which has PXE
Check for event viewer and make sure there are no errors or warning related to WDS
This is a wonderful article written by Frank Rojas which can help
you with PXE problems. https://blogs.technet.com/b/configurationmgr/archive/2011/01/05/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx

Once this part is done confirm the following

You have created a Tasksequence and that it has a deployment \ Advertisemnt
Deployment is for the PXE (it can be Madatory (Required) or Available)
Referenced Packages are distributed including the boot images
Network Access account is specified

Now that we confirmed that the PXE is loaded successfully. Let us now look at the SMSPXE when the client boots. In 2012 PXE message are pretty good , You could see the DHCP packet information.

DHCP message:

Operation:
BootRequest (1)

Hardware Address type: 1

Hardware Address Length: 6

Hop Count: 0

Transaction ID: 05078C5E

Seconds Since Boot: 4

Client IP Address: 192.168.001.023

Your IP Address: 000.000.000.000

Server IP Address: 000.000.000.000

Relay Agent IP Address: 000.000.000.000

Hardware Address: 00:15:5d:8c:07:05:

Magic Cookie: 63538263

Options:

Type = 53 DHCP Message Type: 3=DHCPRequest

Type = 55 Paramerter Request List:
01020305060b0c0d0f1011122b363c438081828384858687

Type = 57 Max DHCP Message Size: 04ec

Type = 97 UUID:
00562a3213a8399044918b6846be50c648

Type = 93 Client system Arch: IA x86 PC

Type = 94 UNDI: 010201

Type = 60 ClassIdentifier:
PXEClient:Arch:00000:UNDI:002001 SMSPXE 21-09-2013 00:09:17 1612 (0x064C)

CLibSMSMessageWinHttpTransport::Send:
URL: CM2012SP1.sudilab.com:80 GET
/SMS_MP/.sms_aut?MPKEYINFORMATIONEX SMSPXE 21-09-2013 00:09:17 6148 (0x1804)

CLibSMSMessageWinHttpTransport::Send:
URL: CM2012SP1.sudilab.com:80 CCM_POST
/ccm_system/request SMSPXE 21-09-2013 00:09:17 6148 (0x1804)

Client lookup reply:
<ClientIDReply><Identification Unknown="0"
ItemKey="0" ServerName=""
ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>

SMSPXE 21-09-2013 00:09:17 6148 (0x1804)

00:15:5D:8C:07:05, 13322A56-39A8-4490-918B-6846BE50C648: device is not in the database. SMSPXE 21-09-2013 00:09:17 6148 (0x1804)

CLibSMSMessageWinHttpTransport::Send:
URL: CM2012SP1.sudilab.com:80 GET
/SMS_MP/.sms_aut?MPKEYINFORMATIONEX SMSPXE 21-09-2013 00:09:17 6148 (0x1804)

Sending StatusMessage SMSPXE 21-09-2013 00:09:17 6148
(0x1804)

CLibSMSMessageWinHttpTransport::Send:
URL: CM2012SP1.sudilab.com:80 CCM_POST
/ccm_system/request SMSPXE 21-09-2013 00:09:17 6148 (0x1804)

DHCP message:

Operation:
BootReply (2)

Hardware Address type: 1

Hardware Address Length: 6

Hop Count: 0

Transaction ID: 05078C5E

Seconds Since Boot: 4

Client IP Address: 192.168.001.023

Your IP Address: 000.000.000.000

Server IP Address: 192.168.001.002

Relay Agent IP Address: 000.000.000.000

Hardware Address: 00:15:5d:8c:07:05:

BootFileName: smsboot\x86\wdsnbp.com

Magic Cookie: 63538263

Options:

Type = 53 DHCP Message Type: 5=DHCPAck

Type = 54 Server idenitifier:
192.168.001.002

Type = 97 UUID:
00562a3213a8399044918b6846be50c648

Type = 60 ClassIdentifier: PXEClient

Type = 250
02010105040000000203020014040200ba0626506c6561736520776169742e20534d53206973206c6f6f6b696e6720666f7220706f6c6963790b0101 SMSPXE 21-09-2013 00:09:18 6148 (0x1804)

DHCP message:

Operation:
BootRequest (1)

Hardware Address type: 1

Hardware Address Length: 6

Hop Count: 0

Transaction ID: 05078C5E

Seconds Since Boot: 0

Client IP Address: 192.168.001.023

Your IP Address: 000.000.000.000

Server IP Address: 000.000.000.000

Relay Agent IP Address: 000.000.000.000

Hardware Address: 00:15:5d:8c:07:05:

Magic Cookie: 63538263

Options:

Type = 53 DHCP Message Type: 3=DHCPRequest

Type = 60 ClassIdentifier: PXEClient

Type = 97 UUID:
00562a3213a8399044918b6846be50c648

Type = 93 Client system Arch: IA x86 PC

Type = 250
0d0208000e010101020006050400000002ff

Type = 55 Paramerter Request List: 03013c8081828384858687 SMSPXE 21-09-2013
00:09:18 1612 (0x064C)

Getting boot action for unknown machine: item key: 2046820353 SMSPXE 21-09-2013 00:09:18 6148 (0x1804)

CLibSMSMessageWinHttpTransport::Send: URL: CM2012SP1.sudilab.com:80 GET /SMS_MP/.sms_aut?MPKEYINFORMATIONEX SMSPXE 21-09-2013 00:09:18 6148 (0x1804)

CLibSMSMessageWinHttpTransport::Send:URL: CM2012SP1.sudilab.com:80 CCM_POST /ccm_system/request SMSPXE 21-09-2013 00:09:18 6148 (0x1804)

Client boot action reply:<ClientIDReply><Identification Unknown="0"ItemKey="2046820353" ServerName=""
ServerRemoteName=""><Machine><ClientID>0496841d-c8ba-4215-bc34-94da8ad4cd12</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime=""
OfferID="LAB20002" OfferIDTime="20-09-2013 10:07:00"
PkgID="LAB0000B" PackageVersion="" PackagePath="https://CM2012SP1.sudilab.com/SMS_DP_SMSPKG$/LAB00004"
BootImageID="LAB00004" Mandatory="0"/></ClientIDReply>

SMSPXE 21-09-2013
00:09:18 6148 (0x1804)

00:15:5D:8C:07:05,
13322A56-39A8-4490-918B-6846BE50C648: found optional advertisement LAB20002 SMSPXE 21-09-2013 00:09:18 6148
(0x1804)

Looking for bootImage LAB00004 SMSPXE 21-09-2013 00:09:18 6148
(0x1804)

BootImage LAB00004 needs
to be updated (new packageID=LAB00004) VersionUpdate=true SMSPXE 21-09-2013 00:09:18 6148
(0x1804)

PXE::CBootImageInfo::CBootImageInfo:
key=LAB00004 SMSPXE 21-09-2013 00:09:18 6148 (0x1804)

Removing Previous Image
from cache: LAB00004 SMSPXE 21-09-2013 00:09:18 6148 (0x1804)

Creating BCD store:
C:\RemoteInstall\SMSTemp\2013.09.21.00.09.18.03.{8E1D5018-7318-4741-B92A-E5B7005E2039}.boot.bcd SMSPXE 21-09-2013 00:09:18 6148 (0x1804)

StoreFilePath:
\??\C:\RemoteInstall\SMSTemp\2013.09.21.00.09.18.03.{8E1D5018-7318-4741-B92A-E5B7005E2039}.boot.bcd SMSPXE 21-09-2013 00:09:29 6148 (0x1804)

Saving Media Variables to
"C:\RemoteInstall\SMSTemp\2013.09.21.00.09.34.0001.{8E1D5018-7318-4741-B92A-E5B7005E2039}.boot.var" SMSPXE 21-09-2013 00:09:34 6148
(0x1804)

CLibSMSMessageWinHttpTransport::Send:
URL: CM2012SP1.sudilab.com:80 GET
/SMS_MP/.sms_aut?MPKEYINFORMATIONEX SMSPXE 21-09-2013 00:09:34 6148 (0x1804)

Sending StatusMessage SMSPXE 21-09-2013 00:09:34 6148
(0x1804)

CLibSMSMessageWinHttpTransport::Send:
URL: CM2012SP1.sudilab.com:80 CCM_POST
/ccm_system/request SMSPXE 21-09-2013 00:09:34 6148 (0x1804)

DHCP message:

Operation:
BootReply (2)

Hardware Address
type: 1

Hardware Address Length: 6

Hop Count: 0

Transaction ID: 05078C5E

Seconds Since Boot: 0

Client IP Address: 192.168.001.023

Your IP Address: 000.000.000.000

Server IP Address: 192.168.001.002

Relay Agent IP Address: 000.000.000.000

Hardware Address: 00:15:5d:8c:07:05:

BootFileName:
smsboot\x64\pxeboot.com

Magic Cookie: 63538263

Options:

Type = 53 DHCP Message Type: 5=DHCPAck

Type = 54 Server idenitifier:
192.168.001.002

Type = 97 UUID:
00562a3213a8399044918b6846be50c648

Type = 60 ClassIdentifier: PXEClient

Type = 243
024530140000000a000000100000000e66000000000000bc093c433d7f061c5fc88a1e181d6b8d0000000000000000000000005bee9d8efa37c0b84fd289dea97339f4833b1cff01515c534d5354656d705c323031332e30392e32312e30302e30392e33342e303030312e7b38453144353031382d37333172

Type = 252
5c534d5354656d705c323031332e30392e32312e30302e30392e31382e30332e7b38453144353031382d373331382d343734312d423932412d4535423730303545323033397d2e626f6f742e62636400 SMSPXE 21-09-2013 00:09:34 6148 (0x1804)

First you would find the PXE client broadcasting. You will find the DHCP request (1). This contains the MAC ID and SMBIOS GUID. Now once this is got the device is checked for its presence in the database so that it knows if it is known client or not. DHCP reply would go with the boot file wdsnbp.com which will be downloaded and architecture detection happens once the same is done then the pxe client will again request to the boot action. If we have a Mandatory advertisement then it will download PXEBootn12.com else
if there is no Mandatory then it will download PXEBoot.com

This checking is done by looking at against the configuration manager DB. In older version SMSPXE used to connect to DB and now it uses Management point to connect to DB and collect this information.

With Mandatory advertisement \ Deployment which is required

Without Mandatory advertisement \ Deployment which is available

This is the usual boot process

1) A client is directed (by using DHCP Options or the PXE Server response) to download Wdsnbp.com

2) Wdsnbp.com validates the DHCP/PXE response packet and proceeds to download PXEBoot.com or PXEBootn12.com.PXEBoot.com requires the client to press the F12 key to initiate PXE boot.

3) PXEBoot.com or PXEBootn12.com downloads Bootmgr.exe and the BCD store. The BCD store must reside in a \Boot directory in the TFTP root folder. Additionally, the BCD store must be called BCD.

4) Bootmgr.exe reads the BCD operating system entries and downloads Boot.sdi and the Windows PE image (Winpe.wim).

5) Bootmgr.exe begins booting Windows PE by calling into Winload.exe within the Windows PEimage.

Once this is done you will find the Configuration Manager screen as shown below

This is the completion of the PXE boot and once done from here on we get rest of information from smsts.log which first gets created in X:\Windows\Temp\SMSTSLog\smsts.log

Hope this will be helpful.

Part II will cover from WinPE to full blown OS

--------------------------------------------------------------------------------

Sudheesh N

Comments

Anonymous
September 20, 2013
Good Stuff !! Sudheesh for posting. Awaiting Part-II
Anonymous
December 15, 2013
ThanksVery good info
Anonymous
January 15, 2014
very good one sudheesh
Anonymous
April 16, 2014
Fantastic! as always. Thank you Sudheesh. I am one of the person asked for your blog. I am requesting(i know i am very demanding :)) to rewrite CM2007 troubleshooting blogs as well whevever required. There is lot of change.

Thanks again.
Anonymous
April 16, 2014
one suggestion: to give the completeness, good to add the protocol and ports used in every stage.
Anonymous
April 29, 2014
Sure will try. But the support of 2007 might end soon :) . request you to switch to 2012 at the earliest
Anonymous
May 28, 2014
hi Sudheesh, thanks for the information! i am facing an issue for the Lenovo system. after pressing F12 it loads the boot file. after that its not loading task sequence wizard, it directly gets rebooted. could you please help me?
Anonymous
February 26, 2015
OMG.. I was looking for this for sometime now and it can't get better than that.
Short, get to the point and simple...
Anonymous
April 23, 2015
Very very detailed information.Thanks lot sudheeshN
Anonymous
March 04, 2016
Hi Sudheesh N

I am trying to do OSD but facing issue. My VM is booting but password windows is not appearing. what could be the issue please guide
Anonymous
March 07, 2016
Hi Sudeesh, for mandatory advertisement the file is PXEBOOT.N12 and not PXEBOOTN12.COM.
Anonymous
March 25, 2016
thanks for sharing........

다음을 통해 공유

Troubleshooting SCCM Part VII .......... OSD .... Part I

Part I : PXE boot

Comments

추가 리소스