To understand the features that the Rangee Thin Client Management Server (TCMS) offers, we want to explain the basic structure, how we designed the management software.

1. The TCMS is a stand-alone server, that offers the complete functionality and set of task of a thin client management server. The required hardware specs are very low. One dual-core CPU (or 2 vCPU) with 4 GB RAM and 20 GB HDD are sufficient for the basic installation.
    
2. You can use the TCMS, for all devices: Rangee Thin Clients with Rangee OS, Rangee Thin Clients with Windows Embedded, all PC with RangeeOS installed or WindowsPC with Kommbox installed.
    
3. You need only one TCMS in your network. All administrative taasks can be done from the webbased interface which you can access from your standard webbrowser. https://ip-address/tcms
    
4. Multiple administrators can work on the TCMS at the same time.
    
5. The TCMS offers a built-in database. Optionally you can attach an external database. For backup routines, please attach a networkdrive to the TCMS. (Kommbox -> Peripherials -> Networkdrive.)
    
6. The TCMS firmware contains the linuxbased RangeeOS and additionally the TCMS software package, which includes the database, the webserver for user frontend and backup tools to backup the local database.
    
7. Updates will be installed partially. You can upgrade the operating system or individual software packages. During the Update only the parts of the software with changes will be replaced. This reduces the update time and network traffic during the firmware update.
    
8. To perform a softwareupdate you can connect the TCMS repository to the Rangee Updateserver. The new software can be downloaded to the TCMS repository and this can be used for updateing the thin client in your network. 
    
9. Softwareupdatzes can also be made from other dedicated FTP-Server, Http-Server and all Rangee Clients with RangeeOS.
    
10. Espercially for environments with lots of clients and multiple network sites, a distributed updateserver concept can optimize the software roll-out and reduce WAN-network traffic significantly.
     
11. The remote Managment feature does not require any further installations or licenses.
     
12. All configuration items and information of installed firmware and software are stored in the TCMS-database.
     
13. For optimised overview of your endpoint environment, you can use unlimited group levels and no of groups on each level. We would recommend to create an organization starting with on the first group level with one group for each company organisation, second group level with organzational entities (e.g. Sales, Production), third level with funktional enitites (VDI, Serverbased computing, Physical Desktop)
     
14. Each group can have a configuration. All thin clients in one group get the same configuration as a member client
     
15. The initial group configuration is always prepared from one thin client configuration, so that you can make sure, that the thin client will be working, as it has been planned.
     
16. To add and configure new thin clients automatically, you should prepare a group configuration and add the MAC address to the appropriate group. Set the DNS name defaulttcms and let the thin client Thin Clients start the setup wizard.
     
17. The discover feature can only be exceuted in a group, where the network address range has been configured properly and the thin client must have the correct management server address in the configuration.
     
18. Before creating a new group configuration on the thin client, change the client role to testclient: Doubleclick on the thin client and change the role from member (default) to test. After the configuration has been changed and tested, you can pull the configuration from right mouse menu. After pulling the configuration reset the client to member client again. 
     
19. Member client will get the configuration and apply it to their system on each boot or reboot. Even if the TCMS is not available, a member client will always keep the last TCMS configuration as productive configuration, untill it can reconnect to the TCMS server or gets reset-to-factory default.
     
20. To start the thin client, the TCMS can send a "wake-on-lan" signal to the network. Make sure, that the broadcast signal can be transmitted from TCMS to client network.
     
21. In case the signal cannot be transmitted between the networks, the TCMS can distribute the task to other thin clients in the network, that are online and have connection to the device it should wake up.