Solved

Wyse T10 & Server 2012 VDI

Posted on 2014-09-05
2
679 Views
Last Modified: 2014-09-11
Hi

I am testing VDI on Server 2012 (not R2) with a Wyse T10 running WTOS 8.0_210

The only way I can see of connecting to VDI is by setting up the thin client in Connection Broker mode (Start > Remote Connections > Broker Setup). However this requires me to enter my domain credentials before I get to the Connect Manager.

 We access many different RDP connections from our Connect Manager - I would ideally just like to add a "VDI" connection to the list and have VDI users connect to that.

 Is this possible without running the Thin Client in "Connection Broker" mode?

 Many thanks
0
Comment
Question by:admincbf
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 58

Accepted Solution

by:
Cliff Galiher earned 500 total points
ID: 40305958
There is no good way around this. 2012 builds heavily on the connection broker for RDVH (and RDSH for that matter) and so it pretty much is required on the client end as well.
0
 
LVL 1

Author Closing Comment

by:admincbf
ID: 40316455
Further research corroborates this is the case :(

Thanks for replying.
0

Featured Post

Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
This paper addresses the security of Sennheiser DECT Contact Center and Office (CC&O) headsets. It describes the DECT security chain comprised of “Pairing”, “Per Call Authentication” and “Encryption”, which are all part of the standard DECT protocol.
In this Micro Tutorial viewers will learn how they can get their files copied out from their unbootable system without need to use recovery services. As an example non-bootable Windows 2012R2 installation is used which has boot problems.
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

738 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