Summary

Guidance for upgrading PXE Everywhere.

The previous names PXE Everywhere Local and PXELite have been replaced by PXE Everywhere Agent which is a client module in 1E Client. Please refer to Name changes introduced in PXE Everywhere 4.0 at the end of this page for full details including changes to log files.

Overview:

  1. Review  Requirements and read through the process below to understand what is involved
  2. Upgrade PXE Everywhere Central
  3. Upgrade or install PXE Everywhere Responders to support subnets where DHCP is blocked
  4. Deploy 1E Client with PXE Everywhere enabled.
  5. Update Task Sequences

If you are implementing DHCP Snooping for the first time, at the same time as upgrading an existing implementation of PXE Everywhere, then:

  • please refer to guidance provided in Design Considerations - Infrastructure requirements regarding deployment of PXE Everywhere Responder(s) and configuring additional DHCP Relays (IP helpers)
  • on computers where 1E Client with PXE Everywhere module is installed, you must change the inbound firewall port from 67 to 2067 (or different custom port)
  • please refer to Known issues: Issues installing PXE Everywhere Responder regarding:
    • PXE Everywhere Agent and PXE Everywhere Responder are not supported on the same computer
    • Installing PXE Everywhere Responder on a legacy PXE Everywhere Agent that was previously installed with support for DHCP Snooping enabled - also see note below.
On this page:

Upgrading to PXE Everywhere 4.0

The process for upgrading PXE Everywhere is:

  1. On the PXE Everywhere Central server, perform any necessary pre-upgrade steps
    • Always make a backup of web.config file if any custom changes have been made to the default settings in it.
    • Ensure that any custom settings that have been modified in the PXELite Application pool are captured.
    • Create a backup of stored procedures deployed by the PXE Everywhere central installer if any custom changes are made to them.
       
  2. Upgrade the PXE Everywhere Central components by following the steps described in Installing PXE Everywhere Central.

    Different versions of PXE Everywhere Central cannot co-exist on the same server.
  3. Perform any necessary post-upgrade steps

    • Restore the backup of web.config file if any custom changes were made to the default settings prior to upgrade.
    • Perform modifications to any custom settings that were modified in the PXELite Application pool prior to upgrade.
    • Restore the backup of customized stored procedures that were created prior to upgrade.
    Some changes mentioned above require an IIS reset before they come into effect.
  4. Verify the PXE Everywhere Central functionality by following the steps described in Verifying - PXE Everywhere Central.
     
  5. If you are implementing in an environment that has DHCP blocked (for example using DCP Snooping), and you have existing Responders, they can be upgraded using the steps for Installing PXE Everywhere Responder.

    PXE Everywhere Responder v4.0 and later has its own installer, which can be used to upgrade the Static Responders. Previous versions of Responders (also known as Static Responders) are legacy PXE Everywhere Agents configured in Responder mode, with its DHCP Port fixed at 67. 

    The PXE Everywhere Responder can also be used to upgrade a normal Agent to function as a new Responder. A known issue exists if the previous Agent had support for DHCP Snooping enabled. Then you will need to forcibly change its DHCP port back to 67 by including DHCPPORT=67 as a command-line installer property when installing the Responder. You can optionally include this installer property when installing or upgrading other scenarios. 

  6. Upgrade all the PXE Everywhere Agents to the latest version by following the steps for Installing PXE Everywhere Agents.

    All Agents on a subnet must be upgraded together. Different versions of PXE Everywhere Agent cannot co-exist on the same subnet.

    1E Client Deployment Assistant 1.5 is the recommended method of installing and upgrading PXE Everywhere Agent.

    If you deployed legacy PXE Everywhere Agent using a previous version of Client Deployment Assistant (CDA) then you should upgrade using the latest version of CDA. If you upgrade a CDA installation using the MSI, for example in a test lab, then the boot files (ADK files and boot image) will not be migrated to the new location used by the 1E Client's PXE Everywhere Agent, and you will need to deploy the ADK files and boot image as a post-install tasks, as described in Deploying Microsoft ADK files.

  7. Update any Task Sequences used to stage 1E PXE Everywhere boot images, with the new path for running CreateBCD.exe

    Please refer to Preparing and deploying 1E PXE Everywhere boot images. The legacy PXE Everywhere Agent was only x86 therefore had different paths for x64 and x86 platforms. PXE Everywhere Agent in 1E Client has separate installers for x86 and x64, and only uses one path, and does not require any OS conditions. Existing Task Sequences will have two Stage boot image steps:

    • Stage boot image (x64 systems)
    • Stage boot image (x86 systems) 

    Edit the Task Sequence (or a clone) as follows:

    • Delete one of the above steps, and edit the other remaining step
    • Change its name to Stage boot image
    • Change the command line as shown in the table below
    • Remove the existing conditions - click Options tab and Remove All
    • Click OK to save the Task Sequence
    PlatformLegacyNew command-line
    x64"%ProgramFiles(x86)%\1E\PXE Lite\Server\x64\CreateBcd.exe"

    "%ProgramFiles%\1E\Client\Extensibility\PXEEverywhere\CreateBcd.exe"

    x86"%ProgramFiles%\1E\PXE Lite\Server\i386\CreateBCD.exe"

    Deploy the updated/cloned Task Sequence to the 1E Client Collection as described in Preparing and deploying 1E PXE Everywhere boot images: Deploy the Task Sequence to stage a boot image.

    You do not need to update boot images.

  8. Update other OS Deployment Task Sequences to use the new 1E PXE Everywhere boot images.

Next steps

Please refer to Verifying to verify your PXE Everywhere implementation.

Prepare and deploy the boot image using Preparing and deploying 1E PXE Everywhere boot images.

Name changes introduced in PXE Everywhere 4.0


PXE Everywhere CentralPXE Everywhere ResponderPXE Everywhere Agent


Legacy

New

Legacy

New

Legacy

New

MSI NamePXELiteCentral.msiPXE EverywhereCentral.msiPXELiteLocal.msiPXEEverywhereResponder.msiPXELiteLocal.msi1EClient.msi

Program Files folder

1E\PXE Lite1E\PXE Everywhere1E\PXE Lite\Server1E\PXEEverywhere\Responder1E\PXE Lite\Server1E\Client\Extensibility\PXEEverywhere

ProgramData Folder

1E\PXELite

1E\PXEEverywhere

1E\PXELite

1E\PXEEverywhere

1E\PXELite

1E\PXEEverywhere

Log File Name

WebService.log

WebService.log

PXELiteServer.log

PXEEverywhereResponder.log

PXELiteServer.log

PXEEverywhere.log

HKLM\SOFTWARE Registry1E\PXELiteCentral1E\PXELiteCentral1E\PXELiteServer1E\PXELiteServer1E\PXELiteServer1E\PXEEverywhere

Service Display name

n/an/a

1E PXE Lite Server

1E PXE Everywhere Responder

1E PXE Lite Server

1E Client

Service name

n/an/a

PXELiteServer

PXEEverywhereResponder

PXELiteServer

1EClient

IIS SitePXELitePXELiten/an/an/an/a