ThinMan & Teradici
From version 8.0.4 ThinMan does not support Teradici devices.
¶ Network Browsing
It will browse the network using parameters that are set in the Group Properties and in the Network tree.
You can browse for devices using the right click menu "Browse" on:
- the Devices tree,
- a Group,
- the Network tree,
- an IP Range.
You can also browse all the devices using the File → Browse all menu.
Browse devices placed in other subnets
Sometimes the ThinMan Server is installed in a different subnet from the one of the devices. In this case, use the Network tree to define all the subnets in your network by creating IP Ranges. Then, associate each of them to a Group.
ThinMan uses TCP and UDP protocols to find devices on your network.
With UDP protocol ThinMan sends broadcast requests in the network. Once a device receives the message, it will send information and status back to ThinMan. This UDP broadcast is a very quick way to discover devices although it can be inaccurate if filtered by network devices such as switch, routers and so on. From version 7.2.0 the UDP protocol has been enhanced so it is better than in the previous ThinMan versions.
At the same time ThinMan will use TCP protocol. The TCP protocol sends a request for every IP Address defined in the IP Ranges (see Network). Due to the network timeouts, the feedback is slower but more precise than in UDP protocol. Once a device receives this message, it will send information and status back to the ThinMan. From version 7.2.0 the TCP protocol has been enhanced so it maintains its precision with more speed.
Configure a device to point the ThinMan Server In order to use all the functionalities ThinMan offers (e.g. ThinMan Profile Manager, Scheduled Activities, Event Activities) you need to setup ThinMan Server Address on each device you want to manage.
It is best practice to use network parameters, as it allows out-of-the-box devices to connect to a ThinMan Server without changing their configuration (for more information read Zero Config with Profile Manager).
Where is placed a new discovered device?
When a new device notifies to ThinMan or it is is discovered by ThinMan, it is placed in the root Devices tree unless its IP Address is contained in an IP Range associated to a Group(see Group Properties)
¶ Refreshing a Group or a Device
Refreshing a device, a group of devices or all devices is done using the same protocols used for browsing. ThinMan will query the devices to obtain their status and eventually changed information. This operation will not discover new thin clients in the network but only update status for already known devices.
Refreshing a device is important because, in some cases, the device status appearing on ThinMan might not be aligned to the real situation. Remember that only linked devices will notify to ThinMan their status changes.
Devices using WSS/WSS-Safe Protocol do not need to be refresh:
Depending on the communication protocol between a device and the ThinMan Server, the column Notified appearing on the Working Area of the ThinMan Console will take one of the possible values: HTTPS linked, WSS, WSS Safe.
Devices using WSS Protocol do not need to be refreshed since the tcp connection is permanently active as a channel between the endpoint and ThinMan. If a device appears as turn-on/turn-off/disconnected on the ThinMan Console, that is actually the device's status.
