Management Server Step-by-Step Installation

This article will outline step-by-step the ThinScale Server installation. #MC-KB2

Written by Giuseppe

Last published at: December 21st, 2020

Note: Installation must be performed by a user with administrator privileges.

Please review the requirements before attempting the installation.

Copy the installation media to a temporary folder on a local drive on the server and run the installation media (ThinScaleManagementServer-5.x.x.exe)

Click ‘Next’

Accept the License Agreement and click ‘Next’

Select the installation folder and click ‘Next’

Click ‘Install’

The installation will install any required Windows Components and configure Internet Information Services.

Click ‘Finish’

After installation, the ‘ThinScale Management Server Setup Wizard’ (if selected) will launch to complete the configuration of the Management Server.


Management Server Deployment Types

The Management Server can be configured as a Primary or Hub server.


Primary

Primary servers require a direct connection to the Local or SQL database.

Primary servers need to communicate directly with all other Primary servers in the deployment



Hub

Hub Servers do not require a connection to the Local or SQL database.

Hub Server communication is proxied via a Primary server and therefore requires access to a Primary server in the deployment.

Hub Servers are ideal for branch offices where direct access to the SQL database may not be possible.

Hub Servers also act as software deployment points which will reduce the amount of data sent between offices when deploying software packages to clients

Hub to Primary server communication is all via HTTP/S

 

Management Server Setup Wizard

After the initial installation, you need to run the ‘ThinScale Management Server Setup Wizard’ to complete the configuration of the Management Server.

The setup wizard will allow you to:

Create a new deployment

Add an additional Management Server to an existing deployment

(Note: If this is the first Management Server you are configuring you will need to create a new deployment)

When adding an additional Management Server, you will be prompted to select either a Primary or Hub server.

The three sections below will take you through the configuration wizard based on your required deployment type for this Management Server:


New deployment

New Primary server (in existing deployment)

New Hub server (in existing deployment)


New Deployment

During the configuration of a new deployment, the setup wizard will install and configure the management server deployment database.



If you are using SQL Server before you create a new deployment you will need the following:

A new, empty database on your SQL Server

A SQL or DOMAIN user account that has SELECT, INSERT, UPDATE and DELETE permissions as well as permissions to create tables in the database


If you are using a Local Database, there are no additional requirements

Launch the setup wizard

Please note: to add another server chose the option Add this server to an existing deployment 

Select ‘New deployment’ and click ‘Next’

Select ‘Local Database’ or ‘SQL Server’ and click ‘Next’


Note: a “Local Database” must only be used during evaluation/testing of the software and not in a production environment.


In the scenario that a Local database is used, please perform a daily/weekly backup of your Server.

A daily backup of the Broker.db file is automatically created every 24 hours by the Management Server component and is located in the Temp folder. 

 


In the likely event that the main Broker.db is corrupted, just copy the file from the Temp folder and rename it as a Broker.db within the TSTMgmt folder. Some data will be lost as a result of the corruption which might occur before the scheduled backup.



If you select ‘SQL Server” you will be prompted with the below database details screen.


Please Note: An empty database must be created beforehand.


SQL Server Authentication – Select this option if you want to use a local SQL server account for authentication to your database.

Additionally :


Windows Authentication – Select this option to use a domain account that has access to your SQL database.

Use IIS application pool authentication credentials – Select this option if you want to connect to the SQL database using the identity that the IIS Application Pool is running under.

Click ‘Test Connection’

If the setup wizard can successfully connect to your database a ‘SQL Server connection verified’ message will appear. If the connection is not successful a message detailing the failure reason will be shown.

When successfully verified click ‘Next’



Enter the URI that other Primary servers in this deployment will use to communicate with this server. The URI must point at this server and cannot be a load-balanced address.


(the wizard will show a default URI based on the installation and should not need to be altered unless you want to configure HTTPS communication between brokers)


Click ‘Next’


Enter the Password you want to use to login to the Management Console using the auto-generated Administrator account. This can be modified later if needed, using the Management Console.

Click ‘Next’


Enter a location for the software packages and temporary file storage and click ‘Next’


Select the required logging level and click ‘Apply’

(Warning is the recommended level, but a more verbose setting (Information) may be required by ThinScale Support)



The wizard will complete the following tasks:

Create the software package and temporary folders

Create the deployment database schema

Save the Management Server configuration file

When the setup has completed you will be prompted to restart IIS for the changes to take effect.

When the deployment database is configured the default login credentials will be displayed.