Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, January 7, 2016 12:14 PM
I'm trying to PXE boot a laptop from a remote DP, but when I PXE boot I can't even get an IP address. I'm not getting an error message either. When I check smspxe.log on the remote DP the last message is from a year ago saying "PXE Provider Shutdown".
I've restarted both the remote DP and main site SCCM 2012 R2. I've also tried restarting WDS service. Flow control and Loop back protection on switch is off, I've verified that the laptop is not listed in Device Assets.
All replies (19)
Wednesday, January 13, 2016 11:03 PM ✅Answered
Making some headway. I found out that my HP procurve didn't have Admin-Edge-Port (FastPort), enabled. Since then I can see the following in smspxe.log:
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
SMSPXE 1/13/2016 2:43:10 PM 2456 (0x0998)
00:26:B9:A7:7E:FF, 4C4C4544-004B-5310-8048-CAC04F344C31: device is not in the database. SMSPXE 1/13/2016 2:43:10 PM 2456 (0x0998)
On the client machine they are seeing error PXE-E53 so I'm redistributing the boot images and packages.
Thursday, January 14, 2016 7:15 AM ✅Answered
I'm redistributing the boot images and packages.
That won't help. The log clearly states that there is no task sequence available because the client is not in the database. Either import it manually (using the MAC address) or deploy to unknown computers.
Torsten Meringer | http://www.mssccmfaq.de
Thursday, January 7, 2016 12:35 PM
Make sure to fix the IP address issue first.
Is the WDS service up and running at all? Have you already examined the eventlog?
Torsten Meringer | http://www.mssccmfaq.de
Thursday, January 7, 2016 1:48 PM
All other computers on that subnet are able to get IP addresses from the DHCP server. WDS is running and I've restarted it.
Thursday, January 7, 2016 2:10 PM
Is it a hardware issue with the laptop? Does it have an OS you can boot to and test NIC can get IP from DHCP?
Cheers Paul | http://sccmentor.wordpress.com
Thursday, January 7, 2016 2:17 PM
Also, are you checking the correct smspxe.log? It moved at some point, see http://blog.coretech.dk/kea/smspxe-log-in-sccm-2012/
Is the PXE enabled DP on the same subnet as the client being PXE booted?
If not, are you using iphelpers or DHCP scope options to direct the PXE boot correctly?
Jason | http://blog.configmgrftw.com | @jasonsandys
Thursday, January 7, 2016 2:52 PM
The laptop has Windows 7 on it and I'm able to access the network/Internet from it.
Thursday, January 7, 2016 3:12 PM
I did search on all drives for remote DP and only smspxe.log I could find was in f:\SMS_DP$\sms\logs
PXE enabled DP is on same subnet as client PXE.
Thursday, January 7, 2016 3:53 PM
If you stop and restart WDS, there will be activity in smspxe.log. If there is no activity then either you are looking at the wrong log or your DP is not DP enabled (or isn't DP enabled successfully).
Jason | http://blog.configmgrftw.com | @jasonsandys
Thursday, January 7, 2016 6:06 PM
I've restarted WDS, but smspxe.log hasn't changed since last year. When I go to main site it shows as DP site. What else can I do?
Thursday, January 7, 2016 10:37 PM
I think I've made some headway. I disabled PXE for the remote DP from the console on the main site, reboot the remote DP then re-enabled PXE on the console. Now I see activity on smspxe.log. In the log I see some errrors with the boot images so I'm redistributing them now. Once that's done I'll have someone text PXE OSD at that site.
Friday, January 8, 2016 12:38 AM
It definitely sounds like PXE was not enabled successfully; i.e., not in a healthy state, on the DP.
Jason | http://blog.configmgrftw.com | @jasonsandys
Friday, January 8, 2016 9:29 PM
Jason,
I can now see updates on F:\SMS_CCM\Logs\smspxe.log, but nothing happens when we PXE boot a client. It doesn't give error during PXE boot and nothing is logged in smspxe.log.
When I disabled PXE for the remote DP and re-enabled it I never remove WDS from the remote DP. Should I do that?
Monday, January 11, 2016 5:51 PM
Okay, I've removed PXE boot option, removed WDS and IIS from remote DP, rebooted remote DP, re-added PXE boot option.
Here is are errors I see in smspxe.log on remote DP.
RegOpenKeyExW failed for Software\Microsoft\SMS\setup SMSPXE 1/11/2016 10:45:25 AM 3280 (0x0CD0)
RegReadString failed; 0x80070013 SMSPXE 1/11/2016 10:45:25 AM 3280 (0x0CD0)
RegOpenKeyExW failed for Software\Microsoft\SMS\DP\Logging\GLOBAL SMSPXE 1/11/2016 10:45:25 AM 3280 (0x0CD0)
RegWriteString failed; 0x80070013 SMSPXE 1/11/2016 10:45:25 AM 3280 (0x0CD0)
RegOpenKeyExW failed for Software\Microsoft\SMS\DP\Logging\SMSPXE SMSPXE 1/11/2016 10:45:25 AM 3280 (0x0CD0)
RegWriteString failed; 0x80070013 SMSPXE 1/11/2016 10:45:25 AM 3280 (0x0CD0)
RegOpenKeyExW failed for Software\Microsoft\SMS\DP\Logging\GLOBAL SMSPXE 1/11/2016 10:45:25 AM 3280 (0x0CD0)
RegReadDWord failed; 0x80070013 SMSPXE 1/11/2016 10:45:25 AM 3280 (0x0CD0)
RegOpenKeyExW failed for Software\Microsoft\SMS\DP\Logging\GLOBAL SMSPXE 1/11/2016 10:45:25 AM 3280 (0x0CD0)
RegWriteDWord failed; 0x80070013 SMSPXE 1/11/2016 10:45:25 AM 3280 (0x0CD0)
RegOpenKeyExW failed for Software\Microsoft\SMS\DP\Logging\GLOBAL SMSPXE 1/11/2016 10:45:25 AM 3280 (0x0CD0)
RegReadDWord failed; 0x80070013 SMSPXE 1/11/2016 10:45:25 AM 3280 (0x0CD0)
RegOpenKeyExW failed for Software\Microsoft\SMS\DP\Logging\GLOBAL SMSPXE 1/11/2016 10:45:25 AM 3280 (0x0CD0)
RegWriteDWord failed; 0x80070013 SMSPXE 1/11/2016 10:45:25 AM 3280 (0x0CD0)
RegOpenKeyExW failed for Software\Microsoft\SMS\DP\Logging\GLOBAL SMSPXE 1/11/2016 10:45:25 AM 3280 (0x0CD0)
RegReadDWord failed; 0x80070013 SMSPXE 1/11/2016 10:45:25 AM 3280 (0x0CD0)
RegOpenKeyExW failed for Software\Microsoft\SMS\DP\Logging\GLOBAL SMSPXE 1/11/2016 10:45:25 AM 3280 (0x0CD0)
RegWriteDWord failed; 0x80070013 SMSPXE 1/11/2016 10:45:25 AM 3280 (0x0CD0)
RegOpenKeyExW failed for Software\Microsoft\SMS\DP\Logging\GLOBAL SMSPXE 1/11/2016 10:45:25 AM 3280 (0x0CD0)
RegReadDWord failed; 0x80070013 SMSPXE 1/11/2016 10:45:25 AM 3280 (0x0CD0)
RegOpenKeyExW failed for Software\Microsoft\SMS\DP\Logging\GLOBAL SMSPXE 1/11/2016 10:45:25 AM 3280 (0x0CD0)
RegWriteDWord failed; 0x80070013 SMSPXE 1/11/2016 10:45:25 AM 3280 (0x0CD0)
Monday, January 11, 2016 6:35 PM
I also found that the client laptop was still in the device list so I created a device collection with it and deployed it to the Task Sequences I use for OSD, but still no luck.
Monday, January 11, 2016 6:59 PM
Here is are errors I see in smspxe.log on remote DP.
All those can be ignored. Do you see the MAC address of the client showing up in the log?
Torsten Meringer | http://www.mssccmfaq.de
Monday, January 11, 2016 9:19 PM
I checked the smspxe.log on the remote dp, but don't see any mention of the MAC address for the test client.
I've run a report on the main site and found two instances of that MAC address and removed it and verified that my TS is deployed to Unknown Computers, but still no luck.
What other log can I look at on the remote dp?
Tuesday, January 12, 2016 3:15 AM
smspxe.log will show PXE activity regardless of the client having a resource in ConfigMgr or not. If you don't see a line for the client in smspxe.log when you PXE boot it, then the traffic is not making it to the PXE enabled DP. There is no other log -- if the DP doesn't see the traffic, it can't do anything about it. Are you sure the client is on the same IP subnet as the PXE-enabled DP?
Jason | http://blog.configmgrftw.com | @jasonsandys
Thursday, January 14, 2016 4:00 PM
All three TS's were deployed to unknown computers so I redeployed the TS's. I also resent boot images to my remote distribution points.
It all works now.
Resolution: Changed HP Procurve switches from "Auto Edge" to "Admin Edge" under STP settings and changes mentioned above.
Thanks Torsten, Jason and Paul.