CM 2002 - Boots into WinPE, then reboots

[xerxes2985]

Hey all,

Since upgrading to CM 2002, I have done the following:

Upgrade ADK to 2004, rebuild boot images. 

Now, when I PXE boot, it loads the WIM, loads up the WinPE environment background - then poof, it restarts (I never get prompted with the password entry to start my OSD). I cannot press F8 to have the command prompt appear (I still have that enabled), therefore I cannot get to any log files to diagnose. I am attempting to deploy Windows 10 1903.

Any suggestions?
 

Edited June 29, 2020 by xerxes2985
resolved one issue. Now another one.

[anyweb]

anything interesting in the smspxe.log ?

[xerxes2985]

Here is an excerpt from SMSPXE on the last boot I did. It doesn't appear to have any issues.

============> Received from client:	SMSPXE	6/29/2020 2:12:56 PM	6544 (0x1990)
 Operation: BootRequest (1)  Addr type: 1 Addr Len: 6 Hop Count: 0 ID: 0001E240
 Sec Since Boot: 65535 Client IP: HIDDEN Your IP: 000.000.000.000 Server IP: HIDDEN Relay Agent IP: 000.000.000.000
 Addr: 2c:ea:7f:24:6a:49:
 Magic Cookie: 63538263
 Options:
  Type=93 Client Arch: EFI BC
  Type=97 UUID: 0044454c4c310010578058b3c04f4e5732
  Type=53 Msg Type: 3=Request
  Type=60 ClassId: PXEClient
  Type=55 Param Request List: 3c8081828384858687
  Type=250 0c01010d020800010200070e0101050400000015ff	SMSPXE	6/29/2020 2:12:56 PM	6544 (0x1990)
Looking for bootImage LIB00298	SMSPXE	6/29/2020 2:12:56 PM	5488 (0x1570)
Prioritizing local MP https://HIDDEN.	SMSPXE	6/29/2020 2:12:56 PM	5488 (0x1570)
SSL, using authenticator in request.	SMSPXE	6/29/2020 2:12:56 PM	5488 (0x1570)
In SSL, but with no client cert.	SMSPXE	6/29/2020 2:12:56 PM	5488 (0x1570)
SSL, using authenticator in request.	SMSPXE	6/29/2020 2:12:57 PM	5488 (0x1570)
In SSL, but with no client cert.	SMSPXE	6/29/2020 2:12:57 PM	5488 (0x1570)
============> REQUEST Reply to client ([HIDDEN:68]) Len:447	SMSPXE	6/29/2020 2:12:58 PM	5488 (0x1570)
 Operation: BootReply (2)  Addr type: 1 Addr Len: 6 Hop Count: 0 ID: 0001E240
 Sec Since Boot: 65535 Client IP: HIDDEN Your IP: 000.000.000.000 Server IP: HIDDEN Relay Agent IP: 000.000.000.000
 Addr: 2c:ea:7f:24:6a:49:
 BootFile: smsboot\x64\bootmgfw.efi
 Magic Cookie: 63538263
 Options:
  Type=53 Msg Type: 5=Ask
  Type=54 Svr id: HIDDEN
  Type=97 UUID: 0044454c4c310010578058b3c04f4e5732
  Type=60 ClassId: PXEClient
  Type=243 01515c534d5354656d705c323032302e30362e32392e31342e31322e35342e303030332e7b38304333394438432d433434332d343536462d383631442d3343413335414341314333347d2e626f6f742e766172
  Type=252 5c534d5354656d705c323032302e30362e32392e31342e31322e35322e30372e7b38304333394438432d433434332d343536462d383631442d3343413335414341314333347d2e626f6f742e62636400	SMSPXE	6/29/2020 2:12:58 PM	5488 (0x1570)
<============ REQUEST Reply (end)	SMSPXE	6/29/2020 2:12:58 PM	5488 (0x1570)

 

[anyweb]

did you fix cmd support so you can also grab the smsts.log ?

[xerxes2985]

unfortunately, no. Once the background shows, no keystrokes work. F8 should bring up command prompt, but it does nothing. The only thing I can see before pressing F8 is the background image (MS Endpoint Configuration Manager default background), then a flash (like a window appears), then the computer restarts.

[anyweb]

are you sure you upgraded Windows ADK properly then ? there are two components to it this time...

[xerxes2985]

Yep. Removed the 1903 ADK, removed the PE component, rebooted. Downloaded the 2004 ADK, and the corresponding PE component from the MS docs page.

installed adk, then PE, rebooted. rebuilt boot images.

I even went as far as creating a new boot image, and using that and enabling it for PXE distribution, thinking that my boot image might be to blame. Ensured also that i have the correct network drivers in the boot image. still results in the same issue.

[anyweb]

very odd, i don't have adk 2004 in my cm2002 lab but i can upgrade it this evening to observe the behaviour

did you verify from the boot package Id that it's pulling down the boot image you set the settings on ?

[xerxes2985]

1 minute ago, anyweb said:

very odd, i don't have adk 2004 in my cm2002 lab but i can upgrade it this evening to observe the behaviour

did you verify from the boot package Id that it's pulling down the boot image you set the settings on ?

Yes. That is what was strange. With the boot image I have been using, I specified a custom background. The boot package ID matched, however the custom background doesn't load. that's what led me to create a new boot image as I thought something was corrupt as it wouldn't load the background.

[anyweb]

and the boot image is definitely distributed to your DP with the right source version ? i'm updating my lab to adk 2004 now....