NEWEndpoint Manager PXE boot issues

M

mpowis

Member
12
0
1
I have followed many of your posts on this subject, i have removed and reinstalled PXE, WDS and the management point etc but nothing seems to solve the issue.
The SMSPXE Log returns the following error everytime.
================= PXE Provider shutdown. ===================== SMSPXE 4/18/2023 2:14:03 PM 8516 (0x2144)
Could not load logging configuration for component CcmProfiler. Using default values. SMSPXE 4/18/2023 2:14:09 PM 9000 (0x2328)
Unable to load profiler: 0x80004005 SMSPXE 4/18/2023 2:14:09 PM 9000 (0x2328)
================= PXE Provider loaded. ===================== SMSPXE 4/18/2023 2:14:09 PM 9000 (0x2328)
Machine is running Windows Longhorn. (NTVersion=0X603, ServicePack=0) SMSPXE 4/18/2023 2:14:09 PM 9000 (0x2328)
Cannot read the registry value of MACIgnoreListFile (00000000) SMSPXE 4/18/2023 2:14:09 PM 9000 (0x2328)
MAC Ignore List Filename in registry is empty SMSPXE 4/18/2023 2:14:09 PM 9000 (0x2328)
Begin validation of Certificate [Thumbprint DEBF2C77545B08E186037DADF28B7018FAFC6BEC] issued to '7919c906-4275-4d5a-a56e-3d76303f4c4b' SMSPXE 4/18/2023 2:14:09 PM 9000 (0x2328)
Completed validation of Certificate [Thumbprint DEBF2C77545B08E186037DADF28B7018FAFC6BEC] issued to '7919c906-4275-4d5a-a56e-3d76303f4c4b' SMSPXE 4/18/2023 2:14:09 PM 9000 (0x2328)
PXE::MP_GetList failed; 0x80070490 SMSPXE 4/18/2023 2:14:09 PM 9000 (0x2328)
PXE::MP_LookupDevice failed; 0x80070490 SMSPXE 4/18/2023 2:14:09 PM 9000 (0x2328)
PXE Provider failed to initialize MP connection.
Element not found. (Error: 80070490; Source: Windows) SMSPXE 4/18/2023 2:14:09 PM 9000 (0x2328)
PXE::MP_GetList failed; 0x80070490 SMSPXE 4/18/2023 2:14:09 PM 9000 (0x2328)
PXE::MP_ReportStatus failed; 0x80070490 SMSPXE 4/18/2023 2:14:09 PM 9000 (0x2328)
PXE::CPolicyProvider::InitializeMPConnection failed; 0x80070490 SMSPXE 4/18/2023 2:14:09 PM 9000 (0x2328)
PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE 4/18/2023 2:14:09 PM 9000 (0x2328)
Adding PS5000F4.6 SMSPXE 4/18/2023 2:14:09 PM 9000 (0x2328)
Found new image PS5000F4 SMSPXE 4/18/2023 2:14:11 PM 9000 (0x2328)
加载Windows DLL(版本的10.0.2262成像API1.1') from location 'C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll' SMSPXE 4/18/2023 2:14:11 PM 9000 (0x2328)
Opening image file D:\RemoteInstall\SMSImages\PS5000F4\WinPE.PS5000F4.wim SMSPXE 4/18/2023 2:14:11 PM 9000 (0x2328)
Found Image file: D:\RemoteInstall\SMSImages\PS5000F4\WinPE.PS5000F4.wim
PackageID: PS5000F4
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (amd64)
Version:
Creator:
SystemDir: WINDOWS
SMSPXE 4/18/2023 2:14:12 PM 9000 (0x2328)
Closing image file D:\RemoteInstall\SMSImages\PS5000F4\WinPE.PS5000F4.wim SMSPXE 4/18/2023 2:14:12 PM 9000 (0x2328)
Begin validation of Certificate [Thumbprint DEBF2C77545B08E186037DADF28B7018FAFC6BEC] issued to '7919c906-4275-4d5a-a56e-3d76303f4c4b' SMSPXE 4/18/2023 2:14:12 PM 9000 (0x2328)
Completed validation of Certificate [Thumbprint DEBF2C77545B08E186037DADF28B7018FAFC6BEC] issued to '7919c906-4275-4d5a-a56e-3d76303f4c4b' SMSPXE 4/18/2023 2:14:12 PM 9000 (0x2328)
PXE提供者完成加载。SMSPXE 4/18/2023 2:14:12 PM 9000 (0x2328)



I have restored the system from a known working setup but still cannot get it to work, the laptop runs through the PXE boot, gets assigned an IP address and then displays Windows Deployment Error - Error code: 0xc000000f

I'm at a loss what to do next and we cannot image any computers, do you have any ideas?
Sort by date Sort by votes
OP
M

mpowis

Member
12
0
1
  • Thread Starter
  • #3
Hi GSterling,
no, the communication for the Dp has always been set to HTTPS Allow intranet-only connections and theprevious network manager has a certificate imported for it.
Upvote 0 Downvote
OP
M

mpowis

Member
12
0
1
  • Thread Starter
  • #5
this is from today
SetLogLocation:: logging path code - C:\Windows\system32\inetsrv\appcmd.exe list site "Default Web Site" /text:logfile.directory SMS_Distribution_Point_Monitoring 4/18/2023 12:00:02 AM 8404 (0x20D4)
SetLogLocation:: site id code - C:\Windows\system32\inetsrv\appcmd.exe list site "Default Web Site" /text:id SMS_Distribution_Point_Monitoring 4/18/2023 12:00:02 AM 8404 (0x20D4)
Initialize::Log location C:\inetpub\logs\LogFiles\W3SVC1 SMS_Distribution_Point_Monitoring 4/18/2023 12:00:02 AM 8404 (0x20D4)
Client is set to use HTTPS when available. The current state is 1504. SMS_Distribution_Point_Monitoring 4/18/2023 12:00:02 AM 8404 (0x20D4)
SelfProve token is available SMS_Distribution_Point_Monitoring 4/18/2023 12:00:02 AM 8404 (0x20D4)
Cannot connect with winhttp; 80072ee5 SMS_Distribution_Point_Monitoring 4/18/2023 12:00:02 AM 8404 (0x20D4)
Failed to get information for MP: . 80072ee5. SMS_Distribution_Point_Monitoring 4/18/2023 12:00:02 AM 8404 (0x20D4)
Initialize::Failed to validate an MP from registry: . 00000000 SMS_Distribution_Point_Monitoring 4/18/2023 12:00:02 AM 8404 (0x20D4)
Gathering statistics from C:\inetpub\logs\LogFiles\W3SVC1\ex230417.log SMS_Distribution_Point_Monitoring 4/18/2023 12:00:03 AM 8404 (0x20D4)
Report state message 0x00000001 to MP SMS_Distribution_Point_Monitoring 4/18/2023 12:00:03 AM 8404 (0x20D4)
Upvote 0 Downvote
OP
M

mpowis

Member
12
0
1
  • Thread Starter
  • #7
I'm sure its not Antivirus related, we do have endpoint on the server but this was on it when it was working, also i can ping both the IP and the name of the server hosting the MP
Upvote 0 Downvote
OP
M

mpowis

Member
12
0
1
  • Thread Starter
  • #8
Endpoint configuration manager tells me that i have a critical error Site Role "Management Point" is not healthy, but no reason why
Upvote 0 Downvote
OP
M

mpowis

Member
12
0
1
  • Thread Starter
  • #11
the DHCP server is pointing to the SCCM server IP address and the boot file is smsboot\x64\wdsmgfw.efi
as far as i can see from the PXE log its connecting to the file but nothing after that just windows deployment has encountered an error 0xc000000f
Upvote 0 Downvote
OP
M

mpowis

Member
12
0
1
  • Thread Starter
  • #12
I tried booting another machine just incase it was a driver issue, to a known laptop that has imaged in the past i noticed that no matter what i set the DHCP 67 boot file name to it always displayed on the laptop the same boot file, could this be the issue all along if so how do i tell it to go to a different location / boot file?
Upvote 0 Downvote
G

GSTERLING

Active Member
41
6
8
I recommend switching to IP Helpers instead of DHCP options.

techcommunity.microsoft.com

You want to PXE Boot? Don't use DHCP Options.

PXE Boot Basics. Booting from the network using the PXE protocol involves a simple series of DHCP packets. There are three parties involved: the DHCP server, the PXE server, and the client. The client broadcasts a DHCP packet asking for the address of DHCP servers (servers that can hand out...
techcommunity.microsoft.com
Upvote 0 Downvote
OP
M

mpowis

Member
12
0
1
  • Thread Starter
  • #16
i still get the same message, it finds the server, then says architecture x64, then boot/x86/wdsnbp.com
this never changes when i was setting a different path in DHCP, the original setup was using DHCP
Upvote 0 Downvote
OP
M

mpowis

Member
12
0
1
  • Thread Starter
  • #17
also just found this warning message in config man status:
MP has rejected registration request due to failure in client certificate (Subject Name: server name) chain validation. If this is a valid client, Configuration Manager Administrator needs to place the Root Certification Authority and Intermediate Certificate Authorities in the MP's Certificate store or configure Trusted Root Certification Authorities in primary site settings. The operating system reported error 2148204809: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
Upvote 0 Downvote
You must log in or register to reply here.

Latest posts

Forum statistics

Threads
5,478
Messages
21,337
Members
11,720
Latest member
noverby
Top Bottom