Reviewed: October 2014
Versions Effected: LDMS 9.6
Problem:
After upgrading the LDMS suite from a previous version to LDMS 9.6 none of the PXE representatives are working and the provisioning templates are not functioning correctly failing at some of the provisioning actions.
Cause:
This is caused by the old agent on the WIN PE installed with the old versions of PXE representative. The new LANDESK WIN PE is based on the latest version from of the WIN PE from Microsoft version 5. Our version includes a agent specially designed to work in the WIN PE environment and facilitate communication and the WIN PE actions from the core to the client machine being imaged. The new LDMS 9.6 is only partially compatible with some of the actions as the new core version communicates slightly differently with the agent on the WIN PE, which the older version cannot always interpret. This has been seen in a couple of support cases.
Resolution:
Firstly make sure that the agent of the PXE representative is up to date and inline with the version of the core. For example If the agent is not a LDMS 9.6 agent upgrade it using these steps:
1. Uninstall the old agent with the unistallwinclient.exe , which can be found in management suite folder under ldmain directory, with the forcecelan switch. (This is to create a clean installation of the agent)
More information on this process can be found here: How to uninstall the LANDesk Agent
2. Restart the target machine
3. Install the LDMS 9.6 agent
Once this is done the machine is ready to have the new PXE representative installed on it. Follow these steps to do this successfully. The removal of the old PXE representative is important, so we can remove anything that cause issue later.
1.In the LDMS console go to Tools > Distribution > Distribution Packages
2. Under the Public Packages folder, right click on the ' PXE Representative Removal' Script and schedule it for deployment.
3. Target the chosen machine, right click , and start now > click on All
4. Once this has complete it would have removed all traces of the old PXE representative version from your old installation.Now restart the machine to fully complete the process
5. Once restarted, Go back to the Public Packages folder, and this time right click on the ' PXE Representative Deployment' Script and schedule it for deployment.
6. As before , Target the chosen machine, right click , and click start now
This will then resolve the issue.