- This topic has 4 replies, 4 voices, and was last updated 7 years ago by marcindotkot.
-
AuthorPosts
-
May 27, 2011 at 9:35 pm #6664
I need some help in using system variables as I can’t find documentation on the correct syntax usage. What I’m trying to do is set thin client (C10LE) “Time/Date” based on the thin client IP Address. I see there’s a “$IP” system variable but I’m unsure how to accomplish this with my wnos.ini file.
Example….
IP 192.168.1.X = Central Time
IP 192.168.2.X = Eastern TimeMy Current wnos.ini
;*************************************************************
;* *
;* This wnos.ini file was generated with the *
;* Configuration File Generator 6.0.011 *
;* Copyright by Thomas Moellerbernd *
;* *
;* https://technicalhelp.de *
;* *
;*************************************************************;*************************************************************
;* General 1 *
;*************************************************************autoload=2
AdminMode=yes Admin-Username=XXX Admin-Password=XXX
Privilege=None;*************************************************************
;* Input Devices *
;*************************************************************Language=Us
;*************************************************************
;* Display *
;*************************************************************; If you are using a version of WTOS code < 7.0.1_13 please use:
; Resolution=DDC Refresh=
Screen=1 Resolution=DDC;*************************************************************
;* Network *
;*************************************************************SignOn=No
;*************************************************************
;* RDP *
;*************************************************************SessionConfig=RDP EnableNLA=no
;
;- RDP Session 1 –
;- Each line but the last must end with a ” –
;
CONNECT=RDP
Host=RDSDEV
Description=”RDSDEV”
Icon=default
Colors=true
Fullscreen=yes
Resolution=default
Domainname=DOMAINDEV
LocalCopy=noJune 3, 2011 at 1:37 pm #20577Nothing? 😳
June 3, 2011 at 1:54 pm #20578Test with Include=$IP.ini and create a file names 192.168.1.1.ini in a subfolder called inc
But you would need one ip.ini for each client. No range supported. I am not even sure if IP is supported but worth a try.
You can also read my “INI file handling” document on this site for more info.CG
July 19, 2016 at 7:40 pm #43061I think I have a network issue after all. I can tracert from my terminal all over my network, but not within my own building.
March 21, 2017 at 4:36 pm #44067Instead of:
include=$IP.ini
you can use:
include=$subnet.ini
that will allow you to create the .ini files for whole subnets. The format would be networkaddress_networkmaskinbits, for example network 10.20.30.0/24 would be associated with 10.20.30.0_24.ini file.MK
-
AuthorPosts
- You must be logged in to reply to this topic.