KNOWN ISSUE: PXE Boot Winpe 2.1 "Exiting Intel Boot Agent" MasterImage folder shows .wrk and .tmp extensions

Products

• Deployment Solution

Issue/Introduction

Scenario:

Client is booting into PXE and at this point you will see the DHCP ////////......... Then immediately "Exiting Intel Boot Agent"

Verify the PXE configuration:

The PXE configuration shows the DS tab > Default Boot Menu option is WinPE.

Client Response Types > Enable response to request from computers not in the DS database is checked box

Enable Response to computer with active DS job assignments only is UN-Checked

The Status Tab when you highlight the PXE server shows the two Services in the bottom pane window Green and Idle.

Highlight the Winpe Managed in the PXE configuration> Select Edit and it will show you the Boot menu option. In this case it is MenuOption161

If MSDOS installed in PXE configuration the client can boot into MSDOS with no issues.

The files that are effected by this issue are located in the eXpress Share\PXE\ PXE.ini and PXEManager.ini

 PXE.ini>

[ProxyDHCP]
Discovery_BCast_Disabled=True
Discovery_List="160,1,127.0.0.1","129,1,127.0.0.1","163,1,127.0.0.1","130,1,127.0.0.1","162,1,127.0.0.1","161,1,127.0.0.1","48059,1,127.0.0.1"
Discovery_Local_Bstrap=True
Discovery_MCast_Addr="224.0.1.2"
Discovery_MCast_Disabled=True
Discovery_Server_List_Only=False

Below it is missing the menuoption161

[ProxyDHCP\X86PC\UNDI]
MENU="0,Next Device (BIOS/EFI)","160,DOS","129,DOS Managed","163,GX Managed DOS","130,Linux Managed","162,Linux pxe"

Below it is also missing the menuoption161, It will show all the other menu options except 161

[ProxyDHCP\X86PC\UNDI\MenuOption162]
ImageFile_Name="0","1","MenuOption162"
Vendor_DLL=""
Vendor_Options=""

In PXEManager.ini

[PXEServer\Shared\BootMenu]
Prompt="Press [F8] to Select a boot option"
AppendServerName=True
Timeout=16
Menu=0,160,129,163,130,162,161
MenuOrder=0,160,129,163,130,162,161
HasCustom=False

.>

[BootMenu\161]
Name="WIN PE"
Editable=True
Deletable=True
SharedScope=True
AllowAsDefault=True
BootImageType=0
OSType=3
Rev=2
RedirectCount=0
CPUMap=1

 

Cause

PXE.ini and PXEmanager.ini are missing the Boot Menu options for WinPE.

The Master Image folder eXpress\PXE\MasterImages was missing the Menu option 161 and, therefore, was not copied down to the Images folder.

When the WinPE 2.1 Image is created within the Master Image folder it does show the MenuOption164 and then select the save button within PXE configuration it renames the MenuOption131.wrk Even though there is another MenuOption131 already exist.

The only reason that menu option folders stay named with the .wrk extension is if a process has the folder locked. In this situation for an unknown reason PXE Manager had a lock on both of these directories. This may occur if a third party product such as antivirus software scans the PXE directory while PXE Manager is attempting to rename the directory.

Resolution

A hotfix is available to resolve this issue. Please contact Altiris / Symantec techncial support to obtain this hotfix with this KB reference on KB 40875 and 41655

 

Symantec Tech Support strongly recommends taking a backup on the PXE files off a remote share before applying this hotfix.

Having ‘two PXE folders’ can cause PXE service issues on the same Deployment Server Drives.

Note the PXE Manager files are for the main PXE Test manager server.zip and the Remote PXE server files are PXE Test servers.zip

1. Stop the Deployment Solution/PXE services.(including PXE Config Helper and PXE Manager services)
2. Copy the PXE hotfixes to \pxe\masterimages\upsrv\51\*.* .
3. Copy the PXE hotfixes to \pxe.
4. Start the services.
5. Create another PXE Boot and verify there are no wrk/tmp

Applies To
Deployment Solution 6.9.164
WinPE* 2.1
Linux* Automation