Remedio SaaS on-boarding
Introduction
The purpose of this document is to provide step by step guidance for onboarding to the Remedio SaaS platform. It applies both to new customers beginning their deployment and to existing customers who are transitioning from an on premises setup to the SaaS environment.
Preliminary steps and ongoing onboarding
User Access: Provide a list of email addresses that should receive access to the Remedio UI.
SaaS Tenant Creation: Once your SaaS tenant is created, Remedio will supply a username and an initial password. You will be prompted to change the password at first login.
Identity Provider (IDP) Integration: Remedio supports integration with your existing identity provider, including OKTA, Azure AD, and others.
Access Levels: Define the access levels each user requires, for example Full Admin, Read access for Windows servers, or Write access for Linux Debian environments.
Operating System Support: Confirm that the operating systems you plan to deploy sensors on are supported. Refer to the supported OS list provided with the documentation.
Firewall Whitelisting: Remedio will provide a list of firewall rules to whitelist, limited to port 443 access to the required SaaS URLs.
Sensor Downloads: All sensor packages can be downloaded directly from the Remedio UI.
Active Directory and GPO Data and GPO Validation: If you would like to view Active Directory data or enable GPO Validation, set up a server according to the AD GPO Assessor and Domain Agent guide. A shared server may be used for this purpose.
Networking misconfiguration information: If you plan to monitor configurations on network switches and routers, prepare a network collector server following the requirements outlined in the network collector documentation.
All information listed above will be included in a welcome email that you will receive once your tenant is ready.
New Customers (PoV or Production)
Deployment and Device Scanning Process
AD GPO Assessor and Domain Agent Server Setup: If required, prepare the AD GPO Assessor and Domain Agent server according to the provided specifications.
Firewall Rules and Server Readiness: Make sure all necessary firewall rules are in place.
Confirm that the AD GPO Assessor and Domain Agent server is ready for use.
Remedio Sensor Deployment: Deploy the Remedio Sensor to a group of devices within your licensing limitations.
You may use any deployment tool, such as SCCM, BigFix, or GPO, to distribute the sensor.
Network Collector for Switches and Routers: Install and configure the network collector server.
Create the required credentials on the network devices.
Scanning and Data Submission: Once the sensor is deployed, each device performs its initial scan.
The collected data is then sent to the Remedio cloud environment.
Metrics Display in the UI: All collected metrics can be viewed and analyzed directly in the Remedio UI.
Full Functionality and Remediation: The platform is fully functional and includes remediation, auto-remediation and revert capabilities.
Exercise Caution with Remediations: Choose your target devices carefully when initiating remediations. It is recommended to test remediations on a small number of devices before applying them to a larger group.
SaaS Proof of Value (PoV) Details
PoV License Scope
The PoV license includes the following:
A limit of fifty devices
A duration of twenty one days
Full product functionality, including all modules for detection, remediation, and revert
Meeting Schedule During the PoV
Onboarding Session
Review of the initial findings
Walkthrough of the UI
Status Calls (usually 2-3 meetings)
Deeper technical review
Discussion of advanced use cases and platform behavior
PoV Summary Call
Review of all findings collected during the PoV
Presentation of results to stakeholders and decision makers
Discussion of next steps
These meetings ensure a complete and effective evaluation of Remedio throughout the PoV period.
Existing On Prem Customers Migrating to SaaS
New Sensor Deployment
Remedio will provide an updated sensor version.
The new sensor replaces the existing installation, recreates the configuration files, and redirects all data to the Remedio SaaS platform.
Deployment Methods
You may deploy the updated sensor using any standard tool such as SCCM, BigFix, Intune or GPO.
You can also rely on Remedio’s auto update mechanism to distribute the new sensor.
Data Submission to Remedio SaaS
After the new sensor is deployed, all scanned device data is sent directly to Remedio SaaS rather than the on-prem server.
Metrics in the UI
All metrics can be viewed and analyzed in the Remedio SaaS UI.
Dual Visibility During the Transition
Devices that receive the updated sensor will report to the new SaaS environment.
They will continue to appear in the previous on premises server for up to fourteen days if Remedio’s auto update was used.
Important Note on Migration
Data migration is not supported.
Remediation tasks, mutes, roles, and permissions must be recreated in the new SaaS UI.
This process ensures a smooth transition to Remedio SaaS while maintaining visibility of devices throughout the migration period.
Sensor installation guide and supported platforms
For detailed sensor documentation, including step by step installation instructions and the full support matrix, refer to the sensor guide. This resource covers everything you need to install and configure Remedio sensors across supported operating systems and will help ensure a smooth and successful deployment.