Liongard Roar

Roar Users Guide & Documentation

Welcome! You'll find comprehensive guides and documentation to help MSPs start working with Liongard's Roar as quickly as possible, as well as support if you get stuck. Let's go #MakeITRoar!

Get Started    

Getting Started with a Roar

These are our best practices for a successful start with Roar. They may be slightly different for you depending on your PSA and particular technology stack, but this should still be a good outline for success.

Unit 1: PSA Integration

The goal of this unit is to get Roar connected to your ConnectWise Manage PSA in order to import companies into Roar and set the stage for further PSA integration features.

If you don't use ConnectWise, there are a couple of other options to get started:

  • If you use IT Glue, you can setup that integration to import ITG Organizations to Roar Environments.
  • Or, you can get started by importing Environments and Internet Domains via CSV. Talk to your friendly onboarding team for this option!

Unit 2: Cloud Inspectors

Throughout your experience with Roar, you'll get to take advantage of a feature called auto-discovery. In short: our inspectors can discover other potential inspectors, which saves you a lot of manual setup work.

These inspectors run from the Managed Cloud Agents provided with your Roar instance.

1

Run the ConnectWise inspector, which will auto-discover Internet Domains from your ConnectWise instance

5 minutes

3

After the Internet Domain inspectors run, setup TLS / SSL inspectors from auto-discovered launchpoints the same way

5 minutes

4

Setup the Cisco Meraki "parent inspector", which will auto-discover a "child" Cisco Meraki inspector for each of your customer environments

10 minutes

5

Setup the Webroot parent inspector, which will auto-discover child inspectors the same way

15 minutes

Unit 3: On-Prem Agents & Inspectors

While many of our inspectors don't require privileged network access, some of them do. For those, we will need to install on-premise Roar Agents.

The most typical deployment strategy is to install one Roar Windows Agent per Environment with Inspectors that require local network access. A single Roar Agent can facilitate inspections across that whole network.

1

10 minutes per Environment, or scripted via RMM

2

Deploy Active Directory inspectors

2(a)

If you installed the Agent on a Domain Controller, activate the auto-discovered AD Inspector

1 minute

2(b)

3 minutes

3

Setup firewall inspectors:

Unit 4: Documentation & Ticketing Integration

With a full suite of inspectors setup, it's time to get that data flowing to other places where it might be useful. You can complete these steps earlier in the process (during Units 2 & 3) if you prefer.

2

Enable pushing of Roar data into ConnectWise Configurations

10 minutes

Getting Support

You can access support from the links right at the top-right of Roar.

But here are some quick links:

Training Your Team

As we integrate your systems, review our relevant Business Use Cases and Training to help train your team on how to use Roar in context.