Peter,
I'd be more than happy if they updated their documentation and training to use the process that Tanner outlined and posted. No sense in spending thousands of dollars in sending our technicians to training, only to then tell them don't use the documented procedures, use this other forum posted suggestion. We've been using LANDesk for several years, long before version 8. We duplicated this same problem in version 8.x and reported it then.
The documented procedure is here: http://help.landesk.com/Topic/Index/ENU/LDMS/9.5/Content/Windows/osd_t_update_pxe_representative.htm also page 117 of the LANDesk training manual that all paid LANDesk training uses and the trainers would walk you through is the documented process in this link.
.
Sorry, but we are both still using a documented work around, only documented by Tanner and other TAMs or other customers. The documentation and LANDesk training for version 8 is also the same set of instructions. The intended process for updating PXE reps is to re-deploy the agents.
Again, we've used this documented work around for years because we were told that the failures were mainly due to our environment or setup. Having replicated this in LANDesk's own boot camp, that statement no longer holds true and we'd be happy to see either one of two things happen. (1) The installation process as currently documented actually works 100% of the time or (2) All training, training documentation and helpdesk documents indicate that re-installing the agent is known to cause problems and a loss of a PXE rep and its services, DO NOT USE IT, but instead use script X as provided by LANDesk.