Remedio PoV Journey: Requirements and Initial Steps

The Remedio PoV is designed to be simple, fast, and easy to manage. Deployment takes only a short time, data begins to appear quickly, and the overall process requires minimal effort from your team. Our structured sessions ensure that each step is clear, efficient, and focused on helping you understand the value Remedio provides from day one.

PoV Process 

Initial Meeting (45 minutes) – PoV Kickoff
We begin by deploying Remedio on a small set of devices and walking you through the setup. After the live demo, your team continues the rollout to the remaining devices in scope, up to fifty systems, ideally starting with privileged users and critical servers.

Follow-up Meetings (30 to 45 minutes each) – Mid-Evaluation Syncs
As data begins to populate, we schedule two or three review sessions. These meetings allow us to walk through the early results, clarify what Remedio is detecting, and ensure your team is comfortable with the findings. Since insights are available quickly, often within the first hour, each session focuses on interpreting the data, identifying quick wins, and guiding safe, low-impact remediation steps.

Final Meeting (45 minutes to 1 hour) – End of Evaluation Review
In the final session we review all findings and remediations completed during the PoV, answer any open questions, and ensure you have a clear view of Remedio’s value and impact.

PoV Pre-Reqs 

Remedio offers two PoV options. You can run it as a cloud based SaaS service or install it on premises. If you are unsure which option is the best fit, we recommend speaking with a Remedio representative who can guide you based on your environment and goals.

If you choose the SaaS route, the setup is simple. All requirements and steps are outlined in the https://gytpol.atlassian.net/wiki/spaces/KB/pages/42565893 document.

If you choose the on premises PoV, prepare the required virtual machines based on the specifications in the https://gytpol.atlassian.net/wiki/spaces/KB/pages/457146377 document. The setup includes a few extra steps compared to a standard appliance deployment.

Before on-prem installation, review the hardware and software requirements for both the PostgreSQL server and the Remedio Services server, confirm you have two reserved IPs with matching DNS records and FQDNs (one per server), and make sure the required firewall ports, permissions, and other prerequisites listed in the KB are in place so the Remedio components can communicate properly.

Install MSI & PoV Kickoff Meeting

After the preparation steps are completed, our team will provide the installation packages for your selected machines. For SaaS deployments, the sensor packages will be available directly in the Remedio UI. For on premises deployments, the installation packages will be sent to you by email.

The sensor can be installed in several ways, and the full instructions are available in the https://gytpol.atlassian.net/wiki/spaces/KB/pages/135954435. Make sure to follow the steps carefully to ensure a smooth setup.

We will also schedule a kickoff meeting to guide you through the installation. During this session, our team will walk you through the process, answer questions, and provide real time support to help you deploy Remedio successfully on your target devices.

GPO Validation and AD Assessment tools

As part of the POV, we will also complete GPO validation and an AD assessment to confirm your environment is configured as expected.

For GPO validation, we will compare the actual versus expected Microsoft policy settings on endpoints and servers, and run queries against the domain controllers to identify policies that are not applying correctly, are conflicting, or were removed from domain GPOs but are still present on the device.

For the AD assessment, we will review the current state of AD and GPO from a standard domain user perspective, focusing on domain user rights and the public data that is visible to any authenticated user in the domain.

The prerequisites for these modules are available here: https://gytpol.atlassian.net/wiki/spaces/KB/pages/633929729 and include the required network ports, permissions, and other setup requirements needed for the AD and GPO sensors to communicate with the domain controllers.