Ghost Solution Suite

We area a school and need to frequently wipe all our laptops. The problem is with them having both wireless and onboard NICs. I can successfully wipe using the onboard NIC and it changes the IP and sets the computer name and joins the domain nicely. The problem is that it does not change the IP of the wireless NIC. The onboard is really only used when ghosting.
1.The wired NIC needs to be enabled in Windows permanently otherwise connectivity is lost after imaging this is not a big deal but it does consume battery power in normal use.
2.Is there any way Ghost can change the IP of the wireless NIC? We don�t like to use DHCP for various reasons. What procedure do other people use for ghosting wireless laptops?
3.I have a set of 50 computers numbered lab-1 to lab-50. Some time I need to wipe them all, sometime only some of them. In the past I have made a folder �machines to install� and cut and paste them into this folder them applied the configurations manually in the task definition. I also have to remember to delete the machine account from AD before Ghosting. There surely must be an easier way? What I�d like is that machine lab-2 always knows that it is lab-2 and always applies the configuration lab-2 whenever it�s Ghosted. It would also be nice if the existing AD account for lab-2 was automatically deleted by Ghost.
4.I just upgraded to GSS 2.0 and did not find these features, only a bug which cause the console to crash. If you have a group of machines in a folder and a task set up with the configurations for these machines, taking the computer out of this folder will mean that the task is no longer editable: go the task properties, and the console hangs for a minute, then crashes. This is just annoying as the only way out if you can remember which computers were in the task definition or to delete the task and start over.
Spec HP Ml350 P4 Dual 3.0 Ghz, 2GB Win 2003, GSS 2.0 XP Clients: D620 (Broadcom/Intel) and ThinkPad R51 laptops

You will probably have to do some cutom scripting to set the IP to a specified IP for each new computer. If you do not want to use DHCP, what about reserved DHCP? That way every computer would get the assigned IP address but you would not have to touch the client.

What are some of the reasons you do not like DHCP? I can't imagine going back to static IP's for all of our clients.

Thanks for the response. We did go to DHCP a few years ago then moved back to static. We had a lot of problems with the wireless laptops not obtaining an IP address pre-logon, even though they had a reservation. I think it has to do with our quirky access points. Tried it again last week and still the same issues, the Thinkpads performing better than the D620s, but still flaky. We spent so much time on it that we decided just to go back to static addresses.