LabTech Support Forums

Template Check box behavior

This forum is for discussion of template related issues.

Moderator: jware.connectwise

Template Check box behavior

Postby sam.formatech-it » Fri Jun 10, 2011 5:31 pm

Sorry to ask such a basic question, but I couldn't find an answer from documentation and the text on the interface isn't clear.

as far as templates go, can someone confirm that the check boxes behave as follows;

1. If the check box is completely empty, that setting is disabled as in the feature (lets say caching) is no longer available.

2. If the check box is checked, then that setting is enabled

3. If the check box is Grey'd, then that setting is not configured, leaving peer templates open to configure the setting.


As far as hierarchy goes;

The only time you will have predictable results when applying templates with conflicting settings is when one is a child of the other. In which case template application follows the FIFO, meaning the Template applied to the child folder will be the setting applied.

Again, sorry for such a basic question, if you know where it is better documented in the online docs a link would be greatly appreciated.

Thanks,
- Sam
sam.formatech-it
Jr. Member
Jr. Member
 
Posts: 58
Joined: Wed Dec 31, 1969 8:00 pm

Re: Template Check box behavior

Postby teamits » Sun Jun 12, 2011 6:40 pm

You're correct on the checkboxes. I believe all settings can be disabled/greyed out except for the Schedule setting which defaults to (and is apparently pushed out as) Not Set, which is a rather annoying longstanding bug.

Regarding which template is applied there no hierarchy (unless this is new in v2011?). The last template that gets applied takes effect so any templates that are applied by autojoin should not have overlapping settings. In essence, this tends to require one template per setting, at least for any that differ from a default/baseline template setting that is applied to all PCs.
Steve
teamits
Hero Member
Hero Member
 
Posts: 1577
Joined: Wed Dec 31, 1969 8:00 pm

Re: Template Check box behavior

Postby vernon.app-care » Sun Jun 12, 2011 8:26 pm

My understanding in 2010 and the older 2.5 versions was that the group with the lowest groupid would win in the case of multiple groups applying templates that set the same template settings. Of course this makes no real world sense, just in a mysql programming sense. So the best policy is to always avoid applying templates via groups where the same template settings would overlap between defined template groups.

Depending on how granular you need to control your settings you may need to go to to the one group/template per setting config. I have been able to group the settings into group/template combination that make sense together and are exclusive. I have two different service brands so I have two separate searches/groups/templates that apply the different branding to the agent, pop up text, etc. Agents can only be in one group based on their contract level.

I apply Windows Updates nightly for workstations which allows me to have an single template/group for patch install window settings. If a client required that I only could patch workstations only on a single specific night of the week, this would require 7 separate template/groups one for each night of the week in addition to my current workstation every night patch install template/group based on the searches and the limit to checkbox is always set to remove agent that no longer fit the search results.

Items that can be set across all agents can be handled in a default group, but if you are going to EVER want to vary any of the settings you are considering in the default group you should not define them in a default group/template. For example, if you ever want to hide your agent during an audit for new or potential clients then the default agent visibility settings should not be set in the default group. Instead you should use branding group(s), even if there is just one that turns on all of the settings you would normally have enabled for your clients when they are not in an audit only state.

Also members of your template/groups should always be autojoined versus and dragged and dropped so that they receive your ongoing template changes. Template settings are applied to drag/drop agents upon their joining the group, or when manually applied through the group template Apply button. Autojoin agents have their template settings reset every 30 minutes when Labtech forces the group autojoins to run.
Vernon Southmayd
Java, Reader, iTunes and others - Audited, Updated, Verified, Ticketed and Billed
web: http://www.app-care.com
vernon.app-care
Hero Member
Hero Member
 
Posts: 1100
Joined: Wed Dec 31, 1969 8:00 pm
Location: Saginaw, MI


Return to Templates

Who is online

Users browsing this forum: No registered users and 1 guest

cron