- This topic is empty.
-
Posts
-
Anybody else still having this issue, or have a fix?
We have been researching this same issue on this forum and fixya.com for sometime. We are running Windows 2008 Terminal Servers – FARM, FARM1 and FARM2 with FARM being the broker.
We have 250 licenses installed on the FARM for Thin Client RDP Connections and we can’t get our Wyse S10’s to pull those licenses.
We have the issue, where we can only have two RDP Session’s logged in are new Farm. The 3rd device to connect gives the 2009 Screen to request to select which Session to remove. Why doesn’t the S10’s pull
and decrement their licensing – we have tried every fix possible, and still
can’t get it to work.We are now up to Version S10_6.4.0_24.exe WTOS on the thin clients, just upgraded straight from 6.4.0_12. Are wnos.ini File is listed Below.
Can anyone tell us how to get our 80 S10 Wyse Terminals to work in our new TS 2008 world, and what are we missing.
Thank you
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
privilege=high lockdown=no
signon=0
autoload=1
Resolution=1024×768
FixLicense=clean;*************************************************************
;* RDP *
;*************************************************************
;
;- RDP Session 1 –
;- Each line but the last must end with a ” –
;
CONNECT=RDP
Host=farm.mchc3.mchcinc.org
Description=”NextGen”
Command=”c:nextgenvcp.exe /thin /ini \nextgen-dbnextgenrootprodngconfig.ini”
AutoConnect=yes
Reconnect=30
Colors=high
Fullscreen=yes
Resolution=default
Username=$TN
Password=********
Domainname=mchc3
Console=yes
Directory=c:nextgen
LocalCopy=yesFirst of all I would recommend to delete “FixLicense=clean ” from your wnos.ini. Otherwise the units will delete the locally stores wnos.ini after each reboot and aquire a new temp license.
Are you using per-device licensing?CG
We are running 250 2008 TS Per Device Cals – And I seemed to be able to get 2 more licenses to degredate from the FARM Server which is the License server as well. I removed the Console=Yes, and put it to Console=NO and put inthe full domain name. The three new S10’s I added to the network 2 of them pulled a Cal License, and 1 pulled a Temporary. So we are very close, as haven’t been able to get more than 2 sessions running without a request to select which session we want to disconnect. On previous version of the WTOS 6.4.0_12 – we tried every combination possible when it comes to FixLicense=Clean, Console and we didn’t ever adjust the Domainname=full.domainame.com until just recently.
We are planning on connecting several more this week, I will remove the fixlicense=clean, that may be why 1 of the 3 newly connected (we have two already connected previously) pulled tempoary license yeah?
I will let you know how that works, and any comments on the domain name setting as well as console= would be welcomed gladly. Thanks for your reply.
What are the implications of having the FQDN name in there, as it seems to be working perfectly with the fixlicense=clean removed.
Also the only isse we need to resolve so far, is the terminals are going back to the windows locked screen forcing our users to login to the terminal user id, which is something they are not used to and therefore would like to have fixed, what command controls the locking of the console, so we can keep that open, they are locking their application when they walk away, and prefer to keep the windows session live to the application for a faster attachment.
Thank you, and where can I send you a donation for the Configuration Generator – whats your paypal id?
- You must be logged in to reply to this topic.