Link to home
Start Free TrialLog in
Avatar of Lee Pepper
Lee PepperFlag for United Kingdom of Great Britain and Northern Ireland

asked on

Citrix prohibit logon and reconnections - disconnecting current users

Hi,
We have a XenApp 6.5 farm, 4 host/worker servers and i set the 'prohibit logons and reconnections' to 2 of the servers to slowly allow the sessions to drop off and then i can do some work on them later tonight. Since i did that we have had calls from the users on these two servers complaining they got kicked off mid sessions (they reconnect fine to one of the other servers).
Question is i thought this was designed to allow sessions to continue working but would stop new sessions and so i could then allow it to become empty 'gracefully' .
is this incorrect or is there something else to do?
any pointer would be great
thanks
Avatar of James Rankin
James Rankin
Flag of United Kingdom of Great Britain and Northern Ireland image

Can't you just prohibit new logons, rather than reconnections?

If they've got a session that is disconnected it may affect all of their current sessions on that server.
ASKER CERTIFIED SOLUTION
Avatar of James Rankin
James Rankin
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Lee Pepper

ASKER

hI James, prohibit 'new' logons isn't one of the options, its either Prohibit Logons, Prohibit logons and re-connections or Prohibit logons until server restart.

Also doing what i did already (prohibit logons and reconnections) - that is putting it in drain mode..

then re-reading the help text - it says it re-routes ALL logons, do you think that means also the current live sessions? my assumption was it would be only new logons attempts and it would leave users on that were already connected.
in which case would the Prohibit Logons be the one to use?
Yeah I would give it a try with Prohibit Logons. I'm assuming that you're publishing applications, not desktops? In that case it may be that if a user has several sessions on one server and one of them is disconnected, it may be preventing access to the remaining "live" sessions.

Sorry I sound a bit vague - I don't have a 6.5 farm up at the moment so can't really recall clearly :-(
thats fine, its just a published desktop, all 4 hosts in the worker group.. users limited to 1 instance so it shouldn't be a case of mixing sessions etc..

i noted the time i made that change and will see if any more calls from the remaining users!
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Hi Sekar, yes but what appeared to happen is when i selected the option to prohibit logons & re-connections  it actually then started to logoff currently connected users - not just new sessions.

So i changed it to prohibit logons only and will check how that behaves
Provided Details