Hy i have changed my scenario Now i have the BDP on the same network of the client. I start the client with the boot media and i must configure the net settings. The ts starts correctly but when the clients reboots after installing sccm client the ts shows the error 0x80070002. I have seen that the lan settings are not the same i have set but the client have the settings from the dhcp so it doesn't reach the bdp. How can i set the lan after reboot too? Thanks

You can have a script take the IP Address set in WinPE and set the Task Sequence variables. http://technet.microsoft.com/en-us/library/dd252744.aspxJohn | Program Manager | System Center Configuration Manager

John or anyone else, Can someone please post the script you would use to take IP information entered in the WinPE environment and move them to the OSD TS variables? This is the last hiccup before we can deploy servers via OSD and I am struggling to get by it mostly because I am not a script guy. If someone can provide their script (should be universal) I would really appreciate it.

what about this one ? My step by step SCCM Guides I'm on Twitter > ncbrady

I tried that one. It errors out with something about a null variable because of one of the 'joins'. At this point I'm willing to look at a workable script or an HTA that takes the statically entered IP info and saves it. Speaking of scripts, is there any way to view the OSD variables to see if your script populated them before laying down the image and rebooting? One problem I am having with all this is that a full test takes around 30 minutes before I know whether or not my script worked or not. This is making things brutally slow in trying to get OSD into our production environment. Can anyone help me here? Is there any way to do this using UDI? We use UDI to choose settings and applications before the image is laid down. The UDI info we enter persists throughout the image lay down and reboot. Any way we can tack IP information into that some how? [rant] How can this question be marked as answered when the solution provided was "Go write a script"??? That isn't a solution nor an answer to this problem. This is becoming increasingly frustrating to deal with and we are beginning to search for another product that will actually work for us and not hold up the entire process because of one missing piece that was readily available and worked flawlessly in the previous version (MDT).