Explorezel Installation Guide
DISCLAIMER
Any advice FYB provide in relation to setting up any FYB App, FYB Add-in, FYB Connector and or advice in relation to opening access to your on-premises or in the cloud systems will be general advice only. This means that the advice is of a general nature and will not consider your network setup, network infrastructure or any security requirements that you may have or in fact need. It is highly advised that you seek advice from internal or external providers to ensure that they are comfortable with what is required prior to going ahead with any deployment, setup, or configuration for external access.
LICENSE DETAILS
Please contact FYB for a valid license if you are yet to obtain one for your Add-In.
INSTALLATION COMPONENTS
The following installation components are required to ensure full functionality of the FYB Explorezel:
- FYB Explorezel web application, this is a server-side installation.
AUTHENTICATION
The Explorezel application uses Azure AD authentication to validate the user’s credentials. Users will be required to enter their Microsoft 365 login details to sign into the application. The user's Office 365 login will need to be populated on their Content Manager profile so that the authenticated user can connect to Content Manager, this is done using the alternate login field.

INSTALLING FYB EXPLOREZEL
LICENSE
-
Create a folder to house the license file (.lic) on the IIS Server
-
Place the license file in this folder
NoteYou will be asked to enter this location during the installation.
TRUSTED USER ACCOUNT
Add the account that will run the application pool as a Trusted User Account in Enterprise Studio. Please refer to your Enterprise Studio help file on adding trusted accounts. If using a system account (application pool identity, network service etc) you will be required to enter the details as DOMAIN\Server Name$
If using a dedicated windows service account, you will be required to enter the details as DOMAIN\username.
INSTALLATION
Before running the MSI ensure that all prerequisites are complete. Including deploying the .NET 10 SDK and Hosting Bundle.
To deploy the Net Core SDK and Hosting Bundle to the server, follow these steps:
-
Install the latest .NET 10 SDK (x64) found here

-
Install the latest ASP.NET Core 10 Runtime Hosting Bundle found here

-
Once both executables have been installed, complete a full server restart to allow for .NET 10 to bind to IIS. If a server restart is not possible an IIS reset can be completed with the following CMDs from an elevated command prompt.
- net stop was /y
- net start w3svc
- iisreset
NoteTo check that the SDK has been attached to the hosting bundle, open Command Prompt and type dotnet --info
The FYB Explorezel MSI will:
- Deploy the installation files.
- Setup the application pool and application in IIS
- Setup the temp folder
- Configure the FYB Explorezel as specified by the user
Installation can be completed by running the MSI or using the command line arguments to prefill most data. To install the FYB Explorezel Application, follow these steps:
-
Run command prompt as an administrator and launch the explorezel-xxx.msi installer
-
Click on the Next button

-
On the Web Application Settings screen select the HTTPS protected dedicated site (see the site section in the Explorezel Prerequisites for more information) to host the application and enter Explorezel for the Virtual Directory
NoteThe virtual directory name must remain as Explorezel. It cannot be renamed.
IIS DirectoryThe application must be installed under the dedicated site as an application. It cannot be installed at the site level
-
Click on the Next button

-
On the Application Pool Settings screen, enter the domain, username, and password for the Application Pool identity
-
Click on the Next button

-
On the Configuration Settings screen enter the required information. Further details are in the table below
NotePlease refer to the AZURE APP REGISTRATION guide for more information on:
- Application ID
- Redirect URL
- Tenant ID

FIELD DESCRIPTION Dataset ID Content Manager two-character dataset identifier Workgroup Server Content Manager workgroup server name. This should generally be set to local Workgroup Server URL Content Manager workgroup server URL. License Path Local path to Explorezel license file Temp Path Local temporary directory used by the application to cache documents Client ID The Client (application) ID for the registered app on AzureAD Tenant ID The organization tenant's unique identifier on AzureAD Redirect URL The configured redirect URL on AzureAD -
On the Custom Setup screen, click on the Next button

-
Confirm the installation by clicking on the Install button

-
Once the installation is complete click on the Finish button

COMMAND-LINE ARGUMENTS
Use "" around values that contain special characters (non-alphanumeric characters)
| ARGUMENT | PURPOSE |
|---|---|
| WEB_APP_POOL_IDENTITY_DOMAIN | Sets the App Pool domain for the application pool |
| WEB_APP_POOL_IDENTITY_NAME | Sets the App Pool username for the account running the application pool |
| WEB_APP_POOL_IDENTITY_PWD | Sets the App Pool password for the account running the application pool |
| DBID | Sets the Database ID that connects to the Content Manager dataset to run the application |
| WORKGROUP_SERVER | Sets the Workgroup Server Name that connects to the Content Manager dataset to run the application |
| LICENSE_PATH | Sets the license for the application |
| TEMP_PATH | Sets the temp path that connects to the application |
| CLIENT_ID | The Client (application) ID for the registered app on AzureAD |
| TENANT | The organization tenant's unique identifier on AzureAD |
| REDIRECT_URI | The URL where Azure will send the authentication payload upon successful authentication. |
CONFIGURATION
IIS CONFIGURATION
-
After the installation process is complete, you will be able to locate the application installed within the site selected during the installation
-
From the Features View double click on Authentication and ensure that only Windows Authentication is enabled


-
Right-click the application in IIS and select explore

-
Right-click the app data folder and select properties

-
Navigate to the security tab and ensure users have read, write and modify permissions

EMBEDDING EXPLOREZEL
To allow for a site to embed Explorezel:
If Microsoft IIS CORS Module has not been installed onto the web server, this will need to be installed prior to embedding Explorezel.
The IIS Core Module can be found here
-
Navigate to the Explorezel install directory and open the web.config file as an Administrator in the text editor of your choice

-
Locate the Content-Security-Policy line highlighted below

-
After 'self', add 'data:' followed by the domain of the site that Explorezel is installed under and the domain(s) of the sites that Explorezel will be embedded in (separated by a space)

-
Save your changes and complete an App Pool stop/start
INSTALLING THE CM LAUNCHER
The FYB CM Launcher needs to be installed on each user's machine. The CM Launcher is required to perform native functions on the user’s machine such as editing documents in their native application.
Please refer to the dedicated CMLauncher Install Guide for further details.
CMLauncher is required to have a separate Azure App registration for use with Explorezel. Please refer to the CMLauncher Azure App Registration guide for further details.
