Ghost Solution Suite

Installed a demo of GSS 3.1 and went through the configuration and several videos and KB's.  Went through the tool to create the PXE image to boot.  Boot a test client up via NIC with PXE, system pulls a DHCP but never boots to the PXE interface.  Never gets past the initial screen, of checking media, checking network, etc.

It appears the PXE server isn't responding to the request.

System is a laptop with UEFI BIOS loaded with Win 10 (1607) x64

Any suggestions?

Do you have any special Network Settings such as VLANs or anything else?

https://support.symantec.com/en_US/article.HOWTO124443.html

https://support.symantec.com/en_US/article.HOWTO1071.html

We do not, this is a normal switch with no special settings.  Actually its the same switch/network we use for our GSS 2.5.  That set up works fine, except for the fact it isn't .x64 compatible.  I just unplugged the "Production" GSS server, and built up the 3.1 system.

Where exactly in the boot process does it stall? Any error message?

Sorry for not repying sooner, I'm not getting the notifications when a reply is posted...

To answer the question, no we aren't getting an error.  System is told to boot to PXE, NIC starts and does a media check and then waits and (appears) to time out.  No other screen or error comes up.

What messages are you geting from the NIC? AFAIK if it just does a media check that's a normal BIOS check and not trying to boot from the NIC.

I tried a differant model system and the results were the same, but it must be a tad slower.  Something popped up on the screen very very briefly so I recorded with my phone.  This is what I get:

F12 to boot menu

UEFI Boot>Onboard NIC (IPv4) <-Selected

Displays:

Checking Media Presence....

Media Present...

Start PXE over IPv4

<Roughly 10 sec later>

Station IP Address is 192.168.170.200

PXE-E16: No offer received.

I haven't yet Googled that, but maybe that will get you started.

OK, thats getting me somewhere.  From another Forum post it says the "respond to unknown computers" option isn't set under the PXE server settings.  That is correct, the setting is set to None.  But "None" is my only option, and secondly it is only selectable when connected to the Shared config, not the PXE server's actual config.

How/where do I give it additional options to select from.  My WinPE environment only shows when I'm connected to the PXE server's config, not the shared config.

I would suggest creating a winpe configuration from shared option.

Then from there on use only shared configuration when working with WinPe options in PXE.

Generally the use for specific PXE server usage is to enable PXE logging on specific PXE server.

Overall usage commonly is still done from shared PXE configuration

Same error message PXE-E16 No Offer Received.  I confirmed that it is set for the WinPE image I created in the shared config for unrecognized devices.

Any ideas

Wireshark, check bootp, if the PXE does an offer or not.

If not enable PXE logs, check if it get's any requests in, might be that the network is forwarding all the broadcast packets to specific PXE server.

Thus the new one does not see any and does not reply to any.

I will see if I can get WireShark installed today.  But there is no physical network besides a unmanaged switch.  Our Ghost network is completely off our Production network is used only for Ghosting.  Literally a server, to switch, to clients for sole purpose of Ghosting.

Our Ghost 2.5 set up works fine with PXE.

If you can't set a default option for "Enable response to..." under the GSS tab then you might need to delete and recreate your "Boot Menu Option for PXE Server: Shared Configuration" under the Boot menu tab.