Normally, that scenario is supported and the agent should install again without issues.
Do you have any agent remnants on the image you use to build theses machines? I could see that causing the install process to fail.
There are a lot of variables to deal with here so I think it would be best to gather logs from both the Protect server and the target Agent client machine.
Complete steps 1-5 for the Protect console and the Agent logging to clear the logs.
Attempt to install the agent then gather the logs noted in step 4 for the console and agent machine.
Open a case with support and ATTN the case to Charles and I will take a look ASAP. https://support.shavlik.com/Login.aspx?path=%2fCaseLogging.aspx
Protect 9.X console logging:
1. Please open the Protect GUI and then go to Tools > Options > Logging and change logging to “All” for both user interface and services.
a. If you are unable to set logging via the GUI see this doc: http://community.shavlik.com/docs/DOC-22938
2. Close the Protect GUI.
3. Stop the following services
a.Shavlik Protect Console Service
b. ST Remote Scheduler Service
4. Delete all the logs from
a. Windows 7, 8, 2008, 2012 & Vista: C:\ProgramData\LANDesk\Shavlik Protect\Logs
b. Earlier OS’s: C:\Documents and Settings\All Users\Application Data\LANDesk\Shavlik Protect\Logs
5. Start the console service and open the Protect GUI.
Protect 9.x agent logging:
1. Open the agent policy assigned to the machine we are gathering logs from.
2. Change the logging level to ‘All’ and Save and update Agents. Choose to update agents if prompted.
3. Go to the target machine, close the agent GUI and stop the services:
o The services start with Shavlik or ST.
4. Delete all the logs from:
o Vista & Later: C:\ProgramData\LANDesk\Shavlik Protect\Logs
o Earlier OS’s: C:\Documents and Settings\All Users\Application Data\ LANDesk\Shavlik Protect\Logs
5. Start services.
Please let me know if you need have any questions.
We appear to have this corrected now. Not sure what exactly was causing it.