/build/static/layout/Breadcrumb_cap_w.png

Systems Management Question


SCCM - PC does not get an IP in Windows PE when trying to access TS

01/23/2020 395 views

I'm a new SCCM admin and have just taken over a 2012 R2 SCCM server. I'm trying to build a Lenovo ThinkPad P53s that already has a driver package and the previous admin had injected the network driver(s) to make this build work. It has stopped working for some reason and after testing I'm seeing that the PC is not getting an IP in Windows PE. I tried injecting the latest driver from Lenovo into the boot image but still no luck.


I have tested with a previous model to make sure this is not a network issue and a P52s is still working just fine.


Also, I apologize if my explanation is unclear or lacking information, I've had this fall into my lap and I'm learning as I go. If I can provide any more information to help with this description let me know.


EDIT - 

What's even more confusing to me is that it looks like all of these models (P50, P51, P52,P53) use the same network driver and the previous models are building just fine.


The difference I have noticed (and I'm not sure if this is the cause of my issues) is that these P53's are using UEFI while the previous models have used BIOS. These new models also have NVMe m.2 drives where all previous PC's have been built on normal 2.5" SSD's.


I'm not sure how those issues would relate to the PC not getting an IP, just an observation.


EDIT #2 - I've placed the driver on a USB drive and loaded it during Windows PE, the PC gets an IP just fine.  This is the same driver I have injected into the boot image.

0 Comments   [ + ] Show comments

Comments


Be the first to answer this question

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ