Jump to content


Photo

Allow Multiple Sessions

Started by Panteraa , 17 July 2017 - 12:25 PM
4 replies to this topic

Panteraa Members

Wolfgang Germ
  • 37 posts

Posted 17 July 2017 - 12:25 PM

Hello,

 

i have a XenApp 7.14.1 environment and wanted to allow one user to have multiple sessions as described on:

 

http://docs.citrix.com/en-us/xenapp-and-xendesktop/7-14/manage-deployment/sessions.html

http://www.carlstalhood.com/catalogs-delivery-groups/#sessions

 

 

I want to run the following command on my Delivery Controller:

 

Set-BrokerEntitlementPolicyRule <Delivery Group Name> -SessionReconnection DisconnectedOnly

 

The command outputs the attached error.

 

The Delivery Group is named as I used in my command.

 

What am I doing wrong?

 

Thank you

Attached Thumbnails

  • Set-BrokerEntitlementPolicyRule.png


Carl Stalhood CTP Member

Carl Stalhood
  • 12,283 posts

Posted 17 July 2017 - 12:59 PM

Run Get-BrokerEntitlementPolicyRule to see the existing rules.



Panteraa Members

Wolfgang Germ
  • 37 posts

Posted 17 July 2017 - 05:23 PM

Thank you.

I did run the mentioned command, found out the correct naming (it is different to <Delivery Group Name>) and then run "Set-BrokerEntitlementPolicyRule. The "SessionReconnection" is now set to "DisconnectedOnly".

 

MultiSession still doesn't work as I would expect.

I started a Published Desktop, waited till loading finished and started a second Published Desktop.

It doesn't start a second Desktop. It is a still reconnect. I expected, that a second Desktop would have started.

 

Do I have to do anything else?



Carl Stalhood CTP Member

Carl Stalhood
  • 12,283 posts

Posted 17 July 2017 - 05:37 PM

From a different client machine?

 

If you want two desktops from the same client machine, I think you have to publish two different desktop icons.



Panteraa Members

Wolfgang Germ
  • 37 posts

Posted 17 July 2017 - 06:06 PM

No, I did try from the same client machine.

On XenApp 6.5 it did work like this and you wrote, that the setting reverts back to the XenApp 6.x and earlier behavior.

At the moment I think it is not a problem. I will try what happens if I use a different client machine ...

 

Thank you for the clarification!