I need to be able to set an IP address on the machine I'm capturing. I have an environment where I don't have DHCP but need to capture. I've got the vb script all ready. I use it on my boot disks so I know it works. I currently get all the way through the install but don't have an IP after the OS has been installed. Where in the capture sequence can I set an IP Address? I'm guessing run command line is my option but where should I place this? At what point in my task sequence?

I would use the "Apply Network Settings" option in the task sequence after the reboot into the OS. You might need to set the task sequence variable to do this, depending on exactly what you need to configure. Here are some references: http://technet.microsoft.com/en-us/library/dd252744.aspx http://technet.microsoft.com/en-us/library/bb633293.aspx

It is a good answer. I found from yours that I can add a static IP via the Apply Network Setttings dialogue.

Jason could you possibly expand on the use of apply network settings? If I punch in an IP address at the very beginning of the OSD deployment process, using the Apply Network Settings after the image is laid down and the system reboots doesn't work. We do not have DHCP in our server VLANs and due to the volume and frequency in which we build and deploy Windows servers, we need to have the static IP address entered at the beginning of OSD persist throughout the task sequence, including after the system reboots so that all of our task sequences run. What mechanism can I use to keep the static IP address persistent? The Apply Network Settings defaults to DHCP and I'm not sure that the variables will help me in my situation. Any help would be appreciated.