1. VIRTUAL SYSTEM ADMINISTRATION
Kaseya Fundamentals Workshop
VIRTUAL SYSTEM ADMINISTRATION
Developed by
Kaseya University
Powered by
IT Scholars
Kaseya Version 6.5
Last updated March, 2014

2. KASEYA SYSTEM ARCHITECTURE
Kaseya Fundamentals Workshop
KASEYA SYSTEM ARCHITECTURE

3. 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…. 3

4. Flexible Deployment of Agents in Kaseya

5. Kaseya Agent Interaction with the KServer
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
Tasks
When Task is scheduled the Agent Grabs the task and executes without needing firewall ports open

6. AN OVERVIEW OF Kaseya Virtual System Administration (VSA)
Kaseya Fundamentals Workshop
AN OVERVIEW OF Kaseya Virtual System Administration (VSA)

7. Supported Browsers for VSA
Recommended
Windows
Chrome 8 and later.
Mac OS X
Safari 4 and later.
Supported
IE8, IE9, FireFox 3.x and later, Chrome 8 and later.
Safari 4, FireFox 3.x, Chrome 8 and later.
ChromePlus is not supported.

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

9. 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.
Navigation Mode
Tree-Based
Classic

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

11. Make sure to visit the Help documents often!
Click the Help icon to display context-sensitive help for the currently selected function page.

12. There are many help documents available to you!

13. Read through Getting Started to learn more about VSA.

14. Help & Bookmarks Online Help Bookmarks
Content Sensitive Help
Bookmarks
Create a list of most visited function
All the other features will be introduced in more detail throughout the course.

15. Progress Check Do you know what browsers are supported?
Were you able to logon to the Kaseya VSA and explore the functions available to you?
Have you scan through Getting Started?

16. Kaseya Fundamentals Workshop
User Administration

17. Creating an organization
LAB 1
Creating an organization

18. Background Story
Imagine that you were just hired by Florida International University (FIU) as the lead IT Administrator to manage 500 computers.
As part of this course, we will provide a virtual lab environment representative of FIU. This lab includes:
One shared SaaS (cloud-based) Kaseya Server
5 dedicated virtual machines
One NAT router

19. 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 x KServer (a SaaS Account with System Role)
1 x Windows 2003 Server (Domain Controller)
4 x Windows XP (only 2 in the domain)
1 x Linux (playing as a NAT router)

20. Internet FIU’s Network Diagram SCIS MR GL CEC … … … …
Your Laptop/Desktop
Kaseya Server
Internet
/24
/24
NAT ROUTER
/24
/24
Instruction
Lab
Machine
Room
Guest
Desktops
PCs &
Laptops
ws1
guest1
pc1 dc … …
laptop1 …
SCIS MR GL
CEC …

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

22. FIU’s Organizational Structure

23. 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.

24. Pre-Defined Organizations
myOrg
the org 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.

25. Pre-Defined Organizations
Unnamed
the default organization to assign an agent.
Kserver (on-premise only)
the org 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 managed machines.

26. Creating an Org for FIU
You have been hired by FIU to manage their computers. You only need to create one internal organization.
WrapUp

27. Note: Avoid Name Clashing
To avoid name clashing on the shared SaaS KServer, you MUST choose unique names in your virtual lab.
There will be some instances where we ask you to add your username as a suffix to some of the labels in your environment.
To determine your username in this virtual environment, visit the “Data Sheet” tab of your virtual lab user interface.

28. 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-johndoe instead of fiu-username1 and fiu-username2), the agents in their two virtual environments may report to the wrong tenant on the SaaS KServer and may become non-responsive to your requests.

29. Steps for Creating an Organization11 4 1 3 2

30. Steps for Creating an Organization4 1 3 5 6 2 7

31. Steps for Creating an Organization8 1 3 2

32. Steps for Creating an Organization8 1 3 9 2 10 11

33. Steps for Creating an Organization1 3 2

34. On-Premise Only
The “kserver” organization is available for On-Premise (non-SaaS) servers only

35. Creating Machine groups
LAB 2
Creating Machine groups

36. 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

37. Steps for Creating Machine Groups
Under the org. name “FIU-<USERNAME>”
create machine groups to specify the physical locations of the computers.
Machine groups
SCIS MR GL
CEC

38. Steps for Creating Machine Groups4 1 6 3 5 7 2 8

39. Steps for Creating Machine Groups4 1 9 6 3 5 10 11 12
FIU-<USERNAME>
SCIS MR GL
CEC 2

40. LAB 3
Creating Departments

41. Create Departments for FIU
There are four departments as follows:
University Technology Services (UTS)
School of Computing and Information Sciences (SCIS)
Green Library (GL)
College of Computing and Engineering (CEC)
You and the the support team are in UTS.
Note that MR is managed under UTS department.

42. Steps for Creating Departments11 4 1 6 3 5 2 7 8

43. Steps for Creating Departments4 1 9 6 3 5 2 10 11

44. Steps for Creating Departments4 1 12 9 6 3 5 13 14 15
FIU-<USERNAME>
UTS
SCIS GL
CEC 2

45. LAB 4
Creating Staff

46. FIU FIU’s Staff UTS SCIS MR GL CEC Manager: John Doe Technicians:
Tim and Tom
SCIS
Contact:
Cat
ws1 user:
Eli MR
dc user:
Ena GL
Cay
guest1 user:
Eve
CEC
Con
pc1 user:
Evy
laptop1 user:
Ewa

47. Steps for Creating Staff11 5 4 1 7 3 6 6 8 9 2 10 11 12 13 14 15 16

48. Steps for Creating Staff5 4 1 7 3 6 2

49. Steps for Creating Staff5 1 17 7 3 3 18 19 20 21 22 23 24 2 25 26 27 6

50. LAB 5
Creating Scopes

51. Creating Scopes
You do not plan to give Master or System scopes to anyone
Therefore, you create the following scopes, each assigned to their corresponding machine groups:
scis-<USERNAME> assigned to scis
mr-<USERNAME> assigned to mr
gl-<USERNAME> assigned to gl
cec-<USERNAME> assigned to cec

52. Steps for Creating Scopes3 1 2 4 5

53. Steps for Creating Scopes3 7 1 8 6 2 9 10

54. Steps for Creating Scopes3 7 1 8 12 13 11 12 11 6 11 6 6 6 2

55. LAB 6
Creating user roles

56. 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

57. Steps for Creating User Roles3 1 2 4 5 6

58. Steps for Creating User Roles3 1 8 7 7 2

59. Steps for Creating User Roles3 10 1 11 9 2

60. Steps for Creating User Roles3 3 10 1 1 11 12 13 9 2 2

61. Steps for Creating User Roles3 1 12 14 13 2 15

62. Steps for Creating User Roles3 3 10 1 1 11 16 14 9 2 2 15

63. Steps for Creating User Roles3 10 1 11 18 17 16 9 2

64. Steps for Creating User Roles3 3 10 1 1 18 17 19 20 9 2 2

65. Steps for Creating User Roles3 1 21 19 20 2 22 23

66. Steps for Creating User Roles3 3 10 1 1 21 18 17 24 9 2 2 22 23

67. LAB 7
Creating VSA Users

68. 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
Username: tom-johndoe

69. Steps for Creating VSA Users3 1 2

70. Steps for Creating VSA Users3 1 4 5 6 2 7 8 9 10 11 12 13 14 15

71. Steps for Creating VSA Users3 1 16 4 5 6 2 7 8 9 10 11 12 13 14 15

72. Steps for Creating VSA Users3 1 16 17 18 19 2 20 21 22 23 24 25 26 27 28

73. Steps for Creating VSA Users3 1 16 16 17 29 18 19 2 20 21 22 23 24 25 26 27 28

74. Testing the New VSA Users
Tim
Should only be able to access Ticketing
Should only be able to see cec
Tom
Should only be able to access Patch Management
Should only be able to see gl

75. Testing the New VSA Users1 2 3

76. Testing the New VSA Users

77. Testing the New VSA Users1 2 3

78. Testing the New VSA Users

79. Progress Check
Were you able to create the org, machine groups, departments, and staff for FIU?
Did you append -<USERNAME> to your organization to avoid name clashing?
Were you able to create new scopes, user roles, and VSA users?

80. The End!