Kaseya Connect 2013: Templates and Policy: The Next Steps
A practical session on reusing your templates to benefit from the power of Policy Management, we'll compare the previous templates concept to latest Policy Management capabilities and highlight key considerations for migrating these settings. We'll also cover some hints and tips on getting the most from the new version of Policy Management and the new View features to improve your Automation.
Good Practice for Policy Management• What makes a machine‟smanagement requirements unique?– OS?– SLA?• Ask yourself:– Is this something I can apply to allmachines of this „type‟?
4 Items that cover all permutationsLocationHardwareRole Utility
Location• Any time a setting is specific to asingle location– Set Credential– File Source location
Hardware• Any time a setting is specific to thehardware– HW Monitor Sets– HW Event Filters– HW Agent Procedures– HW Specific patch policies (not often)
Role• The core purposed of the device,usual decided by either a coreapplication or type of W/S user e.g.:– Exchange– Oracle– Quickbooks– Finance user– Admin user– SQL Server
Role Settings• All major settings that haven‟talready applied to location orhardware– Role Specific Patch settings– Most Agent Settings– Role specific Agent Procedures– Role specific monitoring– All other settings
Utility• Anything that is not Role defining but a„supportive‟ application that may appearon multiple machines– Anti-virus– Anti-malware– Backup• There might be multiple Utility policies thatapply to one machine, so only put veryspecific items for that utility– Monitor Sets– Agent Procedures– Alert Filters
Policy „Rules‟• Start with a minimal amount of policies• Only create a new policy when an existingone _really_ can‟t be made to fit• Try and find ways to make a policy flexibleenough to work on multiple machines toavoid creating too many– E.g. Agent Procedures that check conditionsbefore running• Create a view _before_ you create thePolicy
New Site Rollout Process• First machine• Push „base‟ agent (KDS?)• Apply Base policy• Apply all other policies
Not everything is a policy• Still need 1 template:– Step 4 „the most important step‟
Granularity & ExceptionsDifficultManaging with Templates…Managing with Policies…Scalable and RepeatableEasy
Migrating Templates• Import your templates into policies– Create/Select Policy Folder & Import fromtemplate• But wait...– Why do you have this template?– What settings where you copying?– Where do you use the template?– Do you have the View already?• Setting imported for all policy objects!– Save As is your friend• For each “applicable” policy object• Easy Enough?