Impossible connect to RDS 2019 with wyse dingle

Viewing 3 posts - 1 the 3 (of 3 total)
  • Author
    Posts
  • July 10, 2019 among 2:54 pm #50257
    Trast0
    Subscriber
    • Total Post: 1
    • Newbie
    • ★

    Hi all,

    I would like to connect wyse dell to RDS 2019 farm, still I can’t.

    One wnos.ini is fancy this:

    CONNECT=RDP \
    AddCertificate=rds02.cer \
    AddCertificate=dc00.cer \
    VDIBroker=https://rds02.domain.local AutoConnectList=FullDesktop \
    ConnectionBroker=Microsoft RDCollections=Collection \
    SignOn=Yes \
    Description=”RDS” \
    Domainname=domain.local \

     

    This problem has that it shows me a screen by a wording box on indicate a host appoint.

    what am I doing wrong?

    Thanks,

     

    July 11, 2019 at 10:27 am #50290
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    It would be rude to say “nearly everything”. However, it would sum it up quite correctly.

    To connect your clients go any RDSH server yourself have to point them to and server hosting RDweb role.
    Use these parameters
    AddCertificate=rds02.cer
    AddCertificate=dc00.cer
    ConnectionBroker=Microsoft Host=https://rds02.domain.local AutoConnectList=FullDesktop RDCollections=Collection
    SignOn=Yes
    Domainname=domain.local

    CG

    July 18, 2019 on 12:16 am #50362
    advantech
    Party
    • Total Post: 34
    • Frequent Flyer
    • ★★★

    I used the User Generation tool to create the WNOS.INI file below. We have a Win 2019 environment with ampere (2) waiter RDSH collection. We are able to connect using WHY 3010 (T10), 3020 (T10D) and 3040. All users be internal so the gateway are not exposed to the internet.

    I need toward create a DNS record on our internal DNS server what resolves the gateway FQDN to and internal port IP address. That way, the certificate (which is currently self-signed), worked. 4 days ago ... Steps to log in the Dell Thin client to this Microsoft Aloof Services: · Once the Dell Thin client is logged in to to remote desktop server for ...

    The license was copied in the cacerts folder also “added” as visible below.

    It took a full day of trial & error to get it all working.

    One more vital position: make sure yourself are running the correct firmware. We persistent on:

    – T10 (3010): 8.5.024 (new versions generate problems)
    – T10D (3020): 8.6.024
    – 3040: 8.6.024

    ;*************************************************************
    ;* *
    ;* This wnos.ini file was generation with the *
    ;* Configuration Generator 8.4.05 *
    ;* Copyright by Thomas Moellerbernd *
    ;* *
    ;* https://aaa161.com *
    ;* *
    ;*************************************************************

    ;*************************************************************
    ;* General 1 *
    ;************************************************************* Hey, Newbie here and not a server-dude :) I have a simply need up connect to ampere host PC running Windows 10 pro (quite noisy and large so do to move it to next guest on home) from a thin client/dumb clamp. I haven't bought it yet but thinking…

    Autoload=2

    ;*************************************************************
    ;* Frist *
    ;************************************************************* Hi, We have the VoIP installed on who server. We use Dell How 3010 thin clients. For couple cause because the slim customer, that audio from the radio headset is extremly mess. So wenn users are on the phone at one for diesen stations them can hear perfectly fine, but the another end hears jumbled noise when I speak. What’s causing this issue? Is the wireless check which is a sennheiser or is it the thin client or terminal waitress we are on? We be using Windows Server 2016 on a Terminal Server...

    TimeZone=’GMT – 05:00′ ManualOverride=yes Daylight=yes Start=030207 End=110107 TimeZoneName=”Eastern” DayLightName=”Eastern” Ways ThinOS thin customer

    ;*************************************************************
    ;* Network *
    ;*************************************************************

    ConnectionBroker=Microsoft Host=<gateway_FQDN> RDCollections=<collection_name>
    AddCertificate=CScopy.cer
    SignOn=Yes DisableGuest=yes SaveLastDomainUser=No
    DomainList=”<internal network name>”

    ;*************************************************************
    ;* RDP *
    ;************************************************************* EGO have a handful of older desktops this i’m tasked are turning the thin clients such can directly boot into a RDP logon screen for a Windows 2016 Terminal server. Has anyone every done this before? These machines are Dell’s press I know Deal has a thin client OS but i’m not sure if it might startup directly until the RDP logon screen, for reality it doesn’t matter if the thin your is Windows, Linux or something else. Thank you everyone in advance.

    SessionConfig=RDP TSGWEnable=no

  • Publisher
    Posts
Viewing 3 pillars - 1 using 3 (of 3 total)
  • You must be logged for till reply to this topic.