- This topic is empty.
-
AuthorPosts
-
January 16, 2008 at 1:03 pm #863
Edited to make it less confusing. I have three issues, all device name related. Currently I’m set up with VDM 2, and V10L’s. Our printer scripts map printers based off the RDP Variable clientname.
1) It makes the RDP Connection in Console Mode 1/10 times. This causes printers not to work. I have Console=no in the wnos.ini. Closing the connection and reconnecting fixes it… sooner or later.
2) I am having an issue, some of our V10L’s are passing a different “Clientname”. The Device i’m connecting from might be WT000000000000, but the Clientname in the connection comes up WT999999999999. Rebooting the wyse box several times fixes it. We don’t know if it’s a permanent fix. I checked the Clientname during the RDP session against the mac address sticker, and the mac address, and device name in System Information (in the Blazer OS).
I am currently running version 6.0.0_14 on the Wyse Box. I know my Time Information is wrong so feel free to correct it 🙂 I posted my wnos.ini below. thanks! I love this site.
Console=no
signon=yes
VDIBroker=http://VDIAutoLoad=1
privilege=none;Set screen resolution
Resolution=1024×768 Refresh=75;Set desktop colour
DeskColor=”0 0 0″;Set a logo up in the login box
FormURL=Via.bmpsessionconfig=all MapDisks=yes Disablesound=no
Timeserver=ntp2.usno.navy.mil timeformat=”12-hour format” Dateformat=mm/dd/yyyy
#TimeZoneName=”Eastern” DayLightName=”Eastern”
TimeZone=’GMT – 05:00′January 16, 2008 at 7:44 pm #11374Hi,
I do remember someone seeing the random connections to the desktop as console on XP Pro but not sure what the fix was.
Can you tell me what version of the VDM you have? Is it build 336 or earlier?
Cheers,
-TTJanuary 16, 2008 at 9:58 pm #11379Currently we are on build 336.
January 17, 2008 at 4:39 am #11381Hi,
I believe this is a known issue with the VDM and WTOS, I am sure it will be resolved before release. Also I would contact Wyse and get 6.0.025 firmware if you are testing VDM,
Cheers,
-TT -
AuthorPosts
- You must be logged in to reply to this topic.