1.08k likes | 1.25k Views
IT AUTOMATION. Lectures 4-5. Developed by Dr. Masoud Sadjadi. Powered by Kaseya & IT Scholars. Last updated on August 20, 2012. Kaseya Fundamentals Workshop. LAB REVIEW. Part 1. Define Organization Structure Define fiu -<USERNAME> as the organization
E N D
IT AUTOMATION Lectures 4-5 Developed by Dr. Masoud Sadjadi Powered by Kaseya & IT Scholars Last updatedon August 20, 2012
Kaseya Fundamentals Workshop LAB REVIEW
Part 1 • Define Organization Structure • Define fiu-<USERNAME> as the organization • Define SCIS, MR, GL and CEC as machine groups for this organization.
Part 2 & 3 • Create agent deployment packages • “package4mr-<USERNAME>” • “package4scis-<USERNAME>” • “package4gl-<USERNAME>” • “package4cec-<USERNAME>” • Deploy agents • dc and pc1: Manually • ws1: Using AD Users • guest1: Using AD Computers • laptop1: LAN Watch
Part 4 • Define a “view” named “Windows 2003 Server-<USERNAME>” that once selected will only show machines with Windows Server 2003 operating system on them. • Define another “view” named “XP-<USERNAME>” that will only show machines with the Windows XP operating system on them. • Make sure to check the correctness of this newly created “views” by trying them.
Part 5 • Customize Agent Menus • Remove the agent icon from the servers • On workstations, don’t allow users to exit • Provide an option inside of the agent menu to go to your company’s website
Part 6 • Use the Application Blocker to block solitaire.
Part 7 • Generate a report through the Info Center module showing the successful check-in and install of agents using Agent Logs report.
Progress Check • Are you done with all the Agent labs? • Have you checked the correctness of your work?
Questions? • Please type your questions in the chat section of your GoToMeeting window. • Remember that you can always send your questions to training@kaseya.com too. • If you are falling behind the steps in the lab, please just watch the presentation, take some notes, and perform your labs after the lecture.
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.
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.
AUDIT • Assumption • The auditing has been completed and scheduled • Tasks • View the audit information of the computers
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.
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
Revisit Machine Views • Views (Machine Views) • Review Imported Views from the IT Service Delivery Kit. • Review specific Machine Views
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
Progress Check • Do you know the different types of audit? • Do you know how they are different? • Should all different audit types run at the same interval?
Questions? • Please type your questions in the chat section of your GoToMeeting window. • Remember that you can always send your questions to training@kaseya.com too. • If you are falling behind the steps in the lab, please just watch the presentation, take some notes, and perform your labs after the lecture.
Kaseya Fundamentals Workshop Agent Template vs. Policy Management
Benefits of Agent Templates • Consistency of Service delivery • Standard Practice • Kaseya Agent Basic Configurations is pushed during initial Kaseya Agent Installation
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.
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…..
Agent Templates Settings • Agent settings are copied during installation of Kaseya Agent • Agent Deployment Package can reference an Agent Template
Agent Settings • Menu options • Credentials • Working Directory • Other options • Audit Scan / Patch Scan • Event Log Settings • Agent – Alerts • Monitor Sets • Agent Procedures
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
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.
A Group for Agent Templates • Create a group by typing its name “Templates” under Machine Group Name. Click Save.
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”.
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.
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? • Have you created the three agent templates?
Questions? • Please type your questions in the chat section of your GoToMeeting window. • Remember that you can always send your questions to training@kaseya.com too. • If you are falling behind the steps in the lab, please just watch the presentation, take some notes, and perform your labs after the lecture.
Kaseya Fundamentals Workshop PATCH MANAGEMENT
Patch Management • Patch Scan • Patch Policy • File Source • Reboot Action • Patch Update
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.
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.