Automation is the key to a successful Kaseya implementation and in order to achieve the ultimate goal of 100% automation, it all starts with defining proper policies. This session will walk you through some of the key best practices organizations just like yours can do to ensure proper policies are configured and how to evolve your polices to include additional automation steps through this powerful module.
5. Leveraging Views and Groups
Associate
Organization: Policy:
Acme Inc. #1
View:
Windows Server 2008
Machine Group: Settings:
Infrastructure Monitor RAM & CPU
Machine: Associate
Policy:
IN-SRV-DB01
#2
OS: Windows Server 2008 View:
SW: SQL Server SQL Server 2005
Apply
Resulting Settings: Policies Settings:
Monitor RAM & CPU Monitor SQL Service
Monitor SQL Service
6. IT Systems Management
Evolution
Unmanaged Sneaker-Net Individually Templates Kaseya
Personal Point Solutions Managed w/Deploy Pkgs Policy
Computers Agents & Copy Settings Management
13. Policy Precedence
Define Order In Which Policies Get Processed/Applied
Top Down
Note: The first Policy Object
Type in any Policy that is
assigned, and for which the
View matches, takes affect...
Exception: Multiple item
Policy Object Types such as
Event Log Alerts, Agent
Procedures and Monitor Sets)
14. Policy Compliance
Provides Status of All Assigned Policies
In Compliance
Marked for Deployment
No Policies Assigned
Out Of Compliance
15. Policy Overrides
Occur When Settings Managed Outside of KPM
Policy
Overridden
NOTE: No More Processing of the Overridden Policy When In
Override (In this case -> Agent Menu, Checkin, Log History Objects)
16. Create/Manage Policies
• Manage the Rules Not the Exceptions!
• Example: Basic Settings
– Log History
• Rule:
– Workstations -> 31 Day Retention
– Servers -> 93 Day Retention
– Agent Menu
• Rule:
– Workstations -> No Exit, Set Account, or Disable RC
– Servers -> No Set Account or Disable RC
19. Policies by Object Type
• Granularity at the Object Type Level
• Example: Working Directory
– File System Folder Structure Differ by OS
– Linux -> /tmp/kworking
– Macintosh -> /Library/Kaseya/kworking
– Windows -> c:kworking
24. Monitoring Management
Hardware, OS, and Role Based Monitoring Policies
DOMCTLR
Windows 2003
Domain Controller
File & Print Server
SQL 2005 Server
DNS
DHCP
KSRVR
Windows 2003
SQL 2008 Server
IIS
FTP
SMTP
27. Dynamic Nature of Views
• Views are Dynamic Therefore....
– Policies Apply Dynamically
• Very Powerful Automation
– Monitoring
• Dynamic Role Monitoring
– Agent Procedures
• Conditional Agent Procedures
– Patch Management
• Dynamic Patch Policy Assignments
28. Exception Handling & One-Offs
• Avoid Overrides Whenever Possible!
• Org/Group Specific Exception Policies
– View Speficic to Org/Group
• One Off Criteria Specific Policies
– Very Narrow Criteria Views
• Machine Policies/Assignments
– Policies for Certain Machines using “Only
show selected machine IDs” Views
• Assign Exceptions Above General Policies
29. Other Policy Best Practices
Tips & Tricks
• Views Related to Policies
– Naming Convention
– Limit Sharing/Access Control of Views
• Test Your Policies
– Create Testing Views
• Only show selected machine IDs
30. Template Considerations
• Old School, but needed today for...
– Any Initial Agent Settings (before KPM policies apply)
• Initial Working Directory Path (if not using default)
• Agent Menu (if it must be hidden or custom immediately)
• Event Log Settings
• Log History retention for Agent Uptime Log
• Add-On Modules/Settings
31. Follow On...KDS Deployment
• Deploy Agent via Directory Services
– Agents Checkin
– Perform Audits
– Run Other Automation (Role detection)
• Policy Management Kicks In!!!
32. Organizational Provisioning
• Create Organization
• Create and Customize Template
– Focus on Initial & Non-Policy Managed
Settings
• Create Agent Deployment Package
– New Organization based on AD Domain
– Copy Settings from Template
– Windows Only
– Name it “New Customer - Domain”
36. Quick Look Forward
Next Release
– More Settings
• Event Log Settings
• Suspend Alarms
• Support for Add-on Modules
– Endpoint Security, Antimalware, etc.
– Global Policies
• Applies to All Orgs and Groups
– Usability
• e.g. Reason Description for Out-of Compliance