Locations Manager 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 take into account 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 application.
If migrating from v2 of Locations Manager, please contact Accounts to receive your new Locations Manager license. The previous license will not work with v3 of Locations Manager.
A full uninstall of Locations Manager v2.x needs to be completed PRIOR to installing v3.x
INSTALLING FYB LOCATIONS MANAGER
LICENSE
- Create a folder to house the license file (.lic) on the IIS Server
- Place the license file in this folder Note: You 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\ServerName$ 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 8 SDK and Hosting Bundle.
To deploy the Net Core SDK and Hosting Bundle to the server, follow these steps:
-
Install the latest .NET 8 SDK (x64) found here

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

-
Once both executables have been installed, complete a full server restart to allow for .NET 6 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 Locations Manager MSI will:
- Deploy the installation files
- Setup the application pool and application in IIS
- Setup the temp folder
- Configure the application settings as specified by the user
To install the Locations Manager, follow these steps:
-
Run command prompt as an administrator and launch the locationsmanager-3.0.x.msi and click on the Next button

-
On the Web Application Settings screen, select a Site to host the application and enter a name for the virtual directory
NoteYou can use an existing virtual directory or create a new one with the installer.
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
-
Enter your Configuration Settings as per below

NAME DESCRIPTION Dataset ID The two-digit dataset identifier of the Content Manager dataset you wish to connect to. Workgroup server Name of the Content Manager workgroup server you wish to connect to. Workgroup URL URL of the Content Manager workgroup server you wish to connect to. License Path Local path of the license file including the ".lic" filename. Temp Temp data directory for the application. -
If your environment is configured to only allow OpenID authentication (e.g. Azure AD or ADFS) for your Content Manager, you'll receive the following message:
-
Click OK to navigate to the Open Id settings screen and enter the required values.
NoteA designated CM Location is required to be nominated as the Trusted User.
No specific permissions are required to be provided.
NAME DESCRIPTION Client Id The Client/App Id of the Open Id application used to secure Content Manager. For ADFS authentication, this will be the username of the Confidential Client app. Client Secret The Client/App Id of the Open Id application used to secure Content Manager. For ADFS authentication, this will be the password of the Confidential Client app. Trusted User The Network Login value of the Content Manager Confidential Client app location. For ADFS authentication, this will be the username of the Confidential Client app. -
Open ID Settings (Optional). The values of the required fields can be found in the respective Open ID guides.

NAME DESCRIPTION Open ID Provider Choose an Open ID Provider or select none.
c
- On the Custom Setup screen select the install location and Click the Next button

-
From the Confirm Installation window click the Install button

-
The installation process will commence

-
Once the installation is complete click the Finish button

COMMAND LINE ARGUMENTS (OPTIONAL)
The follow command line arguments can be passed to the MSI if required.
| ARGUMENT | PURPOSE |
|---|---|
| DBID | Sets the Database ID that connects to Content Manager dataset to run the application |
| WORKGROUP_SERVER | Sets the Workgroup Server Name that connects to Content Manager dataset to run the application |
| WORKGROUP_SERVER_URL | Sets the Workgroup Server URL that connects to Content Manager dataset to run the application |
| LICENSE_PATH | Sets the license that connects to the application |
| TEMP_PATH | Sets the temporary path that connects to the application |
| 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. Use "" around the username if there are any special characters |
| WEB_APP_POOL_IDENTITY_PWD | Sets the App Pool password for the account running the application pool. Use "" around the username if there are any special characters |
| LIC_CONTACTS | Sets the email address of who will be contacted regarding the expiring license |
| FROM_ADDRESS | Sets the email address all emails are sent from |
| MAIL_HOST | Sets the mail host. |
| MAIL_PORT | Sets the mail port. |
| CM_CLIENT_ID | The Content Manager Client Id used to establish a connection to Content Manager using Open Id |
| CLIENT_SECRET | The Content Manager Client secret value used to establish a connection to Content Manager using Open Id |
| TRUSTED_USER | The Content Manager Confidential Client location name used to establish a connection to Content Manager using Open Id |
| CLIENT_ID | The Locations Manager Open Id Client Id |
| AUTHORITY_URL | The Locations Manager Open Id Authority URL |
| REDIRECT_URL | The Locations Manager URL |
CONFIGURATION
IIS CONFIGURATION
-
After the installation process is complete, you will be able to locate the application installed within the site selected during installation
-
From the Features View double click on Authentication button and ensure that only Windows Authentication is enabled if you are not using Open ID Authentication

ImportantIf you are using Open ID Authentication, ensure only Anonymous Authentication is enabled
-
Right click the application in IIS and select the explore option

-
Right click on the app data folder and select properties

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

-
Click on Application Pools
-
Within the application pool listing screen, right click on Locations Manager application pool and select the Advanced Settings option from the drop-down menu

-
Within the Advanced Settings window, set Start Mode to AlwaysRunning, Idle Time-out Action to Suspend and Idle Time-out Action (minutes) to 0

-
Click on the OK button
-
Select the Locations Manager application in IIS and navigate to its Advanced Settings

-
Set Preload Enabled to True and click on the OK button

ENABLING LOCATIONS MANAGER FOR A HTTPS SITE
By default, Locations Manager is set up to connect to a http site. To set up the application for HTTPS connection, please complete the following:
-
Right click the application in IIS and select explore

-
Click on the Client App > Build
-
Right Click > Edit the Index.html file

-
Update the Content Security Policy from http to https
-
Save the file.
SETUP DATABASE CONNECTION STRING
Locations Manager will require read-only access to the Content Manager database. This is due to some of the very large location searches it has to complete are much faster at the database layer.
The connection string for the database will need to be set via the Admin Console on the web interface. Navigate to Locations Manager in a browser and press the Admin button in the top right.
Navigate to the Maintenance tab and input the database connection string into the Connection String field.

The account used for the connection will require read access to the TSLOCATION and TSLOCEADDR tables. If you have specified Integrated Security=true in the connection string then the account running the Locations Manager app pool will be used for the connection. Alternatively, you can specify the credentials in the connection string.
UNINSTALLATION
To uninstall the Locations Manager manually please follow the steps below:
-
Navigate to the Control Panel
-
Click on uninstall a program
-
Right click FYB Locations Manager in the list of programs and features and select Uninstall

-
If a warning Prompt appears, click on the Continue button

-
Click the Yes button
-
The uninstallation process will commence.
-
Open IIS once the uninstallation process is completed.
-
Locate Locations Manager in IIS
-
Right click and click the Remove button

-
When the prompt appears, click the Yes button
