1 / 88

Kaseya Essentials Bootcamp

Kaseya Essentials Bootcamp. DAY ONE AFTERNOON. Developed by Kaseya University. Powered by IT Scholars. Kaseya Version 6.2 Last updated on Jan. 24, 2012. Roadmap!. Monday, Day One Morning Overview System Architecture Agents Monday, Day One Afternoon LAB Review

olisa
Télécharger la présentation

Kaseya Essentials Bootcamp

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 Essentials Bootcamp DAY ONE AFTERNOON Developed by Kaseya University Powered by IT Scholars Kaseya Version 6.2 Last updated on Jan. 24, 2012

  2. Roadmap! • Monday, Day One Morning • Overview • System Architecture • Agents • Monday, Day One Afternoon • LAB Review • Agent Template and Policy Management Concepts • Audit • Patch Management • Tuesday, Day Two Morning • LAB Review • Monitor • Ticketing • Tuesday, Day Two Afternoon • LAB Review • Agent Procedures • Remote Control • Live Connect • Friday, Day Three Morning • LAB Review • Agent Template vs. Policy Management • System • Info Center • Monday, Day One Morning • Overview • System Architecture • Agents • Monday, Day One Afternoon • LAB Review • Agent Template and Policy Management Concepts • Audit • Patch Management • Tuesday, Day Two Morning • LAB Review • Monitor • Ticketing

  3. LAB REVIEW

  4. Org & Machine GroupsScreenshot taken after Part1

  5. Agent Deployment PackagesScreenshot taken after Part3

  6. AD UsersScreenshot taken after Part3

  7. AD MachinesScreenshot taken after Part3

  8. LAN WatchScreenshot taken after Part3

  9. Agent StatusScreenshot taken after Part3

  10. Agent Icon in System TrayScreenshots taken after Part3

  11. Views: Windows 2003 ServerScreenshot taken after Part4

  12. Views: XPScreenshot taken after Part4

  13. Agent MenuScreenshot taken after Part5

  14. Application BlockerScreenshot taken after Part6

  15. Agent Log ReportScreenshot taken after Part7

  16. AUDIT

  17. Three Types of Audits • Baseline Audit • The Baseline Audit captures the configuration of the system in a known working state. • System Audit • The System Info captures the system’s information that will rarely change (i.e., processor, disk drive, memory, etc.). • Latest Audit • Latest Audit captures the most up-to-date configuration of the system and you will configure it to audit changes made to the machine on a daily basis.

  18. AUDIT • Baseline Audit and System Info should be executed only once. • Baseline Audit, System Info, and Latest Audit are done by default when an AGENT is installed on a machine. • Future Topic - Use Policy Management Module to schedule the LATEST AUDIT for a specific Organization or Machine Group.

  19. AUDIT • Assumption • The auditing has been completed and scheduled • Tasks • View the audit information of the computers

  20. View Audit • View all the tabs under the two groups, View Group Data and View Individual Data. Note what type of information can be obtained through audit and what it can be used for future applications.

  21. Audit Summary • View Audit Information. • Audit Summary • Provides a view of the data returned by audits of machines. • Configure Column Sets • Create NEW Column Sets

  22. Revisit Machine Views • Views (Machine Views) • Review Imported Views from the IT Service Delivery Kit. • Review specific Machine Views

  23. Review Inventory Information • Perform an Inventory Data Walkthrough • Machine Summary • System Information • Installed Applications • All Executable Files • Add/Remove programs • Note the Uninstall String for each Application • Software Licenses • Documents

  24. Agent Template vs. Policy Management

  25. Benefits of Agent Templates • Consistency of Service delivery • Standard Practice • Kaseya Agent Basic Configurations is pushed during initial Kaseya Agent Installation

  26. Benefits of Policy Management • Consistency of Service delivery • Standard Practice • Ensure distributed systems are in Compliance with IT policies • Simplify the application and management of policies based on Organizations or Machine Groups.

  27. Agent Template vs.Policy management • Agent Template will push agent configuration settings during initial Kaseya Agent Installation • Policy Management will ensure that Agents will follow certain Agent Policies. • Allow for simplified policy enforcement across distributed organizations. • STAY TUNED…..

  28. Agent Templates Settings • Agent settings are copied during installation of Kaseya Agent • Agent Deployment Package can reference an Agent Template

  29. Agent Settings • Menu options • Credentials • Working Directory • Check-in Control • Other options • Audit Scan / Patch Scan • Event Log Settings • Agent – Alerts • Monitor Sets • Agent Procedures

  30. LAB • Assumptions • In the next few months a large number of computers will be added to your environment • You figured that there are only three type of machines in your environment • Tasks • Develop three customized agent templates that incorporate the required agent settings for machines with similar roles • Instructional lab computers • Guest computers • Servers

  31. A Group for Agent Templates • Create a machine group for templates, called “Templates”. • Open the System module. Go to Orgs / Groups / Depts > Manage. • Verify if the Organization “FIU-<USERNAME>” is checked. • Click on Machine Group on the right hand side of the module. • Click on New.

  32. A Group for Agent Templates • Create a group by typing its name “Templates” under Machine Group Name. Click Save.

  33. Creating Agent Templates • Create three agent templates: “Server”, “Instructional”, and “Guest” • Open the Agent module. Go to Install Agents > Create. • Type in “Server” in the textbox under New Machine ID. • Select “Templates” under the Group ID textbox. • Click on Create. • Repeat steps 6-9 for the “InstructionalTemplate” and “GuestTemplate”.

  34. Note • An agent template will have an orange square icon   to emphasize the fact that the agent template will never be installed on a computer. • Its sole purpose is to provide additional customized settings for agents with similar roles so that such setting can be added to the settings of already deployed agents or be used as part of an agent package.

  35. LAB Assist • Review Steps • Watch the Video demonstration • Watch the Interactive demo • Practice on your Virtual Lab

  36. PATCH MANAGEMENT

  37. Patch Management • Patch Scan • Patch Policy • File Source • Reboot Action • Patch Update

  38. Background Story • At this time, operating system patches are applied on an individual basis. • An organized and closely monitored method is needed to facilitate and monitor distribution and application of all necessary patches to the managed computers. • Kaseya's Patch Management module allows you to accomplish all these tasks and monitor patch activities.

  39. Exercises • Implement policies that will keep the computers updated and avoid potential security risks by having non-patched computers within the environment. • Set up Kaseya to scan all the computers to allow the VSA to keep a detailed record as to which patches have been installed. • Configure Kaseya to download the patches from one central server to save bandwidth and decrease redundant network traffic.

  40. LAB • Tasks • To keep an accurate record of all the patches installed on each computer, it would be best to schedule a scan, through Kaseya's VSA, to all the computers. • While this is not a heavy process, it would still be best to schedule the scan during a time when the computer is otherwise idle.

  41. Patch Scan • Using Scan Machine, schedule a scan to run every day at 3:00am on all the agent templates. • Open the Patch Management module. Go to Manage Machines > Scan Machine.

  42. Patch Scan • Go to Manage Machines > Scan Machine.

  43. Patch Scan • Select all the agent templates. • Click on the Schedule button.

  44. Patch Scan • Set the scan to run Daily at 3:00am with a Distribution window of 1 hour. • Click on Submit.

  45. LAB Assist • Review Steps • Watch the Video demonstration (Step 1) • Watch the Interactive demo (Step 2) • Practice on your Virtual Lab (Step 3)

  46. LAB • Background information • Policies are like templates in which you can approve/deny a group of patches, or an individual patch. • Tasks • Create two policies • One for all the XP machines • One for the Windows 2003 Server machines • The policies should automatically apply • All Security Updates approved on all machines • All optional updates pending approval.

  47. Note • We create W2K3 and XP templates. • If there were Windows 2008 servers or other servers in the environment, it would be better to name the policy for all the Windows servers as just "Servers” • By the same token, if the were other workstations in the environment, it would be better to name the policy for all the workstations as just "Workstations".

  48. Creating Patch Policy for W2K3 • Create a patch policy, W2K3-PM-Policy-<USERNAME> • Set it to apply all future Security Updates by default. • Everything else should be set to Pending Approval. • Use a filter to deny patches that are optional and have not been superseded by other updates.

  49. Creating Patch Policy for W2K3 • Go to Patch Management > Patch Policy > Create/Delete. • Type “W2K3-PM-Policy-<USERNAME>” for the policy name. • Click on Create.

More Related