- This topic is empty.
-
Posts
-
I have a very simple wnos.ini that is working once I figured out what I needed to do to set up.
Here is the question/frustration that I am experiencing. Every time a device boots up it gets to the “Contacting Hserver….” message and it takes probably 90 seconds to get booted up.
This happens EVERY time, so no matter if I update the configuration or not it goes through this process. Is this normal behavior that I just need to accept or is something misconfigured?
Any suggestions would be greatly appreciated. Below is my sample test wnos.ini that I am using.
thanks,
Peter
;*************************************************************
;* *
;* This wnos.ini file was generated with the *
;* Configuration File Generator *
;* Copyright by Thomas Moellerbernd *
;* *
;*************************************************************;*************************************************************
;* Display *
;*************************************************************Resolution=1024×768
DesktopColorDepth=32
Screensaver=”1″ LockTerminal=no Type=1;*************************************************************
;* Network *
;*************************************************************SignOn=No
MaxVNCD=1
VncPassword=”xxxxxxx”;*************************************************************
;* ICA *
;*************************************************************;
;- ICA Session 1 –
;- Each line but the last must end with a ‘ ‘ –
;
CONNECT=ICA
Host=test-citrix
Icon=default
Application=”desktop”
Description=”Sunwest Standard Desktop”
AutoConnect=yes
;Reconnect=yes
Encryption=Basic
Domainname=accounting
LocalCopy=noCan you post your network settings? Whats the path on the FTP server you’re using?
Most default paths are C:inetpubftproot then wysewnoswnos.ini
I replaced the below WNOS.ini with this one and my problem went away. Not sure what was wrong with the previous INI file, but something didn’t make it happy. Or so I thought.
I modified my revised file a little and then the problem came back. I am wondering if this is a problem with my WDM.
It is really annoying when the boot takes seconds but the contacting hserver takes minutes.
Any advice would be greatly appreciated.
The path to the server (which is working as I am able to modify the configuration) is c:inetpubftprootwysewnos
Hi,
If you are using WDM Workgroup with WTOS then make sure you have un-ticked the return/INI option under WDM preferences (this is for DDC only)
If you have the correct IP of the WDM server in the client and it takes ages to get past the Hserver section it sounds like your WDM server has an issue. Check the server event log and see if there are any issues about the HserverInit or Hserver service. Often Windows DEP is a problem as it blocks services from running,
Cheers,
-TTHi pdoggi,
what firmware version are you using? There was a known issue on earlier code where the WDM check-in was failing from time to time.
ConfGen
I know this post is quite old by now, but wanted to share what I found in the way of a resolution to this.
I am running C10LE clients and have had this issue off and on over the past few months. It seems the only real way to fix this without tweaking the ini again, is to reboot the thin client and restore the original config, it will come back up with the proper config after the reboot/restore that you have out on your FTP server. Wierd, but it works.
- You must be logged in to reply to this topic.