Forum Replies Created
-
AuthorPosts
-
No idea? Is this possible at all?
Just got the info from Wyse that this bug will be fixed in a forthcoming firmware update, scheduled for September/October 2012.
(This bug also occurs with the C50LE and Z50S devices.)
Fox
Yes, I configure the DHCP server to deliver hostnames, I configure the device to use them (as written above) and the hostname will be set wrongly (= with surrounding double quotes) on the device. This wrong hostname will be shown everywhere (in the WDM console, in the Citrix console, in the CLIENTNAME environment variable inside the Citrix session, in /etc/hosts, on the SSH prompt, …), so issue probably emerges while interpreting the DHCP reply.
Is the DHCP reply stored somewhere in the Linux filesystem (our old Neoware devices do this which has been quite handy for debugging DHCP issues)?
Fox
I have the same problem – I need the two mentioned hotfixes for the upgrade from WDM version 4.7.2 to 4.8.5 in order to manage the forthcoming X50m devices. However, I don’t see any downloads, even if I log into the support site. A click on “My downloads” results in a “No downloads are available” window. (I will never understand why companies will keep hotfixes secret or difficult to get and thus waste the administrators’ time.)
Any help would be appreciated.
Just want to tell everybody that the recently released firmware 11.1.031 indeed seems to have fixed this issue.
@ConfGen wrote:
Yes, that’s the file.
You can modify it to your needs.CG
Okay, but many configuration items (e.g. keyboard layout) aren’t configurable here (at least I haven’t found it out how to do this, the wlx.ini syntax doesn’t work here). Is there a decent documentation of the possible options in pull_config.conf?
@ConfGen wrote:
A full clone is only possible via pulling and pushing the whole image. This can be done via WDM or USB imaging.
A “Get Device Configuration” is extracting the system.conf file which is similar to the Windows registry.
You can manually edit this file after pulling and add or alter values.
The file can be found in your SW repository, eg. ftprootrapportX50LconfigpackageCG
Do you mean the file pull_config.conf in this directory? This file seems to contain only a few of the many configuration parameters I changed (e.g. keyboard layout, WLAN settings, VNC settings are not mentioned there)…
@ConfGen wrote:
This is a known issue. Upgrade your X50L unit to either SLETC11 Build 11.0.139 or SLETC11 SP1 Build 11.1.012.
Thank you for this hint, unfortunately, it hasn’t solved the problem. After the upgrade, the symptoms are exactly as before. Now the following version is installed (it’s the most recent from the Wyse website):
SUSE Linux Enterprise: 11.1.015
SLETC: 1.4.1115
OS Version: 2.6.32.12-0.7-pae
ICA client module: ica-11.100-01.28Any more ideas?
February 23, 2011 at 8:01 am in reply to: How to manage Wyse clients in non-DHCP envorinments? #20076Okay, thanks to your help I have taken some steps further. Hopefully the last question:
Is it possible to configure a pull_config.conf in a way that some parameters (e.g. DNS servers, screen resolution) will be configured while the networking parameters are left as they were before?
Whatever I tried in the [network-eth0] section of pull_config.conf, I didn’t succeed:
1. If I use the line address= in the [network-eth0] section, I can either define an IP address (which means 20 configuration for 20 devices).
2. If I leave the address= linke blank (or delete it completely), an existing IP will be erased from the device’s network configuration and it has to be configured again (manually, of course).
3. If I omit the whole [network-eth0] section, the device’s network configuration is set back to DHCP.
Is there really no possibility to build a pull_config.conf file which doesn’t touch the network configuration at all?
(A similar problem occurs with the terminal name in the [terminal] section.)
Thanks again.
February 22, 2011 at 10:30 am in reply to: How to manage Wyse clients in non-DHCP envorinments? #20058Thanks for your fast response!
@ConfGen wrote:
1. It is save to alter the conf directly and the CRC is not used at all.
Good news, I’ll give it a try. Is there a good documentation of the pull_config.conf parameters (as there is one of wlx.ini)?
@ConfGen wrote:
2. only mac based configs. So 20 mac.ini files.
It’s not the amount of the files I find annoying but the fact that MAC addresses are random, thus having a directory of many hard to distinguish .ini files. Perhaps it’s a good idea to configure subdirectories on the FTP server and point the clients to them?
@ConfGen wrote:
3. leave it like it is.
I hoped there was a better solution like this one – we will soon have to make a third kind of configuration which means 4 more configurations (one for each screen resolution)…
@ConfGen wrote:
I never recommend using the Find Devices option but to use the DHCP option tag 186 instead. This way the client do get the WDM IP directly on boot time and you do not have to search each time for new clients.
More on implementing DHCP option tags can be found in my “First Steps” documents on my website.CG
Myself, I also would prefer this automatic method via the DHCP method. I tried it out as well and it isn’t currently working either (but it was yesterday!). Control Panel – Rapport Agent still shows the correct address and port (80) of the WDM server.
I tried rebooting the WDM server, without success. Of course, I haven’t activated any firewall on the server. Even after a reboot of the thin client, the Device Manager doesn’t list it. A ping from the thin client to the WDM server works.
Rapport4 and MSSQL services are running on the WDM machine, HServerInit service is set to “Automatic”, but isn’t running; if I start it, it stops after a few seconds (maybe this one is just an initialization process as its name suggests?) The event log doesn’t
The WDM server is a virtual machine running under VMware ESX (if this is useful information).
Any further ideas?
-
AuthorPosts