Problem:
New templates appear in the template window in the console. It is very hard to manage templates with all of these unwanted templates.
Provisioning history is very hard to follow when it is split up among all of the different spawned/locked templates.
Cause:
Scheduling open template causes new locked templates to be scheduled. This is done to prevent corruption of the template/database if it is in use and someone else is allowed to edit it.
Resolution:
- When having your techs schedule a template, you want to have them only schedule a template that is locked.
- Once you are done configuring a template, you can lock it by scheduling it against a "dummy device" in the database. Then put your new locked template in the public folder so that your techs can only see the locked template.
- If you want to change the name of your locked template, you can do so in the database. You want to go into the PROV_TEMPLATE_DEF table and change the value in the NAME column that corresponds to the locked template you are trying to make available to be scheduled.
Remember to always have regular backups of your database before making changes in the database. The change suggested here is relatively simple, but if you do not know your way around a SQL database, you do not want to accidentally make a change that can bring your database down. A good rule to adhere to; If you do not have a backup less than 24 hours old, make one before altering your database.