Update - I got a note from Stefan Vermeulen at http://www.printingsupport.com regarding some info from Brian Madden’s forum and have posted it in the Comments - this includes the Registry tweak to increase the buffer to 16Mb per session.
I’ve been asked about multi-monitor support for Citrix ICA Sessions twice in the last week or so from two different sources so I thought it useful to pop this in as a post?
Using Multiple Monitors with Seamless Windows
Seamless Windows Problem with NVidia Dual Screen Client
But this should give a very clear idea on what is possible? As you can see Dual Screens is really only the starting point?
Graphical Display Issues with One or More Monitors
A variety of issues surrounding the graphical display on the client device can be a result of memory setting per ICA session.
The maximum memory allowed for use as a buffer by each client connection on a MetaFrame server is 7,680,000 bytes. This maximum is a limit to the operating system and is not configurable. Up to the maximum amount of memory can be set in the Citrix Management Console at the farm or server level, but this also can be application-dependent. When the memory limit is exceeded in a seamless connection, the session is displayed in a fixed window with scroll bars. Seamless mode factors in the entire resolution of all monitors in a multi-monitor configuration. This chart shows various combinations of color and resolutions with various numbers of monitors and the amount of memory required for the ICA session.
Don’t forget that this is a maximum limit "per session" and ICA will always try to utilize "session sharing" where ever possible to limit the number of licences consumed, so if you are trying to run two large display applications in Seamless mode - and they are sharing the session - then you will have to add together the memory required for each application and ensure that it doesn’t exceed the max.
posted on Wednesday, April 12, 2006 6:18 AM
Feedback
# re: Multi-monitor support for Citrix ICA Sessions - dual screens and the like 4/15/2006 11:30 PM Stefan Vermeulen
Here is a quote from a post from Claudio overruling the 8mb limit on a 2k machine:
http://www.brianmadden.com/forum/tm.aspx?m=12743
Not sure if it’s stull there today and if the total limit is still 16mb.
Remove Comment 75282
# re: Multi-monitor support for Citrix ICA Sessions - dual screens and the like 4/16/2006 5:35 AM Dave Caddick
Thanks Stefan, I’ll post that here as well just in case others find it useful?
Here’s a story from Cláudio he once posted somewhere on how he did so you can use it for your own basis:
I have no idea if it is already fixed on Windows 2003 as none of my monitors can handle such resolutions.
And I have only one monitor so I cannot even try multi-monitor setups.
Although Citrix may allow you to do this, it is still limited on the resolution, color and number of sessions. This means a certain number
(memory allocated to the client) has a maximum value. What means the more resolution you have, you will not be able to have as many sessions as you want in high color for example.
More information:
"Citrix says with there Metaframe for W2k and ‘Feature Release 1′ upgrade, you can support ‘multiple monitors’ and ‘greater colour resolution’. in actuality, the correct word is OR not AND ! Which means it can support 8 screens but only in 2-bit colour mode OR 1 screen at 16 million colours. The reason is due to the amount of memory that Citrix reserves for the video memory for the client.
By default, it is exactly 7680000, which is the maximum value the Citrix utility, "TWConfig", will accept. Now this value is out of 16Mb of total client session memory space. However, running the minimum 3 monitors for the traders at 16-bit requires 7,864,320 bytes, which is 184320 more than the default. So, we asked Citrix why their stuff didn’t work. Finally after almost 2 months of playing email tag, they came back with a Registry entry change.
Here is what they sent us:
Win2k has a session pool limit of 16MB. The ICA pseudo frame buffer comes out of this session pool, and the maximum size of the frame buffer is specified by the registry value:
HKLM\System\Current Control Set\Control\TerminalServer\Wds\icawd\thin16\MaxLVBMem
The MaxLVBMem value specifies (in bytes) the maximum memory that thinwire will allocate for the frame buffer.
It can be modified using twconfig.exe; however, twconfig will not let you specify a value larger than 7680000 bytes.
The remaining 8.4 MB is taken up by other things that we have little or no control over (e.g. GDI itself, printer drivers, etc.).
Microsoft will not modify the 16 mb session limit before WHISTLER. Now, what we found out is that this key can be modified to other values. So when we need to support 4 monitors, we calculated the required memory in bytes (1280 x 1024 x 2 words (or 16-bit) x 4 monitors) and this equals 10,485,760. So, this was the value we entered into this key. And it worked. So, keep this in mind."
As I said it may be fixed with Windows 2003 but I could not try. Microsoft, if they read this post, can shed some light on this.
Cláudio Rodrigues, MVP
Windows 2000/NT Server
Terminal Services
Remove Comment 75291