Forum Replies Created
-
Posts
-
Well,
Searching the “Configuration Generator” and on the “ThinOS_8.5.1_INIGuide” led me to some checks and finely adding the next settings:
SignOn=No (as was set before)
DefaultUser=guest
Password=
That did the trick.
Now I can upgrade all my ThinOS before moving to WMS.
If I have more ThinOS in boxes, should I leave the WDM so I can upgrade the firmware in the future ?
Regards,
Hi,
the logon request is not by the terminal server but from the ThinOS so that setting is not handling the issue.
I can manual login to the ThinOS with guest account and it’s proceeds and makes the terminal logon.
Worked like a charm
but
Now the thinClient asks for user & password something that wasn’t needed before the upgrade (this thinClient is used as singe and needs to auto logon to the ThinOS)
I presume it’s a new property needed on the wnos.ini file !?
Regards,
OK
For the beginning I’ll download now the ZD10_wnos file and try the process with this file.
I presume I’ve should download the file: “ThinOS 8.6_412 English Raw Image” (that is the ZD10_wnos file) !?
I’ll let you know.
Regards,
Hi,
I did everything according to the manuals and nothing helps – the unit isn’t upgraded.
I use WDM 5.7 and wish to upgrade 5010-D10D from version 8.3_012 to version 8.6_024 that i downloaded as a bin file from Dell.
Tried as instructed with the upgrade to put the bin file on the WNOS folder – not working.
I’ve didn’t found any way to upload the bin file to the WDM server and deploy it from the server side.
The upgrade is needed before we move from WDM to WMS.
Any help will be appreciated.
Regards,
Hi,
I most say that this issue came after I reinstalled the entire system because of a HAgent error when opening WDM and expanding any WDM node. (this time I also had the issue of controlling the clients like now).
The procedure I made was to uninstall the WDM, uninstall SQL and then install them from scratch. After that operations the HAgent error has gone but the discussed issue arised.Saying its not an easy issue to fix do you recommend to do again a re-install and now to uninstall the IIS roles also ?
Could this issue arised after the new installation because its an IIS issue role that haven’t been uninstalled before the re-installation of the system !?Thank you for all your advices.
Hi again,
is it can be related to the repository connection ? since I get a HTTP Connection Test Error when doing a Connection Test – the exact error is WebDAV Error : failed to upload buffer. HTTP response code: 404Remote File path {SID}.tmp Error Code: 404
it can be that error causing the problems I mentioned ??
Hi,
I see there al the commands I’ve sent.
I’ve tried to delete then and do another Reboot to client without any success
Regards
Hi there,
I’m returning after a while with the discussed issue.
I’ve downloaded the latest WDM version (Version 5.7) and before the upgrade I’ve spent some time to read the documentation.I didn’t mentioned before we are using Thin clients model D10D with firmware version 8.3_012, HAgent version 4.0.4.2 WCM Support: True – all that information from the unit info that appears in the current WDM.
Is your suggestion to distribute different configurations to different client based on WCM and Profile Manager relevant for those units I’m using ? (I had a feeling from the documentation that D10D/WTOS client aren’t supported !?
I want to remind that my goal is to manage my clients and their configurations in a hierarchical manner.
Do I still need to use the Configuration Generator ? do I need to create multiple wnos.ini files according to the various configurations and deploy them using WCM/Profile Manager ?I found the WCM Administration guide but there I saw that it’s relevant only with clients with OS on them and there is no reference to wnos.ini files !?
Thank you for your patient and professional answer.
Regards,
Thanks,
Solutions 1 is working perfectly so I’ve rolled back any workaround changes that I’ve made and mentioned in my initial message.
For the OT issue:
I’m using a single server as the WDM witch holds the web server and the ftp server and currently I’m using the following OT:
161, 162, 184, 185, 186, 190 (Secure Port 443)
If I’ll drop the 184,185 OT the client will unable to get the WNOS file ! how can I override this so I wont need to reveal the FTP password in the DHCP server ?10X
OK
I’ll have another look on the “INI file handling” doc.
Separate subnets only for a few clients to get a different settings is not an option.
Isn’t there any way to control the settings that are being applied to clients based on groups or hierarchy in WDM ?
Another point is that as I understand all INI files nedd to have the same name WNOS.INI something that is hard to track, if we could name the INI files as we want, I could give them names according to their function and apply more then one settings file to clients.Anyhow, I’ll read again the doc you mentioned maybe I’ve skipped something.
Regards,
