if you are getting the abortpxe.com error message you might want to adjust the CacheExpire value in the registry as detailed in the following post. A quick glance in the registry will reveal the value but you can also check what value is being used by examining the SMSPXE.log file and search for CacheExpire in the Log. Note that if you have several PXE Service Points (Configuration Manager hierarchy) that you’ll need to make the change on each PSP that you want the CacheExpire value set to. Below is a sample of the CacheExpire value via a SMSPXE.log file:-
Loaded PXE settings from reg key HKLM\Software\Microsoft\SMS\PXE:
PXE Settings:
IsActive: Yes
SupportUnknownMachines: Yes
MACIgnoreListFile: <empty>
ResponseDelay: 0
CacheExpire: 300
HTTP Port: 8530
HTTPS Port: 443
IISSSLState: 0x0
BindPolicy: Exclude <empty>
TRK: <non empty>
SiteSignCert: <empty>
Root CA Certs: <empty>
PXE GUID: 653697fc-53e6-4c32-9552-bfd5a1835623
PXEPassword: <non empty>
The CacheExpire value above is set to 300 seconds, or five minutes. If your value is listed as 0 or 3600 then it’s at the default setting of one hour, make your change in the registry and restart the Windows Deployment Service to see the change take effect. During testing you can set the value of the CacheExpire key to 60 (60 seconds = 1 minute). This will minimize PXE booting issues being caused by the SMS PXE cache. The default of the CacheExpire
key is either 0 or 3600, both which are 3600 seconds (1 hour). After
testing is complete, the value of this registry setting will need to be
determined based on environmental conditions.
Note that each time WDS and the PXE Service Point is reinstalled the value of this key is reset back to 0.
For more info see: ConfigMgr 2007: Troubleshooting PXE Service Point Issues and WDS service not starting
