Kaseya Fundamentals Workshop

1. Kaseya Fundamentals Workshop DAY ONE Developed by Kaseya University Powered by IT Scholars Kaseya Version 6.5 Last updatedMarch, 2014

2. Day One Overview • Kaseya System Architecture • Workshop LAB environment • System Administration • Organization, User Roles, and Scopes • Visual System Administrator (VSA) • Agent Deployment • Discovery Module • Audit Module • Views

3. Kaseya Fundamentals Workshop KASEYA SYSTEM ARCHITECTURE

4. What Kaseya’s Framework Provides? Seamless and Consistent Integration Customizable Reporting 24x7x365 Automated System Management Patch Management and Updates Monitoring Remote Management Application Deployment Asset Management Ticketing, / Service Desk Data Protection Privacy – Anti-Spy Anti-Virus User State Management More….

5. Kaseya Agent Interaction with the KServer Tasks Agent Quick Check-in Default 30 Sec Like a Ping Agent Full Check-in When Task is scheduled Instructing the agent to do something Agent Alive When Task is scheduled the Agent Grabs the task and executes without needing firewall ports open

6. Kaseya Fundamentals Workshop Kaseya Virtual System Administration (VSA)

7. Supported Browsers for VSA • Supported • Windows • Internet Explorer 8 or 9 • FireFox 3.x and later • Chrome 8 and later. • Mac OS X • Safari 4, FireFox 3.x, Chrome 8, and later versions. • ChromePlus is not supported.

8. Kaseya Fundamentals Workshop LAB Environment VSA SaaS Instance and IT Scholar VLAB

9. If you have not created your account yet, create one now! Go to: http://www.kaseya.com/lps/global/lp/product-preview.aspx

10. Once your account is created successfully

11. Now, it is time to login to your preview account! Go to: https://preview.kaseya.net/

12. The new notification bar gives you hints on what to do next.

13. Kaseya Fundamentals Workshop IT Scholars LMS Web Site Overview

14. Let’s Start! • Go to www.it-scholars.com • Create a new account

15. Create a New Account • The required fields are marked by * • Username should be in the format of firstname.lastname and should NOT include: " / \ [ ] : ; | = , + * ? < > @ • Do not use your bank account password • A good password is 6 to 10 characters long • Use your work email

16. Create a New Account • Your Kaseya Customer ID is the first 6 characters of your Kaseya License Code (see System > License Manager). • If you do not have a Skype or Google Talk account, enter Do not have one! • If you do not know what is your Kaseya Sales Rep’s email, enter Unknown

17. Note • After clicking on Create my new account button, you may receive a “Session Key Error” message • This is related to the Cookie security settings in your browser. • You can add www.it-scholars.com to list of your trusted sites to address this issue. • Alternatively, you can use Chrome as its default security settings are more relaxed than other mainstream browsers.

18. Create New Account • Once successfully submitted, you will receive an email confirmation with a link to confirm your account. • After visiting the confirmation link, you can login to the portal • www.it-scholars.com • Chrome is a preferred browser

19. Enroll In Kaseya Fundamentals • Once successfully logged in, click on the Kaseya 6.5 Fundamentals Workshop – Instructor Led Kaseya 6.5 Fundamentals Workshop – Instructor Led

20. Enroll In Kaseya Fundamentals • The enrollment key is 201307 • Or the instructor would provide the key

21. This Workshop You can safely ignore this part! You can safely ignore this part! Orientation Video Announcements Quick Links Lecture Notes and Recorded Videos Show Only This Module Agent Module

22. Access You Virtual Lab • If you have not scheduled your virtual lab yet, you will see this window, allowing you to schedule your virtual lab on demand.

23. Virtual Labs PortalNetwork Diagram

24. Virtual Labs PortalData Sheet

25. Virtual Labs PortalConnection Info • Link to the KServer • RDP connection information to your five dedicated virtual machines • HostName:PortName https://preview.kaseya.net Kaseya Login Account IT-Scholars account login name and password

26. Control Buttons and Timer • You do not need these buttons for any of the exercises, but just in case you want full control over your dedicated machines, they are provided to you. • Note: Refresh provides you with a fresh copy of the virtual machine! • Using + or – you can adjust the remaining time of your virtual lab. • Use the eject button to cancel your lab.

27. Kaseya Fundamentals Workshop VSA Administration

28. VSA Layout Overview Notification Maintenance Expand/Collapse Role/Scope Selector Notification Bar Site Header Logged On User Logoff Timers Selector Panel Buttons Toolbox/Tool Bar Tab Specific Buttons Search Navigation Page Selector Module Selector Selector Panel Data Panel Navigation Mode

29. VSA Modules • All VSA functions can be accessed through modules located along the left side of the user interface. • Within each module are the core functions that allow users to perform a variety of tasks on remotely managed machines and the Kaseya Server. • Navigation Mode • Tree-Based • Classic

30. Help & Bookmarks • Online Help • Content Sensitive Help • Bookmarks • Create a list of most visited function • All the other parts and features of VSA will be introduced in more details when the time is right.

31. VSA System Administration • Organization • Machine Groups • Scopes • User Roles • Machine Roles • VSA Users

32. Organizations • In VSA, an organization is • your own organization, as a service provider • a customer, using your service • a business partner, complementing your service • Most user defined objects in the VSA belong to an organization. • Every managed machine, managed device and VSA user belongs to an organization. • They are optionally associated with scopes, tickets and service desks.

33. Pre-Defined Organizations • myOrg • The organization of the service provider using the VSA • The default name of myOrg, My Organization, should be renamed to match the service provider's company or organization name. • Agents installed to internally managed machines can be assigned to this organization. • VSA user logons are typically associated with staff records in the myOrg organization. • myOrg cannot be assigned a parent organization.

34. Pre-Defined Organizations • Unnamed • The default organization to assign an agent. • KServer (on-premise only) • The organization assigned to agents installed on your Kaseya Server. • This makes it easy to apply specialized settings to the Kaseya Server, which is typically maintained differently from other agent managed machines.

35. FIU’s Network Diagram Kaseya Server Your Laptop/Desktop Internet 192.168.0.0/24 192.168.0.1 192.168.2.1 192.168.2.0/24 192.168.3.1 192.168.1.1 NAT ROUTER 192.168.3.0/24 192.168.1.0/24 Instruction Lab Machine Room Guest Desktops PCs & Laptops ws1 pc1 guest1 dc 192.168.3.10 192.168.2.100 192.168.1.100 192.168.0.100 192.168.0.10 192.168.1.10 … … … … MR GL SCIS CEC

36. Technical Information • KServer:preview.kaseya.net • NAT Router has 4 network cards: • 192.168.0.1, 1.1, 2.1 and 3.1 • SCIS hosts workstation 1 (ws1) with one card: • ws1.scis.fiu.edu - 192.168.0.100 • MR hosts domain controller (dc) with 3 cards: • dc.mr.fiu.edu - 192.168.0.10, 1.10, and 3.10 • GL hosts guest 1 (guest1) with one card: • guest1.gl.fiu.edu - 192.168.1.100 • CEC hosts personal computer 1 (pc1) and laptop 1 (laptop1), each with one card: • pc1.cec.fiu.edu - 192.168.2.100 • laptop1.ced.fiu.edu – 192.168.2.200

37. Background Story • Imagine that you were just hired by Florida International University (FIU) as the lead IT Administrator to manage 500 computers. • Obviously, we cannot provide each one of you with 500 computers to play with! • Instead, we provide each one of you with a virtual environment that has • One shared SaaS Kaseya Server • 5 dedicated virtual machines • One NAT router

38. Background Story • The virtual machines are distributed in four buildings • School of Computing & Info. Sciences (SCIS) • Machine Room (MR) • Green Library (GL) • College of Engineering & Computing (CEC) • More information about your environment • 1 xKServer(a SaaS Account with System Role) • 1 xWindows 2003 Server (Domain Controller) • 4 xWindows XP (only 2 in the domain) • 1 xLinux (playing as a NAT router)

39. FIU’s Organizational Structure

40. Creating an Org for FIU • As you are hired by FIU to manage their computers, you only need to create one internal organization. • Organization plays a very important part on how machines are organized, viewed, and managed. • Organization configuration plays a role on assets (machines) visibility through Scopes. WrapUp

41. Note: Avoid Name Clashing • To avoid name clashing in the shared SaaS Kaseya Server, you MUST choose unique names in your virtual lab. • For this, at points we ask you to add your username as a suffix to some of the labels in your environment. • To find out what is your username in this virtual environment, you can visit the “Data Sheet” tab of your virtual lab graphical user interface.

42. Note: Avoid Name Clashing • If you do not follow the naming convention closely, you may run into many issues in future labs as a result of name clashing. • For example, if two individuals happen to choose the same organization name in their virtual labs (e.g., both use fiu-johndoeinstead of fiu-username1 and fiu-username2), the agents in their two virtual environments may report to the wrong tenant on the SaaSKServer and may become irresponsive to your requests.

43. Creating Machine Groups for FIU • You are expected to manage computers distributed over four buildings. • As each building has its own subnet, you decide to define four machines groups as follows: • scis: School of Computing and Information Sciences • mr: Machine Room • gl: Green Library • cec: College of Computing and Engineering WrapUp

44. Creating Scopes • Scopes defines visibility for individual users. Scopes can define visibility for Organization, Machine Groups, Machines, and other types of Data Objects. • You should not give Master or System scopes to just anyone. • Master Scope and System Scope provides access to all data objects: organizations, machine groups, machines, departments, and service desks.

45. Creating User Roles • You do not plan to give Master or System user role to your team members • Tim is only responsible for creating tickets originated from cec issues • Tom is only responsible for patching the gl machines • Therefore, you create the following user roles: • ticket-<USERNAME> can access Ticketing • Patch-<USERNAME> can access Patch Management

46. Example of Creating VSA Users • Technicians: • Tim is the ticketing technician for cec • User role: ticketing-johndoe • Scope: cec-johndoe • Department: fiu-johndoe.uts • Username: tim-johndoe • Password: <same as your password> • Tom is the patch manager for gl • User role: patch-johndoe • Scope: gl-johndoe • Department: fiu-johndoe.uts • Username: tom-johndoe • Password: <same as your password>

47. Kaseya Fundamentals Workshop AGENT COMMUNICATION ARCHITECTURE and REQUIREMENTS

48. Flexible Deployment of Agents in Kaseya

49. Kaseya Agent Interaction with the KServer Tasks Agent Quick Check-in Default 30 Sec Like a Ping Agent Full Check-in When Task is scheduled Instructing the agent to do something Agent Alive When Task is scheduled the Agent Grabs the task and executes without needing firewall ports open

50. Preparing the Network • Setup your Internet host name (Internal vs. External DNS) • Setup port forwarding • Kaseya Server must be able to access • http://vsaupdate.kaseya.net and • http://license.kaseya.net • http://kpls.kaseya.net • Web UI: Typically TCP port 80 or 443 inbound & outbound • Email Notifications: typically TCP port 25 outbound • Agent connections: default TCP and UDP port 5721 inbound and outbound