Learn how customer, First United Bank, leverages Kaseya in a highly regulated environment, including tips and tricks for leveraging Kaseya Patch Management in conjunction with other modules to help ensure compliance. Presented by: Kyle Simpson, Systems Administrator, First United Bank

2. First United Bank
• 15 Branches
• 250 employees
• 320 machines
• 150 miles one way to farthest branch
• IT staff of 3

3. Life Before Kaseya
• Constant Travel
• Relied on end users for patching
• End users had to be available for support
• No off hours support on machines
• Unable to give auditors detailed reports
• No way to ensure compliance

4. Patch Management
How we do it
• Set to weekly scan
• Updates are conducted twice a week to insure
patches are installed properly
• Workstations are restarted in between the update
installation
• All criticalhigh priority updates are installed
• All updates are tested for a week on workstations
located in the IT department
• File Servers at branches are used to distribute the
patches in order to preserve bandwidth

5. Patch Management

6. Patch Management

7. Patch Management

8. Patch Management

9. Patch Management

10. Patch Management
Best Practices
• Initial updates should be done on a well thought
out schedule.
• For low bandwidth organizations use local
servers to distribute the patches.
• Be sure to set the share permissions on the file
servers for everyone to read only on that
directory.

11. Patch Management
• Set patches to delete after install to make sure the
local drive on the workstationserver does not fill
up.
• Set reboot to occur between patch schedules.
• Use reports to check patch status and which
patches failed

12. Remote Managment
• Connect to machines
• No user disruption
• Eliminated need to coordinate schedules for
maintenance
• No longer driving between offices for diagnosis
and remediation
• Monitor Machine statistics

13. Remote Control

14. Remote Control

15. Remote Control

16. Remote Control

17. Remote Control

18. Remote Control

19. Remote Control

20. Remote Control
Best Practices
• If you know you are going to be working on the
specific workstation get connected before you are
ready it can take some time to get connected
• Check the procedure you are going to run or the file
you are going to move wont disrupt the user
• Let users know when you take control of their
machine otherwise you will be fighting each other
• Remove the option to disable remote control

21. Reports
• Auditors love reports
• Patch reports
• Audit reports for machine software
• Active Directory reports – number of login attempts
and when they are attempted
• Streamline the reports to give me them the most
relevant data

22. FDIC Audit
• Document everything
• Check your patches weekly
• Project Management
• Security is key
• Vendor access logs
• Document everything