g-fx Posted January 26, 2015 Report post Posted January 26, 2015 Hey Guys, Yes, this question has been covered by multiple forums but its not exactly the answers Im looking for. In my environment when building Servers via SCCM 2012 R2 CU2, they dont have a dhcp scope for the required subnet. So I manually enter this in at the WinPE stage but ofcourse it gets lost when Windows Boots. So people have devised a couple of workarounds, but this still isnt very dynamic. Lets have a look at these options. 1) In the task sequence - specify the Network adapter information. The problem with this method, is I have to give access to the console, and ensure they change it everytime they do a build. I run the risk of the same task sequence running again , conflicting with another servers IP addressing. 2) Assign task sequence variables to collections Again, this is manually having to enter in the IP address and subnetting information. You can also import this device, but I would have to create CSV files for each machine and bulk import them. 3) VBS or Powershell. Having to update a script for IP Addressing and updating distribution points to run a script to change IP addressing is horrible. Is there anyway to grab that IP addressing from WinPE and apply ? It seems like you need a custom hta or UDI MDT to gather this information. For ease of deployment it should only really need to be added at the time of building the machine. Thanks! Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted January 27, 2015 Report post Posted January 27, 2015 You could use MDT and use ZTINICConfig.wsf to capture the network configuration after supplying in WinPE. You can call the script like this: %Scriptroot%\ZTINICConfig.wsf /ForceCapture Quote Share this post Link to post Share on other sites More sharing options...
g-fx Posted January 27, 2015 Report post Posted January 27, 2015 Thanks Peter, love your work So I implemented the capture network settings and works like a dream. the only thing I noticed is it didnt capture the dns search suffix, is there anyway to accomodate for this? Quote Share this post Link to post Share on other sites More sharing options...
g-fx Posted January 28, 2015 Report post Posted January 28, 2015 I answered my question, I used the variable OSDDNSSuffixSearchOrder to specify Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted January 28, 2015 Report post Posted January 28, 2015 Great! Good to hear! Quote Share this post Link to post Share on other sites More sharing options...