Kaseya Connect 2013: Templates and Policy: The Next Steps


Published on

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.

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Reinforce the importance of views and explain/show the relationship between Views and Policies. Best Practice in V1.0 – these views should be ‘static’, i.e. the items are not likely to change.
  • Limitations on views means for now you may have to run Service or Reg lookups via the base policy and then create a view that uses the procedure
  • Kaseya Connect 2013: Templates and Policy: The Next Steps

    1. 1. Templates and PolicyThe Next Steps
    2. 2. PatchingRemote Control SettingsAgentProceduresLocal Admin UserMonitor SetsAlert ThresholdsScheduling
    3. 3. Policy Objects• Agent Menu• Agent Procedures• Alerts• Check-in• Credential• Distribute File• Logging• Machine Profile• Monitor Sets• Patch Settings• Protection• Remote Control• Working Directory• Many more…
    4. 4. Policys are Driven by Views
    5. 5. 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‟?
    6. 6. 4 Items that cover all permutationsLocationHardwareRole Utility
    7. 7. Location• Any time a setting is specific to asingle location– Set Credential– File Source location
    8. 8. Hardware• Any time a setting is specific to thehardware– HW Monitor Sets– HW Event Filters– HW Agent Procedures– HW Specific patch policies (not often)
    9. 9. 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
    10. 10. 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
    11. 11. 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
    12. 12. 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
    13. 13. New Site Rollout Process• First machine• Push „base‟ agent (KDS?)• Apply Base policy• Apply all other policies
    14. 14. Not everything is a policy• Still need 1 template:– Step 4 „the most important step‟
    15. 15. Migration Overview
    16. 16. How it was
    17. 17. Templates vs Policy Objects
    18. 18. Granularity & ExceptionsDifficultManaging with Templates…Managing with Policies…Scalable and RepeatableEasy
    19. 19. 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?
    20. 20. Example: Exchange Server• Template– Monitor Sets– Event Sets
    21. 21. Lets do this...Exchange Server• Create a „Template Imports‟ Folder• Import From Template
    22. 22. After the Import...
    23. 23. Cleanup Process• Save As - Create Derivatives• Remove „Non-Applicable‟ Policy Objects/SaveContinueon downthe line
    24. 24. Link to View
    25. 25. Rinse and Repeat...Final Steps• Continue same process...• Organize using folders– Base on Assignment Approach• Assign Policies/Policy Folders
    26. 26. ENDThanks