kaseya fundamentals workshop day fourusers.cis.fiu.edu/~sadjadi/teaching/it...
TRANSCRIPT
Kaseya Fundamentals Workshop
Developed by
Kaseya University Powered by
IT Scholars Kaseya Version 6.5
Last updated March, 2014
DAY FOUR
Day Three Review
• State Based Monitoring
• Event Based Monitoring
• Monitoring Labs
• Introduc<on to Agent Procedures
Kaseya Fundamentals Workshop
LAB REVIEW
What is Covered?
• Agent Procedures
• Policy Management
• Standard Solu<on Package – Systems Management Configura<on Wizard
Kaseya Fundamentals Workshop
AGENT PROCEDURES
Agent Procedure Variables
• Procedure Variables* – Variables defined within an Agent Procedures – Use the # symbol to call the variable #AgentTemp#
• Managed Variables (Machine Group specific Variables) – Variables defined using Managed Variables func<on
– Use the <> symbol to call the variable <FileLocation>
• Global Variables – Variables defined within an Agent Procedures, but available to other procedures – Define the variable #global:VariableName#
*NOTE: Agent Procedures and Procedure Variables have a lifespan of 2 hours.
Agent Procedure Variables
• Managed Variables (Machine Group specific Variables) – Variables defined using Managed Variables func<on
– Use the <> symbol to call the variable <FileLocation>
• Public Variables -‐ all users have access to the variable.
• Private Variables -‐ only accessible to the VSA user who created the variable.
Agent Procedures • Agent Procedures Examples
– Applica<on Deployment
– Modifying Windows Registry – Review Standard Solu<on Package Maintenance Procedures
• Viewing Agent Procedure Logs – Use the Write Procedure Log Entry to enter feedback or return informa<on about the Agent Procedure.
• VISIT the help files for IF-‐ELSE-‐STEP Commands
Kaseya Packager • The Packager is a wizard tool used to create an installa<on package when the exis<ng install packages may need user interac<on and may not include some pre-‐ and/or post-‐installa<on steps.
• Packager evaluates the state of the target machine before and a]er the installa<on process.
How the Packager Works? • In Windows, the state of the target machine is simply the state of the Windows registry and its file system.
• The Packager compiles the differences in the before and a]er states into a single executable file—the package—that can be distributed via agent procedures to any managed machine.
Agent Procedure Resources
• Visit Kaseya Community – hap://community.kaseya.com
– Under Resources and KnowledgeBase • Review the Help Files for Command step defini<ons.
• Complete the Hands-‐On lab to become fluent with the editor and procedure command structure.
Kaseya Fundamentals Workshop
POLICY MANAGEMENT
Policy Management
• Manage Agent Secngs • Create Filters for Policy Applica<on
– U<lizing Views • Policy Applica<on • Policy Overrides and Excep<ons • Scheduling Policy applica<ons
Policy Management
Policy Management • Policy Assignment
– Organiza<on or Machine Groups
– Mul<ple Policy Assignments – Precedence Level
• Folder Level – First Come First Served
• Policy Level – First Come First Served • VSA Specific Module Func<onality – Overrides Policy
• Automa<c Policy Deployment – Compliance Check
Policy Crea<on and Organiza<on
• Crea<ng Policies for the different modules – Policy for Basic Agent Configura<on.
• Agent Menu • Creden<als
– Policy for Patch Management – Policy for Monitoring – Policy for Agent Procedures
Kaseya Fundamentals Workshop
STANDARD SOLUTION PACKAGE
Standard Solu<on Package
• Quickly configure and apply machine management policies – Audit Scheduling – Monitoring – Alerts – Patch Management – Agent Procedures for Rou<ne Machine Maintenance
• Policy is assigned to an Organiza<on • Will not override current Agent Configura<on
Standard Solu<on Package
• What does it include? – Policies – Agent Procedures – Monitor Sets – Event Sets – Views – Patch Management Policies
• Standard Solu<on Package creates a Cabinet / Folder – System / Core
Standard Solu<on Package
• Supported OS plaforms – Microso] Windows XP, 2003, 2003 R2, Vista, 2008, 2008 R2, 7, 2012
– Apple Macintosh Mac OS X 10.5 (Leopard), 10.6 (Snow Leopard), 10.7 (Lion), 10.8 (Mountain Lion)
– Linux OS SuSE Linux Enterprise 10 and 11, Red Hat Enterprise Linux 5 and 6, Ubuntu 8.04 and higher, and OpenSuSE 11, CentOS 5 & 6
Standard Solu<on Package • 3rd Party Systems Supported
» Email/Messaging • Exchange 2003, 2007, 2010, SMTP, IMAP, POP3, Blackberry Enterprise Server
» An<Virus / An<Malware • Symantec An<Virus v10, Corporate Edi<on v10, Endpoint Protec<on v11 • McAfee VirusScan / Enterprise, Total Protec<on, Endpoint Protec<on • Sophos An<Virus • Trend Micro OfficeScan v10, Worry-‐Free Business Security v11 • AVG Technologies An<Virus v8 • Kaspersky Endpoint Security v8 • Microso] Security Essen<als, Forefront Endpoint Protec<on • Microso] Security Center Integrated 3rd Party AV/AM Products
» Backup/Recovery • Symantec Backup Exec v10 / 11 / 12 / 12.5 / 2010 / 2012 • Computer Associates BrightStor ARCServe Backup r11.1 / 11.5 / 12 / 12.5 / 15
» Database Servers • Microso] SQL Server 2005/2008/2008 R2
» Remote Access • Terminal Server, Citrix MetaFrame / Presenta<on Server / XenApp
» Network Infrastructure • Microso] Ac<ve Directory, File & Print, DHCP Server, DNS Server, FTP Server
» Web Servers • Microso] IIS 6/7, SharePoint Server 2007 / 2010
Standard Solu<on Policies • How to make changes to the Standard Solu<on Package
• From the System -‐> Import Center create a copy of the Policy System/Core Folder by Expor<ng and Impor<ng the folder – NOTE: Rename the original Core Folder before performing the import.
• Create Labels for the policies to keep track of versions. • Must abide by Policy applica<on precedence Rules
Day Four Wrap Up
Q&A Day Four Hands On Labs
• Day Five Topics – Ticke<ng – Live Connect – Computer Quick View – Site Customiza<on – Info Center / Repor<ng