Ghost Solution Suite

I want to know if I can force the ghost console to use a particular nic when it reboots a laptop into windows pe for ghosting.  I've manage to get a ghost boot image set up and the laptops to reboot into windows pe from the ghost console over a wireless network.  But when they reboot, they get stuck at polling for the ghost console machine and have an ip address of 127.1....  I think this means that it see the wired NIC which is not connected and therefore it does not get an ip address and the laptops cannot connect to the server.  Is there any way I can force the ghost console to use the wireless NIC in windows pe when it reboots to connect to the network.?

i dont think wireless ghosting is possible but if it were it would require a 32bit boot enviroment and a wireless network manager built into the ghost boot disk.  your best bet is to fix your wired network setup.  i would start by verifying that your NIC has an available driver in the boot disk, if not you should integrate one.  if that doesnt work try using the universal boot disk included with GSS2.5

I am using windows pe as the 32 bit environment.  But I am not using a ghost boot disk, I am using the ghost console.  GSS 2.5 allows the user to choose the pre os environment, and I've chosen windows pe, but I want to know how can I force it to use the wireless NIC instead of the wired NIC.  Any thoughts?

Rodney,

Basically you client is pulling a loopback address which a majority of the time is a driver issue. Ghost casting over wireless is not a supported scenario so I would advise you to use the onboard NIC for you imaging needs. If you switch to the onboard NIC and still have the same issues then update the NIC driver in the WinPE wim file using the boot wizard and try again.

..integrating the wireless driver into WinPE. Basically you need the .INF and .SYS files and any related files.