Quantcast
Viewing all articles
Browse latest Browse all 443

During OSD does the DHCP address received remain "sticky"?

Each of the facilities in my organization have multiple subnets assigned to them and are provided DHCP addresses from a few different DHCP servers on the network. We have a couple sites where computers are imaged with SCCM via OSD Task Sequences that during the imaging process end up with the default MS address of 169.254.x.x part way through the process. The issue seems to present itself when 1 of the 3 subnets at that site has used all its DHCP leases while the other 2 are almost completely unused. Before I consult with the network team, I would like to know if there are any "sticky" attributes that SCCM may have where if the machine started imaging with a particular address from a DHCP scope, must it continue to receive an address from the same scope it started on throughout the entire imaging process?

Another question - if the client is in the process of pulling down the operating system and suddenly loses its IP address (say the DHCP lease expired), does the SCCM OSD process have a way to recover from that?

(We use WinPE to boot from and do not use PXE)

Thank you.


Viewing all articles
Browse latest Browse all 443

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>