Peter van der Woude Posted October 16, 2014 Report post Posted October 16, 2014 Do you now have your F8 enabled and can you run an ip config? Quote Share this post Link to post Share on other sites More sharing options...
drewz99 Posted October 16, 2014 Report post Posted October 16, 2014 Yes, F8 is now enabled and I am getting a valid IP on corret vlan Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted October 17, 2014 Report post Posted October 17, 2014 Then check the SMSTS log file on the client if it recieves an task sequence deployment and check the SMSPXE log file on the server to see if it finds a deployment for that machine. Quote Share this post Link to post Share on other sites More sharing options...
Iroqouiz Posted October 24, 2014 Report post Posted October 24, 2014 In our environment this happens for (so far) three reasons. 1. The client is not getting an IP address from DHCP (does not apply to you). Solution: make sure the correct NIC drivers are added to the boot image. 2. The date/time is incorrect in BIOS on the client. Solution: set the correct date/time. 3. There are no task sequences deployed to the client. This one is rare but has happened a few times for us. It seems like the client is in some sort of limbo where it's not unknown but it still isn't a part of a collection to which an OSD TS is deployed. And this all depends on how you deploy your TS, do you deploy to "All Unknown Computers" etc. Solution: find out the MAC address of the client and search for it in the SCCM console (create a query from where you can get the MAC address) --> delete the device from the SCCM console. If your OSD TS is deployed to "All Unknown Computers" this is all you have to do. If you deploy to another collection you need to import the device again and add to the correct collection (watch out for limiting collections etc). Quote Share this post Link to post Share on other sites More sharing options...
