For me, the advantage of the "Configure Agent" action is, that I wouldn't have to change several Prov. Templates in order to make them use the new agent config (agent_20140701.exe for example). I would only need to change the settings, press "save" and the latest agent would be installed on new clients (as the config is referenced in the Prov. Template). If now (like in the "Deploy Image" action) the Preferred Server would be used, I would be happy.
However in Provsioning now you can choose the action to map to a preferred server? which version of LANDesk are you using?
Cant you use the Map to preferred server then copy the agent from there to the c:\ - that's what i am doing. Then it acts like the 'configure agent' action.
This is true. I could use the MapToPS action (we have 9.5SP2), but not together with the Configure Agent action. LANDesk is always getting the files from the Core, which is bad, when installing in remote locations:
The catch is, that our agent configs have different names and this would mean, that I have to adjust several templates when I change them. Right, I use the MapToPS and the self-extracting exe files for agent installation..