WMS auto connect session not auto connecting.

Tagged: ,

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #44981
    Anonymous
    Inactive
    • Total Post: 4
    • Newbie

    Hi all,

    Today I have installed WMS and trying to move my .ini based deployments to a more managable environment.

    After a small issue (Admin Guide doesn’t mention DHCP option 166 / MQTT) most things are starting to work as expected.
    I notice that not all ini options are also available here (e.g. disable screensaver, or disable editing of domain field) but so far I have solved that by providing a small additional ini file on a FTP server.

    My problem: Automatically connecting to a Citrix published desktop refuses to work.
    In my policy under Remote Connections I have configured “Automatically connect to sessions”. The published desktop is called “Citrix Desktop 2012R2”. Tried with and without quotes. When opening the settings of this connection on the thinclient itself, “Auto-connect on start-up” is not checked.

    The session itself does launch after clicking manually.

    Best result I got was with the additional wnos.ini:
    PnLiteServer=https://fqdn ReconnectAtLogon=2 AutoConnectList=”Citrix Desktop 2012R2″
    Which only put this app in the startmenu, but no autoconnect. When checking the settings of this connection on the thinclient itself, Auto-connect was checked.

    I’d expect at least one of those two options should work, but neither are working.
    Hopefully something stupid that I’m forgetting.

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

    In WMS profiles you have the advanced section. There you can add INI parameters.
    Copy and paste your full pnliteserver line to one empty line in this advanced section and try again.

    CG

    #44992
    Anonymous
    Inactive
    • Total Post: 4
    • Newbie

    Edit @ ConfGen: Will check that tomorrow. I assume that is somewhat the same as using a central server with .ini file?

    A weekend solves it. A bit. Until proven otherwise, I think WMS has some bugs 🙂
    I did some more testing, but no luck. In the CCM INI log on the thinclient I can see the line:
    PnLiteServer=https://… autoconnectlist=\”Citrix Desktop 2012R2\”
    The “Citrix Desktop 2012R2” menu entry doesn’t show the checkmark at “Auto connect on start-up”. Resulting in no auto-connect 🙁

    What I previously had was a default thinclient group and under “Remote Connections” I configured Citrix. Since auto-connect didn’t work I configured the central server with a basic wnos.ini with PnLiteServer parameter. The result now was that there was a checkmark at the Auto-connect option for my published desktop, but still didn’t connect automatically.
    Not sure which configuration is leading, but having them both wasn’t working.

    My current workaround:

    • Remove the “Remote Connections” policy.
    • Add central server with a basic wnos.ini and have PnLiteServer=… configured.
    • Restart thinclient.
    • Profit.

    This also solved my other problem: Saving the last username in the “Other” policy.  The policy is configured to save username and domain, and to show the name of last user on login screen.

    Again, in the CCM INI log:
    Signon=Yes SaveLastDomainUser=yes LastUserName=yes
    Nothing wrong with that, but the last username was not saved…

    So I removed the “Other” policy and in my wnos.ini I’ve added:
    DomainList=”domain.local”
    SignOn=Yes SaveLastDomainUser=yes DisableEditDomain=yes
    And the username is saved as desired.

    It looks like the parameters are passed to the thinclient and then being ignored.

    #45006
    Anonymous
    Inactive
    • Total Post: 4
    • Newbie

    Removed my central server and configured Advanced INI options and it is still working. Not using a central server is good. Less dependencies 🙂

    Although those additional INI parameters shouldn’t be needed if the Remote Connections policy was picking up/applying the configuration correctly. Same for saving/displaying the last username in the “Other” policy.

    Anyway, thanks for pointing to the Advanced policy, better then using additional servers which increases the risk of something failing 🙂

     

    #45380
    stuartt007
    Participant
    • Total Post: 2
    • Newbie

    This worked perfectly for me thanks. I was experiencing the same where the XenDesktop delivery group was not autostarting and this described/solved it well.

    #47413
    Phibue
    Participant
    • Total Post: 46
    • Frequent Flyer
    • ★★★

    Thanks SanderR! Quite old thread but even with the new WMS 1.2 HF1 the problems you stated in your first post still seem to exist.  Your workaround via advanced ini options worked like a charm, though. 🙂

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