Ghost Solution Suite

Hello

I installed new laptops in our organization. The machines use DHCP on their WLAN adapter and static IP addressing on their ethernet adapter. After Ghostcasting both adapters have a static address, with the WLAN adapter having the static address the ethernet adapter should have. If I recall correctly, the ethernet adapter had a wrong static address.

When I look into the client properties > General tab in the GSS console, it shows the MAC address of the ethernet adapter. In the Configuration tab it shows the WLAN adapter using DHCP. There is no mention of the ethernet adapter on the configuration tab.

How can I get the system to apply the previous static ip address onto the ethernet adapter and DHCP configuration onto the wlan adapter? I have not had any problems when dealing with computers that have only one active network adapter.

EDIT: I now noticed that the model computer I used to build the image has the ethernet adapter information, including static ip address, in its client properties configuration tab. I think this is because I installed the GSS client onto the model computer only after it was fully configured. The other computers got the GSS client with the ethernet adapter configured but with no WLAN configuration.

EDIT 2: I deleted and recreated the computer "account" in the GSS console for two computer. Now the configuration tab shows the correct NIC and IP address. However, after a ghostcast session the WLAN-adapter has the static IP address (instead of DHCP address it should have) that belongs to the ethernet adapter. The ethernet adapter has the IP address of the computer that the image is based on.  

Thank you for your time!

No replies yet. I'm guessing mixed use of static ip addresses with dhcp on separate NICs is rare, are there any Symantec technical people around who would know?

I don't think this is an issue with Ghost, but more specifically an issue with the image you are deploying.

In order to get a WLAN adapter working you need to be running a full version of windows, and not WinPE, which cannot handle WLANs.  What you might want to try is to install only the ethernet lan and install the WLAN software as a post build task.

I'm using PCDOS to deploy images to these new computers, not WinPE.  

To be specific, both NICs work, they just don't get the IP configuration they should after ghostcasting. 

Now that I thought about it more, I do have older laptops here with the same config (static ip on LAN NIC, DHCP on WLAN NIC) and they work fine. I wonder what the problem is...

This could have something to do with the registry keys for the LAN devices that might be in your build. They are given different numbers in the registry and if the new machines have the devices come up in a different order, the numbering scheme captured in the registry might be the problem.  Comparing the NIC entries under HKLM/System/...  between old and new machines might point you in the right direction.