Prerequisites Checklist

Before the FenixPyre onboarding process can begin admin should make sure the following criterias and requirements are met

• Network Access Settings

• Spam Filter Settings

• Whitelist FenixPyre's Client Software in your Antivirus/EDR/XDR [Needed for Windows agent deployments]

• Complete Minimum system requirements [Needed for Windows agent deployments]

Once complete please contact FenixPyre support so we can schedule a call to begin the FenixPyre onboarding.

Network Access Settings

Below is a list of DNS entries required for communication between FenixPyre client-side software and its cloud servers. Please ensure these endpoints are enabled to guarantee proper operation of the FenixPyre service on user client devices.

We are still in the process of changing our domains from datanchor.io and anchormydata.com to fenixpyre.com. We'll notify you if there any changes in the DNS entries

Server Endpoint	Protocol	Port	Description
apis.anchormydata.com	HTTPS (http over TLS 1.2/1.3)	443	FenixPyre Configuration
fenixshare.anchormydata.com	HTTPS (http over TLS 1.2/1.3)	443	FenixPyre sharing portal
mtls.apis.anchormydata.com	HTTPS (http over TLS 1.2/1.3)	443	FenixPyre mutual TLS
admin.anchormydata.com	HTTPS (http over TLS 1.2/1.3)	443	FenixPyre admin dashboard
oauth.anchormydata.com	HTTPS (http over TLS 1.2/1.3)	443	FenixPyre authentication
office.datanchor.io	HTTPS (http over TLS 1.2/1.3)	443	FenixPyre Document Editors
wopi.anchormydata.com	HTTPS (http over TLS 1.2/1.3)	443	FenixPyre Document Editors
anchormydata-com.us.auth0.com	HTTPS (http over TLS 1.2/1.3)	443	FenixPyre authentication

Spam Filter Settings (Email Settings)

To ensure FenixPyre's emails are delivered during device registration and user authentication for secure sharing, adjust spam filters to allow these messages. Access permission may be necessary.

Confirm users can receive mail from [e-mail], [e-mail], [e-mail] (sent from SendGrid by Twilio - em8537.anchormydata.com)

Whitelist FenixPyre's Client Software in your Antivirus/EDR/XDR

The FenixPyre Windows Agent installs various components such as filesystem drivers, background daemons, and local services. These components might be mistakenly flagged or blocked by your AV/EDR/XDR systems. To ensure seamless operation, consider adding FenixPyre services to the whitelist or trusted applications list in your security software.

Follow this guide to whitelist FenixPyre Client Software in your AV/EDR/XDR systems

Minimum System requirements

The FenixPyre Windows Agent is compatible only with 64-bit (X64) architecture processors. Support for ARM architecture processors is currently not available

Apart from that we also require the following requirements to be met.

• Microsoft Visual C++ Redistributable (x64) 2019 or higher is required
• TLS 1.2 and above enabled
• Install WebView2 if it is not already installed
• The AppData folder, which stores important application data, must be located on local storage rather than network storage. This is critical for performance and reliability during the operation of FenixPyre.

FenixPyre Root Certificate Authority

FenixPyre uses a Private Certificate Authority which issues client certificates for each device using the FenixPyre Windows Agent. Since this Certificate Authority isn't trusted by default, TLS communications between the FenixPyre client on Windows and FenixPyre Cloud APIs may be blocked. To prevent issues, please whitelist the Root CA certificate or add it to the Trusted Root Certification Authorities.

Contact FenixPyre support for more information.