Error using AWS Registration Code with ThinOS 9.1 & WMS 3.2.1 44

Tagged: , ,

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #105402
    alex01
    Participant
    • Total Post: 38
    • Frequent Flyer
    • ★★★

    I’ve followed the instructions here – https://www.dell.com/support/manuals/en-uk/wyse-thinos-maintenance/thinos_9.1_ag/configuring-the-amazon-workspaces-broker-connection?guid=guid-299fa2be-6347-4bf0-9ca5-68e918502b2a&lang=en-us

    When I set default broker type to “Amazon Workspaces”, enable “Connect via Registration Code”, enter the registration code and click “Save and Publish”, I can see the client receive a “Group Policy Changed Command”.

    The client has the following error in the logs

    [Amazon] login to  broker “code://<my reg code>” failed. error -> Error: Init: D-bus Error

    Settings below

    global broker settings

    amazon workspace settings

    Has anyone else seen this issue?  Any known solution if so?  Given that there’s no way to use ini settings with 9.1 I don’t know any other way to set these values??

    Any input appreciated.

    Thanks in advance

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

    I haven’t heard of that.
    INI isn’t available anymore, correct. However, you can enter all details locally if you want. Just go to the local Admin Portal in ThinOS.

    CG

    #105468
    alex01
    Participant
    • Total Post: 38
    • Frequent Flyer
    • ★★★

    Thanks, I did try this as part of my diagnosis of the issue but when I set the Broker connection locally I’m not subsequently presented with a login-box after the reboot.

     

    #105475
    alex01
    Participant
    • Total Post: 38
    • Frequent Flyer
    • ★★★

    Turns out to if you upgrade to 9.x and want to connect to AWS (or any other PCoIP broker) you also need to install the Teradici PCoIP package.  This is a little confusing because when you upgrade from 8.6, you specifically have to use the PCoIP firmware on PCoIP boxes but this doesn’t include the PCoIP driver… go figure.

    Apparently the 9.x firmware doesn’t have any drivers to connect to any type of broker by default and you explicitly have to add whatever you need – this was done as a security consideration which I guess makes sense but I couldn’t find this documented anywhere (the support engineer I spoke with agreed this is badly documented)

    HTH

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.