Solved

Dual monitors with Wyse C10LE clients and Server 2012

Posted on 2014-11-17
8
857 Views
Last Modified: 2014-11-20
Hi,

I am in the process of upgrading our Terminal Servers from Server 2008 to Server 2012 R2 with the bulk of users using Wyse c10le thin clients with Dual monitors set ins span mode to access the servers.

This works well for server 2008 but when I try to access either a TS running 2012 RS or another server which is running server 2012 the dual screen appears as one instead of 2 separate screens.

When accessing the 2012 and 2012 R2 servers from my laptop with an external monitor it works as 2 separate screens.

Thanks Mark
0
Comment
Question by:Balco
  • 4
  • 4
8 Comments
 
LVL 24

Expert Comment

by:VB ITS
Comment Utility
Are you using the Wyse video splitter cable firstly? This gives you 1 digital display and 1 analog display.

If so, the next step is to go into the Properties of the RDP session and tick the Console box. Once you've done this, try logging into your TS servers and check if the issue is still occurring.
0
 

Author Comment

by:Balco
Comment Utility
Hi,

Yes we are using the wyse video splitter cable and I have tried to go into Properties and tick the Console box but still no luck.
0
 
LVL 24

Accepted Solution

by:
VB ITS earned 500 total points
Comment Utility
Do you happen to have the part number for the video splitter cable? Just want to check and make sure it's the correct one.

Next step would be to upgrade the firmware on the devices if they aren't already up to date. This does require an active maintenance contract with Wyse though.
0
 

Author Comment

by:Balco
Comment Utility
The part number for the splitter cable is 920302-02L and the firmware we are running is 7.1

I will check to see if there is a firmware update.
0
Complete VMware vSphere® ESX(i) & Hyper-V Backup

Capture your entire system, including the host, with patented disk imaging integrated with VMware VADP / Microsoft VSS and RCT. RTOs is as low as 15 seconds with Acronis Active Restore™. You can enjoy unlimited P2V/V2V migrations from any source (even from a different hypervisor)

 
LVL 24

Expert Comment

by:VB ITS
Comment Utility
Also post the contents of your WNOS.INI file if possible.
0
 

Author Comment

by:Balco
Comment Utility
Here is the WNOS.ini file

# wyse autoconfiguration file
# version 1.0
# 18 July 2011
#
#
# CHANGE HISTORY
# 18 July 2011
# Initial Configuration
#
#
#
#
# BEGIN TERMINAL CONFIGURATION
#
# Set firmware upgrade to automatically upgrade / downgrade as a forced process
# autoload=201
AutoLoad=2
Signon=0
#
#
# Set the SNMP community string
community=LJew8d
#
#
# Set the desktop colour depth to full colour
DesktopColorDepth=32
Desktop=Balco_Group.jpg Layout=Center
DeskColor="255 255 255"
Resolution=DDC
#
#
# enable the G key reset
EnableGKey=yes
#
#
# Enable user shadowing on the terminal for IT Support
MaxVNCD=1
#
#
# Set the Rapport Server
# Note: using DNSLookup=yes means that the SRV DNS record, _wdmserver._tcp is used to locate
# the Wyse Device Manager server
RapportDisable=no DNSLookup=yes

#
# Set the time server
TimeServer= Timeformat="12-hour format" DateFormat="dd/mm/yyyy"
#
# Turn on/off services
Service=ThinPrint disable=yes
Service=snmpd disable=no
Service=VDA disable=yes
#
#
#
# Timezone setting
TimeZone='GMT + 09:30' ManualOverride=yes Daylight=yes Start=100107 End=040107 TimeZoneName="Cen. Australia Standard Time" DayLightName="Cen. Australia Daylight Time"
#
#
# Set the VNC password for security
VncPrompt=No ActiveVisible=yes
#
#
# Set the network configuration
Device=Ethernet KeepAlive=120
#
# setup the RDP Sessions
SessionConfig=RDP MaxBmpCache=1024 DefaultColor=2
#
#
# Prevent the Wyse Login
Signon=no

CONNECT=RDP \
       Host=\
       Description="New System" \
       AutoConnect=0 \
       icon=default \
       Reconnect=no \
       Colors=true \
       Fullscreen=yes \
       Resolution=default \
       LocalCopy=no \
       Rdp_No_Dragging=yes \
       Rdp_No_Wallpaper=yes \
       Rdp_No_Animation=yes \
       MapDisks=yes
0
 

Author Comment

by:Balco
Comment Utility
It looks like the firmware upgrade has fixed the problem, will do some more testing and let you know.

Thanks for your help.
0
 
LVL 24

Expert Comment

by:VB ITS
Comment Utility
Great! Next step would have been to mess around with the WNOS.ini file but looks like there's no need for that now.
0

Featured Post

Get up to 2TB FREE CLOUD per backup license!

An exclusive Black Friday offer just for Expert Exchange audience! Buy any of our top-rated backup solutions & get up to 2TB free cloud per system! Perform local & cloud backup in the same step, and restore instantly—anytime, anywhere. Grab this deal now before it disappears!

Join & Write a Comment

Healthcare organizations in the United States must adhere to the guidance of both the HIPAA (Health Insurance Portability and Accountability Act) and HITECH (Health Information Technology for Economic and Clinical Health Act) for securing and protec…
In the modern office, employees tend to move around the workplace a lot more freely. Conferences, collaborative groups, flexible seating and working from home require a new level of mobility. Technology has not only changed the behavior and the expe…
This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target. To install the necessary roles, go to Server Manager, and select Add Roles and Featu…
The viewer will learn how to successfully create a multiboot device using the SARDU utility on Windows 7. Start the SARDU utility: Change the image directory to wherever you store your ISOs, this will prevent you from having 2 copies of an ISO wit…

744 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now