-
1. Re: How to set a static IP address during OS deployment
Tanner Lindsay Aug 21, 2017 9:10 AM (in response to RobLent)2 of 2 people found this helpfulThere isn't a specific provisioning action to set the IP address, but you may be able to do it with the Windows unattend file. There is some more info here: Interfaces | Microsoft Docs
-
2. Re: How to set a static IP address during OS deployment
jaysmith Aug 21, 2017 11:51 AM (in response to RobLent)1 of 1 people found this helpfulAnother method would be to create a batch script with the netsh command to set a static ip:
netsh interface ip set address "networkname" static staticip subnetmask dnsip
Replace networkname, staticip, subnetmask and dnsip with the actual values you wish to set. Then use a template actions to map a drive to the script location followed by a "execute file" action to run the script.
That method would require changing the batch for each server which could be cumbersome. Alternatively you could just use one 'execute file' action configured as such:
You would only need to change the command line parameters for this one action to specify the correct static IP for each server. The above commands may need some quotes or syntax adjustment but they should get the ball rolling for you.
-
3. Re: How to set a static IP address during OS deployment
RobLent Aug 22, 2017 1:19 AM (in response to RobLent)Thanks for the tips and ideas.
It would have been great to have some form of pop up like the computer name action.
I may get our Powershell guy to see if he can do something.
My problem is that multiple people will be provisioning servers and we do quite a lot with our test and UAT environments.
I can imagine me ending up with servers with the same IP.
Only other way I can think of is using reservations in DHCP but we wouldn't normally do this for servers but maybe we should be looking at that.
Thanks again and I will update once I have a solution.
-
4. Re: How to set a static IP address during OS deployment
Peteski Aug 23, 2017 10:13 AM (in response to RobLent)- Take what JaySmith said and change the command line parameters slightly to use a provisioning template (local) variable %newserverip% where the staticip word is. Then just change the IP address template variable in the template before running.
- Write a real simple batch file that prompts for input during the WINPE boot portion and save the data entered to a text file on say c:\windows\temp which the template reads later before joining domain. Useful if you provision interactively vs Bare Metal.