- This topic is empty.
-
Posts
-
Ok,
This V10L has a mind of it’s own.
I’m using this as a test machine so it reads different wnos.ini files on a daily basis.
The major issue that I’m having is that all of my wnos.ini files tell the system to AutoSignoff, and shutdown. The problem is that the machine decides by it’s self within the next 5 sec to a minute to start up by it’s self.
Another issue I’m having is that after I have changed the wnos.ini file it will sometime keep behavior of the last wnos.ini for example the previous wnos.ini had a screen saver and the new wnos.ini does not, but V10L still runs the screen saver.
here is a copy of my current ini. (ps. Thanks Thomas for sweet config tool)
;*************************************************************
;* *
;* This wnos.ini file was generated with the *
;* Configuration File Generator *
;* Copyright by Thomas Moellerbernd *
;* *
;*************************************************************;*************************************************************
;* General 1 *
;*************************************************************EnableGKey=yes
Privilege=None Lockdown=yes HideSysInfo=yes HidePPP=yes HidePN=yes HideConnectionManager=yes EnableNetworkTest=yes;*************************************************************
;* General 2 *
;*************************************************************FastDisconnect=yes
FastDisconnectKey=F8;*************************************************************
;* General 3 *
;*************************************************************AutoSignoff=yes Shutdown=yes
Shutdowncounter=0;*************************************************************
;* Display *
;*************************************************************Resolution=1024×768 Refresh=75
DeskColor=”128 128 128″;*************************************************************
;* Network *
;*************************************************************SignOn=No
MaxVNCD=1
VncPrompt=Yes Accept=;*************************************************************
;* General Session *
;*************************************************************SessionConfig=ALL MapDisks=yes
;*************************************************************
;* ICA *
;*************************************************************IcaBrowsing=HTTP
;*************************************************************
;* RDP *
;*************************************************************;
;- RDP Session 1 –
;- Each line but the last must end with a ” –
;
CONNECT=RDP
Host=*************
Description=”ww”
Icon=ww.ico
AutoConnect=yes
Fullscreen=yes
Experience=0
Resolution=1024×768
Username=*******
Password-enc=***********
Domainname=***
Mapdisks=yes
LocalCopy=noDoing a factory reset does fix both issues for a little while but it does come back.
The rebooting is the big issue.
That is really weird, is it possible the units are receiving a wnos.ini from a different source? Do you have a Rapport or WDM server on the network as well?
If you have G-Keyed the unit and had out a wnos.ini with no screen saver and then magically it comes back either a user is setting it up or the unit received the configuration from somewhere.
You may have to do a bit more detective work on this one for us, also as ConfGEN suggests the what firmware version are you using?
Cheers,
-TTSystem Version is 6.0.1_04
No Rapport or WDM running on the network, this is our first TC device that we are testing to see how many different places we can make it work out.
TT, I think you misunderstood me a little, I will try to clear it up.
Screen Saver issue:
After connecting to a ini config that does have the Screen Saver (SS) configured and working. (lets call this config UserA) and I test everything out the SS comes up like it should and works perfectly. Then I change to a different ini config file that does not use or have the SS configured (lets call this config ProdA)
Since I have previously connected to UserA’s ini now running the ini for ProdA the SS is coming on like it did with UserA even though it isn’t in the ProdA ini.
If I G Key it or set it back to factory defaults during the reboot and the boot to the ProdA ini then the SS will not come up. I’m thinking that the V10L is keeping the previous ini file and only over writing new changes and not completely wiping out the old one.
I know that this bug has only shown it’s self because I’m testing several different ini files on the same TC. Once I implement it that machine will only be pulling one ini file all the time and this won’t be an issue.
The rebooting issue:
I will try using only one ini for a day after a G-key reset to see if that will solve this issue also, I don’t believe it will.
Hi wade,
check your UserA config file if you have a line there called EnableLocal=yes.
This would save whole bunch of parameters to the local unit in case the ini file is not available.Regards
CGEnableLocal is not anywhere in the ini file.
Would it be advised to put it in as “EnableLocal=no” ?
You can try the enablelocal=no to see if it helps but it should no be required and really you may want to set it to =yes once you settle on a final configuration.
The screen saver is a “global” command so that explains why you still see it when you change .ini files so that is OK.
The Auto Starting is still strange and one I have never seen before. Is it possible there is a Wake On LAN or SNMP activity going on?
Also try adding the line:
autopower=no
Cheers,
-TTTT,
At first I thought this had worked because it booted and shut down 5 times with no problems.
But on the 6th it did it again.
I have submitted a case with Wyse and so far I’m 2 days with not hearing anything back.
Thanks for everyone’s help.
Any more suggestions are more than welcome.
Wade
OK, now you are in touch with Wyse you should also try getting the latest firmware – 6.1.06.
I have no idea if this will help but I have this at the moment and do not have the issue so at least your setup will be the same as mine.
Post back how you got on,
Cheers,
-TT
- You must be logged in to reply to this topic.