ThinOs 9.1 automatic connection Broker RDS

Viewing 13 posts - 16 through 28 (of 28 total)
  • Author
    Posts
  • #105484
    SkyNet
    Participant
    • Total Post: 12
    • Regular Joe
    • ★★

    Yes, I use RDS-GW-WEB. ######. Fr
    https://RDS-GW-WEB.######. Fr

    But, does not work

    Which certificate should be put ?
    That of the RDS-BRK or RDS-GW-WEB server?

    #105485
    SkyNet
    Participant
    • Total Post: 12
    • Regular Joe
    • ★★

    Configuration

    #105487
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    Next time would be nice if you switch WMS GUI to English before doing a screenshot 😉

    Are you using self-signed certificates on each RDS server? Aren’t you using a Certificate Authority? That way you would just have to install the CA root cert to all clients.

    CG

    #105488
    SkyNet
    Participant
    • Total Post: 12
    • Regular Joe
    • ★★

    Sorry, next time I will switch the interface to English.

    I mainly use self-signed certificates

    #105490
    SkyNet
    Participant
    • Total Post: 12
    • Regular Joe
    • ★★

    For information, I’m going to version 3.2.1 for test

    #105496
    SkyNet
    Participant
    • Total Post: 12
    • Regular Joe
    • ★★

    Hi,

    The update has not changed anything

    #105502
    SkyNet
    Participant
    • Total Post: 12
    • Regular Joe
    • ★★

    Hello,
    I am going through an ADCS but it does not work either

    #105509
    SkyNet
    Participant
    • Total Post: 12
    • Regular Joe
    • ★★

    Hi,

    It is resolved
    I correctly reassigned my certificate on my RDS-BRK server

    Thk you

    #106068
    ethevenet
    Participant
    • Total Post: 3
    • Newbie

    Good morning everyone.

    Could somebody find a fix for this?

    Before , in thinOS 8.6 and FTP server, we had this settings on the [email protected]

    VDIBroker=https://BROKERNAME.<fqdn> AutoConnectList=”Remote-Application-Needed”
    ConnectionBroker=Microsoft
    AddCertificate=brokername.cer

    Now that we use ThinOs 9, we tried all suggestions here but all the time, Wyse end with message “Connection failed to broker https://BROKERNAME.<fqdn&gt; error ==>Error:Error”

    Broker certificate was uploaded and used. We tried with

    -brokername

    -FQDN broker name

    -https://brokername

    -https://FQDN broker name

    None worked. Only when removing the ‘S’ from https, event log display a message related to certificate that is not matching

    Thanks for your suggestions

    Emmanuel

    #106074
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    Do you use a self-signed certificate for the broker, or do you have a full CA set up? Or do you use official certificates?

    CG

    #106075
    ethevenet
    Participant
    • Total Post: 3
    • Newbie

    Hi, I’m using a self-signed certificate
    E.

    #106076
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    and you importing this certificate to the Thin Client, correct?

    #106077
    ethevenet
    Participant
    • Total Post: 3
    • Newbie

    Yes, and I can see it well imported on the Wyse device. When displaying it from the Thin client we can see that it’s the good one

    Thank you

    E.

Viewing 13 posts - 16 through 28 (of 28 total)
  • You must be logged in to reply to this topic.