Skip to Content
Last modified by Tobias Wintrich on 2025/11/21 12:37
From version 5.1
edited by Tobias Wintrich
on 2025/11/21 12:33
Change comment: There is no comment for this version
To version 3.1
edited by Ulrich Mertz
on 2023/07/19 11:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -6.A.C. Assigning
1 +6.A.C. Assigning the client to the group (Manually, Import MAC, Import CSV)
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.twintrich
1 +XWiki.UlrichMertz
Content
... ... @@ -1,40 +1,21 @@
1 -As an alternative to the DNS entry **"Defaulttcms"**, Thin Clients can receive their TCMS configuration via **DHCP option 210**.
2 -To enable this, create a new DHCP option with **ID 210** on the DHCP server. Set the data type to **“String”** and use the following syntax for the value:
1 +To Assign a client to the right group, you can:
3 3  
4 -**<TCMS-Server-IP-Address>:<AdditionalApiPort>**
3 +~1. Manually:
5 5  
6 -The additional API port is optional. It can be configured in the [[basic settings >>doc:Handbuecher.TCMS11\.00.Kapitel 5 - Den TCMS einrichten.5\.E\. Bearbeiten-Menü.5\.E\.A\. Einstellungen bearbeiten.5\.E\.A\.G\. Basiseinstellungen.WebHome]] of the TCMS.
5 +Open the group where the client is locatred (TEMP group by default) and drag and drop the client to the right group in  the group tree view.
7 7  
8 -On the Thin Client, the required TCMS settings are automatically applied by the setup wizard during initial startup. Alternatively, the settings can be configured manually. To do so, enable the option
9 -{{status title="Remote-Administration"/}} → {{status title="TCMS Settings"/}} → {{status title="obtain via DHCP"/}}.
7 +2. Individually by MAC
10 10  
11 -Once the TCMS settings are configured, the Thin Client will automatically be added to the *Temp Group* during its first login to the TCMS.
12 12  
13 -{{toc/}}
10 +Note: The thin client must not be member of TCMS
14 14  
15 -= Examples =
16 16  
17 -= DHCP Server: Windows =
13 +[[image:grafik.png]]
18 18  
19 -Create a new **predefined option**:
20 20  
21 -[[image:image-20230112110546-1.png||height="323" width="305"]]
22 -[[image:image-20230112110615-2.png||height="331" width="648"]]
16 +3. Groups of clients by CSV
23 23  
24 -You can then enable the new option as either a **server option** or a **scope option**:
25 25  
26 -[[image:image-20230112110629-3.png||height="372" width="520"]]
19 +Note: The thin client must not be member of TCMS
27 27  
28 -== DHCP Server: OPNsense ==
29 -
30 -In OPNsense, navigate to
31 -{{status title="Services"/}} → {{status title="DHCPv*"/}} → {{status title="#Network#"/}}.
32 -Under **“Additional Options”**, add a new entry via **“Advanced”** using the following values:
33 -
34 -* **Number:** 210 
35 -* **Type:** String 
36 -* **Value:** "<TCMS-Server-IP-Address>:<AdditionalApiPort>" (Port optional, include quotation marks)
37 -
38 -Save your changes with **“Save”**.
39 -
40 -[[OpnSense TCMS DHCP Tag 210>>image:OpnSense.png||alt="OpnSense TCMS DHCP Tag 210"]]
21 +[[image:grafik.png]]