Ghost Solution Suite

I used to run GSS 2.5 with the provided 3com and tftp tools, that worked great.

Now, I've got GSS 3.0 up and running, I've installed the PXE Server with it, and added the DHCP role to that 2008 server. During the install I added the Linux and Win PE 5.1 preboot environments and I've selected the "Auto detect Microsoft DHCP server and configure for PXE" option in the PXE Configuration Utility.

When booting up a client to PXE I can get an IP address, but the error is PXE-E53: No boot filename recieved.

Don't I also have to have the boot file and location in DHCP (Options 66 & 67) ?

I don't see this anywhere in the documentation or videos.

There is one article available on Symantec Connect which talks about the same error (PXE-E53) that you are seeing.

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

See if this can help to resolve your problem.

 

Using this article I was able to configure the DHCP server so that I now get a little further:

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

 

But, now I recieve an error that states "PXE-E74 bad or missing pxe menu and or prompt information"

I'm not using DHCP option 43 as stated in some solutions, but I haven't tried upgrading or downgrading the BIOS yet either as a solution.

Using Altiris Deployment Server 6.9 (the predecessor to GSS 3) the only thing I've seen that causes the "...bad or missing..." error is if there are too many PXE Boot Menu entries or they contain too many characters, especially on older PCs. So if I add one too many PXE boot entries in my test area, HP 8100 desktops will fail but 8200 and 8300s will still work. If your DHCP Server is on the same Windows server as the PXE Server then Option 60 should be set on the DHCP Server. Check if it's set as a Server Option or DHCP Scope option and there's no conflicts between the two. I think that the PXE Service used to set Option 60 when restarted if "Auto detect Microsoft DHCP server and configure for PXE" option in the PXE Configuration Utility was set, not sure if GSS 3 will still do this or if it's set as a DHCP Server or DHCP Scope option.

I certainly don't have too many boot options, lol. Just the 3 that are there after the install (Continue, Linux, and WinPE).

The DHCP server is on the same as the PXE. Option 60 is just on the scope and there is no Option 60 on the server options.

I'm trying to reinstall the PXE server now, just to see if that will help.

Okay, reinstalling hasn't helped at all. DHCP is on the PXE server, yes. Option 60 is only set at the Scope level. The PC and Server are on 2 different subnets.

I've also tried just making the boot file MenuOption131\x86pc\MenuOption1.0, but that didn't work. it was almost progress. I booted to a MS-style blue blank screen that just restarted the PC.

I've also included a copy of my BStrap.0 file in case that is an issue.

And here are my DHCP options

Hi Hangman669

Please try the following...

Download the PXE Forced Mode Utility.
You can find the Tool here (no need to install the tool)

1. Remove Option Name: 006 PXE_Discovery_Control
2. Remove Option Name: 008 PXE_Boot_Servers

Start the PXE Foced Mode Utility and fill in the IP Adress of your GSS 3.0 Server (see Screenshot)

open the File named DHCPOptionValues.scp using Notepad or any other Editor - you fill find the Value for Option 43.

Add Option 43 to your DHCP Server with the value from the DHCPOptionValues.scp

You can also copy the DHCPOptionSet.bat File and the DHCPOptionValues.scp File to your DHCP Server and start DHCPOptionsSet.bat if you want...

After that try booting to WINPE with a Client and let me know if it works!

Important: Using DHCP Options isn´t up to date because you cannot boot UEFI Hardware and BIOS Hardware with the same Bootfile....(Option 67)

Please take a look at this KB

Using IP Helpers is the recommened method for using mixed Mode Environments (UEFI and Bios HW)

Network23

 

Thanks for the attempt, but that didn't help.

I've tried option 43 before, I just didnt remove 6 & 8 when I did or add the 00 to the end of the Binary string

Hi Hangmann669,

which error are you seeing when trying to boot to WinPE?

If you want we can do a remote session to see if we can fix this!

Network23

 

Network23,

This is the error I'm recieving:

Unfortunately, I can't remote right now. I have a busy day scheduled out. Maybe tomorrow?

HI Hangmann669,

Thanks for the upadate...

Please send me a PM if you want to start a remote session tomorrow...

in the meantime could you please check the following KB: http://www.symantec.com/docs/TECH41327

Network23

I finally got it working! And it was kinda simple, too ;)

Even though I'm using MS DHCP on the server I switched to the "Third Party" option and my PXE menu started coming through!

Thanks! Saved me an hour or two of banging my head on the desk.