Is this possible with user.ini??

  • This topic is empty.
Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #1430
    slips
    Member
    • Total Post: 8
    • Newbie

    Hi Guys,

    I was wondering if it is possible with a user.ini configuration for our users to power on the V10L and it boot straight onto their Virtual Desktop without any need for them to log on either locally onto the V10L or onto the Citrix server? We are trying to make the virtual desktop experience as simple as possible for them.

    Each different V10L will need to have its own unique pre-allocated desktop to connect to using an ICA connection.

    Currently we have the wnos.ini configured to log on the user automatically after they have inputted their credentials into the Citrix server login box and then the V10L loads their pre allocated desktop.

    Is this possible using the include=$MAC entry in the wnos.ini file and then creating a user.ini file on the ftp server in the folder /WYSE/wnos/ini/, i’m pretty confused after reading through the WTOS admin guide (no surprise there) on how the user.ini file works so any explanation or help would be fantastic.

    Many thanks for reading and any help given!
    Dan

    #13811
    thinkthin
    Member
    • Total Post: 1649
    • Jacked into The Matrix
    • ★★★★★★

    Ahh, what you need is a nice white paper on setting up VDI with no broker…hmm if only

    http://www.freewysemonkeys.com/modules.php?name=Downloads&d_op=viewdownloaddetails&lid=109&ttitle=VDI-NoBroker.zip

    There you are!

    This paper is for setting up to do a login however it introduces many advanced concepts for use of the .INI file.

    In your case you can use something like the $TN in the connection string of the wnos.ini to login with a unique name and password. Have a read of the doc and see if this solves it for you,

    Cheers,
    -TT

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

    Using a username.ini implements the use of SignOn=yes. Otherwise WTOS does not know which username.ini to use.
    What you could do is configure an ICA connection to the XP Pro session directly. But instead of using something like Host=XPsession1 or similar you can use variables like UN, TN, MAC, etc here.
    UN=username
    TN=terminalname
    MAC=Mac address
    If you name your XP Pro sessions like the V10Ls macc address or terminalname this will work fine for you.

    CG

    #13820
    slips
    Member
    • Total Post: 8
    • Newbie

    Thats great guys thanks for your help!!!!

    I thought i had gone through all the white papers but must have missed the crucial one!!!

    Are we able to do away with the need for a connection broker completely and connect via ICA from the Wyse V10L directly to a XP desktop and if so, is there anything that will need to be installed on the XP desktop?

    IE, create and configure a ICA shortcut on the V10L to connect to a XP Desktop without having to validate a users credentials through the broker? So all the users have to do is double click the shortcut when they power on to get a XP Desktop?

    #13821
    thinkthin
    Member
    • Total Post: 1649
    • Jacked into The Matrix
    • ★★★★★★

    The short answer is yes and no 🙂

    Its really easy to do what you are after with RDP and have an icon that launches into a desktop with no prompt – you can even load Wyse TCX to get multi media and USB redirection so the environment is very functional!

    Port-ICA requires the use of the XML service to authenticate and do license checks so you would have to use the entire Citrix broker.

    Do you really need ICA would be my question?

    #13822
    slips
    Member
    • Total Post: 8
    • Newbie

    Thanks thinkthin, i have found that the performance with ICA Citrix client to perform better than though RDP with VMware on the V10L’s and the V90 Wyse using Vmware and also Provision Networks so ideally would prefer to use ICA (although that is not yet set in stone).

    It’s sods law that the functionality we would love to have is on the protocol that responds the least while its vice cersa for the Citrix ICA client.

    I thought it would be the case with a ICA connection where we would have to have the entire broker suite.

    To be honest, we would much rather prefer the VMWare RDP solution as we have a VMWare infrastructure for our virtual desktops but the connections that the users will have off site are poor with this.

    Thanks for everyone’s help and your very prompt responses

    Cheers
    Dan

    #13824
    thinkthin
    Member
    • Total Post: 1649
    • Jacked into The Matrix
    • ★★★★★★

    Hi Dan,

    One other suggestion, if you are using XP Pro as a desktop and you own both ends of the WAN check out Expand Networks devices. These are network accelerators can compress and optimise RDP. To enable this Expand have a patch that allows encryption to be disabled on the RDP stream for XP Pro so you will need to apply this to the VDI desktop image.

    I also believe they are coming out with virtual appliances so you can host this on ESX.

    http://www.expand.com/applications/vdi.aspx?URL=/applications/vdi.aspx

    Cheers,
    -TT

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