Custom ini files – Connect to different Citrix Web Interface

  • This topic is empty.
Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #6737
    karmakoma
    Member
    • Total Post: 73
    • Back Stage Pass
    • ★★★★

    Hello, is there a way to configure a particular use login via custom wnos ini to connect to a different Citrix web interface?

    For example, on our subnet we have a wnos.ini which has pnlite details below:

    PnliteServer=http://au-wi/Citrix/PNA-thinclient/config.xml ReconnectAtLogon=2 ReconnectFromButton=0 AutoConnectList=”XenApp Desktop Test”
    SessionConfig=ICA DesktopMode=Fullscreen ProgressiveDisplay=yes AudioQualityMode=Medium

    I have a user.name.ini configured with these pnlite details:

    PnliteServer=http://au-wi2/Citrix/PNAgent-XenApp6/config.xml ReconnectAtLogon=2 ReconnectFromButton=0 AutoConnectList=”XenApp 6 Desktop”
    SessionConfig=ICA DesktopMode=Fullscreen ProgressiveDisplay=yes AudioQualityMode=Medium

    When I login with the user.name account I receive an error “no desktop or application available!”. In the eventlog it has an entry ICA: pnhost = “au-wi”

    So it looks like it the custom ini pnlite settings are not overriding the wnos.ini settings. Is this correct behaviour? Is there a workaround for this? We are building a new Citrix XenApp 6 farm and will need this for pilot testing.

    Thanks.

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

    Just think about one thing.
    At what moment is the username.ini file read? Of course it will read in AFTER the user has entered the credentials and got authenticated against the pre-configured webinterface.
    Said that, it is obvious that a second PNLiteServer entry in a username.ini can not work.
    Either do it via mac.ini (per device) or use the SelectGroup command to let the user select his group and therefore the correct webinterface.

    CG

    #20774
    karmakoma
    Member
    • Total Post: 73
    • Back Stage Pass
    • ★★★★

    I started investigating the SelectGroup command and found the SignOn=Yes DefaultINI=my_defaults.ini option instead which works a treat!

    Thank you!

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