Wtos 7.1 and RDS

  • This topic is empty.
Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #6837
    skeeter
    Member
    • Total Post: 17
    • Regular Joe
    • ★★

    I have a C10LE with Wtos 7.1 beta running. There is an option in the new OS to specify a Microsoft Connection broker. Does anyone know how I can leverage that so I can take advantage of the VM pools provided by my RDS setup? Currently I am using 2 files a wnos.ini file as a global file and a $mac.ini file so each machine will load an rdp session to a win 7 vm. If I can use the connection broker connection now in the new wtos to connect to the pool of vm’s then I would not need individual $mac.ini files.

    Thanks,
    Scott

    #21022
    ConfGen
    Keymaster
    • Total Post: 11485
    • Jedi Master
    • ★★★★★★★

    Provide the address of the broker server with the Desktop Session Host role installed in one of the following ways.

    http://ip
    https://ip
     IP
    http://FQDN
    https://FQDN
     FQDN

    Note that by server default all URLs are converted to https. That’s why you need the SSL certificate imported in WTOS.

    CG

    #21033
    skeeter
    Member
    • Total Post: 17
    • Regular Joe
    • ★★

    I have selected microsoft and added the http://IP in the broker server.

    below are the INI files I am using:

    ;*************************************************************
    ;* *
    ;* This wnos.ini file was generated with the *
    ;* Configuration File Generator 6.1.01 *
    ;* Copyright by Thomas Moellerbernd *
    ;* *
    ;* http://www.technicalhelp.de *
    ;* *
    ;*************************************************************

    ;*************************************************************
    ;* General 1 *
    ;*************************************************************

    autoload=0
    Rapportserver=x.x.x.x
    AdminMode=yes Username=Mhctcadmin Password=Thinclient
    Privilege=None HideConnectionManager=yes
    AutoSignoff=yes Reboot=yes
    Shutdowncounter=0
    AddCertificate=name.cer
    AddCertificate=name.cer

    ;*************************************************************
    ;* Display *
    ;*************************************************************

    ; If you are using a version of WTOS code < 7.0.1_13 please use:
    ; Resolution=DDC Refresh=60
    Screen=1 Resolution=DDC Refresh=60
    Desktop=desktop.jpg Layout=Center

    ;*************************************************************
    ;* Time *
    ;*************************************************************

    Timeserver=time.microsoft.com Timeformat=”12-hour format” Dateformat=dd/mm/yyyy
    TimeZone=’GMT – 07:00′ ManualOverride=yes Daylight=yes Start=030507 End=100507 TimeZoneName=”US Mountain Standard Time” DayLightName=”US Mountain Daylight Time”

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

    SignOn=No

    ;*************************************************************
    ;* General 2 Special *
    ;*************************************************************

    Include=$MAC.ini

    and MAC file is:

    ;*************************************************************
    ;* RDP *
    ;*************************************************************

    ;


    ;- RDP Session 1 –
    ;- Each line but the last must end with a ” –
    ;



    CONNECT=RDP
    Host=Win7VM
    Description=”MHC Desktop”
    AutoConnect=Yes
    Reconnect=-1
    Fullscreen=yes
    Resolution=default
    Domainname=domain name
    LocalCopy=no
    SignOn=no
    Exit=All

    So I guess what I am asking is there a way I can reference the VM pool as a connection instead of having a separate file to connect to a machine in the pool.

    #21035
    skeeter
    Member
    • Total Post: 17
    • Regular Joe
    • ★★

    I have got some more info on this and believe I am close to having this working. I have removed the $mac.ini all together and added:
    VDIBroker=broker_url
    ConnectionBroker=Microsoft

    to the global file, I also added Signon=yes

    I am now getting to a point where the user puts in credentials; however, the rdp session just stays a connecting. I have conformed the pool is working correctly with a windows machine. If anyone has any ideas I am all ears.

    Thanks,
    Scott

    #21036
    ConfGen
    Keymaster
    • Total Post: 11485
    • Jedi Master
    • ★★★★★★★

    Have you imported a certificate?

    CG

    #21051
    skeeter
    Member
    • Total Post: 17
    • Regular Joe
    • ★★

    I have installed the certificate on the terminal. I have tried to capture some traffic on the connection broker server to see what is happening. I have found that there is a key exchange between the terminal and the server and there is a proper hand shake. If I put in invalid credentials I get the error on the terminal “RD-Broker sign on failed” I have also used a valid account with the wrong password a number of times and the account does get locked on the domain controller. At this point I have a few applications published and a VDI pool published I am wondering if I just need the pool and nothing else. Like I said I have been capturing traffic to see what is happening and basically it looks like it is going through a loop and I keep getting the error packet KRB5KDC_ERR_PREAUTH_REQUIRED

    Thanks for the suggestion CG and more ideas are welcome.

    Thanks,
    Scott

    #21064
    ConfGen
    Keymaster
    • Total Post: 11485
    • Jedi Master
    • ★★★★★★★

    What about the local time? Is it set correctly?

    CG

    #21066
    skeeter
    Member
    • Total Post: 17
    • Regular Joe
    • ★★

    The time is correct on the terminal.

    I have been watching the traffic more and it looks like it is trying different things. for example first I have:

    netcheque >https “from the terminal to the server and back”
    then.

    chimera-hwm >https “from the terminal to the server and back”
    then.

    samsung-unidex >https “from the terminal to the server and back”
    then.

    altserviceboot >https “from the terminal to the server and back”

    After each one of these exchanges it is the same there is a Diffie–Hellman key exchange, and a few packets of data sent then it moves to the next example above.

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