Tagged: Include=TN$, Migration, T00X
- This topic has 5 replies, 2 voices, and was last updated 7 years, 9 months ago by ConfGen.
-
AuthorPosts
-
June 9, 2016 at 2:27 am #42933
This is my first post here guys. Positivity would be appreciated.
I need help getting a migration to work. I read the below article and followed it:
https://technicalhelp.de/forums/topic/defining-a-firmware-versionupdate-through-wnos-ini/Hardware- Dell T00X
I have followed the steps in the article above, but the client that I have designated is not getting the firmware load or the .ini settings (in the Migration folder), however, it’s no longer using the default settings designated in DHCP scope options 161 162 either, which is fine. I just am trying to get one client to work using the Migration folder at this time.Does the Include=TN$ work for all thinOS versions? We are currently on version HF 2.0_105 (I think this was shipped with the device when we purchased it).I have downloaded the V2.1_B027 version. Do I have to upgrade to this firmware to get the functionality of using the include=TN$ command?
June 10, 2016 at 11:18 am #42944Can you please post your wnos.ini and your tn.ini?
Include parameter is supported since the early beginning of ThinOS. So no firmware version dependency here.CG
June 15, 2016 at 8:09 pm #42958;*************************************************************************
;* Added Exception for Migration testing
;*
;*************************************************************************
Include=TN$;; Disables domain list dropdown so that users cannot select the wrong domain.
DisableDomain=YESWDMService=yes \
dhcpinform=yes;; Remember last username
SignOn=yes LastUsername=yes;; Wyse ThinOS .ini settings will only replace local engine if an upgrade if available
autoload=102;; Branded desktop for local xenith
Desktop=wallpaper1.7_122.jpg Layout=Stretch;; Lockdown ThisOS clients so that the end user cannot tamper with the settings
;privilege=high \
;lockdown=yes;; Specify timezone on client (in case of timezone passthrough)
TimeZone=”GMT – 08:00″ \
ManualOverride=yes \
Daylight=Yes \
Start=030207 End=110101 \
TimeZoneName=”Pacific Standard Time (US & Canada)” \
DalightName=”Pacific Daylight Savings Time (US & Canada)”;; Printer Setup – Specific to Wyse V10LE / Z10D (THin OS) Clients – Adds printer for LPT2 functionality.
printer=lpt1 \
name=Zebra1 \
class=txt \printer=lpt2 \
name=Zebra2 \
class=TXT \;; Set the Xenith toolbar delay
SysMode=vdi toolbardisablemouse=yes;;Audio Settings
Device=audio \
Volume=middle \
Mute=0;;MirrorFileServer settings when TFTP is unavailable (Will use last known settings)
MirrorFileServer=yes;; PNLiteServerAddress
pnliteserver=http://XX.XX.XX.XX\;;Restart Client after last person signs out
Autosignoff=yes \
reboot=yes \
ShutdownCounter=5;; SSO Password reset Server Settings
PasswordServer=https://XX.XX.XX.XX AccountSelfService=yesAddCertificate=digiCertAssuredIDRootCA.cer
AddCertificate=DigiCertGlobalRootCA.cer
AddCertificate=DigiCertHighAssuranceEVRootCA.cer
AddCertificate=IntermediateSHA2.cer;; Map USB Disk
Sessionconfig=allmapusb=yes
sessionconfig=ica mapdisksunderz=yesNotes:
-I have created the INC folder
-In the Inc Folder I have used two methods to name the TN File (TN with no extension and TN.ini) – Not sure which is proper method to use here?
-In the Migration folder I have placed the firmware and .ini (without the Include=TN$ in it)
-Can I also include a bitmap folder in the Migration folder also, or will it look for the bitmap in the original locationThank you for any help you can provide.
June 16, 2016 at 5:46 pm #42964OK, here is the deal.
First of all, please use my Configuration Generator to generate your INI files. You have several bugs in your current file.Second, the file structure should look like this
\wnos\wnos.ini
\wnos\your_firmware_file like T10D_wnos or T00D_xen
\wnos\inc\tn.ini
\wnos\bitmap\something.jpgIf you use Include=$TN.ini in your wnos.ini, then you have to name the machine specific file with the ending .ini. If you use Include=$TN, then you can forget about the ending. You can even use Include=$TN.txt and name the file with ending .txt. All will work.
Does the above reflect your environment?
CG
June 16, 2016 at 8:19 pm #42965Our file structure is correct per your example:
\wnos\wnos.ini
\wnos\your_firmware_file like T10D_wnos or T00D_xen
\wnos\inc\tn.ini
\wnos\bitmap\something.jpgOur tn.ini points to a migration path that is outside out WNOS, could that be the problem? Does it have to be in the exact path RootPath=wyse/wnos/migration? can it be somewhere else? Can a UNC path be used instead? (I think this is my main problem here)
Are there different migration options other than using include=$TN? Could I somehow change TFTP server in the wnos/Xen.ini that point to only the clients that I specify (INC folder) without changing 161/162 scope options in DHCP? My biggest problem is that I want to use different firmware on select clients during testing.
I will heed your advice and reconstruct my WNOS.ini from Config Gen and will get back to you. Thank you very much again.
June 17, 2016 at 1:36 pm #42966First, I hope the name of your tn.ini is not “tn.ini”, but the correct name of the client plus .ini.
What are you using currently in the tn.ini as Rootpath value and how does your folder structure look like where the migration folder is?
The server has to be a webserver with ftp, http or https.CG
-
AuthorPosts
- You must be logged in to reply to this topic.