shank Posted January 31, 2014 Report post Posted January 31, 2014 Hi all I am having an issue as of late. My setup is as follows, In a particular state; DHCP/ DNS is on an NS server SCCM DP is on a seperate server. When i try to PXE boot using a VM in this particular state, no issues it pxe boots. PXE booting a client laptop - unknown does not work, and according to the person doing it, it moves too fast and no error. I look at the smspxe log in reminst\sms_dp on the DP and it doesn't update, but does when i boot from the VM i think. I have restarted WDS, ensured pxe is enabled and boot images are copied over, i have rebuilt this pxe point from scratch. I am not sure what to do next. Can someone please help. Thanks Quote Share this post Link to post Share on other sites More sharing options...
newadmsccm Posted January 31, 2014 Report post Posted January 31, 2014 I not understanding very well, sorry. VM your PXE is OK. right? Another computer occurred error PXE? Do you see smspxe.log? Did you remember insert manually new computer (mac,hostname) in SCCM? Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted January 31, 2014 Report post Posted January 31, 2014 Well you know the PXE function of SCCM isn't the problem if your VM is PXE booting. So no need to remove the PXE capability. Has a change been made on the client network side, VLAN etc... ? PXE booting a client laptop - unknown does not work, and according to the person doing it, it moves too fast and no error. What moves to fast? Is it atleast getting a PXE offer and the boot.wim is loading to fast and bombing out is that what you mean? Quote Share this post Link to post Share on other sites More sharing options...
shank Posted February 1, 2014 Report post Posted February 1, 2014 Well you know the PXE function of SCCM isn't the problem if your VM is PXE booting. So no need to remove the PXE capability. Has a change been made on the client network side, VLAN etc... ? What moves to fast? Is it atleast getting a PXE offer and the boot.wim is loading to fast and bombing out is that what you mean? There has been no change on the network side of things, no it gets to the stage of contacting server... and after a few seconds it moves on from lan boot to windows boot, and this is too fast for the user to realize if there is an error code of any sort. She was able to tell me all she saw was exiting boot agent and it then moved on. Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted February 1, 2014 Report post Posted February 1, 2014 You can pause screen on PXE advertisement, to see what error code it is giving by simply pressing pause screen on keyboard. Booting to next device..... (generally means the system is known to SCCM) Exiting PXE ROM.... etc Quote Share this post Link to post Share on other sites More sharing options...
shank Posted February 1, 2014 Report post Posted February 1, 2014 Cheers i will give the pause a shot. I tried 2 systems one completely new and one not. I wonder why the pxelog isn't updating on the DP. My guess is because it isn't even getting to winpe ? Quote Share this post Link to post Share on other sites More sharing options...
shank Posted February 4, 2014 Report post Posted February 4, 2014 Ok got an error message, media test failure Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted February 4, 2014 Report post Posted February 4, 2014 ohh okay Seems like you have faulty NIC or no network cable plugged in Quote Share this post Link to post Share on other sites More sharing options...
shank Posted February 4, 2014 Report post Posted February 4, 2014 Thought the same, but 2 computers, 2 network ports and 2 cables, all known to be working!! Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted February 5, 2014 Report post Posted February 5, 2014 Switch ports maybe? Media test failure is no connection\communication. Either network ports damaged in trunking or ports gone on switch, no cable, NIC damaged, port configuration wrong on switch if managed ports or NIC turned off in BIOS. Quote Share this post Link to post Share on other sites More sharing options...
