Management Server Console Requirements and Step-by-Step Installation

This article will outline step-by-step the ThinScale Server and Console installation plus the requirements. #MC-KB2

Written by Diego

Last published at: February 9th, 2024

Estimated reading time: 11 minutes, 34 seconds. 


THINSCALE MANAGEMENT SERVER

The ThinScale Management Server allows you to manage your devices centrally. It provides profile/device management, device grouping, and centralized software updates.

The Management Server is web-based, accessed via HTTP or HTTPS, allowing you to secure all communications with industry-standard SSL encryption, ideal for publishing over your internal network or externally facing over the internet.



Delete

Info

A load balancer with cookie injection load balancing and multiple primary servers can also be used.



REQUIREMENTS:

Delete

**********ARM-based processors are not supported 


The Management Server requires the following:



Server Manager - Add Roles and Features:

  • BitLocker Driver Encryption
  • BitLocker Network Unlock
  • NET Framework 4.7 Features
    • .NET Framework 4.7
      • ASP.NET 4.7
      • WCF Services
        • HTTPActivation
    • Internet Information Services
      • World Wide Web Services
        • Application Development Features
          • .NET Extensibility 4.7
          • ASP.NET 4.7
          • ISAPI Filters
          • WebSocket Protocol
        • Common HTTP Features
          • Default Document
        • Security
          • Request Filtering
    • Windows Process Activation Service
      • Configuration APIs
      •  Process Model


Delete

If not present, the .NET Core 6.0 Runtime will prompt to be installed during setup.



Delete

Attention

The login used in the SQL Database must be the db.owner during installation/upgrade. After installation, it only needs read and write and doesn't require execute permissions. SQL Express is also supported but consider the 10GB space limitation. Check with Microsoft for more details.


Firewall ports needed for communication: 

Port: 80 TCP / 443 TCP

Source: ThinKiosk devices

Destination: ThinScale Management Server

Description: ThinKiosk device communication with ThinScale Management Server

 

Port: 3389 TCP and UDP

Source: Devices running the ThinScale Management Console

Destination: ThinKiosk devices

Description: Remote Control of ThinKiosk devices from the ThinScale Management Console

 

Port: 49152-65535 TCP and UDP

Source: Devices running the ThinScale Management Console

Destination: ThinKiosk devices

Description: Remote Control of ThinKiosk devices from the ThinScale Management Console



Delete

Warning

Please note that the server must be publicly faced when connecting SRW (BYOD) machines unless a VPN is utilized.



1. INSTALLATION:

Delete

A user with administrator privileges must perform the installation.



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



1.2. Click ‘Next’

1.3. Accept the License Agreement and click ‘Next.’



1.4. Select the installation folder and click ‘Next.’




1.5. Click ‘Install.’ The installation will install any required Windows Components and configure Internet Information Services.


1.6. Click ‘Finish.’


After installation, the ‘ThinScale Management Server Setup Wizard’ (if selected) will launch to complete the configuration of the Management Server. This setup wizard can also be launched from the Start Menu.



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 must communicate directly with all other Primary servers in the deployment.
  • The first server added to the deployment must be a primary server.


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, reducing the data sent between offices when deploying software packages to clients.
  • Hub to Primary server communication is all via HTTP/S.




2. MANAGEMENT SERVER SETUP WIZARD


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


Delete

Warning

If you are using SQL Server, you will need a new, empty database on your SQL Server before you create a new deployment.

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.



2.1. Launch the setup wizard.


Delete

Note: to add another server, choose the option Add this server to an existing deployment—step 3 of this article.


2.2. Select ‘New deployment’ and click ‘Next.’


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

 

Delete

Info

"Local Database" must only be used during the evaluation/testing of the software and not in a production environment. Please perform a daily/weekly server backup if a Local database is used. 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.



Delete

Warning

If the main Broker.db is corrupted, copy the file from the Temp folder and rename it as a Broker.db within the TSTMgmt folder. Some data will be lost due to corruption, which might occur before the scheduled backup.



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


Delete

Warning

An empty SQL database must be created beforehand.




2.4. Select "SQL Server Authentication" to authenticate your database using a local SQL server account. Additionally :


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

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

2.5. Click ‘Test Connection’

Delete

A' SQL Server connection verified' message will appear if the setup wizard can successfully connect to your database. If the connection is unsuccessful, a message detailing the reason for failure will be shown. When successfully verified, click ‘Next.’


2.6. Enter the URI that other Primary servers in this deployment will use to communicate with this server. Click ‘Next’



Delete

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.


2.7. Enter the password you want to use to access the Management Console using the auto-generated Administrator account. This can be modified later, if needed, inside of the Management Console. Click ‘Next’



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




2.9. Select the required logging level and click ‘Apply.’





Delete


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 been completed, you will be prompted to restart IIS for the changes to take effect. The default login credentials will be displayed when the deployment database is configured.





Delete

Note

It's mandatory to restart the IIS.



3. NEW PRIMARY OR HUB SERVER


Before you add a new Primary server to an existing deployment, you will need the following:

  • SQL Server connection details
  • The URI of an existing server in the deployment to authenticate this new server
  • Login credentials to the existing deployment that has permission to add management servers


3.1. Launch the setup wizard.


3.2. Select ‘Add this server to an existing deployment’ and Click ‘Next’


3.3. Select "Primary" or "Hub" and click ‘Next.’





"SQL Server Authentication" to authenticate your database using a local SQL server account.

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

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

3.4. Click ‘Test Connection’

Delete

A' SQL Server connection verified' message will appear if the setup wizard can successfully connect to your database. If the connection is unsuccessful, a message detailing the reason for failure will be shown. When successfully verified, click ‘Next.’


3.5. Enter the URI that other Primary servers in this deployment will use to communicate with this server. Click ‘Next’




Delete

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.


3.6. Enter the password you want to use to access the Management Console using the auto-generated Administrator account. This can be modified later, if needed, inside of the Management Console. Click ‘Next’


3.7. To join a deployment, you must authenticate with a Management Server that is part of the deployment you are joining. Enter the URI of an existing server and a user's credentials within the deployment with permission to add Management Servers. Click ‘Verify Management Server.’



If the setup wizard can successfully connect to the existing Management Server, a ‘Management Server verified’ message will appear. If the connection is unsuccessful, a message detailing the reason for failure will be shown.

Delete

Info

Verifying the Management Server does not validate if the credentials have permission to add Management Servers, just that they are correct. When successfully verified, click ‘Next.’


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




3.9. Select the required logging level and click ‘Apply.’




Delete


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 been completed, you will be prompted to restart IIS for the changes to take effect. The default login credentials will be displayed when the deployment database is configured.





Delete

Note:

It's mandatory to restart the IIS.



4. CONFIGURATION CHANGES

After the configuration wizard has been run, you can use the same configuration wizard to alter the active Management Server configuration. Launch the ‘ThinScale Management Configuration’ from the Management Server start menu.


The following Management Server settings can be modified:

  • Management Server Type
  • Primary URI
  • Database Type
  • SQL Connection Details
  • Hub Servers Settings
  • Software Package Repository Location
  • Temp File Location
  • Logging Level
  • Custom Properties

Delete

Warning

All changes will require a restart of IIS to take effect.


If you need to reconfigure this server completely, you can run the following command to start the Setup Wizard:

Delete

C:\Program Files (x86) \ThinScale Management Server\ThinScale.Management.MgmtServer.Setup.exe /reconfigure


5. INTERNET INFORMATION SERVICES CONFIGURATION
 
The ThinScale Management Server is configured as an application / virtual directory within the ‘Default Web Site.’ It can be accessed at http(s)://servername/TSTMgmt

6. CONFIGURING SSL

As the ThinScale Management Server is installed within the ‘Default Web Site,’ it also inherits the ‘Default Web Site’ bindings. Using the Internet Information Services Snap-in, you can add an HTTPS binding to the ‘Default Web Site’ and select the required SSL certificate.

7. LOGGING

The ThinScale Management Server will log any changes/actions to a log file in the Temp File location configured during the Management Server Setup Wizard. The log file’s name is ManagementServerLog.log, primarily used by ThinScale support.

If the ThinScale Management Server is restarted, it will back up to this log file to ThinScaleManagementLog.log_old.

8. LICENSING

The ThinScale Management Server can only be used with Enterprise Licensing. The community edition(s) cannot be used.

Contact sales@thinscaletechnology.com for a quote on licensing or an extension of your trial license.



9. UNINSTALLING THE THINSCALE MANAGEMENT SERVER AND CONSOLE

Delete

A user with administrator privileges must perform the installation.


The ThinScale Management Server is an MSI-based installation and will appear in Program and Features within the Windows Control Panel.

To uninstall:

• Open Control Panel
• Select Programs -> Program and Features
• Right-click ThinScale Management Server or ThinScale Management Console and select ‘Uninstall’
• Follow the uninstall instructions

A reboot may be required once the uninstall has been completed.




10. INSTALLING THE MANAGEMENT CONSOLE


Delete

A user with administrator privileges must perform the installation.



The default installation directories are listed below:

  • 64-bit machine: C:\Program Files (x86) \ThinScale Management Console
  • 32-bit machine: C:\Program Files\ThinScale Management Console

A silent installation is supported using the command:  “msiexec /I ThinScaleManagementConsole-8.0.x.msi /QB /norestart”



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


1.2. Click ‘Next’

1.3. Accept the License Agreement and click ‘Next.’


1.4. Select the installation folder and click ‘Next.’



1.5. Click ‘Install.’ 


1.6. Click ‘Finish.’