I am setting up a deployment server for my college's Computer Engineering lab. I had to do some "unconventional" things to achieve the configuration the program director wanted. The machines we are deploying to have two NICs connected to our network, and she wanted both to have static IPs based on their computer name. I achieved this by adding OSDComputer name in the priorities list and have the NIC settings listed in the deployment rules. I also edited the ZTIGather.xml to include the second set of adapter variables (OSDAdapter1IPAddress etc.) This method worked flawlessly on my test deployment to a virtual machine. I then tried it on our test hardware machine and I had a couple warnings related to the NIC settings. I reviewed the ZTINicConfig log and found that the ZTINicConfig script was running again after a reboot from the WSUS post application pass. It appears the warnings are generated because the script is trying to assign the static IP addresses that are already assigned to the NICs. Also, after the reboot I am prompted to choose a network location (home, work, public.) Is the script running again after the updates normal?
I am using MDT 2012 update 1, and my task sequence is a standard client install with no additional tasks added.