- This topic is empty.
-
Posts
-
Hi All,
Currently we’re running 6 virtualised Xenapp 4.5 servers on Windows 2003 SP2.
There’s a few issues with this, performance, flexibility etc so I’m looking at an upgrade.
One of the big issues we’ve got is we have to enforce a single session limit on the Citrix published desktop so if someone doesnt log off, crashes etc then they have a 1 in 6 chance of reconnecting. Currently our V10Ls are configured with something like:
Connect=ICA
BrowserIP=######
Colors=true
Application=”citrix desktop”
Description=”1. Citrix Desktop 1280×1024″
Resolution=1280×1024
Fullscreen=yes
Domainname=#####
Autoconnect=0
SessionReliability=yes
Reconnect=no
mapdisks=yes mapdisksunderz=yesWhat I want to achieve is for a user to be able to sit down at any desk, log in and be presented with their session – whether it is a disconnected or active on another terminal, so it should follow the user.
My plan was to install 2 physical servers with Windows 2008 and Xenapp 5. These will serve the load balanced published desktop and will also have the web interface installed and balanced through an NLB cluster. Then I was going to configure the V10Ls to connect to the NLB IP address with the PNagent.
Would this then allow users to log in and reconnect automatically to existing sessions?
Hi,
I do not see a reason for the NLB as Citrix provides you with a loadbalancing option by default.
Simply add these lines to your wnos.ini and all should be good:
;*************************************************************
;* *
;* This wnos.ini file was generated with the *
;* Configuration File Generator 5.2.06 *
;* Copyright by Thomas Moellerbernd *
;* *
;* https://technicalhelp.de *
;* *
;*************************************************************
;*************************************************************
;* Network *
;*************************************************************
SignOn=Yes
DomainList=your_domain
;*************************************************************
;* General Session *
;*************************************************************
UniSession=yes
;*************************************************************
;* ICA *
;*************************************************************
PnliteServer=your_XA_server ReconnectAtLogon=2 ReconnectFromButton=2Thanks confgen –
Thats what I wanted to hear!
The reason for using NLB wouldnt be to balance the Citrix sessions, but to provide redundancy for the PN Agent site. Obviously we can have as many Citrix servers hosting desktops as we like, but if the WI server goes down then everything goes down!
One more thing that might be a bit more of a problem…
We currently have 2 connections defined, both connect to the same published desktop but have different resolutions set – this means users with poor eyesight can choose a lower resolution for larget text.
Any way we can reproduce this in this configuration?
Did you tried using/adding “Resolution=DDC” in your ICA connection setting.
At our company we have 1024×768 and 1280×1024 as default and using this option the terminal will “autodetect” the best resolution, and (depending on your security) user can change their resolution if needed.
Hi All,
I’ve tried adding those lines to one of the terminals, I can log in and get the application list, but it doesnt reconnect or have a reconnect button. If i try and connect to the desktop it tells me I already have a session open and I’m only allowed a single session.
Any ideas?
Also – asking the users to change the resolution isnt ideal, they wont understand how to do it. As we do a lot of hot deskting, people would want it changed back too.
Does anyone know if users can change the DPI setting in 2008 sessions?
Got the reconnection working by using the PN Agent site rather than XML on the XA servers. Will try that parameter though.
Any ideas on my resolution problem? I tried to add “include=$UN” to the wnos.ini and then specified the resolution in a file named as my username but it doesnt change anything
this will not work via username.ini as a resolution change needs a reboot.
I do see two options if you are not willing to let the user change the res themself. Both are not ideal.
– create two ICA session with different resolutions
– create two published desktops with different resolutionsCG
We’ve got 2 connections to the same published desktop set up in the wnos.ini file with different resolutions – that works fine. The only issue is if it reconnects, rather than starting a new session, it will do it at the native resolution.
This obviously is a good idea if someone logs in with the web interface at home on a widescreen monitor – so it’s a tricky one to get around.
In theory most people will be starting new sessions and closing them at the end of the day so we’ll just leave it as-is.
Unless there’s any third party products that alloy different DPI settings on a per session basis….
For interest, this actually works.
I had tried putting a file called {username} in the INC folder, I needed to put {username}.ini in the INI folder.
Specifying resolution=DCC in the wnos ini and a lower resolution in the username.ini file works. The terminal boots with the native resolution, but if a username.ini file specifies a lower one then applications are connected/reconnected at the lower resolution. Happy days!
But this can only work if you either do not have a resolution parameter in the wnos.ini or use EXIT=ALL in your username.ini and have the Include parameter in front of the wnos.ini resolution parameter.
CG
- You must be logged in to reply to this topic.