Steps to take before the trial (POV) kick-off

The following configurations are required for a successful trial:

  1. Minimum 5 MDR Agent installs

  2. Minimum 2 Integrations (Azure/Google/EDR, etc...)

  3. Virtual Collector (If necessary)

These can be setup in the MDR console, but we recommend taking advantage of the N-ableMe MDR Resources - Deployment scripts, Azure configuration script and the Windows Syslog collector - available in the MDR.zip file.

This zip file contains an amp allowing for a quick turnaround on device installs (available for N-sight and N-central including documentation). Also included in the downloads section is guidance on deploying the MSI via Group Policy Object.

We also offer a Windows PowerShell script for your Azure Integration, making it easier to deploy to your customers. Lastly, an MSI is available simplifying the infrastructure set up.

  1. Device Install: Install the Adlumin agent on five machines, including a Domain Controller. This will trigger a synch of AD data to examine some data on the initial call.

  2. Azure Integration: N-able advises the Azure integration, which will generate numerous alerts making it easier to showcase the value of MDR during your trial experience.

  3. Virtual Collector: Download and build the virtual collector and have a static IP address ready to go – this will be configured on your POV Kick off Call . See AdluminForwarderInstaller.

  4. During your Trial Kick off session, inform the team about any integrations you wish to implement.

After logging into the console, ensure you do not use your original tenant (Partner Tenant) as your Customer Tenant.

Microsoft regularly reviews and updates permissions and settings. To keep up with these changes, we frequently update the Azure script. We recommend regularly checking your permission sets and rerunning the script to apply the latest permissions to your Entra ID app for existing SKUs, and make sure that full Purview auditing is enabled for your MDR tenants.