Ghost Solution Suite

GSS 3.1

WinPE10

Hi all,

I remotely installed the client onto the Optiplex 5040, created the task to deploy an image that I had created from a different GSS server and tried to send the image to the machine. PxE tries to boot up but it cannot find the PxE server and the task details show that the computer is unable to boot to Windows automation (Status code 16).The services are running on the machine, and the driver that is being used on the 5040 is included in the list of drivers under the PxE boot image.

 

Thanks!

 

 

 

How far does it get in the PXE boot process? Exactly where does it fail and with exactly what message?

We are under the gun to get this set up quickly (w10 testing/deployments) so I downgraded to 3.0 as I have 2 other servers in different locations set up successfully using GSS 3.0 hf4 but I am still getting the same result...

 

The machine attempting to boot into PXE comes up with the client MAC and IP settings and the has the message 

"PXE-E32: TFTP open timeout

PXE-M0F: Exiting Intel Boot Agent"

and then boots into Windows.

 

Aclient.log

[05/24/2016 15:43:30.085 1624 0] bootstrap.cpp:1129 - Error reading input file.
[05/24/2016 15:43:34.125 1624 0] bootstrap.cpp:465 GetCfgFilename(): strName = C: 
[05/24/2016 15:43:39.367 2520 0] ReplyUpdateComputer.cpp:190 - Error removing registry value.
[05/24/2016 15:43:39.373 2520 0] ReplyUpdateComputer.cpp:296 - Error reading logevent status from registry.
[05/24/2016 15:43:39.477 2544 0] apps\dsagent\toolbox\default\handlers\internal\SetOneTimePXEBoot.cpp:201 CSetOneTimePxeBoot::HandleMessage(): caught exception
    apps\dsagent\toolbox\default\handlers\internal\SetOneTimePXEBoot.cpp:193 - One time Pxe boot is not available
    Value=0, SystemError=0x00000000
[05/24/2016 15:43:39.483 2544 0] DsAgent.cpp:488 About to serialize objects
[05/24/2016 15:43:39.489 2420 0] InputThread.cpp:323 - Exiting Input Thread
[05/24/2016 15:43:39.535 2404 0] UiInitialConnectThread.cpp:97 - CUIError error, CUiInitialConnect::ReadConnectPacket() - Shutting down. - 0
[05/24/2016 15:43:39.541 2404 0] UiInitialConnectThread.cpp:138 - CUiInitialConnect::Run RETURNING...
[05/24/2016 15:43:39.546 2412 0] apps\dsagent\agent\LogEventThread.cpp:57 - CLogEventThread::Run CLogEventError
    Thrown from apps\dsagent\agent\LogEventThread.cpp:113 -message = CLogEventThread::ReadLogEvent() - Shutting down.
    SystemError Value = 0x00000000
    
[05/24/2016 15:43:39.552 1624 0] DsAgent.cpp:488 About to serialize objects
[05/24/2016 15:43:53.072 1996 0] main.cpp:786 - Leaving Main()
[05/24/2016 15:43:53.078 1996 0] main.cpp:787 - =============================================================

 

 

Server Details

"Unable to boot to Windows Automation" with a status code of 116

Boot Image settings under PXE Configuration

{No Description]

Operating system: WinPE 5.X
OEM extension: <none>
File server type: Microsoft Windows
Transport: TCP/IP
Screenlock: Disabled
Firewall: Disabled
Compression: Compressed
Installed packages:
  MICROSOFT-WINDOWS-COMMON-FOUNDATION-PACKAGE=Required
  WMI=Required
  WSH=True

IP address: Use DHCP

Network adapter: Autodetect

Workgroup: INTRANET
User: admin
Drive mappings: 
  M: \\Servername\eXpress
  U: \\Servername\ghost

Ghost Solution Suite Server found by IP address
IP address: Ghost Solution Suite IP
Port: 402

Command line: "-pxe" "64bit" "-nonetboot" "-os" "winpe" "-bdc" "BDC\MenuOption160.bdc" "-rootpath" "\\Servername\eXpress\PXE\MasterImages\MenuOption160.tmp" "-x64" "X64" 

 

Distribute Disk Image Additional Parameters:

-CLONE,MODE=RESTORE,SRC=%IMAGE_FILENAME%,DST=1 -sure

 

Thanks!

I have tried it on a couple of different machines to try and troubleshoot if it was a problem with the driver that I included but it looks like the problem is also happening with a Dell 7010 but that model was able to connect to the PXE server in a different location without adding additional drivers last time.

 

Thanks,

 

EDIT:  -Further Testing

It seemed like the client was unable to find the PXE server so I downloaded WinAgents TFTP client and ran a test against the Ghost/PXE server and it was successfully able to download the BStrap.0 file as well as the boot.wim file. I also so an older article on adding Option 60 to the DHCP server and enabling it which I did to no avail as well.

If the PC won't even download the PXE boot menu that's not a driver issue, the driver doesn't get loaded until either WinPE or Windows starts up. Is this a model specific problem? If so try a BIOS upgrade which will update the PXE boot code. If not, how is your PXE server discovered?

Originally I thought it mightve been a driver issue because when I was installing the server in a different location we had the same problem before adding Surface drivers (Prior to the release) and it was my first 5040 that I tried to image. 

It doesnt look like it's model specific as it isn't working for Dell 7010s or 5040s and we have some 7010s at a different location that are working fine. We can remotely push out the agents to the machines and the agents are set to connect directly to the GSS. The computers reboot to try to connect to the PXE server and can't connect, but a test PXE client can connect to the PXE server without any issue.

 

Thanks

 

So how are your PXE clients pointed to the PXE server?