Jump to content


shank

Established Members
  • Posts

    6
  • Joined

  • Last visited

shank's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. It is working now, not sure if it was the whole pull down and re-enabling of PXE or it was just faulty ports or stupid user. Going to go with last 2, as it was a different user this time and different port i am guessing. This was not rocket science, must have got a real dumb one. Thanks for all the tips!
  2. Thought the same, but 2 computers, 2 network ports and 2 cables, all known to be working!!
  3. 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 ?
  4. 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.
  5. 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
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.