Hi we plan to deploy our servers also via SCCM. The server are located in VLAN without DHCP, so a static address has to be applied. During the WinPE phase this isn't really a problem because a static address can be configured. This address is gone after the image is applied. I know I can assign a new address via "Apply Network Settings" plus defining task sequences variables but I want to reapply the same address entered during the WinPE phase. Is something built-in in SCCM or do I have to script it myself via netsh or whatever? Just to point out. I read already the step by step guide part 3 from Niall and I don't want to use a collection to assign variables. It's quite simple: 1) Enter address in WinpE 2) Save address somewhere 3) Reapply saved address after image is applied. Thanks Joachim

You can still use the collection variable method that Niall outlined but instead of populating it from the collection, you can build a UI that appears at the beginning of the TS that prompts for the IP Address to use. Some folks use HTAs to do this and I built a customizable native app designed to prompt the user for info: http://myitforum.com/cs2/blogs/jsandys/pages/osdplusplus.aspx.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Hi Jason nice tool. I don't want to use a collection because it should be possible to setup a server without any action required on the SCCM site. A predefined IP on the collection is also not useful because in case server are setup in a different vlan varibales on a collection have to be changed. Maybe I wrote it wrong but when WinPE starts I can enter an IP address manually. Why should I present another interface to the user to enter the same IP address again. I would expect that the IP address entered already in the WinPE is preserved and reinjected after image is applied. Am I totally wrong?

The IP address you enter there is only for purposes of initiating the task sequence. It's not stored as an OSD variable, and therefore the sequence does not let it persist. However, if you either use Jason's HTA, or download MDT, integrate it, and build a sequence with the "Gather" and "Configure" steps - it will transfer whatever is set as the IP address for you automatically into the OSD variable to persist throughout the sequence.

Hi Mike are you able to give some more details about the required steps because MDT is installed and integrated. I played a little bit with the gather and configure scripts but never was successful. If I look into the ZTIGather Logs I can verify that network settings are gathered, with the Capture Network settings task the network settings are "saved" in the environment and gone after image is applied because a reboot is inititated at the the end of the sysprep phase. Funny I feel like an idot :-) It seems I am the only guy either not understanding how it should work or my requirements are needles. Let me summarize it again mabye I explained it wrong due to language gaps. The server guys want to inject a Windows PE ISO via a remote management board to setup server located in a data centre. The server environment has no DHCP server installed. Server are connected to different VLAN's. Server guys do not have access to SCCM at all The system boots into WinPE. Server staff know to which vlan the server is connected and are able to apply a ip address for this specific vlan. This IP address enter HERE should be applied again later. In the WinPE environemnt the entered IP address need to be save, logged or whatever to reapply it later. NETSH, VBS Script, MDT or OSD++ Server image downloaded and applied ->REBOOT SYSPREP phase Restart of the task sequence and NOW the IP address (IP, DNS etc.) entered in step 3 should be reapplied. NETSH, VBS script or MDT or OSD++ With a valid configured IP address the tahs sequence can access the DP and the server staff hasn't to enter the same ip indformation again. Is that scenario feasible? From my point of view this is a standard process. :-) Thanks

Hi Joachin Did you got it??? How? My IT enviroment is like yours (No DHCP, VLANs, etc) I am using scripts but it doesnt work :( Thanks for advance

I just wanted to bump this question because I am in the exact same boat as the OP and see if we can't get this resolved. We build bare metal boxes on the data center floor in multiple VLANs that have no DHCP. We browse to the pre-configured DRAC or iLO interface and mount an OSD WinPE boot image ISO. We boot up to it and enter the WinPE environment. I want to statically configure the IP address there, and there only and let the build run its course to completion. Am I asking too much of OSD? This worked like a champ in MDT. I have even installed MDT 2010 Update 1 on the SCCM box and created the gather and apply task sequence steps but after the image is applied and reboots, it comes up with no IP address so the build fails as it can no longer contact the DP. Am I missing something extremely easy here? I am not a scripter at all and want to avoid any additional scripts. I feel that since this was so easy in MDT that it should be a feature in OSD and I am not asking that much. Doing this from the SCCM console is not an option as most builds are to brand new bare metal systems. Can anyone assist?

If you are using MDT/SCCM you can specify the IP Address in a custom table in MDT or add it to the settings table, we have added loads of custom tables to the MDT database. If you need any help let me know. This way you can have a totally unattened build process. http://blogs.technet.com/b/mmodin/archive/2010/02/03/how-to-extend-the-mdt-2010-database-with-custom-settings.aspx Louis

Louis, Thank you for the post. However that isn't really a viable solution for us. We build/rebuild 35-60+ servers per month and could increase that to near 100 per month once the VM team starts using OSD for deployment and we do not want to have to go into the database each time to enter an IP address. Also, many times we are deploying multiple systems in tandem, sometimes 6 or 8 boxes are churning at the same time. We need to be able to punch the IP address in at the beginning of the OSD deployment and have it maintain that IP address after the OSD lays down the image and reboots and continues running through our post-install task sequences. I fail to see why this is asking too much considering MDT had these features built in and worked fine for us in the past. Why was this removed? The best solution I believe is some kind of script but most of the solutions provided in other threads are quite vague and just say "Use a script". When you configure the IP address initially within OSD, what file are those immediately written to? As soon as I punch in the static IP address and move forward, a command prompt box pops up and the system runs the ztigather.wfs script. I do not tell it to do that. So where does that info go? The ztigather.log? When the OS image is laid down and the system reboots, what file would I need to populate in order for the system to get online and connect back to the SCCM DP and continue on to the next task sequence?

Louis1962A, Can you please expand on how you are doing this? I added IP address information to the Computers table in the MDT DB, but cannot get them to apply in a SCCM MDT integrated TS. Apparently the OSDADAPTER(x) settings don't get applied to ZTI for configmgr. I have a few machines that I re-image constantly for which I want to set static ip's. Thanks

Hi guys, I just want to share. I don't use the MDT but build a custom HTA where you can enter ip-address etc. The values are storedin the OSDAdapter... variables and applied automatically. here's an example ; If you want the full HTA with script please write me a pm. Regards, Jeroen ipaddress = IPaddress1.value & "." & IPaddress2.value & "." & IPaddress3.value & "." & IPaddress4.value gatewayaddr = gatewayaddr1.value & "." & gatewayaddr2.value & "." & gatewayaddr3.value & "." & gatewayaddr4.value subnetmaskaddr = subnetmask1.value & "." & subnetmask2.value & "." & subnetmask3.value & "." & subnetmask4.value dnsserveraddr1 = dnsserver1.value & "." & dnsserver2.value & "." & dnsserver3.value & "." & dnsserver4.value dnsserveraddr2 = dnsserver5.value & "." & dnsserver6.value & "." & dnsserver7.value & "." & dnsserver8.value dnsserveraddr3 = dnsserver9.value & "." & dnsserver10.value & "." & dnsserver11.value & "." & dnsserver12.value dnsserveraddr = dnsserveraddr1 &","& dnsserveraddr2 &","& dnsserveraddr3 Set env = CreateObject("Microsoft.SMS.TSEnvironment") env ("OSDAdapterCount") = 1 env ("OSDAdapter0EnableDHCP") = false env ("OSDAdapter0IPAddressList") = ipaddress env ("OSDAdapter0Subnetmask") = subnetmaskaddr env ("OSDAdapter0Gateways") = Gatewayaddr env ("OSDAdapter0DNSServerList") = dnsserveraddr env ("OSDAdapter0DNSDomain") = "domain.com" env ("OSDAdapter0DNSRegistration") = false env ("OSDAdapter0TcpipNetbiosOptions") = "0" env ("OSDAdapter0EnableWINS") = true env ("OSDAdapter0WINSserverlist") = "10.32.0.3,192.168.0.1,192.168.0.2" env ("OSDInputlocale") = "0813:00000813" env ("OSDUserlocale") = "nl-BE" env ("OSDUILanguage") = "en-US" env ("OSDSystemLocale") = "en-US" env("OSDComputerName") = servername.value env ("OSDRandomAdminPassword") = False env ("OSDLocalAdminPassword") = adminpw1.value env ("OSDTimezone") = strSiteTimevar window.close End Sub

What do you mean the variables are applied automatically? At what stage in the deployment process? Where are the variables stored while the system reboots and comes up to the next task sequence after the config mgr install?

The script is called as the first step in the tasksequence. The variables are applied during the "apply network settings step" in the tasksequence but you do not have to configure anything in this step.(so it's automatically) The variables are stored somewhere in the _smsts folder on the x-drive or the c-driveonce the c exists ? Thing is that as long as the TS is running (even if a reboot occurs within the TS) the variables and their value are available.

Jeroenda, I am interested in your HTA script for grabbing these variables. I don't see any way to PM users here so could you please contact me via email and perhaps share that HTA? I am still struggling with trying to populate the OSD variables with static IP information and wonder if a custom HTA that does it for me might be a better idea. I've been fighting with vbscripts for the better part of a week now. Any help you could give would be appreciated. Email is: cwb124 AT yahoo.com Thank you!

Can i get it as well i am also having the same problem. When i set the TS varibiles the dns and wins server show up but the ip and gateway and subnet default to APIPA and i am unable to find out. I have MDT and SCCM so any help would be great. james.w.mccutcheon4.civ@mail.mil

Sorry to hijack this thread but I've got a related issue. I've got a handle on how to supply static IPs to the OS as part of the OSD process, but I want to take it a step further and automate setting a static IP to the WinPE environment. It sounds like most on this thread are using the built-in HTA to manually enter their static IPs to the WinPE environment ... I want to be able to automate that step for full Zero touch deployments that run a mandatory OSD advertisement. In other words I'll need a script at the beginning of my Task Sequence which passes the IP info to the WinPE environment so that a system which runs it can set this either just before or just after the TS boots to WinPE environment (prior to the system needing to access the network to run the TS of course). Is this possible? My gut tells me that the script may have to be hosted in the WinPE image itself along with some table which holds the IPs themselves. Has anyone approached such a problem successfully or proved it isn't possible?

Jeroenda, Can you share the code for the HTA you are using? Thanks. rhouchins@gmail.com

Hi Jeroen, Can you send me the code aswell ? r.gerardsATlumc.nl Thanks

Hi Jeroen, - can you please share it. This will be perfect for my SCCM TS solution. mr2urbo@hotmail.com Thanks