SCCM Task Sequence error apllying network adapter settings
Hello all, I'm deploying operating Systems (HyperV) with SCCM 2007. Deploying the operating systems works pretty well, but there are strange behaviours regarding the network interfaces and their configuration. I want to have some machines use static IP adresses and not DHCP. By default, there are 2 network adapters, named Customer LAN and Admin LAN. When the installation finishes, the ip settings are not applied properly. As shown in the screenshot, customer LAN is assigned the ip 172.21.36.16 The network adapter 1 will however be given the name "Customer LAN" but not the IP. Adapter 1 wil be shown using DHCP. The IP originally assigned to adapter 1 will be used by Adapter 2. Adapter 2 will be named Admin LAN as configured, but will be using the wrong IP. The IP assigned to Adapter 2 originally will be dropped completely. This problem seems to be similiar. I am however not using MDT, just the task sequence. Any helpful links/comments will be appreciated :)
July 26th, 2012 11:00am

Both actually use the exact same task sequence engine though thus the behavior should be the same. Note that this task is simply modifying the unattend.xml (or sysprep.inf if deploying 2003/XP) so its ultimately up to Windows setup to configure these things. I resorted to using a custom script in an engagement a few years back to address this shortcoming.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
July 26th, 2012 1:09pm

Thanks for the imput, I almost though so. I'll try that out in the next few days and post my results.
July 28th, 2012 7:27am

Script worked out fine, couldn't find another way to achieve this at the time. thanks again!
Free Windows Admin Tool Kit Click here and download it now
August 26th, 2012 4:19am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics