1 / 328

Kaseya Fundamentals Workshop

Kaseya Fundamentals Workshop. Policy Management. Developed by Kaseya University. Powered by IT Scholars. Kaseya Version 6.5 Last updated March, 2014. What is Covered?. Motivation Overview Policies Organization / Machine Groups Machines Policy Assignment Rules. Settings

iola
Download Presentation

Kaseya Fundamentals Workshop

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Kaseya Fundamentals Workshop • Policy Management Developed by Kaseya University Powered by IT Scholars Kaseya Version 6.5 Last updatedMarch, 2014

  2. What is Covered? • Motivation • Overview • Policies • Organization / Machine Groups • Machines • Policy Assignment Rules • Settings • Policy Matrix • Dashboard • Logs • Standard Solution Package • Summary

  3. Kaseya Fundamentals Workshop • Motivation: • Agent Templates • vs. • Policy Management

  4. Agent Templates • Pros • Enables consistency of service delivery. • Promotes standard/best practices. • Allows agent configurations to be pushed during the initial installation of the agent. • Cons • Requires user intervention. • Any changes must be applied to all the similar agents every time. • May put too much load on the KServer as there may not be a consistent way to distribute the load.

  5. Policy Management • Pros • Enables consistency of service delivery. • Promotes standard/best practices. • Provides automatic policy deployment. • Provides automatic policy compliance check. • Supports load distribution. • Simplifies the application and management of policies based on Orgs, Groups, and Views. • Cons • May take longer than agent templates to apply the initial configuration, but worth the investment.

  6. Agent Templates Settings • Agent settings can be copied during installation of Kaseya agents • Agent Deployment Package can reference an Agent Template or the settings in another agent.

  7. Agent Settings • Menu options • Credentials • Working Directory • Other options • Audit Scan / Patch Scan • Event Log Settings • Agent – Alerts • Monitor Sets • Agent Procedures

  8. Note • An agent template will have an orange square icon   to emphasize the fact that the an agent associated with this record has not checked into the KServer. • Its sole purpose is to provide additional customized settings for agents with similar roles so that such settings can be added to the settings of already-deployed agents or be used as part of an agent package.

  9. Progress Check • Do you know how Agent Templates and Policy Management are different? • When should you use Agent Templates? • When should you use Policy Management?

  10. Kaseya Fundamentals Workshop • Overview

  11. Overview • The Policy Management (KPM) module manages agent settings by policy. • In the following slides, we introduce: • Policies • Policy Assignment • Policy Compliance • Policy Conflicts • Overriding Policies • Importing/Exporting Policies • Policy Terminology • Function Overview

  12. Policies • Each policy comprises sub-categories of agent settings called policy objects. • Policy Objects include: • Agent Menu, Alerts, Audit Schedule, Checkin, Credential, Distribute Files (on-premise only), Event Log Settings, Kaseya Anti-Malware, Kaseya AntiVirus, Kaseya Security, Log History, Machine Profile, Monitor Sets, Patch File Source, Patch Procedure Schedule, Patch Reboot Action, Patch Settings, Patch Windows Automatic Update, Protection, Remote Control, and Working Directory.

  13. Policy Assignment • Policies can be assigned to machines, machine groups, or organizations. • A view further filters the affected machines. • Once assigned, policies are propagated automatically, without further intervention. • Changing a machine's association with a machine group, organization, or view, causes the appropriate policies to be automatically re-deployed.

  14. Policy Compliance & Conflicts • A compliance cycle checks that each machine is in compliance with applied policies. • VSA users can check the status of each machine to ensure it is in compliance with applied policies. • Multiple policies can be assigned to each machine. • If policies conflict, policy assignment rules determine which policy objects are obeyed and which are ignored.

  15. Overriding Policies • A policy can be overridden. • A policy override condition exists if agent settings for a machine have been set manually, outside of the Policy Management module. • For example, making changes to the agent menu of a machine using the Agent > Agent Menu function. • Policy Management policies for that object will be ignored from then on. • Policy overrides can also be cleared.

  16. Importing/Exporting Policies • Policies can be imported and exported using System > Import Center. • A System cabinet provides built-in policies that reflect best-practice solutions for common IT management tasks. • Policies can be configured for an organization automatically using the Systems Management Configuration setup wizard and these System cabinet policies. • Policies can be imported from agent templates.

  17. Policy Terminology • Applying a policy means the changes made to its policy objects are marked for deployment. • Deployment means the applied changes are propagated to target machines, based on the deployment interval set using the Policy Management > Settings function. • Pending changes are changes to policies or policy objects that have been saved but not yet applied.

  18. Note • Because deployment may take a while, the target machine might not be in compliance between the time the policy is applied and the policy is deployed.

  19. Policy Management Function Overview • Overview: Illustrates the Policy Management workflow graphically. • Dashboard: Provides a dashboard view of Policy Management activities. • Logs: Displays a log of Policy Management module activity. • Policy Matrix: Displays the policy status of all machines your scope authorizes you to see. A policy status icon displays in the left most column for every machine on this page. • Policies: Defines agent settings by policy. • Settings: Schedules the interval for automatic deployment of all policies to all assigned machines. • Organizations / Machine Groups: Assigns policies to organizations and machine groups. • Machines: Assigns policies to individual machines. You can also clear Policy Management policy overrides using this function, enabling applied policies to take effect. a b c d e f g h

  20. Policy Management Overview

  21. Kaseya Fundamentals Workshop • Policies

  22. Overview: The Policy Function d e f b c a • The Policy function defines agent policies. • Policies are organized by a folder tree. • A System cabinet provides built-in policies that reflect best-practice solutions for common IT management tasks. • Settings: Agent policy settings are grouped by setting category in this tab. • Assigned Machine Groups: The organizations and machines groups assigned to a policy display on this tab. • Assigned Machines: Use this tab to determine the machines that are members of a policy.

  23. LAB 1 Create Policy

  24. LAB • Create a policy for servers.

  25. Steps to Create a Policy – Add Folder 4 1 3 2 5 6

  26. Steps to Create a Policy – Add Policy 4 8 1 3 7 2 9 10

  27. Steps to Create a Policy – Heading 1 12 3 16 7 11 13 14 2 15 • Name: The name of a policy. • Description: The description of a policy. • View: A view definition associated with the policy. Once a policy is assigned to a view definition, the policy only applies to machines that are members of that view. This prevents the unintentional assignment of a policy to all machines in the VSA. Assigning a policy to a view is not required if the policy is only assigned directly to a machine using the Machines function.

  28. LAB Parts • We have divided the policy creation lab into smaller parts, each addressing the settings required in each category of the server policy. • We first introduce each category and then exercise what we have learned by applying the corresponding server settings to the policy category.

  29. The Agent Menu Category • This category assigns agent menu settings: • Enable Agent Icon: Check to display the agent icon in the system tray of the managed machine. Uncheck to hide the agent icon and prevent the use of agent menu options. • About <Agent>: Check to enable the machine user to click this option to display the About box for the installed agent. The default option label Agent can be customized. • <Contact Administrator...>: Check to enable the machine user to click this option to display either the user's Portal Access page or a different contact URL. The default option label Contact Administrator... can be customized. • <Your Company URL...>: Check to enable the machine user to click this option to display the URL specified in the corresponding URL field.

  30. The Agent Menu Category (cont) • Disable Remote Control: Check to allow the machine user to enable/disable remote control to the user's managed machine. • Set Account...: Check to enable the machine user to click this option to display their machineID.groupID.organizationIDand change the Kaseya Server address the agent checks into. • Refresh: Check to enable the machine user to initiate an immediate full check-in. • Exit: Check to enable the machine user to terminate the agent service on the managed machine.

  31. LAB – Part 1 • Agent Menu: • Set the agent menu on the servers so that they only show the Refresh option.

  32. Steps to Create a Policy – Agent Menu 1 4 8 3 2 5 6 7

  33. The Agent Procedures Category • This category assigns agent procedures: • Add Procedure: Adds and schedules an agent procedure. • Remove Procedure: Removes a selected agent procedure. Note: When multiple policies are assigned to the same machine, all assigned agent procedures in all assigned policies are deployed to that machine.

  34. LAB – Part 2 • Agent Procedures: • Schedule the Server Maintenance agent procedure to run weekly on Sunday sometime between 12am and 4am of the agent’s local time. • If the machine is not turned on when the maintenance is scheduled, then the machine will skip that maintenance cycle and will attempt to run the maintenance a week later.

  35. Steps to Create a Policy – Agent Procedures 1 4 6 3 7 2 8 5 9

  36. Steps to Create a Policy – Agent Procedures 1 4 3 11 2 10

  37. Steps to Create a Policy – Agent Procedures 1 13 14 15 12 16 2 17 18

  38. Steps to Create a Policy – Agent Procedures 1 4 19 3 2

  39. The Alerts Category • This category assigns standard alert notifications. Each type of alert has different configuration settings: • Agent Status: alerts when an agent is offline, first goes online, or someone has disabled remote control on the selected machine. • Application Changes: alerts when a new application is installed or removed on selected machines. • Get File: alerts when a procedure's getFile() or getFileInDirectoryPath() command executes, uploads the file, and the file is now different from the copy previously stored on the Kaseya Server. If there was no previous copy on the Kaseya Server, the alert is created. • Hardware Changes: alerts when a hardware configuration changes on the selected machines.

  40. The Alerts Category (cont) • Low Disk: alerts when available disk space falls below a specified percentage of free disk space. • Event Log: alerts when an event log entry for a selected machine matches a specified criteria. After selecting the event log type, you can filter the alert conditions specified by event set and by event category. • LAN Watch: scans a machine’s local LAN and detects new machines and devices connected to the machine's LAN. • Agent Procedure Failure: alerts when an agent procedure fails to execute on a managed machine. • Protection Violation: alerts when a file is changed or access violation detected on a managed machine. • Patch Alert: alerts for patch management events on managed machines (See Patch Settings category).

  41. Note • When multiple policies are assigned to the same machine, all assigned event log alerts in all assigned policies are deployed to that machine. • For all other types of alerts, only one policy can be in effect at any one time.

  42. LAB – Part 3 • Alerts: • Set Alerts for Agent Status • Alerts: Agent has not checked in for 10 minutes; rearm after 12 hours; User disables remote control. • Actions: Alarm and Email • Set Alerts for Application Changes • Alerts: New applications installed; Existing applications deleted. • Actions: Alarm and Email • Set Alerts for Hardware Changes • Alerts: When any hardware changes. • Actions: Alarm and Email

  43. LAB – Part 3 (cont) • Set Alerts for Low Disk • Alerts: When any fixed partition has less than 20% of free space. • Actions: Alarm and Email • Set Alerts for Event Logs: • Alerts: System and Application Errors; Alert once; Ignore additional alarms for one day. • Actions: Alarm and Email

  44. Steps to Create a Policy – Alerts – Agent Status 1 4 6 3 7 8 2 5

  45. Steps to Create a Policy – Alerts – Agent Status 1 4 6 3 7 2 9 10 11 12 13 14 15 16

  46. Steps to Create a Policy – Alerts – Agent Status 1 4 6 3 2

  47. Steps to Create a Policy – Alerts – Application Changes 1 4 6 3 17 2 18

  48. Steps to Create a Policy – Alerts – Application Changes 1 4 6 3 17 2 19 20 21 22 23 24

  49. Steps to Create a Policy – Alerts – Application Changes 1 4 6 3 2

  50. Steps to Create a Policy – Alerts – Hardware Changes 1 4 6 3 25 2 26

More Related