Don't let techs launch from an unlocked template as that will create a locked template each time. Locked templates are a way of ensuring consistency and a historical trail of everything built using a particular template. Yes, you can just rename a locked template via right click, or clicking again after it has been selected.
MarXtar Ltd/MarXtar Corporation
LANDesk Expert Solution Provider
Update - New v2.3 Adds Process Monitoring & Historical Analysis for Concurrency and Device Based
Update - New v2.3 Now with Automated Subnet Rep Selection and Optional Maintenance of LANDESK Reps
The One-Stop Shop for LANDesk Enhancements
Hmm... whenever I try to rename a locked template, it gives me an error that the name already exists whether on remote console or on the core. I am on 9.5 SP2 and it would throw an error in previous versions also. I may need to run this through support.
A question I have about using locked templates, which wasn't clear from my first post, is what happens when a tech runs a machine from a locked template and that machine fails? How do you ensure that rerunning that same machine will not pick up the failed template and continue from the point of failure?
I was testing using the locked template and a tech had a failed machine that showed up in the history of the task. I deleted the tech's associated task for the template, but it would not start a template from scratch until I deleted the locked template that had the failed history. How do I deal with this?
1 of 1 people found this helpful
Once a template fails it is not accessible from the machines.
No machine can pick up a failed template only active templates.
As for locked templates. I have a single master template which is displayed as a shortcut in the Public folder ( i never place actual templates in Public but thats just me )
this is then chosen and locked as it creates the new build task.
The locked templates can be used again if the engineer started the build task again from their console. But not from provisioning login. They could also add another machine to the task and delete the one they were building. And yes it would use the locked template but it would just start again.
if provisioning is running smoothly and your template is good ( ie the failure reason was user error or a network break ) you should be ok using the same task again. UNLESS you change something in the original template the locked one was created from as no new changes will pick up. Hence the word locked.
If the template would not start then the core thinks the build task is still active. Was it definitely failed in the console?
You cannot run two provisioning jobs on one machine. The previous job has to fail for a new one to start.